I have to say that, while the webapp concept is nice in many respects, it's really not adequate for large, complex applications with multiple component modules. It certainly makes the simple, most common case far more manageable than it was before, but there are some projects (probably a growing number) for which the single-unit webapp model doesn't quite cut it, and those of us building systems like that are constantly struggling against the limitations of the servlet spec. :-\
-- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 > -----Original Message----- > From: Will Hartung [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 14, 2003 12:42 PM > To: Tomcat Users List > Subject: Re: JSP files between many webapps > > > > From: "Edson Alves Pereira" <[EMAIL PROTECTED]> > > Sent: Friday, February 14, 2003 10:08 AM > > Subject: JSP files between many webapps > > > > Hello folks, iīm doubt about which is the best way to share > JSP files > > with many webapps ( in my case, i have 2 ), i donīt want copy the > same > > JSP to another directory and every page is easy configurable with > parameters > > like: > > Why not copy the JSPs? Is it difficult? > > It's a simple Ant task to copy files. There's nothing > stopping you from keeping the JSPs in a common directory > under your source tree and replicating them to the > appropriate spots in the independent Webapps at build time. > > To be clear, this is a build issue, not a Webapp issue. > > The Webapp structure is strict, and basic. Your build > environment is dynamic, fluid and organized to suit your > tastes, preferences, and environment. These are not mutually > incompatible premises. > > When compiling C programs, you have a common area for library > routines on your system, and every time you build, the code > gets copied from these libraries into your final executable. > You end up with N copies of "printf" bundled across all of > your different executables. This issue with the JSPs within > the Webapp is absolutely no different. Make N Webapps, get N > copies of the JSPs within those Webapps, yet they can all > come from a single source. > > There is always (ALWAYS) this confusion that Webapps == the > interlinked, mangled web of resources in a conventional > website. The whole point of the Webapp is to avoid this mess. > To cleanly and clearly demarcate the boundaries of what is > within the Webapp and what is not. This ensures the the > Webapp is moveable, easily, from one container to another. > > The downside is that you "pay" for it with disk space, but > saving disk space has long ago been abandoned considering the > drive densities of modern systems. > > The Webapp is your friend. Embrace it and be happy. > > Regards, > > Will Hartung > ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
