[jira] Commented: (CXF-1426) If JMS destination / JNDI server is missing, publishing an endpoint doesn't fail, only logs exception

["Christian Schneider (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640788#action_12640788 ] 

Christian Schneider commented on CXF-1426:
------------------------------------------

Could you please check out the latest trunk version of cxf and report if the issue still exists?
We have done many refactorings and it is well possible that the issue is solved.


> 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
>            Priority: Minor
>   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.