java too difficult

When I first started doing java I thought it was the worlds greatest language, anything I wanted to do was in one of the system classes.

However now I'd like to relate a little story:

our company builds commerce sites, and we use perl,java and now .net , I had a project to monitor the servers, and decided to get my hand into xml by creating an ini file and reading it in.

It took me a day to install all the different libs, and get my old apps working again.

In the meantime my co workers had written XML reading / writing services in perl and .net in about half a day. I was still compiling schemas with jaxb?

My compnay has pretty much dropped support for jrun etc. and we are now going fully microsoft. As much as this pains me I can only agree with their decision.

can someone please take java back 2 basics?

how many differnt library packs do we need?

wouldnt an XML pack include everything. (including webservices since these are just xml)?

why do we have so many libraries?

please don't flame me, I'm trying to make a point to help java. because it's just not easy to use anymore.

cheers.

[1182 byte] By [blazeya5a] at [2007-9-29 2:29:34]
# 1

the web services developer pack

http://java.sun.com/webservices/downloads/webservicespack.html

include the xml stuff and tomcat server.

Processing xml is easy with jdom (jdom.org) have you tried it?

It not part SE core api yet but will be.

Chap 14-15

http://www.ibiblio.org/xml/books/xmljava/chapters/ch14.html

Jinoa at 2007-7-13 18:51:04 > top of Java-index,Other Topics,Java Community Process (JCP) Program...
# 2

Processing xml with xmlpull (xmlpull.org) is the easiest overall. Much faster too, especially since you actually control the execution of parsing at your convenience and you can "break out" at any point without having to parse the whole doc. It uses less resources than sax2 and is faster in general than any other parser. If you can live without all the "extras" like dtd validation and schema validation, then xml pull parsing is the way to go. Hell, even the code is super easy to read and figure out! Much better than using event based sax or JDOM which eats up to 8x more memory than the size of the xml file just to load it. And at a small 9K to 20K in size for the entire parser, maybe 50K with read/write capabilities and factory methods and such, it is also the smallest xml parser you'll find. Do yourself a favor and go get it now!

buckman1a at 2007-7-13 18:51:04 > top of Java-index,Other Topics,Java Community Process (JCP) Program...