You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "jimma (JIRA)" <ji...@apache.org> on 2007/10/09 05:22:50 UTC
[jira] Created: (CXF-1094) Tooling binding file wsdllcaotion and
schemaLocation improvement
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.
[jira] Resolved: (CXF-1094) Tooling binding file wsdllcaotion and
schemaLocation improvement
Posted by "jimma (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CXF-1094) Tooling binding file wsdllcaotion and
schemaLocation improvement
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534125 ]
Daniel Kulp commented on CXF-1094:
----------------------------------
Jim,
This seems to be working fine on trunk. However, I pulled it into 2.0.x and it the test fails. The xpath isn't finding any nodes. Is this something that will only work with JAXB 2.1? If so, we'll have to change the "fix version" to 2.1.
If you could take a look at it on the 2.0.3 branch, that would be great.
Thanks!
Dan
> 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.
[jira] Commented: (CXF-1094) Tooling binding file wsdllcaotion and
schemaLocation improvement
Posted by "jimma (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CXF-1094) Tooling binding file wsdllcaotion and
schemaLocation improvement
Posted by "jimma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534727 ]
jimma commented on CXF-1094:
----------------------------
Hi Dan ,
I built 2.0.x branch on windows with jdk1.5.06 and jdk1.5.13 , linux with jdk1.5.06 , I did not see this failure. Which platform and jdk version did you use ? The code for this fix is not related JAXB , so it should be
working for JAXB2.
> 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.