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

["steve almeida (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60906#action_60906 ] 

steve almeida commented on SM-1206:
-----------------------------------

i had faced the same issue in jboss as a work around . the following steps were followed 


1) create a jndi propertries  and add this to the conatiner 

example : <sm:container id="jbi" embedded="true" useMBeanServer="false"
		createMBeanServer="false" autoEnlistInTransaction="true"
		monitorDeploymentDirectory="true" monitorInstallationDirectory="true"
		monitorInterval="5" persistent="false"  createJmxConnector="false" namingContext="#namingContext" >
	</sm:container>
	<util:map id="envproperties" map-class="java.util.Properties">
		<entry key="java.naming.factory.initial" value="${INITIAL_CONTEXT_FACTORY}" />
		<entry key="java.naming.provider.url" value="${PROVIDER_URL}" />		 
		<entry key="java.naming.factory.url.pkgs" value="${URL_PKG_PREFIXES}" />
		<entry key="java.naming.security.credentials" value="${SECURITY_CREDENTIALS}" />
		<entry key="java.naming.security.principal" value="${SECURITY_PRINCIPAL}" />
	</util:map>

	<bean id="namingContext" class="javax.naming.InitialContext">
		<constructor-arg index="0" type="" ref="envproperties" />
	</bean>

2) create a duplicate ClientFactory.java with the same package and edit the private String jndiName = "java:JbiClientFactory"; or write some logic to retrive from file or system.properties 

3) in the jndiview 
the following will be displayed under Global JNDI Namespace

+- JbiClientFactory (class: org.apache.servicemix.jbi.framework.ClientFactory)
 

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