> I felt that cfmessage would be very useful as a jms receiver --
> isolating the user from the complexity.
>
> But, you are right, the typical CF app isn't written to sit and listen
> for an asynchronous request,
Yeah, I mean... how would you actually invoke the <cfmessage> tag to
receive a message? It's asynchronous - the message *generates* the
request, there is no existing request to execute CF code until the
message arrives...
> Because CF already has the concept of a CFC, it does seem a natural
> place to implement a jms receiver.
JMS is just one possibility for connecting event gateways. Bear in
mind that the key issue here is that the events are *external* to CF
and it is the Java code that maps them to a CFC method call. The CFC
method itself does not drive the process.
> You could (possible) simplify this interface (for the rest of us) with
> a cfmessage type=receiver... tag.
No you can't. You'd need a request in progress to execute that tag -
the whole point of the event gateway is that it can generate the
requests based on external stimuli. For cfmessage to work, you'd need
a request already in progress...
> > That's it! The Java code
> (this is where you code the requestor or listener, right)
Yes.
> Yeah, I saw that -- I think I understand
Good!
> OpenJMS uses something like:
What you posted looks like a server config file - I posted a client
properties file.
--
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
