Does Seam 2 or Seam 3 support EJB 3.1 ?

[kresimir_popovic]

Hello,

does Seam 2 or Seam 3 support EJB 3.1? When I deploy @javax.ejb.Singleton as Seam 2 project I get errors on JBoss 6.0. Do I need to swith to Seam 3 ?

Best Regards,
Krešimir

[meetoblivion]

That's probably a better question for the Seam 2 users forum.

[kresimir_popovic]

Hello,

I already posted this question to Seam 2 forum: "Seam 2.2.1 Final + EJB 3.1 @Singleton", but nobody answered.

Best Regards,
Krešimir

[asookazian]

You need an EE 6 server to use EJB 3.1.  Even with JBoss 6 I would not use EJB 3.1 with Seam 2.x.  Seam 3 and EJB 3.1 should be fine, however.

[kresimir_popovic]

Hello Arbi,

I use JBoss 6.0 Final, but with Seam 2.2.1 Final. It seams that I will need to switch to Seam 3.x.

Best Regards,
Krešimir

[spinner.joserodolfo.freitas.gawab.com]

which errors are you getting Popovic?

[kresimir_popovic]

Hello,

JBoss 6.0 trace is here:

http://seamframework.org/Community/Seam3EJB31


part of trace:

Dependency "jboss.j2ee:jar=PhCoreService.jar,name=SingletonTest,service=EJB3" (should be in state "Installed", but i
s actually in state "** NOT FOUND Depends on 'jboss.j2ee:jar=PhCoreService.jar,name=SingletonTest,service=EJB3' **")

Best Regards,
Krešimir

[florianhell]

Hi Krešimir,

for me it sounds more like a bug or problem with the @singleton. Wouldn't be the first ;-)

EJB 3.1 works for me, even with seam 2.2.1, but haven't tested EJB 3.1 @singleton in this case yet.

But I also had Problems with @Singleton and @PostConstruct, also with Seam 3. There are still some known bugs in EJB 3.1. like https://issues.jboss.org/browse/EJBTHREE-2227

May you try it without singleton annotations and for first just with plain stateless EJBs, may with local interface. I think that should work also with seam 2.2.

But like Arbi wrote, use Seam 3, CDI and JBoss 6 with EJB 3.1, that is better solution. It will provide you a better programming model and a really better performance than Seam 2 (nothin against Seam 2, I really liked it, but CDI and Seam 3 is so much better...)

May this helps you

Best regards
Florian

[kresimir_popovic]

Hello Florian,

A already tried EJB 3.1 @Stateless (with local interface) and it works.
Instead of EJB 3.1 @Singleton I use Seam singleton.

@Name(test)
@Scope(ScopeType.APPLICATION)
@Synchronized
@AutStart
public class Test {

...

}

I will try Seam 3 sooner or later :)
ps. Maybe to wait Seam 3.x correction? To start from more stable version.

Best Regards,
Krešimir

[pgmjsd]

I was just playing around with @Singleton today, in my first Weld/Seam3 app on JBoss 6.   Same result: The @Singleton EJB doesn't deploy because it needs BeanManager.

I've tried making an @ApplicationScoped bean as well, but I can't seem to find an equivalent to @AutoStart in CDI/Weld/Seam3.   Is there such a thing?

[lightguard]

I don't know of one. You could work around it by using a servlet context listener, or Seam Servlet events. This may be a good one to ask to have added to CDI 1.1, would you mind creating a JIRA ticket for it in the CDI project?

[pgmjsd]

Seam Servlet events - is that similar to @Observer("org.jboss.seam.postInitialization"), mentioned in this post?   Maybe that's something else entirely... I'm still learning Seam 3.

I'll enter a JIRA issue in https://issues.jboss.org/browse/CDI shortly.

[pgmjsd]

This JIRA looks pretty close, but I guess it's not exactly the same as @AutoCreate: CDI-107

There is also a similar discussion here.