Checked out everything you suggested.  Everything's on the up-and-up.  The case is 
right.  The package is right.  I have even go to the extent of unzipping the jar file 
in the appropriate classes directory to no avail.

Thanks for the help.

The search continues....what a way to end the week :(

Sri

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:Kevin.Bedell@;sunlife.com] 
Sent: Friday, November 15, 2002 12:46 PM
To: Struts Users Mailing List
Subject: RE: [OT]Need magic incantation






Gee -

According to the Tomcat site, a webapp looks in all of these places in the order 
listed:

/WEB-INF/classes of your web application
/WEB-INF/lib/*.jar of your web application
Bootstrap classes of your JVM
System class loader classses (described above) $CATALINA_HOME/common/classes 
$CATALINA_HOME/common/endorsed/*.jar
$CATALINA_HOME/common/lib/*.jar
$CATALINA_HOME/shared/classes
$CATALINA_HOME/shared/lib/*.jar

Obviously, you've got this covered.

One issue I've noticed with this is case sensitivity. Sometimes if you're using a 
Windows OS classes can be located even if they have upper case in their directory 
paths. But when running in an APP server, case sensitivity will keep the class from 
being found. In your jar file, are there any upper case letters in any of the 
directory names? It might be worth reviewing the offending jar file structure to make 
sure there are no issues (though you've probably already done this...).

Not sure - it's probably something obvious because you seem to have the jar file 
whereit is visible.

Can you see other classes or properties files in that particular jar file?

Silly question - do you have the package and class names correct? Might be worth 
double checking.

















"Sri Sankaran" <[EMAIL PROTECTED]> on 11/15/2002 12:04:06 PM

Please respond to "Struts Users Mailing List"
       <[EMAIL PROTECTED]>

To:    "Struts Users Mailing List" <[EMAIL PROTECTED]>
cc:     (bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject:    RE: [OT]Need magic incantation


Alright.

What I have tried is to place the jar so that it is available to any of the common, 
shared or the webapp-specific classloaders. In other words, I've placed it in 
CATALINA_HOME/common/lib re-start & test then placed it in CATALINA_HOME/shared/lib 
re-start & test....

Sri

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:Kevin.Bedell@;sunlife.com]
Sent: Friday, November 15, 2002 11:50 AM
To: Struts Users Mailing List
Subject: Re: [OT]Need magic incantation






Can you re-phrase your question in terms of the classloader diagram at this page?

      http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html


That is, identify which classloaders your jar file should be visible to (system, 
shared, webapp, etc.) based on the directories you've put it in?







"Sri Sankaran" <[EMAIL PROTECTED]> on 11/15/2002 11:41:40 AM

Please respond to "Struts Users Mailing List"
       <[EMAIL PROTECTED]>

To:    "Struts-User" <[EMAIL PROTECTED]>
cc:     (bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject:    [OT]Need magic incantation


I'm being stymied by a classpath issue that occurs both on Tomcat 4.1.12 and JRun 3.1.

I get a ClassNotFoundException while the classpath clearly displays the jar file that 
contains the "missing" class.  I've even tried -- in desperation
-- putting the jar file in Tomcat's bin common/lib and server/lib directories to no 
avail.

The kicker is that I can successfully run a command-line application  -- that 
exercises the same business logic -- using the classpath used by Tomcat.

I know it could be any bunch of things -- but do you have any recommendations?

Sri






---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the 
individual or entity to which it is addressed and may contain information that is 
privileged, proprietary , confidential and exempt from disclosure.  If you are not the 
intended recipient, you are notified that any dissemination, distribution or copying 
of this communication is strictly prohibited.  If you have received this communication 
in error, please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------



--
To unsubscribe, e-mail:   <
mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: < mailto:struts-user-help@;jakarta.apache.org>


--
To unsubscribe, e-mail:   <
mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: < mailto:struts-user-help@;jakarta.apache.org>







---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the 
individual or entity to which it is addressed and may contain information that is 
privileged, proprietary , confidential and exempt from disclosure.  If you are not the 
intended recipient, you are notified that any dissemination, distribution or copying 
of this communication is strictly prohibited.  If you have received this communication 
in error, please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------



--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>

Reply via email to