[esb-issues] [JBoss JIRA] Closed: (JBESB-1717) Support additional naming properties in JMS EPRs

[Kevin Conner (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBESB-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Conner closed JBESB-1717.
-------------------------------

    Resolution: Done


Additional properties can now be specified on the provider.

By default the JNDI configuration will inherit all properties which are prefixed with java.naming.  Additional prefixes can be used by defining the jndi-prefixes property on the provider, similar to the following.

<jms-provider name="JMS" connection-factory="ConnectionFactory">
   <property name="jndi-prefixes" value="test.prefix."/>
   <property name="test.prefix.extension1" value="extension1"/>
   ...
</jms-provider>

Committed in revision 21191.


> Support additional naming properties in JMS EPRs
> ------------------------------------------------
>
>                 Key: JBESB-1717
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1717
>             Project: JBoss ESB
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Transports
>    Affects Versions: 4.2.1
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>             Fix For: 4.4
>
>
> Some JNDI providers require the specification of other properties in addition to the normal JNDI properties but, at present, we are restricting their inclusion.
> One example of this is SonicMQ which also requires properties such as com.sonicsw.jndi.mfcontext.domain and com.sonicsw.jndi.mfcontext.idleTimeout.
> We need to extend the JMS EPR so that it can include the specification of additional properties but without including all extensions.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira