That happens if you put the annotations in the services interface. If you
annotate the services implementation and link your service.xml to that class
the parameter names are resolved how you would expect it. But beware that all
methods of the impementation get exposed by the WSDL. If the implementation
extends some base classes, the inherited methods get exposed too.
> I have a jsr181-annotated service that I use XFire to expose. The
> generated WSDL contains anonymous names for parameters of this service.
> For example, I have one service that looks like this:
>
> **************************
> <xsd:element name="retrieveBooks">
>
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true"
> type="xsd:string"/>
> <xsd:element maxOccurs="1" minOccurs="1" name="in1" type="xsd:int"/>
> <xsd:element maxOccurs="1" minOccurs="1" name="in2" type="xsd:int"/>
> <xsd:element maxOccurs="1" minOccurs="1" name="in3" type="xsd:boolean"/>
> <xsd:element maxOccurs="1" minOccurs="1" name="in4" type="xsd:boolean"/>
> <xsd:element maxOccurs="1" minOccurs="1" name="in5" type="xsd:boolean"/>
> </xsd:sequence>
> ...
> **************************************
>
> Instead of these anonymous "in#" for names, is there a way I can specify
> the name so that the WSDL will generate them appropriately? I was hoping
> it would take the name of the parameter as default. Thanks in advance!
>
> -los
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
