Forgot: Using 1.2RC2
On Feb 2, 2005, at 4:03 PM, Linus Kamb wrote:
Curious why when I try to send the simple XML
some text
using axis "message" style, out the other side comes:
some text
Note the empty namespace string.
Are namespaces required on all elements? And
Curious why when I try to send the simple XML
some text
using axis "message" style, out the other side comes:
some text
Note the empty namespace string.
Are namespaces required on all elements? And if so, why isn't one
being put on the outer element?
The inner e
When I view the soap message in tcpmon, it works great, but I keep getting
errors trying to test the client code. Here is the code:
package client;
import stubs.*;
import org.apache.axis.utils.XMLUtils;
/**
* Client.java
*
*/
public class Client {
/**
* main method is what is c
swer.
>
> (1) if i wanted to use document/literal interaction for a web services would
> this be the equivalent of what axis refers to as "message" style?
"Wrapped" and "document" styles produce document/literal services.
"Rpc" style produces
efers to as "message" style?
(2) the axis documentation provides 4 possible signatures for message
style interaction:
public Element [] method(Element [] bodies);
public SOAPBodyElement [] method (SOAPBodyElement [] bodies);
public Document method(Document body);
public void method(S
I don't think Axis can dispatch the call
for you. With message style, you've told Axis that you're effectively handling
the SOAP message yourself (though Axis allows you to use one of several
method signatures), consequently, you'll have to do the dispatching.
This is my read
en RD-BIZZ [mailto:[EMAIL PROTECTED]
Sent: Friday, December 03, 2004 12:31 PM
To: [EMAIL PROTECTED]
Subject: Re: Multiple methods in a single web service (message style)
Eyad Garelnabi a écrit :
> Hi,
>
> I'm interested in having the client call one of two (or three) methods
> th
Eyad Garelnabi a écrit :
Hi,
I’m interested in having the client call one of two (or three) methods
that are within the same web service. I’m using currently using
“message style” webservices and through the research I’ve done so far
it seems to me that with message style I can’t have multiple
Hi,
I’m interested in having the client call one of two (or three)
methods that are within the same web service. I’m using currently using “message
style” webservices and through the research I’ve
done so far it seems to me that with message style I can’t have multiple
methods in a single
Hello !
We are using message-style argument passing with Axis both on the client
and the provider. The signature of all the methods is
Element[] method(Element[]), but in one instance we don't need to read
any arguments. When we invoke this method with
call.invoke((SOAPBodyElement[])
Is it possible to use a schema to validate the request and response
bodies when using message style web services without having to specify
a complete wsdl file?
, 14 Oct 2004, Thomas Forrester wrote:
> Does anyone out there use the message style services?
>
> I am coming to the impression that nobody uses these methods, everyone
> uses the RPC style.
>
> Is this the case, if so what do people use for Message style web
> services, the JAA
as argument when you run the client, say your
name "Thomas"
Krish
-Original Message-
From: Thomas Forrester [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 14, 2004 6:56 PM
To: [EMAIL PROTECTED]
Subject: Does anyone use the message style services in AXIS or is every
oneusing
Does anyone out there use the message style services?
I am coming to the impression that nobody uses these methods, everyone
uses the RPC style.
Is this the case, if so what do people use for Message style web
services, the JAAXM API's in the JWSDP possibly?
I would appreciate some dial
Does anyone out there use the message style services?
I am having real problems just trying to get a simple solution working
with nested elements.
The TestMsg.java example works OK to send individual elements (without
children).
I can not find any references on how to use implement the Document
Rafael,
The primary criterion for choosing between the message provider (message
style) and the RCP provider (RPC/wrapped/document styles) is based on
whether you prefer to parse the XML yourself (message style) or if you'd
rather work with Java objects (RPC provider). When using the me
the
message. You get it for free using a method per possible operation. Then
it might be a good idea to use it. But if this is unexpectably working,
i.e, it is not meant to work like that, then let's forget Option #1.
The reason why I want to use Axis message style is mainly because I am
I apologize -- I'm not an expert on the Axis message handler, so I'm not
100% sure about this answer -- perhaps someone else can pipe up and correct
me if I'm wrong. But here's my reasoning about how it should work:
When using a message style service with a message signatu
l to use it yet.
Any comments on this?
Shantanu
--- Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
More comments bracketed by ... .
-Original Message-
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Friday, September 24, 2004 2:46 PM
To: [EMAIL PROTECTED]
Subject: Re: message style SO
parameters.
But most tools generate the wrapped convention because it makes it easier
for the developer.
Anne
-Original Message-
From: Shantanu Sen [mailto:[EMAIL PROTECTED]
Sent: Friday, September 24, 2004 8:28 PM
To: [EMAIL PROTECTED]
Subject: RE: message style SOAP service
Wh
parameters.
But most tools generate the wrapped convention because it makes it easier
for the developer.
Anne
-Original Message-
From: Shantanu Sen [mailto:[EMAIL PROTECTED]
Sent: Friday, September 24, 2004 8:28 PM
To: [EMAIL PROTECTED]
Subject: RE: message style SOAP service
Wh
t; More comments bracketed by ... .
>
> -Original Message-
> From: Jim Murphy [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 24, 2004 2:46 PM
> To: [EMAIL PROTECTED]
> Subject: Re: message style SOAP service
>
> Shah, Soniya M. [RA] wrote:
>
> > 1. Could me
More comments bracketed by ... .
-Original Message-
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Friday, September 24, 2004 2:46 PM
To: [EMAIL PROTECTED]
Subject: Re: message style SOAP service
Shah, Soniya M. [RA] wrote:
> 1. Could message-based service have WSDL? Could
More comments bracketed by ... .
-Original Message-
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Friday, September 24, 2004 2:46 PM
To: [EMAIL PROTECTED]
Subject: Re: message style SOAP service
Shah, Soniya M. [RA] wrote:
> 1. Could message-based service have WSDL? Could
,
Soniya
-Original Message-
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Friday, September 24, 2004 2:46 PM
To: [EMAIL PROTECTED]
Subject: Re: message style SOAP service
Shah, Soniya M. [RA] wrote:
> 1. Could message-based service have WSDL? Could we generate code
> based
>
Shah, Soniya M. [RA] wrote:
1. Could message-based service have WSDL? Could we generate code based
on WSDL like we do for RPC based? I would think that this is not the
case as with document style you will have parse your own xml data. So
all you would need to publish is the schema for your xml?
Title: Message
Hi
All,
My SOAP service is
RPC based. Recently I am looking into a message-based SOAP service. I read thru
lot of documentation but I am still confused about following
things:
1. Could
message-based service have WSDL? Could we generate code based on WSDL like
we do fo
Hi Dhanush,
I am trying to pass a DOM document to a WebService which is using
"Message" Style of Service. But looking into the Axis Use Guide I
could find that the methods which I write should be of any of these
forms:
public Element [] method(Element
what is in the string you are returning? a response code, or a document?
-pc
- Original Message -
From: Dhanush Gopinath <[EMAIL PROTECTED]>
Date: Wed, 11 Aug 2004 10:33:34 +0530
Subject: REPOST Re: Why there is restriction for Method Signatures in
MESSAGE Style?
To:
Reposting the
Question.
Any Ideas ?? Any Pointers also will
do
- Original Message -
From:
Dhanush
Gopinath
To: [EMAIL PROTECTED]
Sent: Monday, August 09, 2004 3:17
PM
Subject: Why there is restriction for
Method Signatures in MESSAGE Style?
Hi All
Hi All ,
I am trying to pass a DOM document
to a WebService which is using "Message" Style of Service. But looking into the
Axis Use Guide I could find that the methods which I write should be of any of
these forms:
public Element
[] method(Element [] bodies);
public
SOAPB
I am using the message style. I have the following method:
public Document processRequest(Document doc) {
Document res_dom_doc = null;
try {
My_Message msg = new My_Message(doc);
MyConnectionToExternalSystem conn =
newMyConnectionToExternalSystem("&
one of the services for which I need to just plug-in my XML
instead of passing it to the Axis Serializer. I searched on the net and
found something called "message" style. Can somebody tell me if this is
right and if they can point me to some sample programs, it will be
helpful.
Hi All,
We already have an XML Document
with us. I am currently using Axis and this is one of the services for
which I need to just plug-in my XML instead of passing it to the Axis Serializer.
I searched on the net and found something called "message" style.
Can somebody tell me
No, I was using javax.xml.soap.SOAPBodyElement. Thanks for pointing out
an obvious mistake!
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 10, 2004 2:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Trouble with Message-style dep
org.apache.axis.message.SOAPBodyElement. Right?
On Thu, 10 Jun 2004 14:04:39 -0400, Mark D. Hansen
<[EMAIL PROTECTED]> wrote:
>
>
> I can't seem to get Message-style services with this signature
>
> public SOAPBodyElement [] method (SOAPBodyElement [] bodies);
>
I can't seem to get Message-style services with this signature
public SOAPBodyElement [] method (SOAPBodyElement [] bodies);
to deploy on Axis 1.2beta. The deploy.WSDD gets processed OK, but when =
I try to use the service, I get the exception:
"does not match any of the valid sign
Hi guys,
and thanks for the answer.
First of all was a mistake in my message-style web services, so for very
small messages (an xml request with one item)
as I expected the message style looks to be faster then RPC style(3-5
times).
Unfortunatly I had to send a large amount of data over Web
DOCUMENT. Here you should see very little difference
in performance.
Anne
-Original Message-
From: Nelson Minar [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 8:44 PM
To: [EMAIL PROTECTED]
Subject: Re: Is it message style MUCH slower then rpc?
>It looks like the message style
DOCUMENT. Here you should see very little difference
in performance.
Anne
-Original Message-
From: Nelson Minar [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 8:44 PM
To: [EMAIL PROTECTED]
Subject: Re: Is it message style MUCH slower then rpc?
>It looks like the message style
>It looks like the message style web service is 6 -20 times slower
>then the old version using JAXP-RPC model.
I can't answer your questions, but I'd be very interested to know
more. What kind of data are you passing back and forth?
It should be straightforward to make a perfo
Hi guys,
We developed a set of web services with Axis using RPC style, but we need
better performance so we try a message style approch. We though that using a
message style approch willl get better performance, by avoiding the overhead
of the serialization/deserialization process. Instead of
L)
I am passing a select statement, and the method fetches the data and
creates a Document object to return. I continue to get an error
message:
Java.lang.Exception: Method 'getXML does not match any of the valid
signatures for message-style service methods
I did a google search, but
Does Axis C++ 1.0 support message-style web services? If yes, is there some
documentation available on this subject?
Thank you!
Thomas Kirsch
between Java and XML.
Perhaps you're confusing document style with message style?
These terms get confusing because "document" style has two separate
meanings in Axis. From the WSDL perspective (which is a standard
terminology), document style refers to the way that a SOAP message
ument in either
the client, handlers, or service implementation.
Your thoughts?
-Jon
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Monday, April 05, 2004 1:07 PM
To: [EMAIL PROTECTED]
Subject: Re: What are the advantages of Message style web services?
If y
Sorry .. since both ends (Client and Server) deals directly with xml
documents.
-Original Message-
From: Pillai, Ranjith
Sent: Monday, April 05, 2004 11:42 AM
To: [EMAIL PROTECTED]
Subject: RE: What are the advantages of Message style web services?
Hi Anne,
Thanks for the information
Hi Anne,
Thanks for the information.
I had the impression (read earlier in Axis User group) that Message
Style services are better for interoperability since both deals directly
with xml documents.
Thanks,
Ranjith Pillai.
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL
ur thoughts?
-Jon
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Monday, April 05, 2004 1:07 PM
To: [EMAIL PROTECTED]
Subject: Re: What are the advantages of Message style web services?
If your application prefers to work with the information in it&#
If your application prefers to work with the information in it's native XML
format, then you want to use the message style. For example, if your
application simply wants to process one portion of a large document and
then send it along in a workflow, it doesn't make sense to convert t
Hi Axis Community,
Could anyone shed some light on real advantages of Axis Message Style
services compared to passing in and out complex beans?
Any help will be deeply appreciated,
Ranjith Pillai.
,
Jason
On Thursday 18 March 2004 7:31 am, Anne Thomas Manes wrote:
> Better yet -- used doc/lit with the "wrapped" style.
>
> At 02:33 AM 3/18/2004, you wrote:
> >To combine the rpc and the message style, why don't
> >you use the rpc style adding an xml document
get lower level access
to the response so that I can skip the marshal/unmarshal/serialize steps.
Jason
On Wednesday 17 March 2004 11:50 pm, Dario Di wrote:
> To combine the rpc and the message style, why don't
> you use the rpc style adding an xml document as
> attachment?
>
Better yet -- used doc/lit with the "wrapped" style.
At 02:33 AM 3/18/2004, you wrote:
To combine the rpc and the message style, why don't
you use the rpc style adding an xml document as
attachment?
--- Jason Calabrese <[EMAIL PROTECTED]> ha
scritto: > Hi everyone,
>
To combine the rpc and the message style, why don't
you use the rpc style adding an xml document as
attachment?
--- Jason Calabrese <[EMAIL PROTECTED]> ha
scritto: > Hi everyone,
>
> Is there anyway combine the rpc and message styles?
>
> What I would like is
Hi everyone,
Is there anyway combine the rpc and message styles?
What I would like is to have a method signature something like this:
Document doSomething(CustomRequest req);
I will be using the data in the CustomRequest to interface with an existing
application that returns a DOM document and
maybe the way is to use in client
call.addAttachmentPart(ap);
(where ap is an org.apache.axis.attachments.AttachmentPart object)
before invoking the web service?
Dario
Dario Di ha scritto:
Hi everybody,
I'd like the client of a message style web service
(like the "message" e
Hi everybody,
I'd like the client of a message style web service
(like the "message" example) to send an xml and an
attachment to the service.
What should I add to the server-config.wsdd?
How can the client attach the files?
What should be the signature of the echo
move it to
/webapps/axix/WEB-INF/classes/message
Doing the above, I was able to get it to work.
-dexter
--- On Mon 03/08, Vivek Nagulapati < [EMAIL PROTECTED] > wrote:
From: Vivek Nagulapati [mailto: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Mon, 08 Mar 2004 11:58:21 -0600
Sub
Hello Guys,
I am trying to implement message-style web services using one of the
examples provided in the Axis distribution i.e., the one in
"samples/message/MessageService.java".
No matter how I change the implementation in MessageService.java, it returns
the SAME SOAP request rece
If you read the Axis User's Guide, you’ll
find the following description:
………..
Message services
Finally, we arrive at "Message"
style services, which should be used when you want Axis to step back and let
your code at the actual XML ins
msg.getSOAPTransport
();
BufferedReader br =
st.receive ();
thanks and regards hanmayya udgiri
-Original Message-From:
Xiao, Hui [mailto:[EMAIL PROTECTED]Sent: Wednesday, January 28,
2004 11:56 PMTo: [EMAIL PROTECTED]Cc: Xiao, Hui;
Currier, JeffSubject: How to invoke "Messa
.
Read the User Guide for
that .
Regards
Dhanush
- Original Message -
From:
Xiao, Hui
To: [EMAIL PROTECTED]
Cc: Xiao, Hui ; Currier,
Jeff
Sent: Wednesday, January 28, 2004 11:55
PM
Subject: How to invoke "Message" style
services passing a DO
anybody who knows how to invoke my service passing a DOM Document object? Thanks a lot, Hui Xiao
package samples.message ;
import org.w3c.dom.Document;
/**
* Simple message-style service sample.
*/
public class MessageService
{
/**
* Service method, which simply echoes
Hi PASQUER,
At the end of this email, please find the WSDD file, and the sample
request and response for the message style service that comes with
axis/samples.
Just compile the MessageService.java class and place it in
WEB-INF/classes/samples/message directory. Copy-paste this WSDD entry in
Hi all,
I've still having trouble getting document-style SOAP calls to work in Axis with
SOAPBodyElement [] myService (SOAPBodyElement [] bodies) :
SOAPFactoryImpl soapFactory=new SOAPFactoryImpl();
Name a=soapFactory.createName("A","icar","URI");
SOAPBodyElement bodyElement=new SOAPBodyElemen
type is also org.w3c.dom.Element. However I find org.w3c.dom to be
pointlessly difficult when there are so many better solutions available, and
so do my colleagues who must write code for various services that will be
deployed on AXIS.
I would like to know how to invoke a message style service as
Hi!
I've been experiencing some problems when sending attachments to a message
style service.
The service uses the
public Element [] method(Element [] bodies)
method signature.
Everything runs fine when sending attachments < 16k and I'm able to get them
in the service. However,
[EMAIL PROTECTED] operation when the multiple
he.org Message-style operations are
defined in one WSDL and served by
the
sers and developers,
I'm facing a very unique issue and any help, suggestion pointers to resolve this would be highly appreciated.
Context of the issue
I have 6 operations (web services) in one WSDL. All these web services are deployed as Axis-Message style serv
ed as Axis-Message
style services. All of these web services takes Document as input and returns
the document. Following are the method signatures I have for these web services.
1. public Document createProfile(Document
body);
2. public Document updateProfile(Document
body);
3. public Doc
LSchema-instance";>
http://eprofile.globalops.hp.com/eProfileService";>AppIDLangIDHppIDSIDDummyTemplateID
http://eprofile.globalops.hp.com/eProfileService";>
2003-11-14T16:44:50.633Z
Here is how the request generated by Axis client, which fails to invoke the intended
op
Hi Berin,
We haven't still worked on document style or message style as implemented
in axis java. But we are steadily progressing on making axis c++ a fully
grown soap engine with the help of the community. We greatly apprciate
inquiries like we had from you so that we can understand wh
WIth thanks. Unfortunately I need to comply with a spec that requires the
XML be embedded as standard in a Soap body.
Are there any plans to implement the Message style of service in C++?
Alternate question - is there any interest in seeing it implemented (other
than me :>).
Che
; Sent: 15 November 2003 09:01
> To: [EMAIL PROTECTED]
> Subject: Fwd: [C++] message style service
>
> Any thoughts greatly appreciated!
>
> (Or is this a stupid question? :>)
>
> Cheers,
> Berin
>
>>From: "Berin Lautenbach" <[EMAIL
Is it not possible to have an RPC based service accepting a String literal
argument that contains unparsed XML?
Richard
-Original Message-
From: Berin Lautenbach [mailto:[EMAIL PROTECTED]
Sent: 15 November 2003 09:01
To: [EMAIL PROTECTED]
Subject: Fwd: [C++] message style service
Any
Any thoughts greatly appreciated!
(Or is this a stupid question? :>)
Cheers,
Berin
From: "Berin Lautenbach" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [C++] message style service
Date: Sun, 09 Nov 2003 18:33:11 +1100
Peoples,
I am ne
I used the following sinature for massage style,
public void method(SOAPEnvelope req, SOAPEnvelope resp);
In the request (req) I recieve some Japanees charactors(through the client -
I am using Microsoft InfoPath). I need to convert this req envelop to a byte
array so that I can use 'Shoft_JIS
Peoples,
I am needing to use Axis C++ to hand me back the XML body of a soap message.
The provider needs to see the XML (either raw or as a DOM structure), as
that is what it then works on.
The Java version of Axis provides a "message" style service that does just
this - pass
I am new to axis development and am looking for some
sample code that utililzes message style signature:
public void method(SOAPEnvelope request, SOAPEnvelope
response)
Inside the method I will be looking at SOAP headers
and building XML response. Any pointers will be
greatly appreciated.
Igor
ldve: 2003. szeptember 16.
18:33Címzett: [EMAIL PROTECTED]Tárgy: Re: Message
Style SOAP
Thanks Shmuel.
Yes I’m using a request that contains a SOAPEnvelope
as String and END_POINT is Axis Message Style
Service.
Im
getting the following exception now
:
Thanks Shmuel.
Yes I’m using a request that contains a SOAPEnvelope as String
and END_POINT is Axis Message Style Service.
Im getting the following
exception now :
Exception :
---
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
Hello,
Assumption1 - xmlRequest contains an Envelope as String
(you can get from a file)
Assumption2 - END_POINT contains a URL for
Webservice deployed in Axis Message style.
It
works for me with Webservice deployed with signature:
public
Document getBody(Document body)
so I
get
Hi,
Can somebody please provide client sample for the below
method signature
public void method(SOAPEnvelope
req, SOAPEnvelope resp)
Thanks
Satheesh Mani
Title: RE: message-style frustrations (this time in plain text)
You were correct! Adding a namespace (any namespace) to the root element of my Document allowed me to not set the operation name on the Call. Does anyone know why that makes a difference?
-Original Message-
From
Hi,
I would like to know whether the following method :
public void method(SOAPEnvelope req, SOAPEnvelope
resp);
is still a valid signature for message-based services
in AXIS. It gives me an error while deploying. I
used the javax.xml.soap.SOAPEnvelope.
Am I supposed to use a different class
Title: RE: message-style frustrations (this time in plain text)
Hi Volkmann,
Sorry I forgot to mention an important
point ...
In your document ( which you are
passing to the service method) for the root element add namespace.
That may help you to remove call to setOpertionName
Title: RE: message-style frustrations (this time in plain text)
Hi Volkmann,
I can answer one question.. As
I mentioned earlier you cannot embed an XML document within another XML document
Since your SOAPMessage itself is a XML document, you cannot embed your
document inside another
Title: RE: message-style frustrations (this time in plain text)
Based on the suggestions I've received, I now have a working example of passing a DOM Document to a service and getting one back in return. I've included the code below (with comments and some whitespace removed)
Title: message-style frustrations (this time in plain text)
Hi,
Thanks! That helps,
but I can't say I like it. I think that Axis should recognize that you've given
it a Document and wrap it in a SOAPBodyElement by itself if that's what it
needs.
In your
Title: message-style frustrations (this time in plain text)
Thanks! That helps, but I can't say I like it. I think that Axis
should recognize that you've given it a Document and wrap it in a
SOAPBodyElement by itself if that's what it needs.
In
your cod
Title: message-style frustrations (this time in plain text)
Hi Volkmann,
Regarding the third method
signature (passing document), this is how its works for me...
Service service =
new Service();
Call call = (Call)
service.createCall();
String
Take a look at
http://biryani.med.yale.edu:8081/axis/index.jsp?which=6
there is some code for each service available.
Volkmann, Mark wrote:
message-style frustrations (this time in plain text)
I'm trying to learn how to use message-style services
in Axis.
Title: message-style frustrations (this time in plain text)
I'm trying to learn how to use message-style services in Axis. The documentation says that a message-style service can have any of the following method signatures.
public Element [] method(Element [] bodies);
p
Title: message-style frustrations
I'm trying to learn how to use message-style services in Axis. The documentation says that a message-style service can have any of the following method signatures.
public Element [] method(Element [] bodies);
public SOAPBodyElement [] m
Thanks Sanjay. I'll give this a try.
Steve Pannier
> AFAIK, message style service supports only a single
> operation. Since you are using message style service
> and are willing to deal with raw XML one possible
> solution would be to examine the child element of SOAP
>
--Original Message-
From: Steve Pannier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 5:29 PM
To: [EMAIL PROTECTED]
Subject: Does Message style support only one method per service?
I'm using Message style, and when I have one method defined
everything works OK. But, when I
AFAIK, message style service supports only a single
operation. Since you are using message style service
and are willing to deal with raw XML one possible
solution would be to examine the child element of SOAP
body and do your own dispatching based on it: your
WSDL would define multiple
I'm using Message style, and when I have one method defined
everything works OK. But, when I add another method to my
service, I get the following exception:
Couldnt find an appropriate operation for XML QName {0}
I've searched the mailing list for information regarding this, a
The Axis user guide states that "Message" style services support four valid
signatures. All four appear to map request/response WSDL. Is it possible to use
"Message" style with a one-way operation so that Axis doesn't send SOAP back on the
HTTP response, but just a simple "HTTP 200/202"?
1 - 100 of 183 matches
Mail list logo
