[
https://issues.apache.org/jira/browse/CXF-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535199
]
jimma commented on CXF-1094:
----------------------------
It seems the xpath "xsd:element" does not work in Jaxb 2.0 . I changed it to
"//xsd:element" and it is working for both JAXB2.0 and JAXB2.1
> Tooling binding file wsdllcaotion and schemaLocation improvement
> ----------------------------------------------------------------
>
> Key: CXF-1094
> URL: https://issues.apache.org/jira/browse/CXF-1094
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Affects Versions: 2.0.2
> Reporter: jimma
> Fix For: 2.0.3
>
>
> In each external binding file, I must specify a 'schemaLocation' or
> 'wsdlLocation', even though this information was already supplied to
> wsdl2java from the command line. This is frustrating, because it means I
> cannot re-use my bindings files: Instead I must create a separate JAXB
> customization file for each XSD file, and a separate JAXWS customization file
> for each WSDL file, even if the customizations are exactly the same each
> time! Can wsdl2java not inject this information into the JAXB/JAXWS
> customization code at runtime, either as a parameter or a property? Doing
> this would greatly reduce the number of files required for JAXB/JAXWS
> customizations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
