|
>I am thinking about having one WF project for each >menu item for my application (about 80 items). >Then I can copy the resulting folders into >a single WAS project. Why? What do you expect to gain from this organisation? Are each of the 80 menu items housed in separate source files? Libraries? I have a large beta project in WebFacing (5000 displays) and they are all in a single project. To me, the pain of trying to pick out what programs are on what menus sounds worse than any benefit I Might see, but that's why I'm asking you what you expect to achieve! :-) As for manually copying the resulting folders, I can guess that you mean that you will do something like Export menu 1 as a WAR file Deploy WAR 1 Export menu 2 as a file system Copy menu 2 file system to WAR file system created by WAR 1 deploy repeat... I would not want to deal with the hassles of updating this once it's in production. A single WAR file is bad enough... --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
