We are providing TCP socket connection to App Server using JCA in the inbound mode . This causes the Message Driven Bean to come into the picture and process the message by giving the message to Stateful Session Bean since we are interested to store some client related information...
Now , [*]how the responce we can send to the client (producer ) [*]The most challenging is that how we can ensure that requests after the second requests will be mapped to the Stateful Session Bean used above [*]Whether inbound mode of JCA can allow only MDB to use for the initial point of contact
In a nutshell , we need to provide inbound communication to Appserver from Client using TCP sockets and also using some Stateful Session beans (to keep track of client)
Will appreciate if you can respond as soon as possible
[*]how the responce we can send to the client (producer )
Not very sure what do you mean by this.... If I understand it correctly do you want to notify the Message Producer that you received the message? If yes then the JMS session has different acknowledge modes. If you want to send another message to the producer then you have to get the CF and send a message to another queue.
[*]The most challenging is that how we can ensure that requests after the second requests will be mapped to the Stateful Session Bean used above I do not see any proper way of doing this... Even if you get it to work... somehow it would be really inefficient. Have you ever given a though of saving the state of your client to the database instead?
[*]Whether inbound mode of JCA can allow only MDB to use for the initial point of contact If you are working with a messaging application then yes, but the good part is you could build your own custom Resource Adapter and use it to invoke anything you want.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com