You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by gdprao <gd...@yahoo.com> on 2007/10/20 02:38:45 UTC
CXF JAXWS hiding JAXB binding language
Hi,
I have a CXF-2.0.2 web service. The schema location is external. I
generate JAXB mappings out of Schema first and then configured my services
with JAXWS annotations on POJO. I have JAXB binding language to customize my
schema properites as follows:
<xs:element name="id" type="xs:int">
<xs:annotation>
<xs:appinfo>
<jaxb:property>
<jaxb:baseType>
<jaxb:javaType name="int"
parseMethod="javax.xml.bind.DatatypeConverter.parseInt"
printMethod="javax.xml.bind.DatatypeConverter.printInt" />
</jaxb:baseType>
</jaxb:property>
</xs:appinfo>
</xs:annotation>
</xs:element>
My service configuration:
<!-- SOAP End point configuration -->
<jaxws:endpoint id="myServiceSoapEndPoint"
implementor="#myWebService" address="/ServiceSoap">
<jaxws:schemaLocations>
<jaxws:schemaLocation>
classpath:com/mydomain/schemas/myServiceSchema.xsd
</jaxws:schemaLocation>
</jaxws:schemaLocations>
</jaxws:endpoint>
But the WSDL generated by CXF is hiding this information. It is just showing
up empty <xs:annotation/> element. Because of this, the clients which
generate mappings from the exposed WSDL needs to define their mappings
externally which does not look nice. Is there a solution to this problem?
Thanks,
Durga
--
View this message in context: http://www.nabble.com/CXF-JAXWS-hiding-JAXB-binding-language-tf4656450.html#a13305418
Sent from the cxf-user mailing list archive at Nabble.com.