That is the correct behavior. When you goto a JSP page through the
browser it will do the same thing.
The spec leaves the package naming to the implementation
-Original Message-
From: Khamsouk Souvanlasy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 08, 2002 9:34 PM
To: Tomcat
But surely if you have two files with the same name in different directories
they will conflict and cause a compilation error if they have the same
package name?
I.e.
/messageboard/search.jsp
/mail/search.jsp
Will create the .java files:
com/mycompany/jsp/messageboard/search.java with package
]]
Sent: Wednesday, October 09, 2002 7:45 AM
To: Tomcat Users List
Subject: Re: Jasper and java source package problem
But surely if you have two files with the same name in
different directories they will conflict and cause a
compilation error if they have the same package name?
I.e
It's been a while since I scripted this all out (I'm using a script to do
this part instead of an ant task), so I went back to see how ours works
with regard to recursion on directories. Turns out we run jspc for each
jsp file in each directory, passing the correct value for the package with
I've seen this as well and worked around it by compiling each directory
(mail, messageboard, etc) with separate calls to jspc (and changing the
target package name). Would love it if I missed a built-in way to handle
this, but I couldn't find it either.
justin
At 06:34 PM 10/8/2002, you
Hi,
I thought of doing this as well, however when you need to compile the root
directory wouldn't it also compile the others as well? Or would you compile
the root first then the other directories again separately?
Thanks,
Kam
On 10/9/02 11:02, Justin Ruthenbeck [EMAIL PROTECTED] wrote:
