Glen, I have successfully deployed SOAP 2.2 on JRun as you have mentioned
(except I had Xerces replaced a while ago now).
It was just a matter of deploying the war file as normal. The main problem
with JRun is that it's support for XML is not up to date when you download a
copy (or purchase). We came across this problem a while ago when trying to
perform XML/XSL processing through JRun.
Provided the xml parsers are up to date, deploying SOAP 2.2 on JRun
shouldn't be complex: just deploy the war file.
Tomcat has been another story. Although I managed to deploy it, I have had
weird errors cropping up that didn't appear when running in JRun and trying
to run the addressbook sample. But as I said thats another story...
Cheers,
Anthony.
----- Original Message -----
From: "Glen Daniels" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 02, 2001 1:54 PM
Subject: Re: ServiceManagerClient install problem
> Now that SOAP 2.2 has been JAXP-fied, the install instructions might want
to
> change for JRun - you shouldn't now need to mess with the classpath in
> global.properties, as JAXP will automatically take care of things for you.
> (doing it still won't hurt, but it should be unnecessary)
>
> You do need to do exactly as you say, Anthony, remove the parser/jaxp jars
> from the JRun installation and replace them with copies of JAXP 1.1's
> jaxp.jar and a JAXP 1.1-compliant XML parser jar of your choice (I use
> crimson lately, but Xerces 1.4 should work fine as well) in JRun/lib/ext.
> Then all should be well.
>
> I believe the 2.2 installation has also been fixed to set up the war file
> more completely, so adding the soap libs/samples to your classpath likely
> isn't necessary either. In other words, installation should be as simple
as
> 1) setting up JAXP 1.1 and then 2) deploying soap.war....
>
> (caveat: I need to try this on a fresh JRun install to confirm it works
with
> SOAP 2.2 - it definitely works fine this way with Axis.)
>
> --Glen
>
> ----- Original Message -----
> From: "Anthony Ikeda" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 01, 2001 6:13 PM
> Subject: Re: ServiceManagerClient install problem
>
>
> > If it's a JAXP problem, then there really is only one way I know of on
how
> > to fix it. I've been trying to get an answer from Allaire about this for
> > ages (with no luck) but here is the way to sort it out:
> >
> > 1. Go to the JRunHome\lib\ext folder and remove the parser.jar and
> jaxp.jar
> > 2. Copy another XML driver (I use the latest version of Xerces) into the
> > JRunHome\lib\ext folder
> > 3. Restart your server.
> >
> > I haven't tested this with any other XML Parser, but as long as it's
JAXP2
> > compliant then it should alright (even the latest version of JAXP should
> > also fix this problem.
> >
> > I have found, however, that JRun is much better at deploying the soap
> server
> > than Tomcat. When trying to develop my own classes to publish on Tomcat
I
> > get too many errors compared to zero on JRun. (JRun actually worked
first
> > time)
> >
> >
> > Good luck,
> > Anthony Ikeda
> >
> >
> > ----- Original Message -----
> > From: "Tom Myers" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Sunday, July 01, 2001 10:38 PM
> > Subject: Re: ServiceManagerClient install problem
> >
> >
> > > At 11:58 PM 6/30/2001 -0700, JP Bonn wrote:
> > > >I'm trying to run soap under JRun 3.0. I followed the installation
> > > >directions for JRun (substituting soap.war in place of pointing to
the
> > > >directory). I can go to the rpcRouter URL and get the "post not get"
> > > >message so everything appears OK up to that point.
> > > >
> > > >If I try running the org.apache.soap.server.ServiceManagerClient I
get:
> > > >Ouch, the call failed:
> > > > Fault Code = SOAP-ENV:Server.Exception:
> > > > Fault String = java.lang.NoSuchMethodError
> > > >
> > > >Any ideas as to what I may have done wrong?
> > >
> > > 0ddly enough, this error is described in the docs under iPlanet
install,
> > > i.e. path-to-soap-2_2\docs\install\iPlanet.html:
> > >
> > > >If you encounter the following messages when running a sample,
> > > >the most likely cause is not having the JAXP compatible parser
> > > >library at the front of the server's classpath:
> > > >
> > > >D:\soap-2_2\samples\addressbook>testit
> > > >This test assumes a server URL of
> > http://127.0.0.1/NASApp/soap/servlet/rpcr
> > > >
> > > >Deploying the addressbook service...
> > > >Ouch, the call failed:
> > > > Fault Code = SOAP-ENV:Server.Exception:
> > > > Fault String = java.lang.NoSuchMethodError
> > > >...
> > > >This error occurs because the XML parser bundled with the
> > > >application server does not contain a class required by Apache
> > > >SOAP. Once you place a JAXP compatible parser at the front of
> > > >the server's classpath, you will solve this problem.
> > > >
> > > >If you encounter errors when running the Calculator sample,
> > > >ensure that you've added both the bsf.jar and js.jar
> > > >libraries to the start of the application server's classpath.
> > >
> > > (looks like that somebody clipped the output from a screen
> > > that wasn't wrapping, hence "/servlet/rpcr" at the end of a line
> > > instead of "servlet/rpcrouter"). Actually the error may occur
> > > even if you have Xerces 1.4 or better (do _not_ use 1.3.1) at
> > > the front of the classpath, but usually that has to do with
> > > things in your lib/ext directory.
> > >
> > > Tom Myers
> > >
> > >
> >
>
