Hello Experts,
I was wondering if I could pose a question in regards to creating Web Dynpro applications for Portal use.
My current project involves creating a Shopping Cart web application with several different functions: Account Management, Shopping, Checkout, Delivery, etc.
Ideally I would like to use the Portal WorkSet tabs to separate the above functional groups.
I was hoping I could get some pros/cons on the development scenarios below. This is a pretty small project team and currently, I will be the only Web Dynpro developer.
<u>1. One Big WD Application</u>
-Application will compose of all views for every function
Selecting the “Shopping Tab” will open the WD application with an application parameter, indicating that the Shopping View should open
-Selecting the “Delivery” will open the WD application with an application parameter, indicating that the Delivery View should open, etc
<u>2. Separate WD Application per functional group</u>
-“Account Management Tab” will display open the Account Management application
-Any communication from one WD application to another will be performed using PortalNavigation
<u>3. Create each functional feature as a Development Component.</u>
-Develop the Shopping Cart feature, Product Detail feature, Product Comparison feature as separate DCs
Incorporate DCs into Portal Page and communicate through PortalEventing and Navigation
-OR Incorporate DCs as needed into different WD applications as needed and load into Portal
I am working on a project now where I am communicating between WD applications through PortalNavigation and feel as though the transition “flicker” and loading of applications is distracting.
I am also not too sure how and when DCs should be used. Any advice you can give me based on system performance or personal experience would be greatly appreciated.
Thank you all for your time.
Kind Regards,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.