resource injection in WS handler not working in jboss JAX-WS

[actonwang]

hi,

I tried to use resource injection in WS Handler as described in JAX-WS spec which is a MUST feature.

I tested it in both Sun impl and Jbosss JAX-WS 2.0.x with Jboss 4.2.2. It is working well in Sun impl but not working in JBoss WS.

here is the simple test. I am using web war as deployement, inside web.xml, I have the following:

<env-entry>
<env-entry-name>customFormat</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>Path1: $PATH_INFO, Outbound: $MESSAGE_OUTBOUND_PROPERTY - $NODE</env-entry-value>
<injection-target>
<injection-target-class>testjaxws.handler.DefaultCustomLoggingWrapperHandler</injection-target-class>
<injection-target-name>customFormat</injection-target-name>
</injection-target>
</env-entry>

inside DefaultCustomLoggingWrapperHandler class, I have:

@Resource
private String customFormat = null;


defined.

It is never gets injected with this value no matter what I tried.

Anyone could help to explain if jboss WS has implemented it or not? If it is implemented, how should we make it work?

Thanks a lot!!
actonwang

[ropalka]

http://jira.jboss.org/jira/browse/JBWS-2074

[actonwang]

hi,

FYI: by looking at source code of HandlerResolverImpl, it looks at public fields and public methods with @Resource annotation and if it is any, it just throws "Not implemented" error.

Really hope that it can also look at private fields and possible retrace back to any mark in parent classes as well after this ability is added in.

thx
acton

[gang.yang]

Hi,

I also hit this problem now, which is a blocking one since I can not pass in any info to the handler w/o this capability.

According the JAX-WS spec, you should also be able to lookup up the names defined by the associated Java EE component using JNDI from the handler. I tried that. It worked for handlers that is configure for the Web container. But it did not work for handlers that is configure for the EJB3 container. So I'm really dead in the water since we use EJB3 annotated WS endpoint.

I understand that the fix for the resource injection is targeted for JBossWS 3.1.1. But could there be a fix for the JNDI lookup not working earlier? Or should I create a trouble report for the JNDI?

Thanks,
Gang