Re: Message element name and documen tstyle service

2007-02-07 Thread Pedro Silveira Vieira da Silva
style services? Pedro Anne Thomas Manes wrote: I recommend that you edit the generated WSDL and fix the import, and make sure that the invDoc element is properly defined (i.e., not xsd:anyType), then gen your service from the WSDL using wsdl2java. Anne On 2/6/07, Pedro Silveira Vieira da

Message element name and documen tstyle service

2007-02-06 Thread Pedro Silveira Vieira da Silva
I've created a web service that has a simple function that receives a parameter: package pt.gedi.ws; import oasisNamesSpecificationUblSchemaXsdInvoice2.InvoiceDocument; public class ReceiveInvoice { public void receive(InvoiceDocument invDoc) { doSomething(invDoc);

Re: What style fits best?

2007-01-09 Thread Pedro Silveira Vieira da Silva
/rpc/encoded Given that your application works at the XML/DOM level, then you want to stick with "message" style. Anne On 1/8/07, Pedro Silveira Vieira da Silva <[EMAIL PROTECTED]> wrote: Hi, Although it might be strange to be asking this after developing an application with

What style fits best?

2007-01-08 Thread Pedro Silveira Vieira da Silva
Hi, Although it might be strange to be asking this after developing an application with Axis, the truth is that there are some questions still open. I've developed an application that makes use of axis for creating a web service for XML message exchanging. More accurately I have a service t