You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jesse McLaughlin (JIRA)" <ji...@apache.org> on 2008/03/06 10:36:57 UTC

[jira] Created: (CXF-1465) WSDL2Java error when using binding customization

WSDL2Java error when using <jaxb:serializable/> binding customization
---------------------------------------------------------------------

                 Key: CXF-1465
                 URL: https://issues.apache.org/jira/browse/CXF-1465
             Project: CXF
          Issue Type: Bug
    Affects Versions: 2.0.4
         Environment: JDK5, OS X, Eclipse/Ant
            Reporter: Jesse McLaughlin


WSDL2Java fails with a runtime exception when generating a JAXB client.  To reproduce this error, do the following:

1. Create a WSDL that uses an <import> to import its types from a separate XSD file (ie. as opposed to in-lining them in the WSDL itself).
2. Put the WSDL and XSD files somewhere in the filesystem under a directory with a name containing a space character.
3. Create a binding customization file that uses the <jaxb:serializable/> customization to cause all generated Java types to implement java.io.Serializable.
4. Invoke WSDL2Java to generate the client for the WSDL, passing the binding customization file via the -b option.

An error will be generated.  In this scenario, either leaving out the binding file or removing the space from the directory name will cause everything to work as expected.  The issue only occurs when both of these conditions are present.

Please refer to the following user-list thread for a complete discussion and some example data:

  http://www.nabble.com/WSDL2Java-error-when-using-%3Cjaxb%3Aserializable-%3E-binding-customization-to15786637.html



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CXF-1465) WSDL2Java error when using binding customization

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-1465.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.5

> WSDL2Java error when using <jaxb:serializable/> binding customization
> ---------------------------------------------------------------------
>
>                 Key: CXF-1465
>                 URL: https://issues.apache.org/jira/browse/CXF-1465
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.0.4
>         Environment: JDK5, OS X, Eclipse/Ant
>            Reporter: Jesse McLaughlin
>             Fix For: 2.0.5
>
>
> WSDL2Java fails with a runtime exception when generating a JAXB client.  To reproduce this error, do the following:
> 1. Create a WSDL that uses an <import> to import its types from a separate XSD file (ie. as opposed to in-lining them in the WSDL itself).
> 2. Put the WSDL and XSD files somewhere in the filesystem under a directory with a name containing a space character.
> 3. Create a binding customization file that uses the <jaxb:serializable/> customization to cause all generated Java types to implement java.io.Serializable.
> 4. Invoke WSDL2Java to generate the client for the WSDL, passing the binding customization file via the -b option.
> An error will be generated.  In this scenario, either leaving out the binding file or removing the space from the directory name will cause everything to work as expected.  The issue only occurs when both of these conditions are present.
> Please refer to the following user-list thread for a complete discussion and some example data:
>   http://www.nabble.com/WSDL2Java-error-when-using-%3Cjaxb%3Aserializable-%3E-binding-customization-to15786637.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.