Hi everyone,
I’m currently working on redeveloping an existing Oracle JDeveloper 10g application into JDeveloper 12c, and I’ve run into a design challenge.
In the old application, the architecture and UI are tightly coupled in a non-standard way, and I’m required to keep the same structure and user interface behavior in the new version.
The issue is that the UI does not follow a clean master-detail pattern. Instead, fields from multiple related tables are mixed across different pages, regardless of their relationships. For example:
- The first page may contain fields from what is logically a “last” or child table.
- The second page may include fields from the master table along with fields from two or three related tables.
- The design doesn't strictly rely on primary/foreign key relationships in the UI flow.
To replicate this behavior, I’ve started implementing the flow using ADF bounded task flows with a Train component, but I’m struggling with how to properly manage:
- Data bindings across multiple pages
- View Objects and their relationships
- Passing and syncing data between steps that involve different tables without clear hierarchy
Has anyone dealt with a similar scenario when migrating from 10g to 12c?
What would be the best approach to structure View Objects / Application Modules in this case?
Should I consider using a single View Object with joins, multiple VOs with a shared data control, or some other pattern?
Any advice, best practices, or examples would be greatly appreciated.
Thanks in advance!