On 15 Feb, Alexander Kogan wrote:
> Hi,
> 
> [EMAIL PROTECTED] wrote:
>> 
>> Hi,
>> I never see any one using Message Driven Bean here, but any way...
> 
> I've been using MDB (for quite complicated stuff - long optimization
> process with DB access and call for other beans) for 2 weeks already.

Great news,

> 
>> 
>> The examples in jbosstest and in my short howto has been broken for a
>> while. I have not know nabout this since I have not used MDB for a
> 
> Yes, but it was explained to the list.

And I missed it.

> 
>> 
>> Hiriam has fixed this, and MDB are now working correct again. They are
>> now also easier to configure since they now can use the
>> standardjboss.xml file for a standard container configuration (see below
>> for an example).
> 
> Tell me when? Last time (cvs from 02.13.01) it didn't work.
> Is it in CVS now?

A couple of hours before I sent the letter. It should work now.
> 
>> 
>> I also have to tell that MDB are now truly transacted, since Hiriam has
>> implemented both the XA part of the JMS provider and added XA code to
>> the MDB implementation.
> 
> Great!
> 
> 
> Now a question:
> 
> why do I have to put 
> 
> <jms-message-selector></jms-message-selector> in ejb-jar.xml
> 
> and use
> 
> <jms-destination-type> instead of <destination-type> (EJB2.0)
> 
> 

Hm,hopefully because that what was in the spec I read then and that it
has changed(but perhaps because I fumbled). I will check that up.
ejb-jar must be fully spec compliant.

//Peter
> Thanks.
> 

-- 
------------------------------------------------------------
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]
List Help?:          [EMAIL PROTECTED]

Reply via email to