cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CXF-1426) If JMS destination / JNDI server is missing, publishing an endpoint doesn't fail, only logs exception
Date Sat, 18 Oct 2008 17:48:44 GMT

     [ https://issues.apache.org/jira/browse/CXF-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Schneider reassigned CXF-1426:
----------------------------------------

    Assignee: Christian Schneider

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


Mime
View raw message