This week's book giveaway is in the HTML Pages with CSS and JavaScript forum.
We're giving away four copies of React Cookbook: Recipes for Mastering the React Framework and have David Griffiths & Dawn Griffiths on-line!
See this thread for details.
Win a copy of React Cookbook: Recipes for Mastering the React Framework this week in the HTML Pages with CSS and JavaScript forum!

subramaniam vaidyanathan

+ Follow
since Jun 25, 2001
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by subramaniam vaidyanathan

I have been working with Jaxp, Sax, Dom, Crimson and XP for the past year and it surprises me to see so many people getting all the wrong ideas about what jaxp is. Jaxp is not a parser, it is not a parsing API.. Yes Jaxp is an API, but Sax and Dom are APIs for parsing XML.. Jaxp is an API which can be seen more as a layer on top of a Sax or Dom implementation.. It makes it easier to deal with Sax and Dom tasks.. It is more of an abstraction layer.. Without Sax or Dom or any other XML parsing API, you cannot parse XML.. Jaxp is NOT an XML parsing API.. I beleive part of this misunderstanding is because the jaxp distribution from Sun carries the Crimson parser, the Sax and Dom implementation classes as part of it.. But if we would look closer, we would see that the distribution has actuall two parts, jaxp.jar which is the jaxp API and parser.jar which has nothing to do with Jaxp but is the Crimson parser and implementations of the Sax and Dom API classes.. Hope this helps for a better understanding..
I am working on a project which involves ejbs and regular java classes.. Our team seems to have agreed on a package structure like
com.myproject.mymodule.classes.(the class files here) and com.myproject.mymodule.ejb.myejb.(the ejb files here)
This package structure starts under a folder called code.. There is another team which prefers a package structure like
code/ejb/ com.myproject.mymodule.myejb.(the ejb files here) and
code/classes/ com.myproject.mymodule.(the class files here)
Which of these is the better one? Why? We are working with Weblogic.
I started with Crimson parser which is the parser from Sun. It is a packaged with the JAXP (Java Api for Xml Parsing) download from sun. It is free and fast. XP is another good parser that I've used. If you're starting with Xml using Java, then I would recommend Crimson.

Originally posted by Stanley Tan:
I'm just starting to learn XML. I am also interested in what would be a good parser to start off with.

I'm too green a horn to be able to comment why its not available.. But I did have a similar problem in an application I worked on.. We had to resolve it ourselves.. We did it by having a Timestamp column in the table.. Every read from the table reads the timestamp too for that row.. Every update on that row updates the timestamp to current server time.. Now if a second user updates the row after a first user has read it and then when the first user tries to update the row, the timestamp that he read and that which is on the row now do not match and we do not update.. a simple where conTimeStamp = etc.. etc.. as part of the update statement..
I work with weblogic server. Here is how I get a connection:
DataSource ds = (DataSource) ctx.lookup (dsJNDIName);
conn = ds.getConnection();
and when I am done with it I just close the connection. The welogic server actually releases it.
Basically leave it to the app server to manage the pool.
I have an XML document which contains millions of user records from a database. I need to search that XML document ofr a particular user by his name. How would I go about doing it without having to parse through the whole document till I reach the record. Is there some way I can duplicate the functionality of indexing a column in a database by indexing the XML document by the user name? DOM? ???
Bangalore, India
Check out the following site..
They seem to be selling charting tools.. I have never used them.. But however 'java charting tools' on google seem to return a number of such references.. Maybe you could do it yourself by using the GifEncoder.. check out
20 years ago
I'm Subbu and have 4 years of software development experience. I am extremely strong in server side java (JSP, Servlets, EJB, Jaxp..), javascript, vbscript, XML, ASP and HTML. If you think I would fit this job then do mail me at
Looking forward to your reply,
20 years ago
Hi this has been discussed at this thread
Lets answer your questions all the same
1. limits on density of data: I hope you mean amount of data.. Get can handle much lesser data than Post.. Get can handle as much data as can be appended to the URL (I guess you know that 'Get' data is passed as part of URL).. Now that means it is browser dependent (I'm not sure of this).. All the same 1000 bytes is considered widely as a limit.. As for Post, theoretically it can carry any amoun t of data since now the data is part of the HTTP body... However it makes sense to keep in mind that the lesser data you pass the better.. network etc etc..
2. I guess 1. answers this
3. It is basically more secure to use Post since data is not appended to the URL and is not visible explicitly.. However even Post data is easily retreivable and one should adopt other security mechanisms if the data needs to be secured such as in a transaction based site...
I have quoted below as is from Art Metzers posting in the other mentioned thread..
According to Jason Hunter, author of Java Servlet Programming (an excellent book on the topic of servlets, by the way),
"In practice, the use of GET and POST has strayed from the original intent....Just remember that GET requests, because they can be bookmarked so easily, should not be allowed to cause damage for which the client could be held responsible. In other words, GET requests should not be used to place an order, update a database, or take an explicit client action in any way." (p. 17)
20 years ago
One of the simple ways is to store the resultset data in a vector of hashtables.. i.e each entry in the vector (hashtable) represents a row.. the entries in the hashtable itself are a key value pair of the form column_name = column_value... I hope you see the picture.. i guess you would be doing the database operations in a servlet or bean.. now you attach this vector to the request object as an attribute and forward it to the jsp page.. you can retreive it and dispaly on the jsp..
However there certainly might be better ways to do all this such as maybe a HashMap etc.. but then thats for you to find out..

Originally posted by jay Rotti:
I have a Java Beans which gets result set object. For simplicity I am getting same resultset object to JSP page. I know this is costly affair with connection being open.
I need simple and clean solution to replace this logic.
I have 100 records with 10 columns each.
I know bit about hashtabel, arraylist But I don't know how to store rows and columns and how to fetch them back.
any help appreciated.

[This message has been edited by subramaniam vaidyanathan (edited June 25, 2001).]
20 years ago