cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jimma (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-1094) Tooling binding file wsdllcaotion and schemaLocation improvement
Date Thu, 18 Oct 2007 02:17:51 GMT

     [ https://issues.apache.org/jira/browse/CXF-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

jimma resolved CXF-1094.
------------------------

    Resolution: Fixed
      Assignee: jimma

> 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
>            Assignee: 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.


Mime
View raw message