You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@servicemix.apache.org by "Lars Heinemann (JIRA)" <ji...@apache.org> on 2011/04/19 20:35:06 UTC

[jira] [Resolved] (SM-1206) ClientFactory JNDI bind fails in non-standalone ServiceMix installs

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

Lars Heinemann resolved SM-1206.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 3.4

fixed

> ClientFactory JNDI bind fails in non-standalone ServiceMix installs
> -------------------------------------------------------------------
>
>                 Key: SM-1206
>                 URL: https://issues.apache.org/jira/browse/SM-1206
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.2.1, 3.3
>            Reporter: Chris Custine
>            Assignee: Lars Heinemann
>             Fix For: 3.4
>
>
> ClientFactory tries to bind to java:comp/env/jbi/ClientFactory by default and this only appears to work when run as a standalone server.  The java:comp/env naming context is read only according to the JEE spec so the ClientFactory can never bind to JNDI when deployed with JBoss deployer, WAR file, etc.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira