AW: [JBoss-user] WSDL Part names within messages.

[Jung , Dr. Christoph]

Title: Nachricht

Mark,

 

Axis has several ways of annotating such meta-data to be used by the WSDL Emitter (which uses reflection and builtin naming rules

to build its default meta-data thats why the parameter names are so ugly).

 

First the deployment descriptor itself, but in this case it does not leave you much options except giving a service name.

 

You could also subclass the provider implementation (EJBProvider in this case) for preparing the WSDL emitter with

additional information, .e.g, doing the reflection via a different bytecode analyzer, such as BCEL or xjavadoc or ...

 

What Ive also seen is the possibilty for some target beans (Im not sure for EJBProvider, but you should look in the Axis docu) to

implement a static method that will return the already prepared meta-data to the emitter. 

 

CGJ

 

-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 24. Juni 2003 13:51
An: [EMAIL PROTECTED]
Betreff: [JBoss-user] WSDL Part names within messages.

Hi folks,

           I'm exposing a few session beans as web services. In the generated WSDL the part names are given automatic names i.e. in0,in1 etc. I was wondering if there was anyway to be able to set these to the argument name presented in the session bean?

 

i.e. I have a bean called FPGbean which has the following method signature

public double orderFPGTest(String mrn){

    :

    :

}

 

The wsdl for this is described as

 

- <wsdl:message name="orderFPGTestResponse">

  <wsdl:part name="orderFPGTestReturn" type="xsd:double" />

  </wsdl:message>

- <wsdl:message name="orderFPGTestRequest">

  <wsdl:part name="in0" type="xsd:string" />

  </wsdl:message>

and as you can see the part name attribute for the Request is in0.

I'm hoping eventually to use a UDDIBrowser and some sort of DragNDrop functionality into an open source UML

suite from which I will generate clients. I don't exactly need the names I suppose it would just mean I wouldn't have to worry about the parameters being in order as I added them to the call.

 

Thanks,

Mark.

###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/