You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Los Morales (JIRA)" <ji...@apache.org> on 2006/11/20 16:33:02 UTC
[jira] Created: (SM-749) JSR181 component does not generate WSDL
types for JAXB2-annotated classes
JSR181 component does not generate WSDL types for JAXB2-annotated classes
-------------------------------------------------------------------------
Key: SM-749
URL: https://issues.apache.org/activemq/browse/SM-749
Project: ServiceMix
Issue Type: Bug
Components: servicemix-jsr181
Affects Versions: 3.0.1
Environment: JSE 6 RC, Win XP
Reporter: Los Morales
Fix For: incubation
JSR181 component fails to unmarshal data from an XML document into JAXB2-annotated objects because the WSDL for types does not get properly generated. Similar to an already existing issue: (https://brutus.apache.org/activemq/browse/SM-739), the bug(s) seem to occur only when the POJOs have JAXB2 annotations. Removing these annotations seem to produce the proper WSDL (with all the respective types) when the JSR181 component is deployed (using JConsole), although the unmarshaling still does not work due to the missing annotations. The complete thread regarding this issue can be found here: http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-749) JSR181 component does not generate WSDL
types for JAXB2-annotated classes
Posted by "Anders Hammar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-749?page=comments#action_37530 ]
Anders Hammar commented on SM-749:
----------------------------------
I've uploaded code to reproduce the issue discussed.
> JSR181 component does not generate WSDL types for JAXB2-annotated classes
> -------------------------------------------------------------------------
>
> Key: SM-749
> URL: https://issues.apache.org/activemq/browse/SM-749
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
> Affects Versions: 3.0.1
> Environment: JSE 6 RC, Win XP
> Reporter: Los Morales
> Fix For: incubation
>
> Attachments: jira_sm749 reproduce.zip
>
>
> JSR181 component fails to unmarshal data from an XML document into JAXB2-annotated objects because the WSDL for types does not get properly generated. Similar to an already existing issue: (https://brutus.apache.org/activemq/browse/SM-739), the bug(s) seem to occur only when the POJOs have JAXB2 annotations. Removing these annotations seem to produce the proper WSDL (with all the respective types) when the JSR181 component is deployed (using JConsole), although the unmarshaling still does not work due to the missing annotations. The complete thread regarding this issue can be found here: http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-749) JSR181 component does not generate WSDL
types for JAXB2-annotated classes
Posted by "Anders Hammar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38453 ]
Anders Hammar commented on SM-749:
----------------------------------
Just a quick comment that I did get this to work (smx 3.0.1 + some extra patches from pre-3.1) even though the generated wsdl is not complete. One of the things that did the trick was having the jaxb.index file in every package that contains jaxb2 annotated classes.
> JSR181 component does not generate WSDL types for JAXB2-annotated classes
> -------------------------------------------------------------------------
>
> Key: SM-749
> URL: https://issues.apache.org/activemq/browse/SM-749
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
> Affects Versions: 3.0.1
> Environment: JSE 6 RC, Win XP
> Reporter: Los Morales
> Attachments: jira_sm749 reproduce.zip
>
>
> JSR181 component fails to unmarshal data from an XML document into JAXB2-annotated objects because the WSDL for types does not get properly generated. Similar to an already existing issue: (https://brutus.apache.org/activemq/browse/SM-739), the bug(s) seem to occur only when the POJOs have JAXB2 annotations. Removing these annotations seem to produce the proper WSDL (with all the respective types) when the JSR181 component is deployed (using JConsole), although the unmarshaling still does not work due to the missing annotations. The complete thread regarding this issue can be found here: http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-749) JSR181 component does not generate WSDL
types for JAXB2-annotated classes
Posted by "Anders Hammar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-749?page=comments#action_37572 ]
Anders Hammar commented on SM-749:
----------------------------------
OK, looks like this problem is related to a bug in XFire. This is reported in this XFire JIRA:
http://jira.codehaus.org/browse/XFIRE-739
Please vote for it to be fixed! :-)
> JSR181 component does not generate WSDL types for JAXB2-annotated classes
> -------------------------------------------------------------------------
>
> Key: SM-749
> URL: https://issues.apache.org/activemq/browse/SM-749
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
> Affects Versions: 3.0.1
> Environment: JSE 6 RC, Win XP
> Reporter: Los Morales
> Fix For: incubation
>
> Attachments: jira_sm749 reproduce.zip
>
>
> JSR181 component fails to unmarshal data from an XML document into JAXB2-annotated objects because the WSDL for types does not get properly generated. Similar to an already existing issue: (https://brutus.apache.org/activemq/browse/SM-739), the bug(s) seem to occur only when the POJOs have JAXB2 annotations. Removing these annotations seem to produce the proper WSDL (with all the respective types) when the JSR181 component is deployed (using JConsole), although the unmarshaling still does not work due to the missing annotations. The complete thread regarding this issue can be found here: http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-749) JSR181 component does not generate WSDL
types for JAXB2-annotated classes
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-749?page=all ]
Guillaume Nodet updated SM-749:
-------------------------------
Fix Version/s: (was: incubation)
> JSR181 component does not generate WSDL types for JAXB2-annotated classes
> -------------------------------------------------------------------------
>
> Key: SM-749
> URL: https://issues.apache.org/activemq/browse/SM-749
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
> Affects Versions: 3.0.1
> Environment: JSE 6 RC, Win XP
> Reporter: Los Morales
> Attachments: jira_sm749 reproduce.zip
>
>
> JSR181 component fails to unmarshal data from an XML document into JAXB2-annotated objects because the WSDL for types does not get properly generated. Similar to an already existing issue: (https://brutus.apache.org/activemq/browse/SM-739), the bug(s) seem to occur only when the POJOs have JAXB2 annotations. Removing these annotations seem to produce the proper WSDL (with all the respective types) when the JSR181 component is deployed (using JConsole), although the unmarshaling still does not work due to the missing annotations. The complete thread regarding this issue can be found here: http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-749) JSR181 component does not generate WSDL
types for JAXB2-annotated classes
Posted by "Anders Hammar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-749?page=all ]
Anders Hammar updated SM-749:
-----------------------------
Attachment: jira_sm749 reproduce.zip
Code to reproduce the reported issue.
> JSR181 component does not generate WSDL types for JAXB2-annotated classes
> -------------------------------------------------------------------------
>
> Key: SM-749
> URL: https://issues.apache.org/activemq/browse/SM-749
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
> Affects Versions: 3.0.1
> Environment: JSE 6 RC, Win XP
> Reporter: Los Morales
> Fix For: incubation
>
> Attachments: jira_sm749 reproduce.zip
>
>
> JSR181 component fails to unmarshal data from an XML document into JAXB2-annotated objects because the WSDL for types does not get properly generated. Similar to an already existing issue: (https://brutus.apache.org/activemq/browse/SM-739), the bug(s) seem to occur only when the POJOs have JAXB2 annotations. Removing these annotations seem to produce the proper WSDL (with all the respective types) when the JSR181 component is deployed (using JConsole), although the unmarshaling still does not work due to the missing annotations. The complete thread regarding this issue can be found here: http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-749) JSR181 component does not generate WSDL
types for JAXB2-annotated classes
Posted by "Anders Hammar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-749?page=comments#action_37571 ]
Anders Hammar commented on SM-749:
----------------------------------
Possibly this could be due to an XFire bug as I get the same problem when creating the wsdl through plain XFire. However, it would be great if someone else could look into this and verify as the problem could be that I'm doing something wrong.
> JSR181 component does not generate WSDL types for JAXB2-annotated classes
> -------------------------------------------------------------------------
>
> Key: SM-749
> URL: https://issues.apache.org/activemq/browse/SM-749
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
> Affects Versions: 3.0.1
> Environment: JSE 6 RC, Win XP
> Reporter: Los Morales
> Fix For: incubation
>
> Attachments: jira_sm749 reproduce.zip
>
>
> JSR181 component fails to unmarshal data from an XML document into JAXB2-annotated objects because the WSDL for types does not get properly generated. Similar to an already existing issue: (https://brutus.apache.org/activemq/browse/SM-739), the bug(s) seem to occur only when the POJOs have JAXB2 annotations. Removing these annotations seem to produce the proper WSDL (with all the respective types) when the JSR181 component is deployed (using JConsole), although the unmarshaling still does not work due to the missing annotations. The complete thread regarding this issue can be found here: http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira