We agree.
/********************************** * David Jencks * Partner * Core Developers Network * http://www.coredevelopers.net **********************************/
On Friday, September 26, 2003, at 12:04 PM, Richard Monson-Haefel wrote:
Yes, I agree. That's a solution you can use to get your unit tests in place,
because it allows you to control the delivery of messages and the
interaction between the faux JCA resource and the MDB container. I guess I
was talking about a production system. Still, the MDB container itself
should be designed to adhere to the JCA message-delivery contract even if
the resource you are using is designed purely for testing. Did I understand
your post, or am I off on a tangent?
Richard -- Richard Monson-Haefel Co-Founder\Developer, Apache Geronimo Author of: J2EE Web Services (AW 2003) Enterprise JavaBeans, 4ed (O'Reilly 2004) Java Message Service (O'Reilly 2000) http://www.Monson-Haefel.com
On 9/26/03 2:01 AM, "David Jencks" <[EMAIL PROTECTED]> wrote:
Yes, but James can probably write an mbean that uses the jca 1.5
message delivery contracts and starts the tx appropriately with just
the WorkManager implemented. I did this with the JBoss 4.0 jca 1.5
support testcases until I wrote the jca 1.5 deployment stuff. I.e.,
don't use actual jms, just fake the message delivery part of an adapter.
BTW my opinion ATM is that mdbs don't need an instance pool, the jca 1.5 inbound adapter does that work. All you need is to create MessageEndpoints as requested up to the maximum number you want...
/********************************** * David Jencks * Partner * Core Developers Network * http://www.coredevelopers.net **********************************/ <snip>
