This is a limitation outlined in the spec...
I wish it was different. It isn't.
I have to trust that the folks that wrote the spec put the limitation in
there for a reason that I haven't come to understand yet...
vbk
Witold Szczerba wrote:
> 2006/12/6, Tim Quinn <Timothy.Quinn_at_sun.com>:
>> The GlassFish unit tests include several that test annotations and
>> injection. One in particular is the test in this directory:
>>
>> appserv-tests/devtests/ejb/ejb30/hello/session
>>
>> The client/Client.java class uses @EJB, and I just now ran the test
>> and it
>> passed, meaning that the annotation processing and the injection worked
>> correctly.
>>
>> I wish I could compare that scenario with what you have been working
>> with
>> to try to see what the key differences are, but I'm afraid I don't
>> have the
>> time right now.
>>
>> - Tim
>>
>
> Hello there,
> I am really surprised now, as I just made a simple 'hello world' with
> EJB3+Client App, where client is using @EJB and it just works. I
> investigated it a little bit (because I know id did not work for me)
> and here is what I can see:
> if injection is to be made in the class which starts client
> application, then injection works. But, when injection is to be
> performed in some another class - then it doesn't work.
>