I've used FioranoMQ previously and have had good luck.  It's quite the
compliant, performant JMS implementation.  The only concerns I have are it's
proprietary persistence mechanism, WebLogic and SonicMQ use JDBC and
Cloudscape respectively, and it's cost (at least compared to Orion).  Of
course Orion also uses it's proprietary filestore for persistence.  Though I
can not claim that it's truly proprietary as I've yet to see it persist a
message.

--
Jason Rimmer
[EMAIL PROTECTED]


----- Original Message -----
From: "Mike Sick" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Sunday, October 29, 2000 11:16 AM
Subject: Re: JMS implementation, is it for real?


> 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