You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2009/10/14 13:53:52 UTC
[jira] Created: (SMXCOMP-650) CXF-SE doesn't put the WSDL in the
endpoint descriptor
CXF-SE doesn't put the WSDL in the endpoint descriptor
------------------------------------------------------
Key: SMXCOMP-650
URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
Project: ServiceMix Components
Issue Type: Bug
Components: servicemix-cxf-se
Affects Versions: servicemix-cxf-se-2009.01
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: servicemix-cxf-se-2009.02
Currently, a CXF-SE endpoint descriptor is null. The component doesn't push the generated WSDL into the endpoint descriptor.
It's a problem when you want to use a HTTP or CXF-BC in front of a CXF-SE endpoint to expose it as a webservice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-650) CXF-SE doesn't put the WSDL in the
endpoint descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54750#action_54750 ]
Jean-Baptiste Onofré commented on SMXCOMP-650:
----------------------------------------------
Thanks for your feedback Freeman.
However, I have tried to expose a CXF-SE endpoint using a CXF-BC and a HTTP endpoint but both provide the same error: I got a NullPointerException when invoking:
// get the target endpoint descriptor
Document targetEndpointDescriptor = componentContext.getEndpointDescriptor(targetEndpoint);
// get the target endpoint definition (based on the descriptor)
Definition targetEndpointDefinition = javax.wsdl.factory.WSDLFactory.newInstance().newWSDLReader().readWSDL(null, targetEndpointDescriptor);
It looks like the targetEndpoint (which is a CXF-SE one) descriptor is null.
In the same way, it seems that whatever I define in my xbean.xml like this:
<cxfse:endpoint service="nanthrax:test" endpoint="test">...</cxfse:endpoint>
the service and endpoint are overrided by the component (putting the annotated service name and the ClassImplPort as endpoint).
> CXF-SE doesn't put the WSDL in the endpoint descriptor
> ------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> Currently, a CXF-SE endpoint descriptor is null. The component doesn't push the generated WSDL into the endpoint descriptor.
> It's a problem when you want to use a HTTP or CXF-BC in front of a CXF-SE endpoint to expose it as a webservice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-650) CXF-SE doesn't put the WSDL in the
endpoint descriptor
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54755#action_54755 ]
Freeman Fang commented on SMXCOMP-650:
--------------------------------------
Hi JB,
Yeah, that's the case.
I'm totally ok with your solution. We may need update the title of this issue now :-)
Freeman
> CXF-SE doesn't put the WSDL in the endpoint descriptor
> ------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> Currently, a CXF-SE endpoint descriptor is null. The component doesn't push the generated WSDL into the endpoint descriptor.
> It's a problem when you want to use a HTTP or CXF-BC in front of a CXF-SE endpoint to expose it as a webservice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SMXCOMP-650) CXF-SE should populate the
endpoint descriptor with the WSDL in the validate() method in place of the
start() method
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMXCOMP-650 started by Jean-Baptiste Onofré.
> CXF-SE should populate the endpoint descriptor with the WSDL in the validate() method in place of the start() method
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> When you package a CXF-SE SU and a CXF-BC or HTTP SU in the same SA, if the CXF-BC or HTTP endpoint target the CXF-SE one, you got a NullPointerException.
> This is due to the fact that the CXF-SE component populates the descriptor with the WSDL in the start() method. So the endpoint descriptor is null (not yet populated) when the CXF-BC or HTTP endpoint tries to access.
> The current workaround is to package the CXF-SE SU and the CXF-BC/HTTP one in two differents SA to force a kind of deployment order.
> A clean solution is that the CXF-SE populates the descriptor WSDL in the validate() method in place of the start() one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-650) CXF-SE doesn't put the WSDL in the
endpoint descriptor
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54752#action_54752 ]
Freeman Fang commented on SMXCOMP-650:
--------------------------------------
Hi JB,
Ensure you put cxf se endpoint and cxf bc/http bc endpoint into different SAs, and you need deploy/start the SA containing cxf se endpoint first.
Freeman
> CXF-SE doesn't put the WSDL in the endpoint descriptor
> ------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> Currently, a CXF-SE endpoint descriptor is null. The component doesn't push the generated WSDL into the endpoint descriptor.
> It's a problem when you want to use a HTTP or CXF-BC in front of a CXF-SE endpoint to expose it as a webservice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-650) CXF-SE doesn't put the WSDL in the
endpoint descriptor
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54749#action_54749 ]
Freeman Fang commented on SMXCOMP-650:
--------------------------------------
Hi JB,
I don't think the cxf se endpoint descriptor is null.
Actually we do have a testcase to guarantee cxf bc endpoint can retrieve the wsdl from the internal cxf se endpoint.
Take a look at [1]
[1]https://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/src/test/java/org/apache/servicemix/cxfbc/CxfBcRetrieveWsdlFromInternalEndpointTest.java
Regards
Freeman
> CXF-SE doesn't put the WSDL in the endpoint descriptor
> ------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> Currently, a CXF-SE endpoint descriptor is null. The component doesn't push the generated WSDL into the endpoint descriptor.
> It's a problem when you want to use a HTTP or CXF-BC in front of a CXF-SE endpoint to expose it as a webservice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-650) CXF-SE should populate the endpoint
descriptor with the WSDL in the validate() method in place of the start()
method
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated SMXCOMP-650:
-----------------------------------------
Description:
When you package a CXF-SE SU and a CXF-BC or HTTP SU in the same SA, if the CXF-BC or HTTP endpoint target the CXF-SE one, you got a NullPointerException.
This is due to the fact that the CXF-SE component populates the descriptor with the WSDL in the start() method. So the endpoint descriptor is null (not yet populated) when the CXF-BC or HTTP endpoint tries to access.
The current workaround is to package the CXF-SE SU and the CXF-BC/HTTP one in two differents SA to force a kind of deployment order.
A clean solution is that the CXF-SE populates the descriptor WSDL in the validate() method in place of the start() one.
was:
Currently, a CXF-SE endpoint descriptor is null. The component doesn't push the generated WSDL into the endpoint descriptor.
It's a problem when you want to use a HTTP or CXF-BC in front of a CXF-SE endpoint to expose it as a webservice.
Issue Type: Improvement (was: Bug)
Summary: CXF-SE should populate the endpoint descriptor with the WSDL in the validate() method in place of the start() method (was: CXF-SE doesn't put the WSDL in the endpoint descriptor)
> CXF-SE should populate the endpoint descriptor with the WSDL in the validate() method in place of the start() method
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> When you package a CXF-SE SU and a CXF-BC or HTTP SU in the same SA, if the CXF-BC or HTTP endpoint target the CXF-SE one, you got a NullPointerException.
> This is due to the fact that the CXF-SE component populates the descriptor with the WSDL in the start() method. So the endpoint descriptor is null (not yet populated) when the CXF-BC or HTTP endpoint tries to access.
> The current workaround is to package the CXF-SE SU and the CXF-BC/HTTP one in two differents SA to force a kind of deployment order.
> A clean solution is that the CXF-SE populates the descriptor WSDL in the validate() method in place of the start() one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMXCOMP-650) CXF-SE should populate the endpoint
descriptor with the WSDL in the validate() method in place of the start()
method
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved SMXCOMP-650.
------------------------------------------
Resolution: Fixed
> CXF-SE should populate the endpoint descriptor with the WSDL in the validate() method in place of the start() method
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> When you package a CXF-SE SU and a CXF-BC or HTTP SU in the same SA, if the CXF-BC or HTTP endpoint target the CXF-SE one, you got a NullPointerException.
> This is due to the fact that the CXF-SE component populates the descriptor with the WSDL in the start() method. So the endpoint descriptor is null (not yet populated) when the CXF-BC or HTTP endpoint tries to access.
> The current workaround is to package the CXF-SE SU and the CXF-BC/HTTP one in two differents SA to force a kind of deployment order.
> A clean solution is that the CXF-SE populates the descriptor WSDL in the validate() method in place of the start() one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-650) CXF-SE should populate the endpoint
descriptor with the WSDL in the validate() method in place of the start()
method
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54756#action_54756 ]
Jean-Baptiste Onofré commented on SMXCOMP-650:
----------------------------------------------
Done, thx Freeman :)
> CXF-SE should populate the endpoint descriptor with the WSDL in the validate() method in place of the start() method
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> When you package a CXF-SE SU and a CXF-BC or HTTP SU in the same SA, if the CXF-BC or HTTP endpoint target the CXF-SE one, you got a NullPointerException.
> This is due to the fact that the CXF-SE component populates the descriptor with the WSDL in the start() method. So the endpoint descriptor is null (not yet populated) when the CXF-BC or HTTP endpoint tries to access.
> The current workaround is to package the CXF-SE SU and the CXF-BC/HTTP one in two differents SA to force a kind of deployment order.
> A clean solution is that the CXF-SE populates the descriptor WSDL in the validate() method in place of the start() one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-650) CXF-SE doesn't put the WSDL in the
endpoint descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54751#action_54751 ]
Jean-Baptiste Onofré commented on SMXCOMP-650:
----------------------------------------------
You can see my test case here:
http://svn.nanthrax.net/cxfse-ns-test/
> CXF-SE doesn't put the WSDL in the endpoint descriptor
> ------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> Currently, a CXF-SE endpoint descriptor is null. The component doesn't push the generated WSDL into the endpoint descriptor.
> It's a problem when you want to use a HTTP or CXF-BC in front of a CXF-SE endpoint to expose it as a webservice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-650) CXF-SE doesn't put the WSDL in the
endpoint descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54753#action_54753 ]
Jean-Baptiste Onofré commented on SMXCOMP-650:
----------------------------------------------
OK Freeman, I try using two SAs.
I guess that the issue is due to the fact that CXF-SE component populate the descriptor with the WSDL in the start() method (and not in the validate() one). So my CXF-BC endpoint tries to access to the descriptor whereas it hasn't yet been populated by the CXF-SE one.
I think it can disturb the users.
Does it make sense to, at least, publish the WSDL in the validate() method and really start the service in the start() method ?
Are you ok if I begin an update in this way ?
> CXF-SE doesn't put the WSDL in the endpoint descriptor
> ------------------------------------------------------
>
> Key: SMXCOMP-650
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-650
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-cxf-se
> Affects Versions: servicemix-cxf-se-2009.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-cxf-se-2009.02
>
>
> Currently, a CXF-SE endpoint descriptor is null. The component doesn't push the generated WSDL into the endpoint descriptor.
> It's a problem when you want to use a HTTP or CXF-BC in front of a CXF-SE endpoint to expose it as a webservice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.