Hello Rickard,
>
...
> processing with the
> > EJB?
>
> Well, since you mentioned the magic words "the method call returns" you
> will at least know you want to use JMS, i.e. MessageDriven Beans. Your
> first EJB will send a message to a queue, with the work to be processed.
> An MDB can then process whatever that is.
> Then you have (at least) two options:
> 1) You can embed an RMI callback object in the message which the
> processing bean can use to call the client. If the client has crashed
> you're in trouble, but that's something you will simply have to account
> for
> 2) Have the processing bean send another message to another queue, and
> have the client listen to that queue.
After thinking to your suggestion, I think it fits quite well in my actual
problem. The only things which make me not completely happy (until now) are
that:
- the work to be done must be serialized (or encoded) in some kind of
message. Do you know of any possibility to have AMI (Asynchronous Method
Invocation) using, for example, JMS and which would deal with these details?
- the MDB has no identity i.e. you cannot send a particular message to a
particular bean i.e. you need to encode this "personnality" in the message
(a little confusing as when you call a method on an non-protected Ada 95
object : myMethod(object, para1, para2).)
In fact, both problems are linked (i.e. with AMI, you generally call a
method on a particular object)
Furthermore, it does not seem possible to dynamically create a new queue and
attach it (at runtime) a MDB instance which would know (by some way) from
which queue it receives messages (onMessage) and thus trying to simulate
this MDB with identity.
Nevertheless, I hadn't in mind these MDB and they will probably (more or
less cleanly) solve my problem. So thank you for this info.
Do you know if the SpyderMQ JMS implementation is running well? I've tried
to find some documentation about it but... Do you know if, as with MSMQ from
MS, it is possible to define domains and have some "routing" taking place
i.e. when a message travels from A to B, it may travel through more than two
hosts (A and B) thus allowing the message to successfully reach B even if
host A and host B are never up at the same time (by using intermediate
nodes).
Thank you. Cheers,
Sacha
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
