On 22 Nov, marc fleury wrote:
> Hello Peter,
> 
> Project Game Over is done.  We completed *all* targets but the JBoss3.0
> features that we defered (along with EJB 2.0 support)
> 
> Message beans is one of our priorities.  Feel free to help :)


OK, I have started to dig into jboss to do a first experimental
implementation of Message Driven Beans. 

I wrote a private mail to Richard to get some design guidlines, but he
never replied. Here are my design decissions:

1. Message Driven Beans are verry much like Stateless Session beans, but
   without a remote interface and a home. From the Container and down,
   code will be reused or stolen from the Stateless Session stuff. (most
   are already done here)

2. From the container perspective, the only "client" it has is the
   ContainerInvoker. I will therefore implement a specific
   JMSContainerInvoker. The responsibility of this invoker is to set up
   the subsciption against the JMS queue or topic, and when messages
   arive invoke the Interceptor chain.

3. The interaction with JMS will go through the JMS Application Sever
   Facility. This is designed to handle JMS messages cuncurrently, so
   its seems to be the natural choice.

4. Message Driven beans should be able to interact with other
   MOM-systems, such as XmlBlaster. Ideally jboss will be agnostic about
   this from the container and down (using configuration and reflection)
   but I am not shure about this yet. At the ContainerInvoker level its
   pretty straight forward, but I have not verified Transaction handling
   yet).

Problems:

1. Some core classes in jboss have to be extended, for example
   ConatinerFactory, ConfigurationMetaData, ApplicationMetaData and
   probably more.

2. SpyderMQ have no implementation of the JMS ASF. I will work against
   openjms to get this.

3. Some of jboss optimizations will probably be a problem. If I
   understand it correctly jboss will compare remote interfaces to see
   if an invokation is local. Since Message Driven beans don't have a
   remote interface this will crach if it invokes another bean (I have
   not verified this yet).

Well, more will probably pop up. Give me a week or to and we will see (I
only have time to spend one hour or two each evening when my kids have
gone to sleep).

//Peter

> 
> marc
> 
> 
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Peter Antman
> |Sent: Wednesday, November 22, 2000 2:01 AM
> |To: 'jBoss'
> |Subject: [jBoss-User] Message driven Beans
> |
> |
> |Hi,
> |first I should probably say: congratulation to the FINAL. Working good
> |here with perculated beans ;-)
> |
> |To the subject: the old "take over the world" list has disapeared from
> |the website, there for I ask: what are the current plans when it commes
> |to message driven beans? Are someone doing this already? Have someone
> |just the responsibillity for it, but no implementations have been done?
> |Is message driven beans a high priority for jboss, or not?
> |
> |Personally I feel that message driven beans has the highes priority
> |among the EJB 2.0 features.
> |
> |//Peter

> 
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
> 

-- 
------------------------------------------------------------
Peter Antman             Technology in Media, Box 34105 100 26 Stockholm
Systems Architect        WWW: http://www.tim.se
Email: [EMAIL PROTECTED]  WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 
------------------------------------------------------------



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to