OK, I'll have a look. Thanks Carlo for information.

The situation is little bit more complicated.

First of all I need to verify if the following usecase is valid.

There's a EJB3Bean web service bean

with the following DD. It defines boolean1 env entry.

<ejb-jar>

   <enterprise-beans>
    <session>

      <ejb-name>EJB3Bean</ejb-name>
      <ejb-class>org.jboss.test.ws.jaxws.ejb3Integration.injection.webservice.EJB3Bean</ejb-class>

      <env-entry>
        <env-entry-name>boolean1</env-entry-name>
        <env-entry-type>java.lang.Boolean</env-entry-type>
        <env-entry-value>true</env-entry-value>
      </env-entry>

    </session>

  </enterprise-beans>

</ejb-jar>

There's a handler associated with this EJB3Bean

@WebService
@HandlerChain(file = "jaxws-handler.xml")
@Stateless
public class EJB3Bean extends AbstractEndpointImpl
{

   public String echo(String msg)
   {
      return super.echo(msg) + ":EJB3Bean";
   }

}

The content of jaxws-handler.xml is:

<handler-chains>

  <handler-chain>
    <handler>
      <handler-name>TestHandler</handler-name>
      <handler-class>org.jboss.test.ws.jaxws.ejb3Integration.injection.shared.handlers.TestHandler</handler-class>
    </handler>
  </handler-chain>

</handler-chains>

This TestHandler tries to access both EJB3Bean and it's env-entry

public final class TestHandler extends GenericSOAPHandler {
   @Resource private Boolean boolean1;
   @EJB private BeanIface bean1;

   ...

}

Using global JNDI I'm able to fix @EJB injection.

Question for EJB3 team:

Do you think this JAX-WS handler should see env-entry of EJB3Bean?

That would mean required access to EJB3Bean specific JNDI context (the reason why we're using it instead of global JNDI).

I'll double check JAX-WS and EE6 specification for clarification, but would like to know your opinion

Related issue JBWS-2558

Copy/paste from JSR-109, section 6.2.2.2

The container must carry out any injections (if any) requested by the handler, typically via the @Resource
annotation (see section 2.2 of JSR-250 Common Annotations for Java Platform specification). After all the
injections have been carried out, the container must invoke the method carrying a
javax.annotation.PostConstruct annotation.

The question is the scoping. Should this EJB3 associated JAX-WS handler

(part of WS runtime) see environment entries of particular EJB3 bean?

<bgeorges> ropalka: I was wondering what is happening with https://jira.jboss.org/jira/browse/JBAS-7888 as we still have regressions with WS
<JiraBot> [#JBAS-7888] Investigate EJB3 Injection Integration Issue [Reopened, Major, Richard Opalka]
<ropalka> bgeorges, https://community.jboss.org/message/535366#535366
<ropalka> bgeorges, I'm waiting for Alessios and Carlos opinion on this topic
<bgeorges> ropalka: ok, thank you. carlo: can you have a look
<ropalka> bgeorges, However IMHO it's not a blocker for M3 release
<carlo> I don't know how a Handler is scoped.
<carlo> But JSR-250 injection happens from java:comp
<bgeorges> ropalka: that would be good, carlo: wdyt
<JiraBot> JIRA at jira.jboss.org reports that JSR-250 does not exist. https://jira.jboss.org/jira/browse/JSR-250
<carlo> bgeorges: okay by me
<ropalka> carlo, bgeorges If JSR 250 injection happens from java:comp only then I know how to fix it. I'll remove this handler.
<ropalka> carlo, bgeorges I'll review also JSR 250 to be 100% sure

I reviewed JSR 250 but didn't find relevant information but I found it in EJB 3.1 spec.

Copy/paste from EJB 3.1 spec. - 16.2 Enterprise Bean’s Environment as a JNDI Naming Context

The container must make an enterprise bean’s environment available to any interceptor class
and any JAX-WS message handler for the bean as well. The interceptor and web service han-
dler classes for an enterprise bean share that bean’s environment.

IOW JBossWS implementation is correct in terms it's trying to access EJB 3 specific JNDI context.