[
https://issues.jboss.org/browse/AS7-4879?page=com.atlassian.jira.plugin.s...
]
Michael Gronau commented on AS7-4879:
-------------------------------------
I have tested it with current nightly build. On server side it works now. But on remote
clients the reference is not resolved via its ObjectFactory. All I got is the Reference
object bound in the jndi.
Objects implementing javax.naming.Referenceable are not bound to jndi
correctly
-------------------------------------------------------------------------------
Key: AS7-4879
URL:
https://issues.jboss.org/browse/AS7-4879
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: Michael Gronau
Assignee: John Bailey
Labels: javax.naming.Referenceable, jndi, naming
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
Normally when those object are to be bound to the jndi its getReference() method is
called and this reference is then bound. When looking up this reference from a remote
client it is resolved and instantiated with the ObjectFactory class stored in this
Reference object. All this corrently does not work (the invocation of getReference() and
the instantiation of the object).
One little workaround is only to bind the Reference object directly, i.e. create the
Referenceable object, call the getReference() and bind this reference to the jndi. But the
instantiation only works with local clients (inside jboss jvm), not with remote clients.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira