Robert Capps wrote:
So I guess my question is using this architecture with the J2EE container will not work because when I access localhost I really have to call localhost/web/ and then localhost/frameworks is also available in the browser. How do you set up access to your frameworks?
I treat everything as a 100% self-contained project, meaning each project has its own copy of all the files it needs, including frameworks. I've found that the benefits of doing things this way far outweigh any concerns about duplicate files, versions of frameworks, etc. because then I know my apps are entirely self-contained and I'm not going to run into any issues with someone changing a mapping, upgrading a framework, etc. and breaking my apps.
The other thing I like about this approach is that it's much cleaner and simpler in my opinion, because you don't even have to worry about mappings and aliases to resources outside your application.
Happy to clarify further if this isn't making sense. -- Matt Woodward [email protected] http://www.mattwoodward.com/blogPlease do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
