axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "THOMAS, JAI [AG-Contractor/1000]" <>
Subject RE: Weblogic and Axis 1.2 - packaging EJBs and axis
Date Tue, 19 Jul 2005 18:53:55 GMT
If you are adding Axis as a separate webapp, try adding your util jar to its manifest file.
You can also add Axis servlet to your web application as opposed to having a separate one.


-----Original Message-----
From: Krishnan Kannan []
Sent: Tuesday, July 19, 2005 12:22 PM
Subject: Weblogic and Axis 1.2 - packaging EJBs and axis

Hello all,

I am new to Axis and I am trying to use it to expose the Stateless 
Session EJBs in our application as webservices on Weblogic 8.1sp4.

So, I bundled up axis and it's libraries as "axis.war" and included this 
in our application  "myapp.ear" and deployed it on Weblogic.

Now, I can see the axis webapplication on the weblogic console and 
invoke the Admin and validation services. 

When I call the AdminClient to install my custom service using the 
deploy.wsdd file and invoke the services as


I get a ClassNotFoundException on the remote interface 

The Home and Remote interface classes are packaged in a common util jar 
file and is part of the APP-INF/lib directory in the myapp.ear file. So 
I assume the classes will be available for any  web application (.war) 
deployed as part of th same EAR file.

Could anybody point out what I am missing or doing it wrong ? 

Have anyone successfully used  Weblogic 8.1 with Axis 1.2.1 and exposed 
their EJB's as Webservices ?



This e-mail message may contain privileged and/or confidential information, and is intended
to be received only by persons entitled to receive such information.  If you have received
this e-mail in error, please notify the sender immediately.  Please delete it and all attachments
from any servers, hard drives or any other media.  Other use of this e-mail by you is strictly

All e-mails and attachments sent and received are subject to monitoring, reading and archival
by Monsanto.  The recipient of this e-mail is solely responsible for checking for the presence
of "Viruses" or other "Malware".  Monsanto accepts no liability for any damage caused by any
such code transmitted by or accompanying this e-mail or any attachment. 

View raw message