ADF Application Architecture

Question

Hi All,
I am new to ADF and working with some vendor to transform our in-house Oracle Form Application to ADF Application and we have more than 300 Oracle Forms to translate.
Basically after the login page, we will have a main menu, and then from the main menu, user can access to different modules (e.g. Customer Profile / Supplier Profile / Order Processing etc..). One of the critical point is that there will different shared variable pass from the main menu to each module and from each module back to the main menu.
We have successfully translate a few Oracle Form to ADF JSF Application. However, before continue the project, we would like to confirm the application architecture.
Checking on Oracle Website / different ADF forum, basically they will packaging all their ADF program in 2 different approach.
Approach (1):
i) Create a common workspace which put all the common EO, VO, AM, Task Flow Template, Page Template, Skin, etc and export as an ADF Library
ii) Create different Bounded Task Flow Workspace with its corresponding Model and View Controller for different modules (e.g. Customer Profile / Supplier Profile / Order Processing etc..) and then export as an ADF Library
iii) Create a master workspace with View Controller to contains an Unbounded Task Flow to tier all the different modules together as an EAR file.
Approach (2)
i) Create a common workspace which put all the common EO, VO, AM, Task Flow Template, Page Template, Skin, etc and export as an ADF Library
ii) Create different workspace with its corresponding Model and View Controller for different modules (e.g. Main Menu / Customer Profile / Supplier Profile / Order Processing etc..) and then export as an EAR file
From Approach (2), when I need to pass parameter from Main Menu to Customer Profile, since they are from different application, I can only pass it through URL or database. But it seems to be not a very approach. May I know is there other way to passing parameter between different ADF Application ?
From Approach (1), it seems that the parameter can be passed using the bean since they are under one master workspace. However, from some of the forum said, if there is too many modules (my case is ~ 300 modules, there will be a problem on the CPU, RAM and JVM may not be able to start.
May I know is it correct from my assumption ? Also may I know which approach should I use ? Thanks !!
Best Regards,
Eric

Answer 1

Hi Timo,
Thanks for your reply. Yes I have watch the ADF Architecture TV Episode too. But I still cannot figured out which approach I should using. From the video, it said that sum of the parts may risk from the start up of JVM when you have too many application. Pillar architecture can solve that problem however parameter may need to pass through different ADF application since they are compiled as different EAR file. But passing the parameter through URL / database package seems not an excellent idea.
Moreover, since all those ~300 modules are different and may not related from each other, so it may not be a suitable case to put multiple forms into one ADF application in my case. Also our system have frequently change request from the user and those request are usually handled by different developer. So I guess it may be better to put it in different ADF application instead of putting in a single one.
Any advice ?  Thanks !
Eric