<snip>
>
> JDK 1.1.7 wouldn't be a problem; to my knowledge JMS
> is 1.1.7-compatible.
> Larger problem is WebSphere. WAS does not have it's
> built-in JMS and there is no standard way of pluging
> in an JMS into an app-server. (Even though it is in
> EJB 1.1 a supported resource.)
> I think it could be done, but buying an external JMS
> is pretty expensive. It's easier in for example
> WebLogic where a JMS-implementation is "bundled".
> So let's skip JMS for now.
Not true. WebSphere Enterprise Edition comes bundled with both the App
Server and IBM MQSeries. JMS over MQSeries is the standard way to peform
Queuing in a WebSphere installation.
<snip>
> There are many, many problems of this which is solved
> by JMS (transactions, robustness, security,
> persistence, scaleability etc.). I reiterate that JMS
> is the "correct" solution to this and is definitely
> worth looking into twice. RMI is simply not designed
> to implement this type of publish-subscribe in an
> enterprise-level distributed system
+1.
===========================================================================
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".
