Gents!
I appreciate your advices, but the client application is getting not just the query result ( from Oracle 8.1.6 database ),
but the result of some computations which could not be performed in SQL and hard to do in PL/SQL.
So, I can't just do it by tricky SELECT phrase using ROWNUM pseudocolumn or anything else.
The SessionBean method getWellHistory() execute the query, get the ResultSet and perform some computations like
calculating work time, debits, accumulated values of oil, gas production, watering, etc.
Of course this code can be done in PL/SQL, but I'm developing pure Java application with thin client (Swing) and server side EJBs
and I think its simpler to do it using Java. Besides, while doing computation in the SessionBean I'm sending a progress to
the client application using JMS. It's very important for my users to see the progress of the long operations!
Anyway thanx for the replies! Now I knew a couple of ways to do the subject :)
Nevertheless what you think about using JMS to send the portion of the result? Is it correct?
> 2. Using JMS Queue
> Session bean method execute query, getting data from ResultSet and periodically sending result object to queue.
> Clients are listen for this queue and getting the result. It's seems complicated isn't it? How to restrict the clients receivers to get exactly what they > > requested?
> I am afraid that all of the clients which listen to this queue, no matter what they requested in SessionBean will get large objects and overload the LAN.
> Only today, I read about message selector when creating Message or QueueReceiver. Does it means when I sending the Message from the SessionBean, it > sends only the message header (messageSelector) to all QueueReceivers and then send message body if exists the QueueReceiver for this > > messageSelector?
---
Kirill Mikhailov
