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

Posted to dev@servicemix.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2008/01/28 04:59:24 UTC

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

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

Chris Custine reassigned SM-1206:
---------------------------------

    Assignee: Chris Custine

> ClientFactory JNDI bind fails in non-standalone ServiceMix installs
> -------------------------------------------------------------------
>
>                 Key: SM-1206
>                 URL: https://issues.apache.org/activemq/browse/SM-1206
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.2.1, 3.3
>            Reporter: Chris Custine
>            Assignee: Chris Custine
>
> 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.
-
You can reply to this email to add a comment to the issue online.