Avi,
I completely agree with Avi here. Been there a couple of times. Either switch
to a different application server or even better, put pressure on IBM to
release a JMS Provider for IBM MQSeries which has supporty for the XA*
facilities (as outlined by the JMS spec). Once this support is provided, you
can have distributed tansactions between any RDBMS (given there's a JDBC 2.0
compliant JDBC driver implementing the Optional Extensions of this spec) and
MQSeries.
Regards
Werner Guttmann
Avi Kivity wrote:
> > I"m working with a WebSphere application server advanced edition.
> > it doesn't have trasactive Jms Queue. ( the JMS implementation is over
> > MQSeries)
> > i want to implement them using an Oracle DB.
> > meaning to insert message into a Table (my queue). and extracting them
> > later.
> > has anyone ever done this ?
>
> Yes, many have: BEA, Inprise, Sun, practically anyone who ships an app
> server, as well as a few standalone JMS products.
>
> > i"m running into a few problems, desining the table / primary
> > key ( yes
>
> Don't. Either switch your server or buy a standalone JMS application.
> While JMS doesn't seem very difficult, there's no reason to duplicate all
> the work done by the vendors.
>
> - Avi
> --
> s/\be(\w+)/e-\1/g;
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
