[ https://issues.jboss.org/browse/AS7-1407?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-1407: ---------------------------------- Here's an example: {noformat} [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=xmpp-ra.rar:read-attribute(name=connection-definitions) { "outcome" => "success", "result" => [{ "class-name" => "com.ramphastos.xmpp.XmppConnectionFactory", "jndi-name" => "java:jboss/eis/xmpp", "pool-name" => "xmpp-ra_rar-Pool" }] } {noformat} {noformat} [standalone@localhost:9999 /] /subsystem=naming:jndi-view { "outcome" => "success", "result" => { "java: contexts" => { "java:jboss" => { "jaas" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "children" => {"other" => { "class-name" => "org.jboss.as.security.plugins.SecurityDomainContext", "value" => "org.jboss.security.authentication.JBossCachedAuthenticationManager@2c9fac35" }} }, "TransactionManager" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@36a75e9f" }, "datasources" => { "class-name" => "javax.naming.Context", "children" => {"ExampleDS" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "org.jboss.jca.adapters.jdbc.WrapperDataSource@6f1a7e7f" }} }, "TransactionSynchronizationRegistry" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple@55611ed3" }, "mysql" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "org.jboss.jca.adapters.jdbc.WrapperDataSource@5eba06ff" } }, "java:global" => undefined }, "applications" => { "mysql-connector-java-5.1.15.jar" => { "java:app" => {"AppName" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "mysql-connector-java-5.1.15" }}, "modules" => {"mysql-connector-java-5.1.15" => {"java:module" => {"ModuleName" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "mysql-connector-java-5.1.15" }}}} }, "xmpp-ra.rar" => { "java:app" => {"AppName" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "xmpp-ra" }}, "modules" => {"xmpp-ra" => {"java:module" => {"ModuleName" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "xmpp-ra" }}}} } } } } {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1407?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned AS7-1407: --------------------------------- Assignee: John Bailey (was: Brian Stansberry) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1407?page=com.atlassian.jira.plugin.s... ] Richard Opalka edited comment on AS7-1407 at 7/28/11 5:47 AM: -------------------------------------------------------------- There's another issue with our Naming store :( I have the following piece of code in our web.xml DD: --- <env-entry> <env-entry-name>jaxws/entry1</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>web</env-entry-value> <injection-target> <injection-target-class>org.jboss.test.ws.jaxws.enventry.EnvEntryBeanJSE</injection-target-class> <injection-target-name>strValue</injection-target-name> </injection-target> </env-entry> <env-entry> <env-entry-name>jaxws/entry2</env-entry-name> <env-entry-type>java.lang.Integer</env-entry-type> <env-entry-value>8</env-entry-value> </env-entry> --- This results in the following output in the CLI: --- ... "jaxws-enventry-jse.war" => { "modules" => {"jaxws-enventry-jse" => {"java:module" => { ... "env" => { "class-name" => "javax.naming.Context", "children" => { "entry1" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "web" }, "entry2" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "8" } } }, }}} } ... --- Note the missing 'jaxws' prefix? And at the end when I was debugging our JNDI naming store, I noticed that missing 'jaxws' context is present in the debugger. It's just not displayed. Another thing that I noticed is when I'm doing the following lookup: --- new InitialContext().lookup(POJO_JNDI_PREFIX); --- then for above web.xml DD configuration "env/jaxws" is returned instead of expected "env/" context :( was (Author: ropalka): There's another issue with our Naming store :( I have the following piece of code in our web.xml DD: --- <env-entry> <env-entry-name>jaxws/entry1</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>web</env-entry-value> <injection-target> <injection-target-class>org.jboss.test.ws.jaxws.enventry.EnvEntryBeanJSE</injection-target-class> <injection-target-name>strValue</injection-target-name> </injection-target> </env-entry> <env-entry> <env-entry-name>jaxws/entry2</env-entry-name> <env-entry-type>java.lang.Integer</env-entry-type> <env-entry-value>8</env-entry-value> </env-entry> --- This results in the following output in the CLI: --- "jaxws-enventry-jse.war" => { "java:app" => {"AppName" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "jaxws-enventry-jse" }}, "modules" => {"jaxws-enventry-jse" => {"java:module" => { "Validator" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "org.hibernate.validator.engine.ValidatorImpl@c2e42fe" }, "ValidatorFactory" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "org.jboss.as.ee.beanvalidation.LazyValidatorFactory@54a8c871" }, "UserTransaction" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "Transaction: unknown" }, "ModuleName" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "jaxws-enventry-jse" }, "env" => { "class-name" => "javax.naming.Context", "children" => { "entry1" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "web" }, "entry2" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "8" } } }, "TransactionSynchronizationRegistry" => { "class-name" => "org.jboss.as.naming.context.ModularReference", "value" => "com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple@3ff9ddb5" } }}} } --- Note the missing 'jaxws' prefix? And at the end when I was debugging our JNDI naming store, I noticed that missing 'jaxws' context is present in the debugger. It's just not displayed. Another thing that I noticed is when I'm doing the following lookup: --- new InitialContext().lookup(POJO_JNDI_PREFIX); --- then for above web.xml DD configuration "env/jaxws" is returned instead of expected "env/" context :( -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1407?page=com.atlassian.jira.plugin.s... ] John Bailey commented on AS7-1407: ---------------------------------- Any chance I can get the basic setup used for the RAR example above? I would like to get it replicated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1407?page=com.atlassian.jira.plugin.s... ] John Bailey commented on AS7-1407: ---------------------------------- I believe this is resolved. I would need proper test cases to confirm. I will put something together when time permits. -- 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

[ https://issues.jboss.org/browse/AS7-1407?page=com.atlassian.jira.plugin.s... ] John Bailey commented on AS7-1407: ---------------------------------- This appears to be fixed. Re-open if there is still an issue. -- 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