kinman 02/02/01 13:54:21
Modified:jasper/src/share/org/apache/jasper CommandLineContext.java
Log:
PR: 5471
Submitted by: [EMAIL PROTECTED] (Steve Downey)
Revision ChangesPath
1.8 +28 -4
glenn 01/02/08 05:36:56
Modified:jasper/src/share/org/apache/jasper CommandLineContext.java
Log:
Put runtime jsp page servlets in a package
Revision ChangesPath
1.6 +12 -3
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/CommandLineContext.java
The new jasper makes it very easy to find and view
the java source for
a translated jsp page, it is located in
work/somehost/someapp/some/context/path/MyJSP.java.
Does it not seem logical to assign a package to the
MyJSP class based on all or part of the above path?
, the code that is developed and
tested can be identical to the code that is shipped to QA and to production.
-Original Message-
From: Glenn Nielsen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 9:48 PM
To: [EMAIL PROTECTED]
Subject: Re: cvs commit:
jakarta-tomcat-4.0/jasper
in, it is
all internal to jasper.
Regards,
Glenn
-Original Message-
From: Glenn Nielsen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 9:48 PM
To: [EMAIL PROTECTED]
Subject: Re: cvs commit:
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper
CommandLineContext.java
Mel
"Craig R. McClanahan" wrote:
Glenn Nielsen wrote:
"Craig R. McClanahan" wrote:
[EMAIL PROTECTED] wrote:
When Jasper is run in a servlet
container it no longer puts the class files in a package, they are now
in the default package.
As was discussed earlier
The package naming solution I've opt'ed for in my own
enhancement to Jasper (which I'll gladly share) is to
derive package names that are related to the location
of the jsp relative to the server context. This is
simple, flexible and should avoid collisions.
Some implementation details are:
Mel Martinez wrote:
The package naming solution I've opt'ed for in my own
enhancement to Jasper (which I'll gladly share) is to
derive package names that are related to the location
of the jsp relative to the server context. This is
simple, flexible and should avoid collisions.
There
--- Glenn Nielsen [EMAIL PROTECTED] wrote:
There is no need for all this complexity to generate
a package name
in the new Jasper.
Hmmm... compared to the gobbledy-gook that was being
done before, I'd hardly call what I did complex.
Aside from options, all it does is very simply asign
the
[EMAIL PROTECTED] wrote:
When Jasper is run in a servlet
container it no longer puts the class files in a package, they are now
in the default package.
As was discussed earlier on TOMCAT-DEV, this is going to cause
portability problems for people who use beans that are not in packages.
"Craig R. McClanahan" wrote:
[EMAIL PROTECTED] wrote:
When Jasper is run in a servlet
container it no longer puts the class files in a package, they are now
in the default package.
As was discussed earlier on TOMCAT-DEV, this is going to cause
portability problems for people
11 matches
Mail list logo
