Hello All, I am developing a Data Transfer Application using JMS. It involves sending an automatically generated (from database)XML file to a remote server using JMS Queue. I am using Weblogic Server 7.0. My (simple console) JMS client must have environment (Initial Context) installed on its pc for the messaging to take place. Is it proper 2 have a fat client(with the environment) in this case? What is the best way to do this? Is there any other alternative? Also how does one use a JDBC persistent store in JMS? Any sample code? Kindly help. Thanks in advance. Vivek
Hi Vivek, It is okay to send the xml file using a simple JMS Client(console). Can you please brief on details regarding how the xml file is created, is it the database engine does at a pre-defined time interval, how do you that the file has been generated. JMS does not deal with the persistence mechanism, you have to use the Messaging Service provider. As JMS provides a mechanism to send and receive messages using the Messaging Server. The persistenace is handled by the server in its own way, JMS did not contain the feature of what you are asking about. Hope this helps.
Hi Vivek, I have seen your private message, I feel you post your message so that many people can address. Also I don't prefer private messages. If you want faster response post it in the forum, I am keeping track of the forums I am answering. Please help me to help you.... Also our number of posts gets incremented everytime we post here . This would not be the case otherwise. The main intension is that my answers are watched by many eyes, a security check whether I am right Regarding the JDBC persistence of Messages, You have to check the BEA documentation and since configuring a Messaging Service Provider is not under the scope of J2EE, that will not be available in JMS. I didnot get your point what do you mean by environment, the fat client? Choosing between a fat and thin client depends on the nature of the application and it is recommended if the application needs to accessed from any where in the world then a brower based (thin client) application should be used. Hope this helps.