[
https://issues.apache.org/jira/browse/ARIES-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved ARIES-1704.
------------------------------------
Resolution: Fixed
Assignee: Guillaume Nodet
Fix Version/s: jndi-core-1.1.0
Fixed with
https://github.com/apache/aries/commit/97862effa50c36ae7b0931ac404ae7dc5436c7ed#diff-f0b80e9c0647340ed880c1227ba40c66
> JNDI implementation does not follow the specification
> -----------------------------------------------------
>
> Key: ARIES-1704
> URL: https://issues.apache.org/jira/browse/ARIES-1704
> Project: Aries
> Issue Type: Bug
> Components: JNDI
> Affects Versions: jndi-url-1.1.0
> Reporter: Hao Zhong
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: jndi-core-1.1.0
>
> Attachments: aries.patch
>
>
> The ObjectFactoryHelper.getObjectInstance method does not follow the
> specification. Jarek Gawor reported and fixed a similar bug in ARIES-311.
> The fixed code in that bug report is as follow:
> {code}
> public Object getObjectInstance(final Object obj,
> final Name name,
> final Context nameCtx,
> final Hashtable<?, ?> environment,
> final Attributes attrs) throws Exception {
> return Utils.doPrivileged(new PrivilegedExceptionAction<Object>() {
> public Object run() throws Exception {
> return doGetObjectInstance(obj, name, nameCtx, environment,
> attrs);
> }
> });
> }
>
> private Object doGetObjectInstance(Object obj,
> Name name,
> Context nameCtx,
> Hashtable<?, ?> environment,
> Attributes attrs) throws Exception {
> {code}
> I believe that similar fixes work for this bug report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
