[
https://issues.apache.org/jira/browse/CXF-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645625#action_12645625
]
Christian Schneider commented on CXF-1426:
------------------------------------------
The current implementation will throw an exception if the connectionfactory can
not be found in jndi or if the jndi connection fails.
If the targetDestination can not be resolved an exception will be thrown in the
activate method of JMSDestination. So I think we can close this issue.
I will keep the issue open some days and if there are no objections I will
close it.
> If JMS destination / JNDI server is missing, publishing an endpoint doesn't
> fail, only logs exception
> -----------------------------------------------------------------------------------------------------
>
> Key: CXF-1426
> URL: https://issues.apache.org/jira/browse/CXF-1426
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0.4
> Environment: ActiveMQ 5
> Reporter: Mayank Thakore
> Assignee: Christian Schneider
> Priority: Minor
> Fix For: 2.0.9, 2.1.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When publishing a service on the JMS transport, if the jndi server cannot be
> found, or the named destination is missing, CXF will only log the exception.
> It will not throw. Hence, it is not possible to know that the service
> creation failed.
> Endpoint impl = Endpoint.publish(url, object);
> if ((impl != null) && impl.isPublished()) {
> // success
> }
> The above code will go to success case even in failure conditions mentioned
> above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
