[JBoss JIRA] (AS7-4240) NameNotFoundException thrown when trying to read java:*/env context in Servlet container.
7:06 p.m.
Robert Edgecombe created AS7-4240:
-------------------------------------
Summary: NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: John Bailey
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
7:13 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Robert Edgecombe commented on AS7-4240:
---------------------------------------
The exception thrown when listing java:module/env in the initial context is as follows:
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1)
javax.naming.NameNotFoundException:
naming/context/java/module/jboss-as-helloworld-ear/jboss-as-helloworld/env -- service
jboss
.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:308)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.InitialContext.listBindings(InitialContext.java:139)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:319)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.naming.InitialContext.listBindings(Unknown Source)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:97)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listInitialContext(HelloWorldServlet.java:73)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.doGet(HelloWorldServlet.java:57)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
java.lang.Thread.run(Unknown Source)
[Server:server-one]
The exception thrown when listing env from java:comp is as follows:
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1)
javax.naming.NameNotFoundException:
naming/context/java/module/jboss-as-helloworld-ear/jboss-as-helloworld/env -- service
jboss
.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:308)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:319)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:97)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:86)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.doGet(HelloWorldServlet.java:61)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
java.lang.Thread.run(Unknown Source)
[Server:server-one]
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: John Bailey
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
7:15 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Robert Edgecombe edited comment on AS7-4240 at 3/20/12 8:15 PM:
----------------------------------------------------------------
The exception thrown when listing java:module/env in the initial context is as follows:
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1)
javax.naming.NameNotFoundException:
naming/context/java/module/jboss-as-helloworld-ear/jboss-as-helloworld/env -- service
jboss
.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:308)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.InitialContext.listBindings(InitialContext.java:139)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:319)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.naming.InitialContext.listBindings(Unknown Source)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:97)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listInitialContext(HelloWorldServlet.java:73)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.doGet(HelloWorldServlet.java:57)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
java.lang.Thread.run(Unknown Source)
[Server:server-one]
The exception thrown when listing env from java:module is as follows:
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1)
javax.naming.NameNotFoundException:
naming/context/java/module/jboss-as-helloworld-ear/jboss-as-helloworld/env -- service
jboss
.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:308)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:319)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:97)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:86)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.doGet(HelloWorldServlet.java:61)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
java.lang.Thread.run(Unknown Source)
[Server:server-one]
was (Author: rob.edgecombe):
The exception thrown when listing java:module/env in the initial context is as
follows:
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1)
javax.naming.NameNotFoundException:
naming/context/java/module/jboss-as-helloworld-ear/jboss-as-helloworld/env -- service
jboss
.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:308)
[Server:server-one]
[Server:server-one] 10:15:01,719 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.InitialContext.listBindings(InitialContext.java:139)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:319)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.naming.InitialContext.listBindings(Unknown Source)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:97)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listInitialContext(HelloWorldServlet.java:73)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.doGet(HelloWorldServlet.java:57)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one]
[Server:server-one] 10:15:01,735 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[Server:server-one]
[Server:server-one] 10:15:01,750 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[Server:server-one]
[Server:server-one] 10:15:01,766 ERROR [stderr] (http--127.0.0.1-8080-1) at
java.lang.Thread.run(Unknown Source)
[Server:server-one]
The exception thrown when listing env from java:comp is as follows:
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1)
javax.naming.NameNotFoundException:
naming/context/java/module/jboss-as-helloworld-ear/jboss-as-helloworld/env -- service
jboss
.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:308)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.listBindings(NamingContext.java:319)
[Server:server-one]
[Server:server-one] 10:15:02,171 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:97)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:106)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.listContext(HelloWorldServlet.java:86)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.doGet(HelloWorldServlet.java:61)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[Server:server-one]
[Server:server-one] 10:15:02,187 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[Server:server-one]
[Server:server-one] 10:15:02,203 ERROR [stderr] (http--127.0.0.1-8080-1) at
java.lang.Thread.run(Unknown Source)
[Server:server-one]
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: John Bailey
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
9:33 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas reassigned AS7-4240:
-----------------------------------
Assignee: Stuart Douglas (was: John Bailey)
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
9:40 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4240:
-------------------------------------
This appears to be a problem with the list() operation when nothing is bound to java:*/env
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
11:43 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved AS7-4240.
---------------------------------
Fix Version/s: 7.1.2.Final
Resolution: Done
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
12:35 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Robert Edgecombe reopened AS7-4240:
-----------------------------------
This fix seems to imply that the jboss-cli operation:
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
creates the java:module/env context but doesn't bind the GREETING_TEXT entry into it.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
12:46 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4240:
-------------------------------------
Hmm, that binding should actually fail when you attempt to create it. It is not possible
to bind to java:module directly using that mechanism, only the global JNDI namespaces
(java:global, java:jboss and java:/ ).
After looking at the code I think that list() would have also had problems for any */env,
not just the empty ones. (*/env is a bit of a special case, normally contexts are created
on demand, however env always has to be present even when it is empty).
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
12:48 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Robert Edgecombe commented on AS7-4240:
---------------------------------------
I don't know whether this is relevant?
The following code:
Context context = new InitialContext();
Context moduleContext = (Context) context.lookup("java:module");
Object lookup = moduleContext.lookup("env/GREETING_TEXT");
throws the following:
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1)
javax.naming.NameNotFoundException: env/GREETING_TEXT -- service
jboss.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env.GREETING_TEXT
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.quickstarts.helloworld.HelloWorldServlet.doGet(HelloWorldServlet.java:57)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[Server:server-one]
[Server:server-one] 16:09:45,023 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one]
[Server:server-one] 16:09:45,039 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[Server:server-one]
[Server:server-one] 16:09:45,039 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[Server:server-one]
[Server:server-one] 16:09:45,039 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[Server:server-one]
[Server:server-one] 16:09:45,054 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[Server:server-one]
[Server:server-one] 16:09:45,054 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[Server:server-one]
[Server:server-one] 16:09:45,054 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[Server:server-one]
[Server:server-one] 16:09:45,054 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[Server:server-one]
[Server:server-one] 16:09:45,054 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[Server:server-one]
[Server:server-one] 16:09:45,054 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[Server:server-one]
[Server:server-one] 16:09:45,054 ERROR [stderr] (http--127.0.0.1-8080-1) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[Server:server-one]
[Server:server-one] 16:09:45,054 ERROR [stderr] (http--127.0.0.1-8080-1) at
java.lang.Thread.run(Unknown Source)
[Server:server-one]
Which has a different service name than would be indicated by the list on
"java:comp/env"
jboss.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env.GREETING_TEXT
vs
[Server:server-one] 16:09:45,148 ERROR [stderr] (http--127.0.0.1-8080-1)
javax.naming.NameNotFoundException:
naming/context/java/modulejboss.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.naming.context.java.module.jboss-as-helloworld-ear.jboss-as-helloworld.env
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
12:52 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Robert Edgecombe commented on AS7-4240:
---------------------------------------
So how do I bind something into java:module?
The JavaEE spec states that the server provides a tool for setting environment entries and
this is the only tool I have seen that could do it.
I cannot find any documentation for this.
Including jboss-web.xml is not a proper solution.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
12:54 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4240:
-------------------------------------
You can't do the binding to java:module via the CLI, it needs to be done via web.xml
or jboss-web.xml
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
12:56 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4240:
-------------------------------------
If you really need the binding in java:module you could also use an @Resource annotation
that looks up another java:global binding.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
1:08 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Robert Edgecombe commented on AS7-4240:
---------------------------------------
using a @Resource in java:global forces the servlet developer to make assumptions about
how it is packaged into an application and how that application is deployed on a server.
These are assumptions that the servlet develper should not be making.
Section 5.2.1 of the4 JAvaEE6 soecification states
2.The container provides an implementation of the JNDI naming context that stores the
application component environment. The container also provides the tools that allow the
Deployer to create and manage the environment of each application component.
the component provide CAN use the web.xml to specify a value (at their own choice) but the
container must provide tools to override this or supply a value if that is not done by the
component provider.
jboss-web.xml is not a tool.
The very least you can do is provide access to java:app/env as then the packager can use
alternade deployment descriptor entries in the application to map java:comp to java:app
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
7:39 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-4240:
----------------------------------
By spec I believe that DD processors are considered "tools".
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
5:39 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Robert Edgecombe commented on AS7-4240:
---------------------------------------
I would accept this comment if:
* Running the DD processor can be separated from the act of uploading the deployment
artifacts (war/ear/jars); and
* The DD processors accept DDs that are outside of the deployment artifacts.
As I am now starting to understand it the current situation demands that to install a
third party EAR file. the deployer must:
* Unpack the ear file
* Unpack any war files
* Unpack any ejb-jars
* Unpack and bean-jars
* Add jboss-*.xml deployment desctiptors (or modify the standard deployment descriptors);
* Repack any war files
* Repack any ejb-jars
* Repack and bean-jars
* Repack the ear file
This multistep process must be done differently between system testing and production
deployment to produce 2 different deployment artefacts (one that will work in each of the
2 different environments).
I think all other application servers I know of provide another option for overriding
these settings.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
5:48 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-4240:
----------------------------------
Sure, I think it's an important feature, I'm just saying that the spec doesn't
actually require it. I've been talking with Stuart about some implementation
options.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
8:04 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Robert Edgecombe commented on AS7-4240:
---------------------------------------
Can I just add that in my opinion the best solution would allow configuration of the
server before deployment,
Failing that it needs to be done with the upload or between upload and enabling the
application.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
5:26 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Tom Fonteyne updated AS7-4240:
------------------------------
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
7:44 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved AS7-4240.
---------------------------------
Resolution: Done
Closing, as the issue with actually reading java:*/env should be fixed. AS7-4296 is the
new JIRA to do with being able to override the deployment descriptor at deployment time
without opening the archive.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
10:10 a.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Yan Pak commented on AS7-4240:
------------------------------
I have a similiar problem.
Can't to enumerate java:comp/env. I get NameNotFound exception in the JBoss AS.
But this works Ok in the GlassFish server.
Think, there is a problem in the implementation of listBindings() and list().
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final-redhat1
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
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
11:45 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Ayrat Nurtdinov commented on AS7-4240:
--------------------------------------
Also, this work in the Weblogic AS 10.3.5
I have similar problem, but I tried listBinding on ejb-bean.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final (EAP)
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:47 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Ayrat Nurtdinov edited comment on AS7-4240 at 10/4/12 12:45 AM:
----------------------------------------------------------------
Also, this work in the Weblogic AS 10.3.5
I have similar problem, but I tried listBinding on ejb-container.
was (Author: klopper):
Also, this work in the Weblogic AS 10.3.5
I have similar problem, but I tried listBinding on ejb-bean.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final (EAP)
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:49 p.m.
[
https://issues.jboss.org/browse/AS7-4240?page=com.atlassian.jira.plugin.s...
]
Ayrat Nurtdinov edited comment on AS7-4240 at 10/4/12 12:47 AM:
----------------------------------------------------------------
Yan.
Also, this work in the Weblogic AS 10.3.5
I have similar problem, but I tried listBinding on ejb-container.
was (Author: klopper):
Also, this work in the Weblogic AS 10.3.5
I have similar problem, but I tried listBinding on ejb-container.
NameNotFoundException thrown when trying to read java:*/env context
in Servlet container.
-----------------------------------------------------------------------------------------
Key: AS7-4240
URL: https://issues.jboss.org/browse/AS7-4240
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Environment: Windows7 Enterprise x64
Intel Core 2 Duo
Oracle Java jdk1.6.0_29
Reporter: Robert Edgecombe
Assignee: Stuart Douglas
Fix For: 7.1.2.Final (EAP)
We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server
These applications rely on configuration using Environment Entries
Most of the answers to issues I have read indicate that this is done using jboss-web.xml
but this is not an acceptable solutin as it requires repackaging of the deployment
artifact for different servers and different environments and is therefor contrary to the
spirit (and I believe the letter) of the JavaEE spec.
The documentation on this capability is either hidden or missing.
I was tasked with working out how to use the JBOSS tools to configure these values and
have been unable to do so.
I modified the quickstart helloworld example to accept a value using the @Resource
annotation and attempted to set this value using jboss-cli.
After several attempts to guess how to do this I modified the servlet to walk down the
context tree.
This servlet throws a NameNotFoundException when trying to list the bindings at:
* java:comp/env
* java:app/env
* java:module/env
I have written the servlet to perform this walk in the following contexts:
* Ithe initial context
* java:
* java:jboss
* java:comp
* java:module
* java:app
* java:global
java:global seems to be able to accept values added using jboss-cli (not surprising)
java:comp, java:module and java:app seem to return some of the expected values (eg
ModuleName and AppName) but throw the exception when trying to list entries under */env
The initial context and java: seem to display the entries added through jboss-cli
Adding a Deployment descriptor (web.xml), that provides values for these entries, results
in no entries that are visible through jboss-cli or any of the contexts listed in the
servlet.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE")
This resulted in the same NameNotFoundException being thrown at java:app/env when walking
the initial context as has been thrown all along when listing env in java:app
It also resulted in java:app appearing in the java: context but being empty.
Prior to running the add command, java:app did not appear in the initial context or java:
context at all.
I then ran the following command through jboss-cli and restarted the app
/profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM")
This resulted in the same NameNotFoundException being thrown at java:module/env when
walking the initial context as has been thrown all along when listing env in java:module
It also resulted in java:module appearing in the java: context but being empty.
Prior to running the add command, java:module did not appear in the initial context or
java: context at all.
My conclusion is that my commands in jboss-cli may be the appropriate ones to add the
correct entries but that the servlet cannot reach the java:module/env or java:app/env
contexts that should be available to it according to the javaEE6 spec.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4979
days inactive
5176
days old
22 comments
6 participants
participants (6)
-
Ayrat Nurtdinov (JIRA) -
David Lloyd (JIRA)
-
Robert Edgecombe (JIRA)
-
Stuart Douglas (JIRA)
-
Tom Fonteyne (JIRA)
-
Yan Pak (JIRA)