Just to add to this topic my 2 fold question:
1) why is it that a function or variable specified to be of type
EndpointReference always ends up being declared as an Element (I believe
that this wasn't the case a long time ago). When defined in the wsdl as:
<xsd:element name="epr" type="wsa:EndpointReference"
maxOccurs="unbounded"/>
The same is true for this definition as well:
<xsd:element ref="wsa:EndpointReference" maxOccurs="unbounded"/>
2) Given the definition below, shouldn't I be able to get a function
declared that returns a list of EndpointReferences (or Elements given
the current implementation)?
<xsd:element name="ListResourcesOperation" />
<xsd:element
name="ListResourcesOperationResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="epr"
type="wsa:EndpointReference" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
I'm just slightly confused.
/Lenni
-----Original Message-----
From: Daniel Jemiolo [mailto:[EMAIL PROTECTED]
Sent: 16 April 2007 18:27
To: [email protected]
Subject: Re: Generating a capability that accepts a byte[] as parameter
I think the problem is that the collection of built-in serializers
doesn't
include support for byte/byte[]. I'm going to add this so that you can
make parameters like this:
<xsd:element name="MyParam" type="xsd:byte"
maxOccurs="unbounded"/>
and get a byte[] parameter (or return type). This change will show up in
tonight's nightly build.
Dan
"Manolo Gomez Lopez" <[EMAIL PROTECTED]> wrote on 04/16/2007
08:00:41
AM:
> Hi,
>
> I have a WSDL with the following definition of an operation (I'm
pasting
> only the relevant parts):
>
> <xsd:element name="TransformRequest">
> <xsd:annotation>
> <xsd:documentation>Solicitud de
> transformacion</xsd:documentation>
> </xsd:annotation>
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="documentToTransform"
> type="xsd:integer">
> <xsd:annotation>
> <xsd:documentation>Documento a
> transformar</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
>
>
> <wsdl:message name="TransformRequest">
> <wsdl:part name="TransformRequest"
element="tns:TransformRequest"/>
> </wsdl:message>
>
> <wsdl:operation name="Transform">
> <wsdl:input wsa:Action="
> http://test.net/testing/services/TransformationService/Transform";
> name="TransformRequest" message="tns:TransformRequest"/>
> <wsdl:output wsa:Action="
>
http://test.net/testing/services/TransformationService/TransformResponse
"
> name="TransformResponse" message="tns:TransformResponse"/>
> <wsdl:fault name="TransformFailedFault"
> message="tns:TransformFailedFault"/>
> <wsdl:fault name="ResourceUnknownFault"
> message="tns:ResourceUnknownFault"/>
> <wsdl:fault name="ResourceUnavailableFault"
> message="tns:ResourceUnavailableFault"/>
> </wsdl:operation>
>
>
> I want this WSDL to represent an operation named void Transform
(byte[])
> using base64 as the mechanism for encoding binary data. When I execute
> wsdl2java for generating the server part of the service, it generates
the
> following code:
>
> public void transform(Element documentToTransform) throws
Exception
{
> //TODO implement transform
> throw new RuntimeException("Unimplemented Method: transform");
> }
>
>
> I want Apache Muse to generate a prototype like this: public void
> transform(byte[] documentToTransform) throws Exception or anything
that
> treats the received base64 as an array of bytes. Somewhere in the
> documentation it is said that Apache Muse uses Element as a
rerpresentation
> of a parameter when the element has AnyType or void types...
>
> Does anybody knows how to get a service that has an capability that
gets
a
> byte[] as parameter?
>
> Greets,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
