It sounds reasonable, but probably isn't tested or by design, so probably
best to just have a go. Re portability, the best advice I can offer is an
old chestnut: read the servlet spec. This is particularly relevant in this
case. The spec is generally pretty good at telling you you pretty
From: Steve Kirk [EMAIL PROTECTED]
Sent: Friday, May 27, 2005 11:44 AM
It sounds reasonable, but probably isn't tested or by design, so
probably
best to just have a go. Re portability, the best advice I can offer is an
old chestnut: read the servlet spec. This is particularly relevant in
Could you instead store the JSP in a database?
Let's say you have a table with the following structure:
jsp_nameString
jsp_content BLOB
jsp_name is your primary key and is literally a JSP name.
Now, create a servlet filter that examines the path that was requested
and pulls out
From: Frank W. Zammetti [EMAIL PROTECTED]
Sent: Friday, May 27, 2005 1:04 PM
Could you instead store the JSP in a database?
... snip ...
Now, get the BLOB from the database based on that JSP name. Convert the
BLOB to a string and stick it in request, then forward to a JSP that is
the
for.
And that's an easy choice to make :)
-Original Message-
From: Will Hartung [mailto:[EMAIL PROTECTED]
Sent: Friday 27 May 2005 20:38
To: Tomcat Users List
Subject: Re: Adding content/JSPs on the fly
From: Steve Kirk [EMAIL PROTECTED]
Sent: Friday, May 27, 2005 11:44 AM
