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