AW: Installing Problems

[Florian Schlosser]

Thank you for your answer. I have now copied all needed libaries to web-inf/lib directory this are the files in my webapp:   axis.jar, activation.jar, servlet.jar, wsdl4j.jar, jaxrpc.jar, saaj.jar, commons-logging.jar, commons-discovery.jar, axis-ant.jar, log4j-1.2.8.jar   and on the webserver are this files:   activation.jar, ant.jar, commons-collections.jar, commons-dbcp.jar commons-logging-api.jar, commons-pool.jar, jasper-compiler.jar, jasper-runtime.jar, jdbc2-0-stdext.jar, jndi.jar, jta.jar, mailapi.jar, naming-common.jar, naming-factory.jar, naming-resources.jar, servlet.jar   Ok I have tried different combinations of the libaries but without any positive result for example I deployed my webapp without activation.jar in the web-inf/lib and with it as so on… what is my fault?         -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Kevin Duffey Gesendet: Dienstag, 18. Januar 2005 02:29 An: [EMAIL PROTECTED] Betreff: Re: Installing Problems   What this error is referring to is the ClassLoader process is not able to find a dependent class. Basically, if you know much about ClassLoader delegation, a "parent" loader can NOT look down into children loaders without some special intervention to find classes. So, if you put the axis.jar in the web server classpath, but you deploy activation.jar or some other jar/class that axis needs to find, within the /lib dir of your .war file, the axis.jar can NOT find the jar it needs. Axis.jar, in this scenario is being loaded by a "parent" classloader than the one your web-app is loaded by. Each web app get's its own classloader instance, usually a classloader child to the application classloader (or one that is a child to the app classloader). So, your web-inf/classes can ALL see any class within your web-inf/lib *.jar and *.zip files as well as any classes in ANY parent loader, including the web server, which is why you dont need to deploy servlet.jar, and others with your web app. If axis.jar is deployed at the same level as servlet.jar, and axis.jar has code that needs to use classes out of activation.jar, and activation.jar is in your web-inf/lib dir, you are screwed. Either axis.jar needs to be deployed with your web app directly as part of its web-inf/lib dir, OR activation.jar (and others it needs) should be put in the same app server lib dir so they can all see each other.     --- Florian Schlosser <[EMAIL PROTECTED]> wrote:   > Hi! > >  > > I have added axis to my web application. The .war > file includes all files > which are needed. When I run happyaxis I get this > error message all other > tests are ok: > > Error: could not find a dependency of class > org.apache.axis.transport.http.AxisServlet from file > axis.jar > Axis will not work > See  <http://xml.apache.org/axis/> > http://xml.apache.org/axis/ > The root cause was: null > This can happen e.g. if > org.apache.axis.transport.http.AxisServlet is in the > 'common' classpath, but a dependency like > activation.jar is only in the > webapp classpath. > > What does this mean? I have read all mail group > entries I have found no > solution for this problem. > >  > > I hope you can help me! > >  > > With kind regards > > Florian Schlosser > >  > >  > >                          __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail