Hi QM,
-Because real pages has more "power" over them than, say, a more simple wiki-page parsed to an XML-format and XSLT'et to HTML/XHTML/WML/XHTML-MP -whatever. I want to be free to stash the content in a database, the file-system or some other WAR-external resource. I want to be free to have my hieracial "wiki-like" system deliver content by different means of processing - dynamic JSP's being the "missing link". If the application is in control, it can pre-validate or restrict the pages to exclude, say, scripting and to enforce, say, a valid XML form of JSP's, in any way it wants to. It is a matter of technical freedom. Up until now, no filter or front-controller can control the origin or WAR-resources. Morten Sabroe Morten -----Original Message----- From: QM [mailto:[EMAIL PROTECTED] Sent: 9. april 2005 23:32 To: Tomcat Users List Subject: Re: Application-level control of web-resources On Sat, Apr 09, 2005 at 06:35:51PM +0200, Morten Sabroe Mortensen wrote: : This would open up for e.g. creating a wiki-like application, where each : wiki-page is a valid JSP-page, which is created dynamically and stored : elsewhere than within the deployed WAR-file. Why use real pages? Those are a pain to manage, especially in Java webapps (which are supposed to be sealed applications). Many such systems (think blogs) stash the content in a database (or some other data store) and map URIs to those entries. In turn, accessing a URL merges the content and a static template at runtime. The end-user doesn't know they're hitting a virtual resource and, quite frankly, they shouldn't care. Read up on the "Front Controller," "Page Controller," and "Decorator" design patterns for insight. -QM -- software -- http://www.brandxdev.net/ tech news -- http://www.RoarNetworX.com/ code scan -- http://www.JxRef.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
