Binod wrote:
> That seems like a good choice. You would also probably know that with
> connector 1.5, you can actually
> deliver non-JMS messages to the MDBs in a portable way.
+1. Someone recently had a similar protocol adapter use-case in GlassFish forums
[1] and was planning to use connectors. There are a set of resources listed in
that thread to help get started.
>> The second is having the JCA Connector manage it's own threads. I know that
>> the JCA architecture has the ability to have work tasks, but I need a little
>> more control on when these tasks run. So I think I would need to manage my
>> communications threads myself.
Did you have any particular scenario in mind when you mentioned this?
Thanks
--Siva.
[1]
http://forums.java.net/jive/message.jspa?messageID=233278
>> Thanks for the feedback. On my ride home from work tonight on my
>> motorcycle, I came to the same conclusion. I think an MBean to
>> communicate with the connector and I'm going to see if I can use the
>> "Work" capability of the JCA to perform the threading. I'm going to
>> see if I can keep the connector "clean" in that it will only be
>> managed through the MBean and will have no knowledge of databases, etc.
>>
>> I should know in a day or so..
>> [Message sent by forum member 'bbergquist' (bbergquist)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=234959
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>