[SMXCOMP-650] CXF-SE should populate the endpoint descriptor with the WSDL in the validate() method in place of the start() method

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: servicemix-cxf-se-2009.01
• Fix Version/s: servicemix-cxf-se-2009.02
• Component/s: servicemix-cxf-se
• Assignee: Jean-Baptiste Onofré
• Reporter: Jean-Baptiste Onofré
• Created: 14/Oct/09 11:51
• Updated: 24/Oct/09 13:55
• Resolved: 24/Oct/09 13:55

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.