
	Where results make sense

Topic: JDOM

	Chapter 14. JDOM
		JDOM was invented by Brett McLaughlin and Jason Hunter in the Spring of 2000.
		James Strachan forked JDOM in late 2000 to experiment with using interfaces built by factory methods to represent the nodes instead of concrete classes built by constructors.
		JDOM strives to be correct not just with respect to XML but also with respect to Java.
	www.cafeconleche.org /books/xmljava/chapters/ch14.html (1512 words)

	JDOM
		JDOM ist eine XML-Darstellung in der Programmiersprache Java, sie wurde von Jason Hunter und Brett McLaughlin begründet und ist inzwischen eine implementierte API zur Arbeit mit XML in Java.
		JDOM bietet (im Gegensatz zu DOM und SAX) die Möglichkeit, den JDOM- Baum als Textdokument("XMLOutputter",also als XML- Dokument) auszugeben.
		Des Weiteren kann der "SAXOutputter" das Dokument in Form von SAX- Ereignissen ausgeben, wie sie beim Parsen des Dokuments durch SAX auch erzeugt werden würden oder den JDOM- Baum in einen DOM- Baum konvertieren ("DOM- Outputter").
	www.toonorama.com /encyclopedia/J/JDOM (212 words)

	Simplify XML programming with JDOM
		JDOM is a unique Java toolkit for working with XML, engineered to enable rapid development of XML applications.
		In addition, JDOM is not concerned with parsing XML from text input, although it provides wrapper classes that take much of the work out of configuring and running a parser implementation.
		JDOM isn't meant to supercede your favorite parser or XML-aware database, but its design principles make for a particularly rapid learning curve for Java developers entering or well on their way to ruling the XML world.
	www.ibm.com /developerworks/java/library/j-jdom (2551 words)

	XML.com: JDOM and TRaX
		JDOM is an open source API for easily and efficiently reading and writing XML data.
		The goal of JDOM is to solve 80% (or more) of a Java programmer's XML problems with 20% (or less) of the traditional effort.
		JDOM is based around a tree interface similar to the DOM, but does not make use of the W3C DOM interfaces.
	www.xml.com /pub/a/2000/05/03/deviant/index.html (961 words)

	XML, DOM, SAX, JAXP und JDOM mit Java
		Mögliche Alternativen zur XML-Behandlung sind JDOM und dom4j.
		Zu JDOM läuft ein Java Specification Requests (JSR 102), vielleicht wird es in zukünftigen J2SE-Versionen enthalten sein.
		' mit JDOM erfüllt, um den unterschiedlichen Programmieraufwand einschätzen zu können.
	www.torsten-horn.de /techdocs/java-xml.htm (2839 words)

	O'Reilly Network: JDOM Provides Fast, Easy Access to XML from Java
		The JDOM Project has a website dedicated to promoting the understanding and use of JDOM (http://jdom.org), and the site has joined the O'Reilly Network, according to O'Reilly officials.
		JDOM is an open source API which provides an alternative to the more complicated APIs such as the Document Object Model (DOM) and the Simple API for XML (SAX).
		JDOM's open source license is the least restrictive license available, enabling developers to use JDOM in creating new products without requiring them to release their own products as open source.
	www.oreillynet.com /pub/a/mediakit/pressrelease/20000427.html (651 words)

	The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 102
		JDOM is already a popular open source product in beta release at http://jdom.org, and with this JSR we hope to define its final 1.0 form.
		JDOM should have a run-time pluggable parser architecture so any DOM or SAX implementation may be used.
		JDOM should not attempt to be an "XML parser" or "XML processor"; rather it should use XML parsers and processors to enable convenient input and output.
	www.jcp.org /en/jsr/detail?id=102 (1170 words)

	JDOM and XML Parsing, Part 2
		JDOM was created after the namespace recommendation was published, so unlike other APIs there's no pre-namespace and deprecated leftovers.
		JDOM provides built-in support for in-memory XSLT transformations, using the JAXP standard interface to XSLT engines.
		JDOM is at Beta 8, with the next beta release producing a near-final API.
	www.oracle.com /technology/oramag/oracle/02-nov/o62odev_jdom.html (1349 words)

	JDOM and XML Parsing, Part 1
		JDOM is an open source library for Java-optimized XML data manipulations.
		One nice perk with JDOM is how easy it can be to move elements within a document or between documents.
		With JDOM the only thing you need to remember is to remove an element before adding it somewhere else, so that you don't create loops in the tree.
	www.oracle.com /technology/oramag/oracle/02-sep/o52jdom.html (2363 words)

	xmlhack: JDOM heads towards Java core
		The acceptance of JDOM as a JSR is significant as it opens the door for JDOM to become a part of the core Java platform.
		JDOM will still be released as open source software, and technical discussion will continue to take place on public mailing lists.
		JDOM is not the same thing as JAXP at all.
	www.xmlhack.com /read.php?item=1093 (215 words)

	Re: JDOM vs. JAXP/Xerces for XML document creation (Site not responding. Last check: 2007-10-15)
		I have yet to > be able to run a significant DOM program on two different DOM > implementations (in Java) without debugging and rewriting some code, > even in those parts that are allegedly standard.
		JDOM has the advantage that there is no specification since it is only one implementation.
		It is true that extending the DOM requires to be implementation specific - most of the DOM implementations are using internal attributes/methods when manipulating the DOM nodes - but still being able to manipulate the extension as a transparent DOM Node is useful.
	www.stylusstudio.com /xmldev/200207/post40590.html (773 words)

	JDOM
		It hasn't been a priority for us, but if the JSR process is willing to work with JDOM without breaking its backward compability, we may push forward with the JSR.
		The biggest work would be in writing the TCK (compatibility test kit).
		XQuery is a new W3C language and the only thing that makes XML manipulation as easy as JDOM.
	www.jdom.org (212 words)

	mySpotter.com - DOM vs. JDOM (Site not responding. Last check: 2007-10-15)
		JDOM has proven to provide more features sooner, while still in beta, and has a lot of potential to expand and improve even more in terms of features and performance.
		But to save you a further headache, you should only consider JDOM and DOM because DOM is already supported in J2SE 1.4 and JDOM has potential to be part of the J2SE core in the future (JDOM is in the JCP).
		With JDOM, it is very easy to accept DOM input using the DOMBuilder class and easy to send DOM as output using the DOMOutputter class, but if you are working primarily in DOM and processors expect DOM then this rules out passing around JDOM documents.
	www.myspotter.com /dom_jdom.shtml (2139 words)

	JDOM: XML Meets Java Meets Open Source (Site not responding. Last check: 2007-10-15)
		One such API is JDOM, an open source project whose goal is to make XML manipulation easier for Java programmers.
		Using an underlying SAX or DOM parser, an XML document is parsed and represented as a Document object.
		JDOM addresses this issue by providing an object representation of the XML document which act as your interface to the information contained in the XML document as well as its structure.
	softwaredev.earthweb.com /sdopen/print/0,,12077_630951,00.html (964 words)

	XML and Web Service Glossary: JDOM (Site not responding. Last check: 2007-10-15)
		Unlike DOM, which has been designed to be used in a variety of Programming Languages, JDOM has been created specifically for the Java Programming Language.
		Thus, JDOM has been optimized for Java, and is easier to use than DOM.
		JDOM is not based on DOM, and it can be used independently from the underlying XML Processor.
	www.dret.net /glossary/jdom (157 words)

	XML Magazine - A Better XML API for Java (Site not responding. Last check: 2007-10-15)
		For example, JDOM relies on the Java2 collection classes when returning collections of elements, unlike DOM, which has defined its own interfaces.
		In JDOM there is no common interface; everything is its own unique type—the org.jdom.Element interface represents all elements.
		Either an Infoset already exists (an XML file maybe), in which case a JDOM document can be built from that Infoset, or the document has to be created in memory as part of the application's processing.
	www.fawcette.com /xmlmag/2002_03/magazine/columns/collaboration/kjones (377 words)

	Easy Java/XML integration with JDOM, Part 1
		JDOM users don't need to have tremendous expertise in XML to be productive and get their jobs done.
		JDOM takes the best concepts from existing APIs and creates a new set of classes and interfaces that provide, in the words of one JDOM user, "the interface I expected when I first looked at org.w3c.dom." JDOM can read from existing DOM and SAX sources, and can output to DOM- and SAX-receiving components.
		JDOM also provides a full document view with random access but, surprisingly, it does not require the entire document to be in memory.
	www.javaworld.com /javaworld/jw-05-2000/jw-0518-jdom.html (1120 words)

	Servlets.com Weblog: JDOM Hits Beta 10
		Brett had already dropped his involvement in late 2000, so he couldn't lead the project, and others who were active in the project didn't want to take the mantle of leadership.
		Looking at JDOM 1.0 now, it's going to be the best, most solid, most tested, and most polished 1.0 product I've ever seen.
		I want to thank everyone, from users to bug finders to bug fixers to redistributors, whose contributions have made JDOM what it is. I also want to thank by name a few of the core contributors.
	www.servlets.com /blog/archives/000054.html (686 words)

	What JDOM doesn’t do
		JDOM loads the entire document tree into memory and keeps it there.
		JDOM is more memory efficient than some DOM implementations and less efficient than others.
		Merely parsing a document with JDOM and then immediately writing it back out again, may create a subtly different document, though it should still contain the same basic information.
	www.ibiblio.org /xml/books/xmljava/chapters/ch14s12.html (330 words)

	JDOM: XML Programming with a Java Touch (Site not responding. Last check: 2007-10-15)
		One such API is JDOM, available from http://www.jdom.org.
		A very nice feature of JDOM is that different parts of the XML document can be created separately.
		You can still use JDOM to do all of the dirty work and then present the result in a standard format.
	softwaredev.earthweb.com /xml/article/0,,10697_641031,00.html (764 words)

	JDOM: Documentation
		Documentation is provided for users wanting to learn more about JDOM before downloading code, and as a reference companion to using the code.
		The JDOM Documentation includes the JDOM Specification and complete JavaDoc for the JDOM project, as well as information related to JDOM such as presentation slides and handouts.
		This series of articles published by Oracle Magazine cover JDOM's Beta 8 release and are the most thorough and up-to-date articles.
	www.jdom.org /downloads/docs.html (403 words)

	JDOM in the Real World, Part 3 (Site not responding. Last check: 2007-10-15)
		JDOM is a simple and straightforward way to handle XML files with Java.
		Best of all, JDOM has been published under an open-source Apache-style license with a wide user and developer community that has developed the application-programming interface (API) to solve real-world problems.
		JDOM is also in the process of going through Sun's Java Community Process (JCP) as a Java Specification Request (JSR)—the first open-source project to become a JSR.
	otn.oracle.com /oramag/oracle/03-mar/o23javaxml.html (1828 words)

	Servlets.com Weblog
		The March/April issue of Oracle Magazine has a new "JDOM in the Real World" article showing how I use JDOM to manage the RSS feeds on Servlets.com, including how I get this entry to show up on the front page.
		Elliotte Rusty Harold asked on jdom-interest today about the "Genesis of JDOM", for his book "Processing XML with Java", and I wrote a little history paper.
		JDOM now includes build-in XPath support with the org.jdom.xpath.XPath class, written by Laurent Bihanic and supported by the Jaxen back-end by default.
	www.servlets.com /blog/jdom.html (1620 words)

	O'Reilly: Java and XML: Interested Parties Apply Here
		JDOM, the Java Document Object Model, is a new API for handling XML from Java.
		Perhaps more important than the JDOM API itself is the shift in paradigm that it represents; instead of forcing Java developers to become XML gurus, it allows developers to leverage their existing Java expertise, and brings XML to them.
		In fact, I would argue that the converse is true: XML gurus, and Java developers who do live and breathe XML, have a responsibility to leave their preconceptions and high standards at the door; and they need to work to make XML easy to use, simple to understand, and exciting to implement.
	java.oreilly.com /news/javaxml_0500.html (1525 words)

	Tip: Using JDOM and XSLT
		You'll learn how to take a JDOM document representation, transform it using the Apache Xalan processor, and obtain the resulting XML as another JDOM document.
		Transforming a document using XSLT is a common task, and JDOM makes the transformation go quite easily once you know how to avoid the missteps.
		Being one of the co-creators of JDOM, I simply couldn't pass up the chance to throw in a few JDOM tips in a series of XML tips and tricks.
	www-106.ibm.com /developerworks/java/library/x-tipjdom.html (739 words)

	Java(TM) Boutique - Java and JDOM: the perfect couple (Site not responding. Last check: 2007-10-15)
		JDOM is a very user-friendly Java API for handling XML documents.
		JDOM builds a tree structure of an XML document in memory, and therefore resembles the DOM API.
		JDOM is made specifically for Java and XML, and is therefore much simpler to use for a Java programmer.
	javaboutique.internet.com /tutorials/JDOM (905 words)

	wer-weiss-was \| "XML-Validierung mit JDOM" \| aus Forum Java
		Zu beachten: Es handelt sich um keine aktuelle Diskussion, daher kann auf die Artikel nicht mehr geantwortet werden.
		Das klappt auch alles ganz gut bis auf die Tatsache, dass der Parser (SAXBuilder) sich ueber ein XML-Tag beschwert, das er fuer ungueltig erklaert.
		Beim Validieren (oder schon beim Einlesen) wirft der JDom Parser eine org.jdom.IllegalTargetException und meldet, dass "xml:stylesheet" fuer ihn nicht erlaubt sei.
	www.wer-weiss-was.de /theme35/article1900904.html (246 words)

	O'Reilly: An Interview with Brett McLaughlin
		JDOM provides for developing in XML in a Java-centric world without having to learn new constructs.
		JDOM also approaches XML data without any intention of porting it to C. Chapter 8 in the book gives all the JDOM classes as well as a complete appendix with with an API reference.
		The JDOM API will be open source, and by the time the book is released, there may be another completely native implementation not built on DOM or SAX.
	java.oreilly.com /news/mclaughlin_0500.html (3779 words)

	Re: ANN: JDOM from Arnaud Le Hors on 2000-04-27 (www-dom@w3.org from April to June 2000)
		I'll be the first one to say that the DOM is far from being the cleanest and leanest API one could dream of but, unlike JDOM, at least it truthfully represents XML.
		JDOM appears to fail to even simply represent the XML document tree as it should.
		The way namespaces are handled show a clear misunderstanding of the basics of XML namespaces and, unless a serious redesign is undertaken, it will only work for simple cases.
	lists.w3.org /Archives/Public/www-dom/2000AprJun/0090.html (615 words)

	Easy Java/XML integration with JDOM, Part 2
		JDOM accomplishes those tasks, using standard conventions as much as possible, and lets you create, change, or move nearly every document component at runtime.
		One word of warning before we begin: The JDOM API is in beta and subject to change until the 1.0 release.
		That release is expected within the next few months, but it may happen sooner or later, depending on when the JDOM community approves on the solidity of the design and implementation.
	www.javaworld.com /javaworld/jw-07-2000/jw-0728-jdom2.html (826 words)

Try your search on: Qwika (all wikis)