[jboss-jira] [JBoss JIRA] (AS7-3437) JMS clients - Remote JNDI lookup does not work in EAP6/AS7
Miroslav Novak (JIRA)
jira-events at lists.jboss.org
Wed Jan 25 04:09:20 EST 2012
[ https://issues.jboss.org/browse/AS7-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661675#comment-12661675 ]
Miroslav Novak commented on AS7-3437:
-------------------------------------
JNP is not important in example code. "properties" should just express that lookups are remote. Main point of this jira was to have remote JNDI. Since AS7-1338 was re-opened, all discussions can move there.
> JMS clients - Remote JNDI lookup does not work in EAP6/AS7
> ----------------------------------------------------------
>
> Key: AS7-3437
> URL: https://issues.jboss.org/browse/AS7-3437
> Project: Application Server 7
> Issue Type: Feature Request
> Reporter: Miroslav Novak
> Assignee: David Lloyd
> Priority: Blocker
> Fix For: No Release
>
>
> EAP6/AS7 have not yet implemented remote jndi lookups. This feature is important for standalone jms clients to work and also ensure backward compatibility with EAP5/AS6 applications. Following piece of code should work without change:
> Properties properties = new Properties();
> properties.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
> properties.setProperty("java.naming.provider.url", "jnp://server_hostname:1099");
> properties.setProperty("java.naming.factory.url.pkgs", "org.jnp.interfaces.NamingContextFactory");
> context = new InitialContext(properties);
> ConnectionFactory cf = (ConnectionFactory) context.lookup("RemoteConnectionFactory");
> con = cf.createConnection();
> session = con.createSession(false, Session.CLIENT_ACKNOWLEDGE);
> Queue queue = (Queue) context.lookup("/queue/test");
> For now there is a workaround but it's not suitable for us. Example code:
> https://github.com/jbossas/jboss-as/tree/master/demos/legacy/src/main/java/org/jboss/as/demos/client/jms/runner
> There are AS7 jiras related to this missing feature which are closed as rejected/duplicated. In AS7-1338 J. Green explains that some kind of remote jndi functionality will be in AS 7.1 (as part of the EE full profile). Unfortunately AS 7.1 is still missing this feature.
--
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
More information about the jboss-jira
mailing list