Noooooooobeeeee requires some help

Dear All I wondered whether someone could lead me to a good tuturial or some decent code. I'm trying to write some web services using the eclipse platform and wtp tools. I need the client web service to create a SOAP header - from my server-side web service, when i create the methods and the w

sessionID outHeader WSDD

I also have run into a problem using sessionID in soap header. I want the sessionID to be in the soap:header not in the soap:body. My WSDD looks like that: ... The answer of a Request looks like this: http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="0" href="#id0"/> ..

OT: Glue

Hi   I’m taking up my interest for Axis/Glue/XX – doing WebService development in Java, that is. I know this is a Axis forum, but I was looking at Clue – does any one know what the price-tag on Clue is – 1 developer – approx.?   Best regards Jan  

Re: wrapped vs. document

Because there is no such style as "wrapped" in WSDL. The only permitted styles in WSDL are "rpc" and "document". Axis WSDD style="wrapped" produces WSDL style="document". ("wrapped" is a programming style rather than a service style -- it presents a programming interface comparable to "rpc" style,

Re: OT: Glue

I assume you mean webMethods Glue? You have to ask webMethods for pricing. I have to warn you -- webMethods isn't particularly interested in selling you a single developer license. At a minimum, they will sell you a Glue server runtime license, but they want to sell you all of Fabric. You can dow

invoke methods wsdl file

Hello I've got to develop a web service client, but don't know where to start I have the external wsdl file which exposes the methods i wish to invoke. Is it something like this public static void main(String args[]) { URL url = new URL("http://thirdpartycallservice/third_party_calling_service.wsd

second parameter is null when using wsdl with wsdlsoap:binding style="document"

Hi, in a futher message I read about a similar problem and it's solution. posted solution: change wsdlsoap:binding style="document" to wsdlsoap:binding style="rpc" But the solution posted there is not applicable to me. My little webservice has to be used in a IIS from MS. And the developer suit

Re: invoke methods wsdl file

Hi there! You could let ANT (using the axis-tasks) generate the necessary stub files. In my opinion that is a much cleaner approach. Then you simply call the service as if it were a local object: // the locator is generated by axis/ant... someLocator locator = new someLocator(); // ...the servic

Does this make sense

I'm trying to do the following. Can someone tell me whether it is OK/possible doing it this way Is there a better way of doing it I'm writing server-side web services, exposing methods to clients (these can be anything). I need to create a custom soap header. Would it be best for the client

Re: client default constructor ?

maybe it coul be useful for somebody someday : Don't add empty constructor, just check two things : - On the server side, the wsdd file must define the proper serializer/deseralizer when mapping your Enum type : http://myUrl/myService""; qname="ns:EnumerationConfType" type="java:org.MyEnum

Overloaded methods and Wrapped literal

Hi, I use axis 1.1. When I used RPC style, java2wsdl and wsdl2java produced good proxies for classes with overloaded methods. However, they fail to produce good proxies when WRAPPED Style is used. While I know web services do not support overloaded methods, is there an option for ensuring that

FW: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.

  From: Cid, Jose Sent: Monday, May 02, 2005 5:24 PMTo: 'axis-user@ws.apache.org'Subject: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. Can anyone shed some light as to what may be going on here. I am use axis 1.2RC3. Mul

Re: second parameter is null when using wsdl with wsdlsoap:binding style="document"

When using document style, you don't specify "parameters" in the definition. Instead you have one message , and that part points to a wrapped element. The wrapper element should be defined as a sequence of elements -- which are your parameters. If you want to create a parameterized interface, the

ANNOUNCE : Axis 1.2 RELEASE

Hi folks: After *much* too long, the Axis team would like to announce the release of Axis 1.2 final. You can get it at: http://www.apache.org/dyn/closer.cgi/ws/axis/1_2/ (if your favorite mirror doesn't have it yet try another, it's propagating now) A few words about this release - * A LOT of