[
https://issues.apache.org/jira/browse/ARIES-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803736#comment-13803736
]
Ajit Pendse commented on ARIES-1127:
------------------------------------
Object factories can be configured using "java.naming.factory.object"
environment key. From javax.naming.Context javadoc -
String javax.naming.Context.OBJECT_FACTORIES = "java.naming.factory.object"
Constant that holds the name of the environment property for specifying the
list of object factories to use. The value of the property should be a
colon-separated list of the fully qualified class names of factory classes that
will create an object given information about the object. This property may be
specified in the environment, an applet parameter, a system property, or one or
more resource files.
There should be some way of supporting this for external JNDI look-ups,
requiring some type of object resolutions, to work.
E.g. currently Tibco EMS JNDI connections from Aries cannot work as
OSGiObjectFactoryBuilder cannot create required objects for Tibco EMS JNDI.
> External JNDI Lookup and Object creation fails for embedded scenario
> --------------------------------------------------------------------
>
> Key: ARIES-1127
> URL: https://issues.apache.org/jira/browse/ARIES-1127
> Project: Aries
> Issue Type: Bug
> Components: JNDI
> Affects Versions: 0.3
> Reporter: Ajit Pendse
>
> In case of embedded scenario (e.g. in WAS CE container), no external lookups
> are successful as the object factory returned is always of type
> org.apache.aries.jndi.OSGiObjectFactoryBuilder. There is no way to override
> this currently and hence any object factories required by external JNDI
> lookups are ignored and object resolution, if required does not work.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
