[JBoss JIRA] Created: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the handlers via JNDI for EJB3-based WS components.
10:07 a.m.
Component's resources defined in the \<env-entry\> are not available to the
handlers via JNDI for EJB3-based WS components.
---------------------------------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-metro-3.0.1, jbossws-2.0.1.SP1
Reporter: Gang Yang
Priority: Critical
While the resources defined in \<env-entry\> are not injected using the @Resource in
handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1?) and JBoss 5.0.0.GA
(JBossWS 3.0.1?). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:35 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the handlers via JNDI for EJB3-based WS components.
[
https://jira.jboss.org/jira/browse/JBWS-2558?page=com.atlassian.jira.plug...
]
Gang Yang updated JBWS-2558:
----------------------------
Workaround Description: No workaround known.
Affects Version/s: jbossws-native-3.0.4
jbossws-2.0.1
(was: jbossws-metro-3.0.1)
(was: jbossws-2.0.1.SP1)
Description:
While the resources defined in \<env-entry\> are not injected using the @Resource in
handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
was:
While the resources defined in \<env-entry\> are not injected using the @Resource in
handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1?) and JBoss 5.0.0.GA
(JBossWS 3.0.1?). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Component's resources defined in the \<env-entry\> are not
available to the handlers via JNDI for EJB3-based WS components.
---------------------------------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-2.0.1, jbossws-native-3.0.4
Reporter: Gang Yang
Priority: Critical
While the resources defined in \<env-entry\> are not injected using the @Resource
in handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:52 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the handlers via JNDI for EJB3-based WS components.
[
https://jira.jboss.org/jira/browse/JBWS-2558?page=com.atlassian.jira.plug...
]
Gang Yang updated JBWS-2558:
----------------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213196#...
Description:
While the resources defined in \<env-entry\> are not injected using the @Resource in
handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Can this be fixed more easily and therefore earlier since it already works for Web
container based WS endpoint/handler? This is a show stopper since there's no way to
pass in info into the handler for EJB3 based WS endpoint/handler.
was:
While the resources defined in \<env-entry\> are not injected using the @Resource in
handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Component's resources defined in the \<env-entry\> are not
available to the handlers via JNDI for EJB3-based WS components.
---------------------------------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-2.0.1, jbossws-native-3.0.4
Reporter: Gang Yang
Priority: Critical
While the resources defined in \<env-entry\> are not injected using the @Resource
in handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Can this be fixed more easily and therefore earlier since it already works for Web
container based WS endpoint/handler? This is a show stopper since there's no way to
pass in info into the handler for EJB3 based WS endpoint/handler.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:35 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the handlers via JNDI for EJB3-based WS components.
[
https://jira.jboss.org/jira/browse/JBWS-2558?page=com.atlassian.jira.plug...
]
Richard Opalka updated JBWS-2558:
---------------------------------
Fix Version/s: jbossws-native-3.1.2
Affects Version/s: jbossws-native-3.1.1
(was: jbossws-2.0.1)
(was: jbossws-native-3.0.4)
Component's resources defined in the \<env-entry\> are not
available to the handlers via JNDI for EJB3-based WS components.
---------------------------------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.1
Reporter: Gang Yang
Assignee: Richard Opalka
Priority: Critical
Fix For: jbossws-native-3.1.2
While the resources defined in \<env-entry\> are not injected using the @Resource
in handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Can this be fixed more easily and therefore earlier since it already works for Web
container based WS endpoint/handler? This is a show stopper since there's no way to
pass in info into the handler for EJB3 based WS endpoint/handler.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the handlers via JNDI for EJB3-based WS components.
[
https://jira.jboss.org/jira/browse/JBWS-2558?page=com.atlassian.jira.plug...
]
Richard Opalka updated JBWS-2558:
---------------------------------
Fix Version/s: jbossws-native-3.2.0
Component's resources defined in the \<env-entry\> are not
available to the handlers via JNDI for EJB3-based WS components.
---------------------------------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.1
Reporter: Gang Yang
Assignee: Richard Opalka
Priority: Critical
Fix For: jbossws-native-3.1.2, jbossws-native-3.2.0
While the resources defined in \<env-entry\> are not injected using the @Resource
in handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Can this be fixed more easily and therefore earlier since it already works for Web
container based WS endpoint/handler? This is a show stopper since there's no way to
pass in info into the handler for EJB3 based WS endpoint/handler.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:28 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the handlers for EJB3-based WS components.
[
https://jira.jboss.org/jira/browse/JBWS-2558?page=com.atlassian.jira.plug...
]
Richard Opalka updated JBWS-2558:
---------------------------------
Summary: Component's resources defined in the \<env-entry\> are not
available to the handlers for EJB3-based WS components. (was: Component's resources
defined in the \<env-entry\> are not available to the handlers via JNDI for
EJB3-based WS components.)
Component's resources defined in the \<env-entry\> are not
available to the handlers for EJB3-based WS components.
------------------------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.1
Reporter: Gang Yang
Assignee: Richard Opalka
Priority: Critical
Fix For: jbossws-native-3.1.2, jbossws-native-3.2.0
While the resources defined in \<env-entry\> are not injected using the @Resource
in handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Can this be fixed more easily and therefore earlier since it already works for Web
container based WS endpoint/handler? This is a show stopper since there's no way to
pass in info into the handler for EJB3 based WS endpoint/handler.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the EJB3 JAX-WS handlers
[
https://jira.jboss.org/jira/browse/JBWS-2558?page=com.atlassian.jira.plug...
]
Richard Opalka updated JBWS-2558:
---------------------------------
Summary: Component's resources defined in the \<env-entry\> are not
available to the EJB3 JAX-WS handlers (was: Component's resources defined in the
\<env-entry\> are not available to the handlers for EJB3-based WS components.)
Component's resources defined in the \<env-entry\> are not
available to the EJB3 JAX-WS handlers
------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.1
Reporter: Gang Yang
Assignee: Richard Opalka
Priority: Critical
Fix For: jbossws-native-3.1.2, jbossws-native-3.2.0
While the resources defined in \<env-entry\> are not injected using the @Resource
in handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Can this be fixed more easily and therefore earlier since it already works for Web
container based WS endpoint/handler? This is a show stopper since there's no way to
pass in info into the handler for EJB3 based WS endpoint/handler.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:34 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the EJB3 JAX-WS handlers
[
https://jira.jboss.org/jira/browse/JBWS-2558?page=com.atlassian.jira.plug...
]
Richard Opalka commented on JBWS-2558:
--------------------------------------
Test associated with this issue is: org.jboss.test.ws.jaxws.jbws2074.usecase4.*
Component's resources defined in the \<env-entry\> are not
available to the EJB3 JAX-WS handlers
------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.1
Reporter: Gang Yang
Assignee: Richard Opalka
Priority: Critical
Fix For: jbossws-native-3.1.2, jbossws-native-3.2.0
While the resources defined in \<env-entry\> are not injected using the @Resource
in handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Can this be fixed more easily and therefore earlier since it already works for Web
container based WS endpoint/handler? This is a show stopper since there's no way to
pass in info into the handler for EJB3 based WS endpoint/handler.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:58 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the EJB3 JAX-WS handlers
[
https://jira.jboss.org/jira/browse/JBWS-2558?page=com.atlassian.jira.plug...
]
Alessio Soldano updated JBWS-2558:
----------------------------------
Fix Version/s: (was: jbossws-native-3.2.0)
Assignee: (was: Richard Opalka)
Component's resources defined in the \<env-entry\> are not
available to the EJB3 JAX-WS handlers
------------------------------------------------------------------------------------------------
Key: JBWS-2558
URL: https://jira.jboss.org/jira/browse/JBWS-2558
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.1
Reporter: Gang Yang
Priority: Critical
Fix For: jbossws-native-3.1.2
While the resources defined in \<env-entry\> are not injected using the @Resource
in handlers for both Web and EJB3 containers (an issue has been created for this problem),
they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109
requires. Therefore, for EJB3-based WS components, there's no way to pass any data
into the associated handlers. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1) and
JBoss 5.0.0.GA (JBossWS 3.0.4). Here's the details on the code:
- A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain
- ejb-jar.xml has the following \<env-entry\> definition for the session bean:
\<env-entry\>
\<env-entry-name\>configFile\<env-entry-name\>
\<env-entry-type\>java.lang.String\<env-entry-type\>
\<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\>
\<env-entry\>
- The hanler is a SOAP handler and has the following code segment:
@Resource(name="configFile")
String configFile;
....
@PostConstruct
public void init() {
if (configFile == null) {
InitialContext icxt = new InitialContext();
Context myEnv = icxt.lookup("java:comp/env");
configFile = (String)myEnv.lookup("configFile");
....
Note: the same handler configured for Web-container WS endpoints works OK - although
configFile is not injected by @Resource, but at least it looked up fine using JNDI.
Can this be fixed more easily and therefore earlier since it already works for Web
container based WS endpoint/handler? This is a show stopper since there's no way to
pass in info into the handler for EJB3 based WS endpoint/handler.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5483
days inactive
5552
days old
jbossws-issues@lists.jboss.org
8 comments
3 participants
participants (3)
-
Alessio Soldano (JIRA) -
Gang Yang (JIRA)
-
Richard Opalka (JIRA)