Hi Allistair,
The JAR looks fine to me. It was created using ant. I've tried using an
exploded version, so with separate .class files, but that still doesn't
work. The testcase I posted in ASF bugzilla works for other people, so
something must be wrong on my side.
I'm going to try to test this
Paul Hamer wrote:
Hi Shankar and others,
I've filed it in Bugzilla... it has become Bug 39093.
The test case you provided made it very easy to check this and the bug
is not valid. The test case works fine for me with 5.5.15 and the
current HEAD. My environment is not identical but close
Hi again,
Just checked: the same problem occurs with Tomcat 5.5.15.
Regards,
Paul Hamer
management development
[EMAIL PROTECTED]
toHAVE websolutions
www.tohave.nl
[EMAIL PROTECTED]
-Original Message-
From: Paul Hamer [mailto:[EMAIL PROTECTED]
Sent: Thursday, 23 March 2006 13:59
To:
Tomcat is just adhering to the Sun Java specification naming
conventions. Packages should be lowercase. If Eclipse allows it, it's
being nice to you in the same way that IE is nice about rendering
invalid HTML.
It's better Tomcat forces you to correct your bad naming conventions
than encouraging
From: Allistair Crossley [mailto:[EMAIL PROTECTED]
Tomcat is just adhering to the Sun Java specification naming
conventions. Packages should be lowercase.
The OP's described package names *are* all lower-case, and the class
names are uppercase.
- Peter
Yes, apologies, that does indeed look suspect.
-Original Message-
From: Peter Crowther [mailto:[EMAIL PROTECTED]
Sent: 23 March 2006 13:40
To: Tomcat Users List
Subject: RE: Tomcat 5.5.16 Bug? messes up when a class has the same name
as a package
From: Allistair Crossley [mailto:[EMAIL
I cannot reproduce this issue in 5.5.16
I created a class qas at
com.qas
Resulting in a fully qualified class name of
com.qas.qas
Which in a JSP I instantiated with
com.qas.qas qas = new com.qas.qas();
No issue.
I then refactored to
com.qas.Qas
And re-tested again without issue.
Perhaps
Hi Allistair,
You're missing one vital part :-)
You've got only 1 class:
com.qas.Qas
The problem should occur when you add a second class called:
com.Qas
Now try
com.qas.Qas qas = new com.qas.Qas();
in your JSP again.
Regards,
Paul Hamer
management development
[EMAIL PROTECTED]
toHAVE
Except it doesn't :) It works for me.
%
com.Qas qas1 = new com.Qas();
com.qas.Qas qas2 = new com.qas.Qas();
out.println(qas1.test());
out.println(qas2.test());
%
I think it's your JAR. Rename your JAR to .ZIP and examine how its
packaged
