Has anyone made any progress on this? I have been fighting this same issue
for two days now.. I can not get the xfire services to produce the same WSDL
as the original input WSDL. We're starting from a WSDL that our UI guys
(.Net and Flex) hand craft... Then we create the Java based Web Services..
I too have tried a variety of annotations and service factories. I would
really like to keep the Pojo's to JSR181 annotations and not use the xfire
specific ones (if possible.. :-) )
I'll post whatever is needed.. I just didn't want to randomly post
everything so let me know what might be useful.
I am using MyEclipse based xfire tooling.. It looks like it's using XFire
1.2.2.
Snippet of Original WSDL:
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema";
targetNamespace="urn:services-foo-com:aaa" elementFormDefault="qualified"
attributeFormDefault="qualified">
<xsd:element name="AuthenticateInput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Name"
type="xsd:string"/>
<xsd:element name="Password"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="AuthenticateOutput">
<xsd:complexType>
<xsd:sequence>
<xsd:element
name="IsAuthenticated" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
Generated WSDL from Services:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://aaa.services.foo.com";>
<xsd:complexType name="AuthenticateInput">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="password" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="AuthenticateOutput"/>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="urn:services-foo-com:aaa">
<xsd:element name="AuthenticateInput" type="ns1:AuthenticateInput"/>
<xsd:element name="AuthenticateOutput" type="ns1:AuthenticateOutput"/>
</xsd:schema>
</wsdl:types>
Gary
cmathrusse wrote:
>
> I pursued your recommendation and found that the namespace of the WebParam
> elements was indeed incorrect in the wsdl generated by the service. Even
> though
> the WebParam annotations were correct. I started looking closely as to the
> cause
> of this and found that is was the service factory that seems to be causing
> the
> inconsistency. Originally I had defined the serviceFactory as jsr181. Of
> course
> this services produced an incorrect wsdl.
>
> So I changed my serviceFactory to
> org.codehaus.xfire.jaxws.JAXWSServiceFactory.
> This one produced a more accurate representation of the wsdl, however the
> wsdl
> was missing the schema definitions for the passed in WebParams.
>
> I then tried the serviceFactory of
> org.codehaus.xfire.jaxb2.JaxbServiceFactory.
> This one produced a wsdl similar to the JAXWSServiceFactory with minor
> differences, but still was missing the schema definitions for the
> WebParams.
>
> So what am I missing here? Why are the schema data types not being
> generated?
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
--
View this message in context:
http://www.nabble.com/Inbound-parameter-contains-no-data-tf3183855.html#a9763642
Sent from the XFire - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
