Not really.  There are various messages on the internet about certain
(usually older) versions of Weblogic's classloader having problems with .war
and .ear deployments.  I've also found notes suggesting someone had this
kind of problem but had the code duplicated into two jars so there was an
unresolved conflict in which 'one' to load.  Also, you never did answer my
question: jar or WEB-INF/classes.

Here are various notes about older weblogic classloaders.  Have you searched
the weblogic site for struts problems for your version of weblogic?
http://www.onjava.com/pub/a/onjava/2001/06/26/ejb.html

This note from Craig could be useful:
http://www.mail-archive.com/struts-user@jakarta.apache.org/msg01788.html

Are ALL required .jar files copied into WEB-INF/classes?  This is key since
everyone forgets this note on the installation page and is a safe generic
statement from: http://struts.apache.org/1.2.x/userGuide/installation.html

WARNING - If you are going to be hosting multiple Struts based applications
on the same servlet container, you will be tempted to place the struts.jar
file into the shared repository supported by your container. Be advised that
this may cause ClassNotFoundException problems unless all of your
application classes are stored in the shared repository.

You can test this by putting the struts-examples.war on both your Weblogic
and Tomcat containers and making sure both start up.  If they are then copy
the jar files in WEB-INF/lib over to yours to be safe and if you have any of
those jars in a shared weblogic space you might (not sure) consider removing
the shared copy and ensuring each webapp that needs it gets its own copy of
that jar.

Regards,
David

-----Original Message-----
From: Tom Jerry [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 09, 2006 2:38 AM
To: Struts Users Mailing List
Subject: Re: bean exception when using weblogic and NOT tomcat

however dumb the question maybe... the output should come.... As per you
said, I deployed a copy of tomcat's version into weblogic... still the same
error. I deployed the folder as a exploded module and NOT as archived one. I
am sorry if you think it is a dumb question. But think from my point of
view, it is more weird than U think. :(:(:(


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to