RE: java:MSG vs. document binding style

This is the WSDL for MessageService generated on my Websphere Application developer Test env. I don't know why are we getting different result. Either way it seems to have problem. Can someone from AXIS explain this a little? By the way, can someone tell me what exactly is the xsd:anyType telling

Re: Sending arbitrary XML document

Sen, Puny wrote: What would be the best strategy for sending an arbitrary XML document as a parameter using Axis? Convert the string to an array of bytes, then send it. It is base64 encoded, so it will be sent fine.

RE: java:MSG vs. document binding style

Welcome to the confusion club! Also, notice that a document style WSDL will also have encoding specified..is that a bug too? I am posting a so-called document style WSDL generated (which .NET fails to parse; complaining about the encoding present in the WSDL) - http://localhost:8080/axis/servic

Re: What is wsdl2java for?

Thank u for the response. I am not familiar with the underlying implementation of AXIS. Even JAX-RPC is its fundation, all that should really be transparent to the web services developers. Looking at the samples, some of them doesn't the stub and skeleton stuff, just and client and a service, handl

(newbie) Axis and JMS

Hi all. Maybe this is a stupid question but I need to invoke to various web service who can response in diferent time, but i can't wait all the time the web service could spend. I have to set a timeout limit. Exploring axis, I take care of call.setTimeout method. I test it, and when the timeo

Sending arbitrary XML document

Hi all, What would be the best strategy for sending an arbitrary XML document as a parameter using Axis? Using document/literal, and a sequence, generates a MessageElement[] array, but I haven't been able to test because the generated WSDL has errors (see previous post). Another option seems to

Non Well-Formed WSDL document

Hi, After deploying, the generated WSDL has errors like the one shown below. I'm using Axis 1.0. Is this a known bug? Also, is it possible to deploy with a static hand-coded WSDL (ie. not automatically generate one)? Thanks, Puny

Re: What is wsdl2java for?

- Original Message - From: "alanz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, October 27, 2002 09:02 Subject: What is wsdl2java for? > It seems to me WSDL2Java should generate the > testclient and the service classes for the web service > described in the WSDL. it does ju

REPOST - Problem with multi-dimensional array

Could someone at least tell me whether multi-dimensional arrays are meant to work in 1.0?  The only reason I am assuming they should is because of the claim on the website that "Axis ... has passed Sun's JAX-RPC and SAAJ compliance tests", and the JAX-RPC specification covers multi-dimension

signature mismatch problem

I'm using axis-1.0 (server side) and MS SOAP Toolkit 3.0 (client side) to send a dime attachment. Starting from the attached WSDL, a call from MSSOAP Toolkit to axis raise the following error: -- Tried to invoke method public java.lang.String org.tempuri.Service1SoapBImpl.sendMail(byte[]) th

java:MSG vs. document binding style

In the user guide it seems indicates java:MSG mapping to the document binding style defined in the WSDL. I am looking at the sample MessgeService. In the WSDD the style is java:MSG. However after deployed to AXIS v1.0, the ?wsdl url showed the binding style is rpc instead of document. Also the WSD

What is wsdl2java for?

It seems to me WSDL2Java should generate the testclient and the service classes for the web service described in the WSDL. But instead, wsdl2java generates a bunch of RMI like stubs and skeletons and interfaces. I guess this effort is for the JAX-RPC support? For people doing Web Services this see

SV: Does Axis include a lightweight standalone server?

Return Receipt Your SV: Does Axis include a lightweight standalone server? document :

SV: Does Axis include a lightweight standalone server?

Hi all, My I add some additional questions to this thread. 1) As I understand it, SimpleAxisServer must be feeded with a deploy.wsdd file using the AdminClient, before it can serve a service. Is it possible to use a server-config.wsdd file instead, to make it more shrink-wrapped? If it's