hihi,
i have gotten into the habit of precompiling my jsps and then
obfuscating everything. while not 100% bullet-proof (but then again,
nothing is in theory), i think this is a reasonably decent solution for
source security.
woodchuck
--- "Shapira, Yoav" <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
At 09:11 PM 11/30/2004, you wrote:
> It would seem that if a web page request comes in for a .jsp page,
Tomcat would have no file to compare the date against in your scheme of
putting the compiled .jsp page in a .jar file only.
This is only done for non-compiled jsp files that are served by the
Js
Hi,
>When Tomcat receives a request for .jsp page, isn't the first order of
>business to compare the date of the .jsp page against the .java file in
>the working directory, so Tomcat knows whether to re-translate and
>compile the .jsp page?
For normal JSP pages, but not for pre-compiled ones. T
> There is no reason why your app wouldn't be able to find classes from
a jar in common/lib -- there's something else going on here.
I agree.
The following comment in the WebappClassLoader javadoc might be relevant.
"IMPLEMENTATION NOTE - Due to limitations in Jasper compilation
technology, any
When Tomcat receives a request for .jsp page, isn't the first order of
business to compare the date of the .jsp page against the .java file in
the working directory, so Tomcat knows whether to re-translate and
compile the .jsp page?
It would seem that if a web page request comes in for a .jsp pag
Hi Steve,
Hopefully I read your question right. There is no reason why your app
wouldn't be able to find classes from a jar in common/lib -- there's
something else going on here. Do you have duplicate copies of these
classes anywhere? Do these classes rely on other classes found only in
the
One person suggested putting all your logic in .java files.
Make your .jsp's like this:
<% page import="com.yourcompany.YourJavaClass" %>
<%
YourJavaClass.YourJavaMethod ( request, response, config, application,
session, out ) ;
%>
YourJavaClass.java contains:
package com.yourcompany.Y
Hi,
If I understood your issue, you have some required
jars installed at tomcatX/server/lib because of some
reason you can not have it at yourapp/WEB-INF/lib? And
your issue is this is not accessable from your apps,
which seems to be the correct behaviour per the:
http://jakarta.apache.org/tomca
Authentication uses a database to store user information, and the
database is accessed via an object mapping package.
--Steven
parviz wrote:
I'm a little confused as to what you mean by object repository.
You have your Realm in common/lib which is fine. All the other
Realm(jdbc,jndi...) exist in
Sorry if this wasn't clear; the source code is not delivered. It is the
compiled jsp files which are placed into the jar file.
--Steven
Quinton Delpeche wrote:
On Tuesday 30 November 2004 01:32, Steve Procter wrote:
We have a web application that uses jsps. We want to deliver the
application to
I'm a little confused as to what you mean by object repository.
You have your Realm in common/lib which is fine. All the other
Realm(jdbc,jndi...) exist in common/lib. I'm not clear what your Realm
does with your object repository? whats the connection between these
two?Does your compiled jsp files
On Tuesday 30 November 2004 06:39, you wrote:
> Ummm - I think you need to read the original message again. He's putting
> _compiled_ JSPs into the jar - not source. These are .class files, not
> .jsp or .java. Of course, there are some pretty decent disassemblers out
> there.
Ooops ...sorr
On Tuesday 30 November 2004 01:32, Steve Procter wrote:
> We have a web application that uses jsps. We want to deliver the
> application to the customer without source for the jsps. We have done
> this in the past by putting all of the compiled jsps into a jar file.
Hi,
Hate to burst your bubbl
13 matches
Mail list logo