problem with @EJB notation

[gnulp]

I have a stateful sessionbean and want to inject a stateless SessionBean using @EJB-injection, but at deployment I get the following exception. It seams as if I have got a problem with jndi names, but have no clue what's wrong.
(without @EJB I can deploy).
The error tells me already the right class - but what does it really mean ?

Caused by: java.lang.RuntimeException: For EJB AdminCurrencyController could not find jndi binding b

 ased on interface only for @EJB(my.test.ContractService) not used by any EJBs

here is a small code-cut from AdminCurencyController for better understanding:

/**
 * the simple ejb3 syntax for injection ;-)
 **/
@EJB
protected ContractService contractService
===> results in deployment exception

the same with lookup works fine

 /**
 * the not so simple syntax of the past ...
 **/
 Context context;
 try {
 context = new InitialContext();
 CurrencyService service = (CurrencyService) context.lookup("earfilename/CurrencyServiceSessionBean/local");
 } catch (NamingException e) {
 e.printStackTrace();
 }

thx for help

[heinrich]

Do you inject your local or remote interface?

[gnulp]

I have disabled my RemoteIntercface for testing purposes - thought there might be the problem !

Now I have just a local interface ...

Might it be that I deploy within a ear-file ? I somewhere read that this causes troubles. But all my classes are in one jar file within the ear-file ...

[jvramana]

@EJB(beanName="CurrencyServiceSessionBean")
protected ContractService contractService

should work..

[gnulp]

unfortunatelly it did not fork ...

I tried both

@EJB(beanName="CurrencyServiceSessionBean")
protected ContractService contractService

as well as

@EJB(beanName="CurrencyService")
protected ContractService contractService

end up in the same exception ...

[bill.burke]

can you describe your deployment? are you deploying these EJBs as part of an EAR? Can you reproduce this in a small test case? I fixed a lot of bugs in CVS in regards to references and want to see if I can reproduce your problem within CVS.

http://jira.jboss.com/jira/browse/EJBTHREE

Thanks.

[gnulp]

yes - its within an ear-file (see message 3:23 AM). To be more exact its part of a SEAM implementation. Maybe I can write a small patch within the booking example of SEAM - but I am not sure if I can reproduce it there ...

So please tell me first, that ears should work and I will try to make a reproduceable testcase ...

+ear.ear
+seam.jar
+ejb3.jar <---------- here are all ejbs !
+web.war


thx

[bill.burke]

ears should work, but there are some bugs that I fixed in CVS, as I said.

[gnulp]

I was able to reproduce the problem - and delivered a patch for seams booking example - for simplicity and file-size

http://jira.jboss.com/jira/browse/EJBTHREE-476

hope that helps

thx