Hi Jason,

We are using FioranoMQ and it seems to be working well. see:

http://www.fiorano.com/

OrionTeam - If your JMS implementation is good - do speak up. I've read
several emails saying that it is not ready for prime-time and NOT A SINGLE
response from the Orion team saying that it is. I know if someone said these
things about your webserver/servlet/ejb implementations you'd be all over it
like white on rice.

So what's the deal?

Regards,

Mike

----- Original Message -----
From: "Jason Rimmer" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Saturday, October 28, 2000 10:42 PM
Subject: JMS implementation, is it for real?


>     Is Orion's JMS implementation for real?  While it supports the
> simplistic behavior as demonstrated by the chat and coffeemaker demo it
> doesn't appear to support much else.
>     JMS parts I can't get working:
>     o Transactions.  Doesn't seem to matter what you call: commit,
rollback,
> etc.  Doesn't make a difference.
>     o Persistence: Make the change in the jms.xml to define a queue's
> persistent-file, set the message delivery mode to persistent, watch it get
> ignored.
>
>     Has anyone had much luck with this?  Perhaps SwiftMQ is the answer
here
> (even though I want to use the MessageDrivenBeans).
>
> --
> Jason Rimmer
> [EMAIL PROTECTED]
>
>
>
>
>


Reply via email to