Hi Nick,
here is how I do it.
// get Axis MessageContext
MessageContext msgCtx = MessageContext.getCurrentContext();
// get Servlet request object
HttpServletRequest httpReq =
(HttpServletRequest)
msgCtx.getProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST);
// get address of remote caller
St
a SOAP client? Is this the extent of the session management in
Axis?
Thanks,
Grant
- Original Message -----
From:
Volanis, Alexander
To: '[EMAIL PROTECTED]'
Sent: Friday, September 27, 2002 8:48
AM
Subject: RE:
MessageCont
Title: Message
The
correct way to enable session management is in your deploy.wsdd file. Add
to your service deployment. To
get the desired effect your clients have to enable session management as well.
Use ((org.apache.axis.client.Stub) ws).setMaintainSession(true) where "ws" is
your serv
I believe this problem is related with '-' in jar filenames and the manifest
file validation. SP3 for WL 6.1 corrects this problem.
-Original Message-
From: Jeff Drost [mailto:[EMAIL PROTECTED]]
Sent: Saturday, July 13, 2002 8:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Error loading AXIS be
Hi
Joseph,
I had
the same problem and called BEA support and here is what happens. In SP2 the
introduced validation for manifest files (I cannot think why). This breaks some
third party jars. In my case the problem seemed to go away once I split the jars
cleanly between the main classpath
Hi,
I have successfully used Axis in the way you describe and discovered that
adding the "javax.net.debug=ssl" property can cause this error in Weblogic
6.1. It helped diagnose misconfiguration during setup but once all
configuration/keystore problems were corrected it was actually causing a
prob
Hi,
I reported the same thing in the axis-dev list but did not get any
resolution. There was a bit of discussion on the subject. Look into the
thread "[BUG] Beta2 interop (was RE: Interoperability issue with
MSVC++.Net)".
This seems to have changed in beta2. It was OK in beta1.
-Original Me
Hi Neil,
I had a similar problem and discovered that you must use the
attribute style="document" in the service element. In beta 1
Axis would not retain this attribute in server-config.wsdd.
I had been editing the server-config.wsdd to add this after
the service deployment. In beta 2 this seems t
All,
This is a two part question.
PART 1.
I am trying to create a document/literal service using Axis and have not had
much success. My service would have a single method with a signature like
this:
public class SAMLRequest {
public Document SAMLAssertion( Document doc ) {
