If you use jdk 1.4 their might be a problem with loading javax.* classes.
May be you have to put them in a common dir of you server, or in the jre/lib/endorsed
dir.
Just a thought.
>>> [EMAIL PROTECTED] 13.12.2002 10.43 Uhr >>>
I use Axis as both a client and server.
As a web service engine
2 09:43
To: '[EMAIL PROTECTED]'
Subject: RE: Packaging Axis into an EAR file
I use Axis as both a client and server.
As a web service engine, I use Axis to basically map a web service to a
stateless session bean. This is where the Axis WAR has to be able to
access the EJB. If this i
I use Axis as both a client and server.
As a web service engine, I use Axis to basically map a web service to a
stateless session bean. This is where the Axis WAR has to be able to
access the EJB. If this is all I wanted to do, everything would be
fine... because that more or less works.
Howev
Hi Michael,
May I ask why the EJBs need to see Axis? We use Axis in WLS6.1sp4
with no problems, but we use it to provide a simple facade to a
Stateless Session Bean. That is, we expose our business methods
from the bean and have a thing POJO which Axis calls. This POJO
is responsible for understan
But I don't want the JARS in my classpath... that's the whole point of
trying to package them into the EAR file.
If I package the JARS as part of an AXIS WAR file, then AXIS can see my
EJBs however the EJBs can't see access. I assume I could somehow
reference these WAR JARS in the manifest file
Title: Re: Packaging Axis into an EAR file
Hello,
I have put the Axis jars in the webapp/lib/ directory and put the new jars in the classpath of the start.cmd file. WebLogic now finds all the necessary Axis classes and my Beans can use Axis and Axis can use my EJBs.
I hope this will help
