J2EE specification compliance

[Matthew Phillips]

Is Resin Enterprise fully compliant with the J2EE specification?

[Chris Mathews]

I really like Resin but it seems shaky in this area.
The big absence, for me, is JMS. Almost every project I have worked on over the past two years has utilized MDBs and/or JMS. We can always add on SwiftMQ but I am still disappointed JMS is not built into Resin. Of course it goes without saying, no JMS, no MDBs.
Another feature lacking is BMP Entity Beans. Sure I don't like to write BMPs now, but there are still many applications written using BMP that could be moved to Resin if supported. It seems to me that supporting BMP should be trival to supporting CMP. But then again I don't write EJB Containers .
Not that you need the invitation but what is your take on this Rick?

[Rick Hightower]

Resin supports MDB and JMS. It has a light weight version of JMS, and allows you to integrate with a full fledged version easily.

[Rick Hightower]

I was not aware that Resin does not support BMP... In fact... I think it does.
Hmmmmmmmmmmmmmmmm.....
After close examination of the mailing list... it does support BMP.
I have only used CMP Entities (not BMP) with Resin.
In fact, I started using Resin CMP (now Resin EE) because it was the first commercial product that supported CMP entity beans.
Taken from
http://www.rickhightower.com/ejbcmpcmrtut.html

A self-proclaimed technology masochist, Rick often enjoys working with cutting-edge technologies. "Expect to bleed a lot if you are on the cutting edge", is one of Rick's favorite sayings. On a recent project that predates the EJB 2.0 specification, Rick and others adopted EJB CMP/CMR as there persistence layer of choice before the EJB 2.0 specification was finished.
Many a night, they doubted their decision, but it all worked out in the end. Rick states: "We did not want to use a non-J2EE compliant persistence solution, since we want the freedom of porting our application to other J2EE application servers, and the possibility of selling components that we created. In the end, it looks like going with EJB CMP/CMR was a good decision, but there was some pain along the way as we were using the specification a lot as our main form of documentation, and we were one of the first users of this implementation of CMP/CMR."
"We were able to help the vendor by reporting problems. Some of the problems were our perception of the specification versus the vendors perception of the specification. The vendor was usually right (that said we were credited with reporting (and one time fixing) quite a few bugs)."
"One of the advantages of this decision was our team got to work with a solid implementation of CMP/CMR a long time before it was available anywhere else. We now use EJB CMP-CMR for all projects. I am a big EJB CMP-CMR fan! This new feature will drive the adoption of EJB even further."
Since the team was practicing XP, they were able to come up to speed really fast on EJB CMP/CMR and EJB QL. Pair programming really spread the knowledge as each member learned and shared different parts of EJB CMP/CMR and EJB QL.

Sorry about the third person bit, but I did not want to edit it.... lazy.
[ September 26, 2002: Message edited by: Rick Hightower ]

[Chris Mathews]

Wow. I was pretty far off. I was looking at Resin EE's site and it focuses so heavily on CMP with no mention of any other J2EE technology that I just assumed it wasn't supported. I would think that Caucho would be pushing the whole J2EE angle but they don't.
Here is a link to the Introduction to Resin Enterprise page. It is just CMP, CMP, CMP. I think they are doing themselves a disservice by not pushing all of Resin EE's J2EE features.
I have to say that if Resin EE is anything at all like Resin's Web Container than I'm hooked.
Sorry for being so misinformed.

[Rick Hightower]

I meant to put this here

JMS, the Java Messaging Service, is a elaborated queueing system. Clients add messages to the queues and servers remove the messages.
Resin-EJB's EJB message-bean implementation can use any JMS implementation which conforms to the specifications. Resin-EJB also includes a basic memory-based JMS implementation.

http://www.caucho.com/resin-ee/ejb-ref/messaging.xtp

[Rick Hightower]

Chris wrote

Wow. I was pretty far off. I was looking at Resin EE's site and it focuses so heavily on CMP with no mention of any other J2EE technology that I just assumed it wasn't supported. I would think that Caucho would be pushing the whole J2EE angle but they don't.

Don't feel bad. Resin is mostly an engineering company and there is no fancy marketing campaigns.
(No fluff, just stuff type of thing going on)

[Rick Hightower]

Bingo!

I have to say that if Resin EE is anything at all like Resin's Web Container than I'm hooked.

Yeah... running J2EE apps on Resin... a dream come true! Lightnening Fast, developer friendly.... cool beans.
Resin 3.0 is going to strive to implement J2EE 1.4 including EJB web services support.

[Rick Hightower]

Supports Burlap (SOAP lite), Hessian (fast binary wire protocol) and CORBA,
CORBA Support

EJB 2.0 requires servers to implement CORBA/IIOP as a wire protocol. So in addition to Burlap, Resin-EJB makes CORBA/IIOP available.