I'm sure there are some statice methods or variables that you can get this
information from. I think this same question was answered quite recently...
Try accessing the Mailing List archives from the Axis website to search for
an answer.
HTH
Jim
> -Original Message-
> From: Jeyakumaran.C
I had
a similar situation with one of my services Dimuthu...
It
doesn't seem to affect the operation of the service on when using Axis at both
ends but is a little unsightly... To make sure the xmlns is given a value,
when you add the parameter to the call, make sure you use a QName to ad
Hi,
I have just come across some interesting behaviour regarding the use of the
setOperationName() method. It turns out that if you do not specify any
Parameters in your call (which would normally fill the SOAP Body of the
request) then the name of the operation (as set by the setOperationName
m
I had a problem where my client-side handler was not being envoked last
week. The only way I could solve it was to declare the handler in the
of the client-config.wsdd - declaring handlers per
service does not seem to work, maybe this is a bug...
HTH
Jim
> -Original Message-
> From: [EM
Skovenborg [mailto:[EMAIL PROTECTED]
> Sent: 18 August 2003 15:08
> To: '[EMAIL PROTECTED]'
> Subject: SV: Axis MessageContext to the WebService
>
>
> Hej Jim
> How does that work with concurrent WebServices? Wont you get a
> MessageContext belongs to another sess
> Sent: 18 August 2003 15:55
> To: [EMAIL PROTECTED]
> Subject: Re: RE: Axis MessageContext to the WebService
>
>
> Hej Jim
> How does that work with concurrent WebServices? Wont you get a
> MessageContext belongs to another session.
> /Jakob
>
> Jim Harr
Hi,
I'm hoping someone can help me with this problem which I has caused me
sleepless nights over the weekend!!!
I have a client program accessing a Web service with a handler being invoked
on the service- and client-side in between. Infact, my handler is based on
the SimpleSessionHandler from th
Jakob
Usually the MessageContext is available to a Web service invoked by axis
through the static method of the MessageContext class as follows:
MessageContext msgContext = MessageContext.getCurrentContext();
I think that is the one...
HTH
Jim
> -Original Message-
> From: Jakob Skovenb
> The "Done Processing" indicates that the AdminClient successfully
> processed the WSDD file.
Just to add some context to that, the AdminClient is used to deply the
webservice using the deploy.wsdd as the deployment descriptor. In terms of
seeing things happen, you could look at the server-confi
Guys,
Is this not an argument about web service namimg conventions? I have never
seen a web service name with spaces (although I am fairly new to this game)
so could someone on the list advise whether spaces in service names are
advisable at all?
Jim
> -Original Message-
> From: Shantanu
I would advise using the SOAP 'message' format instead of RPC for this (see
the SOAP specifications at w3.org for definitions). There is a section in
the user guide about the basics of this. Using message-based calls to your
web service allows you to pass in an xml document as you suggest which is
Junaid,
Instead of using the AdminClient tool to deploy your services you could
always just edit the server-config.wsdd file by hand. I realise this is a
fudge but I don't know of any other way of doing what you want at the moment
apart from adding the functionality yourself as you sugges
HTH
Jim Harris
> -Original Message-
> From: Jorge Alberto Rodriguez Suarez [mailto:[EMAIL PROTECTED]
> Sent: 12 August 2003 21:16
> To: [EMAIL PROTECTED]
> Subject: AdminClient Exception...
>
>
> Hi there!
>
> When iam making:
>
> java -cp %AXIS_CLASSP
Kareem,
I have just spend a fair while solving a 500 Internal Server error. For me
the problem was that my method used classes that could not be found by axis
(I had named the classes incorrectly). I would advise that as a first step
you look at your code and figure out which classes are being u
rovider"/>
> type="java:org.apache.axis.handlers.SimpleAuthenticationHandler"/>
> type="java:org.apache.axis.providers.java.MsgProvider"/>
>
>
>
>
> http://xml.apache.org/axis/wsdd/
>
>
>
>
>
>
>
>
>
>
>
>
>
> ...
>
>
Said,
In your client it seems that you are going to invoke the session handler
twice due to it being in the global and service-specific chains. I would
remove the parts from the global chain so that your client-config.wsdd looks
more like this:
http://xml.apache.org/axis/wsdd/";
xmlns:java="htt
dler"/>
> type="java:org.apache.axis.providers.java.MsgProvider"/>
>
>
>
>
> http://xml.apache.org/axis/wsdd/
>
>
>
>
>
>
>
>
>
>
>
>
>
> ...
>
> pivot="java:org.apache.axis.transport.http.HTTPSender">
&g
Frank,
The information from the Client seems to give the best pointers:
> and the Clientapplication:
> Tried to invoke method public boolean
> indeedsimulation.ws.IndeedsimulationSoapBindingImpl.setFile(java.l
ang.String,java.lang.String,javax.activation.DataHandler) throws >
java.rmi.RemoteExcep
> DOH! I think restarting Tomcat was the key I was missing.
Haha - that one has cost me hours too!!!
> Also, using this:
>
> > java org.apache.axis.client.AdminClient -l
> > http://host:port/axis/classes/serviceName path\to\deploy.wsdd
>
>
> Style call to the AdminClient returned a fault (HTTP
Said,
One thing I can see is that you are referencing the SimpleSessionHandler by
the wrong name in the request and response flows of your service:
> type="java:org.apache.axis.handlers.SimpleSessionHandler"/>
>
>
>
>
>
>
>
> ..
>
You give the handler the name 'S
> IMHO, I still think that Axis should provide this facility in a future
> release.
Good stuff! Why not submit your code to the axis folks for consideration?
Jim
Adhamh,
Have you tried using the AdminClient tool to deploy and/or view your
deployed services?
To deploy use:
java org.apache.axis.client.AdminClient -l
http://host:port/axis/classes/serviceName path\to\deploy.wsdd
Then to list the deployed services use:
java org.apache.axis.client.AdminClient
> I run the WSDL2Java tool and then cut and paste the service entry
> from the deploy.wsdd file into the server-config.wsdd file. Seems
> to work.
For more complicated services thats exactly what I do Stuart - you are
right, it does seem to work very well and I find is much easier than using
the
e it must be
possible!!!
Note:I am using Axis 1.1
Thanks in advance for any help.
Regards
Jim Harris
.
Also,
are you using DOM or SAX for your XML work - SAX would be better as it is more
efficient and does not load the entire document into memory prior to doing
anything with it like DOM does.
Just
some thoughts...
Jim
Harris
-Original Message-From: MicHael Galkovsky
[mailto
25 matches
Mail list logo
