Embeddable EJB3 Container on WebLogic 9.2: Too Good to be tr

[neilac333]

I've been studying Seam as I prepare to begin development of a JSF/Hibernate JPA solution to be deployed to WebLogic 9.2 in production. I have to admit being intrigued by the embeddable EJB3 container. It seems almost too good to be true. All the joys of EJB 3 without the need for a Java EE 5 app server?

I've learned though to be wary of things that are too good to be true. Is there any reason why I shouldn't use this approach? All I can think of is the huge number of jars, but that seems a small price to pay for something so glorious.

What other concerns are there? Scalability in production? Is the container only useful for testing and not production use? Anything else I should know?

Thanks.

[norman.richards]

You'd really prefer to be running on the app server directly to take full advantage of all its capabilities. So, I'd rather be running on JBoss or even Glassfish than on embedded JBoss in Weblogic. When that isn't an option, then I'd be very comfortable running embedded JBoss. I've only run embedded JBoss in Tomcat, but when I do I'm barely aware that it is there.

[neilac333]

Believe me, it it were up to me, I would love to run my app on JBoss. Unfortunately, the platform of choice for my client is WebLogic--and old-school WebLogic at that. So I have no recourse.

Given that constraint though, I have to admit it is really cool that I can deploy an EJB3 app to WebLogic without any worries.

Does anyone else have any experiences or tips they care to share?

Thanks, Norman.