Kindly send all your messages to [EMAIL PROTECTED] This mail account is not
functioning anymore.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks. Hope you like them. Nice looking site by the way.
Erik
Vic wrote:
You do need a life.
But... I just bought 2 books from your list.
I keep a track of cool design ideas here: http://sandrasf.com/kiss -
so if anyone wants to append there they can.
(I like "SQL Tuning", "SQL for smartites" an
You do need a life.
But... I just bought 2 books from your list.
I keep a track of cool design ideas here: http://sandrasf.com/kiss - so
if anyone wants to append there they can.
(I like "SQL Tuning", "SQL for smartites" and Doug Lea's book on
concurency.)
.V
Erik Weber wrote:
Joe Germuska wr
Joe Germuska wrote:
Also, while I see your point that the overall concept of DOM might be
more sensible in theory than that of SAX, I found that it's just
easier to get going with the SAX API than with DOM or even JDOM. You
can get something working with very few lines of code, and good
exampl
+1 on JDOM unless you know upfront that the XML file is going to be big
(greater than a couple of MB).
--- sudip shrestha <[EMAIL PROTECTED]> wrote:
> JDOM: http://www.jdom.org/.
> If you are new to xml-java parsing, then this is the way to go. When
> I started learning about xml parsing with
JDOM: http://www.jdom.org/.
If you are new to xml-java parsing, then this is the way to go. When
I started learning about xml parsing with java a while ago, I
researched various methods and found that JDOM provides the easiest
route to get things done. A quote from JDOM mission: "It behaves like
Also, while I see your point that the overall concept of DOM might
be more sensible in theory than that of SAX, I found that it's just
easier to get going with the SAX API than with DOM or even JDOM. You
can get something working with very few lines of code, and good
examples are all over the W
Joe Germuska wrote:
At 8:42 AM -0500 1/14/05, Erik Weber wrote:
If you are not familiar with a lot of XML-related APIs, the easiest
approach is to use the SAX API, in my opinion*.
You may be the first person I've ever encountered who finds SAX the
easiest way to process XML!
Heh. I guess it's
At 8:42 AM -0500 1/14/05, Erik Weber wrote:
If you are not familiar with a lot of XML-related APIs, the easiest
approach is to use the SAX API, in my opinion*.
You may be the first person I've ever encountered who finds SAX the
easiest way to process XML!
* There are higher level APIs that might
9 matches
Mail list logo
