4:48 a.m.
[
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:48 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("java:comp/env/");
---
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" => {
"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 :(
JNDI view operation doesn't show all entries
--------------------------------------------
Key: AS7-1407
URL: https://issues.jboss.org/browse/AS7-1407
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Reporter: Heiko Braun
Assignee: John Bailey
don't ask me why, but a queue (java:/jboss/queues/myQueue) for instance is not shown.
Same thing for resource adapter, etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira