Its also useful to note that classes outside of a package must be
imported explicitly - each class has to be named and you can't use any *'s
to pick all of the unpackaged classes.

        Randy


> -----Original Message-----
> From: Pal, Anshu [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 12, 2001 12:38 PM
> To: 'Tomcat Users List'
> Subject: RE: Weird Tomcat 4.0 class exception?
> 
> 
> I had a similar problem with my servlet once. Turned out that 
> I did not put
> the class in my import statement.
> 
> Once I put the import statement ( import packagename.classname;)
> it worked fine.
> 
> Hope it helps
> 
> Anshu 
> 
> Proprietary/Confidential Information belonging to CGI may be contained
> in this message. If you are not a recipient indicated or intended in
> this message (or responsible for delivery of this message to such
> person), or you think for any reason that this message may have been
> addressed to you in error, you may not use or copy or deliver this
> message to anyone else. In such case, you should destroy this message
> and kindly notify the sender by reply e-mail.
> 
> 
> -----Original Message-----
> From: Shashi Dookhee [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 12, 2001 12:24 PM
> To: [EMAIL PROTECTED]
> Subject: Weird Tomcat 4.0 class exception?
> 
> 
>  
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi all,
> 
> I have recently built and deployed Tomcat 4.0.1.  Everything seems to
> go well when starting it, and I can access the examples, etc, but I
> have a very weird problem when deploying my own application (which
> runs fine under Tomcat 3.2):
> 
> I have a series of JSP and class files which are deployed as
> followed:
> 
> webapps/jsp -- contains JSP files
> webapps/jsp/WEB-INF/classes -- contains class files
> 
> My JSP files attempt to access the classes with the following
> directive:
> 
> <jsp:useBean id="someBean" scope="session" class="SomeBean" />
> 
> When this gets executed, I get a ClassNotFound exception, even though
> SomeBean.class is in the classes directory...  BUT the weird part is
> that it doesnt look for SomeBean - it actually looks for
> org.apache.jsp.SomeBean!!  (if I put the SomeBean.class in the
> org.apache.jsp.* framework, it will find it - but then of course
> complain that SomeBean.class is not of the required type!).
> 
> I know I am probably missing something pretty small - but I cant find
> it!
> 
> Anyone got any ideas?
> 
> Thanks
> 
> Shashi Dookhee
> Head of IT Infrastructure
> 
> e-mail:  [EMAIL PROTECTED]
> Telephone (Direct Line):        +44 (0)20 7298 8222
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 7.1
> 
> iQA/AwUBPBeSrB81+wdHSEUlEQLLlACgq2zLyQPiwas5n6M8r3u9ER4GCVAAoNyQ
> YtwYSGZM36BE8K7DFNVz0L1B
> =MiIa
> -----END PGP SIGNATURE-----
> 
> ==============================================================
> ==============
> ===
> 
> Traffic Proximity Limited
> 191 Old Marylebone Road
> London
> NW1 5DW
> United Kingdom
> Registered number: 3164767
> Registered in England
> 
> Tel:  +44 (0) 20 7298 8200
> Fax:  +44 (0) 20 7298 8201
> 
> 
> This email its contents and any files or images with it are 
> intended solely
> for the addressee(s) and are confidential. If you have 
> received this email
> in error you may not copy or use the contents, attachments or 
> information in
> any way. Please destroy it and contact the sender on the 
> number printed
> above, via the Traffic Proximity switchboard or via email return.
> 
> DISCLAIMER
> Material contained in this email may be copyright material of 
> Traffic Proximity or protected by other intellectual property 
> rights. It
> may only be reproduced with the express permission of Traffic 
> Proximity. 
> Traffic Proxmity does not accept responsibility for any 
> changes made to
> this email by unauthorised parties after it was sent. Whilst Traffic
> Proximity runs antivirus software on all Internet emails it is not
> liable for any loss or damage caused by an infected email. 
> The recipient
> is advised to run their own antivirus software. All 
> information contained
> in this email has been prepared using information believed by 
> the author
> to be reliable and accurate, but Traffic Proximity makes no 
> warranty as
> to accuracy and completeness. Any opinions expressed in this email are
> those of the author and do not necessarily reflect the 
> opinions of Traffic
> Proximity or its affiliates.
> 
> ==============================================================
> ==============
> ===
> 
> 
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
> 
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
> 

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to