You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2007/04/16 12:32:34 UTC

[jira] Created: (SM-935) Allow to specify additional JNDI properties

Allow to specify additional JNDI properties
-------------------------------------------

                 Key: SM-935
                 URL: https://issues.apache.org/activemq/browse/SM-935
             Project: ServiceMix
          Issue Type: New Feature
          Components: servicemix-jms
    Affects Versions: 3.1
            Reporter: Gert Vanthienen
            Priority: Minor


In addition to using initialContext and jndiProviderUrl to configure a JMS endpoint, it should be possible to specify additional JNDI properties (e.g {{java.naming.security.principal}}, {{java.naming.security.credentials}})



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-935) Allow to specify additional JNDI properties

Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gert Vanthienen updated SM-935:
-------------------------------

    Attachment: SM-935.patch

Phiroze,

The attached patch should enable you to specify jndiProperties="..." on the <jms:endpoint/>.  Can you help me try it out before I commit it?

Gert

> Allow to specify additional JNDI properties
> -------------------------------------------
>
>                 Key: SM-935
>                 URL: https://issues.apache.org/activemq/browse/SM-935
>             Project: ServiceMix
>          Issue Type: New Feature
>          Components: servicemix-jms
>    Affects Versions: 3.1
>            Reporter: Gert Vanthienen
>            Priority: Minor
>         Attachments: SM-935.patch
>
>
> In addition to using initialContext and jndiProviderUrl to configure a JMS endpoint, it should be possible to specify additional JNDI properties (e.g {{java.naming.security.principal}}, {{java.naming.security.credentials}})

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SM-935) Allow to specify additional JNDI properties

Posted by "Phiroze Dastoor (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/SM-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39637 ] 

Phiroze Dastoor commented on SM-935:
------------------------------------

Please will someone tell me if there is any progress on this issue?

We are also interested in user authentication when configuring a specific JMS endpoint.

Phiroze

> Allow to specify additional JNDI properties
> -------------------------------------------
>
>                 Key: SM-935
>                 URL: https://issues.apache.org/activemq/browse/SM-935
>             Project: ServiceMix
>          Issue Type: New Feature
>          Components: servicemix-jms
>    Affects Versions: 3.1
>            Reporter: Gert Vanthienen
>            Priority: Minor
>
> In addition to using initialContext and jndiProviderUrl to configure a JMS endpoint, it should be possible to specify additional JNDI properties (e.g {{java.naming.security.principal}}, {{java.naming.security.credentials}})

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.