JBossDeveloper

Its pretty clear based on the error messages that you get, the instance that it is trying to inject is not of a compatible type. Now why it happens is unknown to me.

Can you provide more info on your application and deployment configurations ?

Seam 2.1.0 is still in alpha stage.

Try with Seam 2.0.2.SP1 which is the latest production release. I would also use a more recent version of JBoss AS such as 4.2.2GA but that probably does not matter in this case.

Let me know if the issue still occurs in that version.

When I was asking about configuration and deployment I was asking about you EAR/WAR packaging setup and central configuration files such as web.xml, components.xml, etc..

Robert, you can inject an EJB into an EJB. I'm not sure why you can't achieve this. In my project I inject EJBs into EJBs without any problems.

Shouldn't he use RegistrationLogicInterface as type instead of RegistrationLogic, since it's his @Local interface?

I think Adrien is right. The type you refer in the injected instance variable must be the same type where you declared your @Local annotation. Would that be RegistrationLogicInterface ?

If so, then try this:

@Stateful

@Scope(SESSION)

@Name("registrationBean")

public class RegisterBean implements Register, Serializable{


    @In(value="registrationLogic")

    private RegistrationLogicInterface regLogic;

Below is how I do it:

@Stateless

@Name("partyService")

@Local(PartyService.class)

public class PartyServiceImpl implements PartyService 

@Stateful(mappedName="ClassificationUseAction")

@Scope(ScopeType.CONVERSATION)

@Name("classificationUseAction")

@Local(value=ClassificationUseAction.class)

public class ClassificationUseActionBean implements ClassificationUseAction {

     

     @In(create=true)

     private PartyService partyService;

You can declare the @Local annotation in your concrete class and refer to the interface inside. This way your interface is completely generic and client classes don't know more than they should about a given implementation of the interface. Implementing classes are not constrained either by the interface @Local EJB annotation.

Yeah this is EJB3 specific stuff. Basically the exportable types (that can be referred by clients) are the ones tagged with @Local or @Remote annotations.

Yes, the strict necessity is related to EJB, but referring to interaces is good practice in a JavaBean context, too. If you extract an interface from a JavaBean component and have all clients inject the component with the interface as type, you can easily exchange the implementation classes by using the @Install annotation (see the docs).

On the other hand, using interfaces can sometimes be tedious, especially during prototyping. That's why I use concrete JavaBean components for the controllers which are directly accessed by JSF components. Forgetting a method on an interface here would result in an annoying runtime error and could not be cought at compile time.