Hemanth Pallavajula

Good one Sandip !!

Kudos to you....

Hi Atul,

I too has faced certain situations like this.

My suggestion is:

1. Take data using Joins statement.
2. Instatiate a String as nameStr, and two ArrayList objects as phonesList & carsList.

3. Now as you get data from the query, for the first row of the resultset:
3.a) Set value of "Name" column to nameStr.
3.b) Set value of "phone" column to phonesList
3.c) Set value of "car" column to carsList.

4. For subsequent rows from the resultset:
4.a) If value for "phone" column is already present in phonesList, ignore. Else, add it to the list.
4.b) If value for "car" column is already present in carsList, ignore. Else, add it to the list.

5. After the entire resultset is processed, you will get name, phonesList, carsList.

Hi Rohit,

As already mentioned in this thread, you just go ahead and implement what all you learn. No issues, if you face problem(s) while implementing. You can definitely come back to us.

All the best.
[ March 16, 2006: Message edited by: Hemanth Pallavajula ]

Hi Kris,

The T3 protocol is proprietary to BEA Weblogic and this needs to be used while using its JNDI for lookup.

Hi Reddy,

I believe, we use the first approach (con.close()) while closing connections obtained from Connection Pool (Implemented via Data Sources in Weblogic).

Can you please give us the other approaches for closing connection obtained via the Connection Pool.
[ March 15, 2006: Message edited by: Hemanth Pallavajula ]

Hi,

Before we come to conclusion, we need to take care of this point.:

As part of BEA Weblogic, we have the concept of MultiPool. Here, we can have connection pools of seperate DBs. The BEA definition goes like this:

A MultiPool is a pool of connection pools. All the connections in a particular connection pool are created identically with a single database, single user, and the same connection attributes; that is, they are attached to a single database. However, the connection pools within a MultiPool may be associated with different users or DBMSs.

But I am not sure of other Application Servers.

Hi Reema,

If you are having SQL queries, for which you don't pass parameter values dynamically, then you can for Statment itself.

Otherwise, PreparedStatement is preferable.

The reason is that the SQL queries being passed to the Oracle are parsed by the DB Engine. If you are using the Statement, everytime the parsing is done, and this impacts the performance. In case, you use PreparedStatement, the parsing is done only once and everytime you send a value it is attached to the query just before execution.

Hi Bill,

You are already on the stage. Just go ahead. The JDBC is same irrespective of the backend it connects to.

Thats why we have interfaces defined as part of the JDBC, and the drivers are DB specific.

All the Best.

Hi

The basic illustration of the problem is:
1. I am having a textbox within a JSP page.
2. The value provided in the text box needs to be processed.
3. For processing the value I need to use a Java method as I need to pick up data from the session.
4. Now the problem is that I am not able to send the value of the textbox to the Java method when onBlur event occurs on the textbox.

Please help me in this regard. I have Googled but was unable to get any help.

Thanks in advance.

Hi,

I have an XML which is of size 8 MB. The size of this XML is increasing constantly. For picking up the data from this XML, we are using Castor.

The problem is that it is increasingly becoming very difficult to maintain this XML. And also, the XML is taking huge space in Cache memory as we are loading this XML from database during the server start-up itself.

Now we are looking a solution through which we can:
1. Split the XML into parts (for better maintainance)
2. Occupy less cache size

and still do the castoring for retrieving the data from the xml.

Thanks in advance

Hi,

Thanks Dave,

The pattern has shown me a new approach for handling this.

Hi All,

I am facing problem regarding pagination of the results. I am putting my problem more clearly to you.

I need to get the data from the database based on 6 values. The data which I get is very huge. This data needs to computed and I need to show the computed data to the user in seperate pages with each comprising 100 rows of data. The search criteria changes with every user.

In regard to my application configuration, I have a web server comprising UI, Action classes. These will communicate with the stateless session facade deployed in an App Server, and I can hit the database only through the App server.

Please provide me a solution so that I can hit the DB as less number of times as possible, and also that I need not store large chunks of data in the session (which is on the web server).

Thanks in advance.

P.S.: If I am wrong in posting this topic here, please move to the correct forum.
[ July 24, 2005: Message edited by: Hemanth Pallavajula ]

Oh! sorry.

I got it. Its StateLess Session Bean.

Hi,

One small doubt, what is the full form of SLSB?

Hi Anirudha,

I think when you are sending messages from the BOX2, the onMessage() method of the MDB is not getting called. You can put an System.out.println(SOP) as the first statement in the onMessage() of your MDB and verify this. As because, this method is not getting called, that message is not getting shown in the JSP.

Please post your reply telling whether the SOP is getting executed or not, when you are sending message from BOX2.

A last word, do check your JMS configuration once, before going ahead.
[ June 25, 2005: Message edited by: Hemanth Pallavajula ]