Auto-reply: EJB failover/replication?

2002-03-21 Thread Sam Chou 

I am on vacation from 3/1 to 3/22.  Please contact my
manger, Wendy Liau for any issue.

Sam

---BeginMessage---


Hello,

  I'm starting to evaluate Orion as a application server for a project and 
I'm trying to figure out if/how Orion supports EJB failover.  Oracle/AS 
appears to, but I can't tell if thats a feature that they added on top of 
Orion.

If EJB failover/replication is supported, could somebody point me to any 
documentation?

Thanks,

  Michael


---End Message---

Auto-reply: Transactions help - nevermind

2002-03-14 Thread Sam Chou 

I am on vacation from 3/1 to 3/22.  Please contact my
manger, Wendy Liau for any issue.

Sam

---BeginMessage---



Nevermind the last message I wrote on help with 
transactions. I got it. My mind is fluff today. :)

Thanks anyways.

Joe

---End Message---

Auto-reply: Fw: [smq3beta] MDB

2001-11-27 Thread Sam Chou 

Please contact my manager Wendy Liau (650.506.8364) for any issues.

Sam
---BeginMessage---


There is a thread going on the swiftmq 3 beta mailing list about MDBs and
SwiftMQ.

While the resource-provider technique works for MDBs (my MDB gets the
message),
other folks wonder about transactions when using the technique described on
the orionserver
site.

Does anyone know about XA transaction support in this case ?

 - Renaud

- Original Message -
From: Andreas Mueller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 27, 2001 8:28 AM
Subject: [smq3beta] MDB


 That's great! It seems Orion doesn't need ASF to drive the MDBs.

 For the other question: The usual way to drive MDBs is to use the JMS
 provider's application server facilities (ASF) in conjunction with
 distributed transactions (XA). These things are specified in chapter 8 of
 the JMS spec. It is optional for a JMS provider to implement it. SwiftMQ
 doesn't implement it to avoid to the effort to support the different plug-
 in interfaces of the various container provider, because the contract
 between container and JMS provider is unspecified (the JMS spec describes
 only behaviors). There is also a transaction flow problematic which has
 to be addressed.




---End Message---