[
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.
