You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dirk Rudolph (JIRA)" <ji...@apache.org> on 2015/10/15 16:29:05 UTC

[jira] [Updated] (SLING-4789) Support custom properties in the JNDI context

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

Dirk Rudolph updated SLING-4789:
--------------------------------
    Attachment: jndi-additional-environment-properties.patch

See attached a patch, that adds a new component property to add additional environment properties to the env of the InitialContext (unfiltered)

> Support custom properties in the JNDI context
> ---------------------------------------------
>
>                 Key: SLING-4789
>                 URL: https://issues.apache.org/jira/browse/SLING-4789
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR Registration 1.0.2
>            Reporter: Dirk Rudolph
>            Priority: Minor
>         Attachments: jndi-additional-environment-properties.patch
>
>
> Currently the JNDI context is generated and populated with the service properties of the registration service. Those properties are filtered using a whitelist {{java.naming.}}
> {code}
> if (key.startsWith("java.naming.")) {
>     env.setProperty(key, (String) props.get(key));
> }
> {code}
> So it is not possible to add custom environment properties that are actually used by the JNDI implementation like those defined for simple-jndi: {{org.osjava.sj.}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)