[jdom-interest] 28. RE: Why should I have to detach()? (philip.nelson@omniresour
ces.com)
JANSZ,PETER (HP-Roseville,ex1)
peter_jansz at hp.com
Fri Mar 23 08:06:04 PST 2001
-----Original Message-----
From: jdom-interest-admin at jdom.org [mailto:jdom-interest-admin at jdom.org]
Sent: Thursday, March 22, 2001 11:05 PM
To: jdom-interest at jdom.org
Subject: jdom-interest digest, Vol 1 #528 - 33 msgs
Send jdom-interest mailing list submissions to
jdom-interest at jdom.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.denveronline.net/mailman/listinfo/jdom-interest
or, via email, send a message with subject or body 'help' to
jdom-interest-request at jdom.org
You can reach the person managing the list at
jdom-interest-admin at jdom.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of jdom-interest digest..."
Today's Topics:
1. RE: Doctype entity declaration (Harry Evans)
2. RE: using crimson (Kesav Kumar)
3. RE: Doctype entity declaration (Harry Evans)
4. Re: JDOM and JDSL (Dennis Sosnoski)
5. RE: JDOM friendly conferences? (Matthew MacKenzie)
6. using crimson (Lawrence Fry)
7. JDOM Parser and DTD support (Stefan ALBOI)
8. RE: Tomcat and JDOM (Gary Bentley)
9. How to check document before parsing it (Alex Colic)
10. JDOM vs. Java XML Data Binding (Scott Ellsworth)
11. RE: Validation in SAX/DOMBuilders (Eric M. Burke)
12. Re: XML file corrupted by XMLOutputer (Jason Hunter)
13. List messages are flowing freely again (Jason Hunter)
14. Re: JDOM Parser and DTD support (Jason Hunter)
15. Error with JDom? (Chad LaJoie)
16. Re: JDOM 1.0b6 bug in Element.hasChildren()? (Thomas Koch)
17. Re: insert (Laurent ROMEO)
18. Re: insert (Uwe_Hale at i2.com)
19. RE: JDOM friendly conferences? (philip.nelson at omniresources.com)
20. RE: insert (elephantwalker)
21. Re: Implementation of JAXP TraX Source and Resultfor
JDOM (Jason Hunter)
22. Re: Bug in CDATA reading/writing? (Jason Hunter)
23. Why should I have to detach()? (Steven D. Keens)
24. RE: Doctype entity declaration (Harry Evans)
25. Re: JDOM 1.0b6 bug in Element.hasChildren()? (Jason Hunter)
26. RE: Error with JDom? (philip.nelson at omniresources.com)
27. RE: Doctype entity declaration (philip.nelson at omniresources.com)
28. RE: Why should I have to detach()? (philip.nelson at omniresources.com)
29. RE: JDOM vs. Java XML Data Binding (philip.nelson at omniresources.com)
30. RE: JDOM friendly conferences? (philip.nelson at omniresources.com)
31. Re: Error with JDom? (Jason Hunter)
32. Re: Doctype entity declaration (Jason Hunter)
--__--__--
Message: 1
From: Harry Evans <hevans at elite.com>
To: "Jdom-Interest at Jdom. Org" <jdom-interest at jdom.org>
Cc: "'Jason Hunter'" <jhunter at collab.net>
Subject: RE: [jdom-interest] Doctype entity declaration
Date: Wed, 21 Mar 2001 17:16:50 -0800
I have been working on support for Internal and External Entity declarations
within a DocType declaration.
While this is mostly done, I am struggling with how to handle the output of
these declarations with XMLOutputter.
Should I call DocType.getSerializedForm(), and allow this to write out the
"children" declarations, or handle this explicitly in XMLOutputter?
Right now, XMLOutputter.printDocType(...) and DocType.getSerializedForm()
are basically duplicating the same code. Which is the preferred method of
outputting a DocType? Should both methods be modified, or should this be
standardized to one form or the other? Any ideas?
(I realize that SAXOutputter and DOMOutputter will also require some changes
to handle EntityDeclarations, but I started with XMLOutputter because it is
easier conceptually.)
I would like to resolve this so that I can submit a set of diffs and classes
to the list later this week. (Support for the other declaration types in a
DocType are in the works as well.)
Harry Evans
--__--__--
Message: 2
From: Kesav Kumar <kesavk at voquette.com>
To: "'elephantwalker'" <elephantwalker at home.com>, jdom-interest at jdom.org
Subject: RE: [jdom-interest] using crimson
Date: Thu, 22 Mar 2001 15:58:44 -0800
The laest JDOM is compatible for Crimson parser. The SAXBuilder in JDOM
searches for Crimson parser and creates the necessary builder using JAXP
factories.
Kesav Kumar
Software Engineer
Voquette, Inc.
650 356 3740
mailto:kesavk at voquette.com
http://www.voquette.com
Voquette...Delivering Sound Information
-----Original Message-----
From: elephantwalker [mailto:elephantwalker at home.com]
Sent: Tuesday, March 20, 2001 9:59 PM
To: jdom-interest at jdom.org
Subject: [jdom-interest] using crimson
Hello,
I am new to the list, although I have used jdom for about a year. I was
curious to use crimson SAX 2.0 parser for jdom, but noticed that I would
need a direct class name to use SAXBuilder. It appears this is quite
impossible with Crimson, since it uses a factory to get an instance of the
parser (the jaxp stuff).
What should I do?
Regards,
Elephantwalker
.ps I was unsuccessful using the new beta SAX 2.0 parser from Oracle,
because it seems to hangup on the SVG dtd, which makes HEAVY use of
entities.
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--__--__--
Message: 3
From: Harry Evans <hevans at elite.com>
To: "'jdom-interest at jdom.org'" <jdom-interest at jdom.org>
Subject: RE: [jdom-interest] Doctype entity declaration
Date: Thu, 22 Mar 2001 15:59:36 -0800
I have been working on support for Internal and External Entity declarations
within a DocType declaration.
While this is mostly done, I am struggling with how to handle the output of
these declarations with XMLOutputter.
Should I call DocType.getSerializedForm(), and allow this to write out the
"children" declarations, or handle this explicitly in XMLOutputter?
Right now, XMLOutputter.printDocType(...) and DocType.getSerializedForm()
are basically duplicating the same code. Which is the preferred method of
outputting a DocType? Should both methods be modified, or should this be
standardized to one form or the other? Any ideas?
(I realize that SAXOutputter and DOMOutputter will also require some changes
to handle EntityDeclarations, but I started with XMLOutputter because it is
easier conceptually.)
I would like to resolve this so that I can submit a set of diffs and classes
to the list later this week. (Support for the other declaration types in a
DocType are in the works as well.)
Harry Evans
--__--__--
Message: 4
Date: Thu, 22 Mar 2001 16:08:22 -0800
From: Dennis Sosnoski <dms at sosnoski.com>
Organization: Sosnoski Software Solutions, Inc.
To: Bruce Altner <baltner at hq.nasa.gov>
CC: jdom-interest at jdom.org
Subject: Re: [jdom-interest] JDOM and JDSL
The library looks interesting, but the license prohibits any commercial use.
This
makes it pretty much useless for most developers.
- Dennis
Bruce Altner wrote:
> Greetings:
>
> I just came across an article in the April Dr Dobbs Journal about Java
Data
> Structures Library (JDSL), which provides a rich set of APIs for element
> manipulation while still being compatible with the Java Collections
> framework. As I read more, and checked out the web site (see
> www.cs.brown.edu/cgc/jdsl/) it strikes me that, at a fundamental level,
> this library may prove to be extremely valuable to XML developers because
> many of the interfaces should naturally accommodate the structure of XML
> documents.
>
> I am a little too inexperienced at this time to know for sure, but I
> suspect that this might be so. Has anyone applied this library to XML data
> yet? Are there plans to incorporate any of these structures into JDOM?
>
> Thanks,
> Bruce
>
> _______________________________________________
> To control your jdom-interest membership:
>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--__--__--
Message: 5
From: "Matthew MacKenzie" <matt at xmlglobal.com>
To: <philip.nelson at omniresources.com>, <jdom-interest at jdom.org>
Subject: RE: [jdom-interest] JDOM friendly conferences?
Date: Thu, 22 Mar 2001 16:14:01 -0800
Myself and a coworker might be able to make it to a BoF at the SD show,
so that's two more :-)
-Matt
-----Original Message-----
From: jdom-interest-admin at jdom.org [mailto:jdom-interest-admin at jdom.org]
On Behalf Of philip.nelson at omniresources.com
Sent: Wednesday, March 21, 2001 12:51 PM
To: jdom-interest at jdom.org
Subject: RE: [jdom-interest] JDOM friendly conferences?
> Brett and I are speaking on JDOM at the O'Reilly Enterprise Java
> conference later this month. I'm free for a get-together on Tuesday
> night, the 27th. Then I'm speaking at SD West a couple weeks
> later. I
> could be free that Tuesday night too, April 10th.
>
> Phil, do you want to arrange something?
It's a little late for me to get to the O'Reilly conference. I was
worried
that the 4/8-4/12 timeframe might me a little of a travel problem so
close
to the holiday but it looks like the airlines are OK. So I can do
SDExpo,
but nobody else responded.
The idea is to meet somewhere in the evening near the conference center
on
4/10. Any takers?
That night is the start of the Web Services conference. There are
probably
other BOF's going on but the web site doesn't list what they are. I
know
last year, the BOF's were the best part of the show for me.
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@you
rhost.com
--__--__--
Message: 6
From: "Lawrence Fry" <lawrencefry at home.com>
To: <jdom-interest at jdom.org>
Date: Wed, 21 Mar 2001 08:24:41 -0800
Subject: [jdom-interest] using crimson
Hello,
I am new to the list, although I have used jdom for about a year. I was
curious to use crimson SAX 2.0 parser for jdom, but noticed that I would
need a direct class name to use SAXBuilder. It appears this is quite
impossible with Crimson, since it uses a factory to get an instance of the
parser (the jaxp stuff).
What should I do?
Regards,
Elephantwalker
.ps I was unsuccessful using the new beta SAX 2.0 parser from Oracle,
because it seems to hangup on the SVG dtd, which makes HEAVY use of
entities.
--__--__--
Message: 7
Date: Thu, 22 Mar 2001 06:59:32 +0200 (EET)
From: Stefan ALBOI <sbll at ss.pub.ro>
To: jdom-interest at jdom.org
Subject: [jdom-interest] JDOM Parser and DTD support
Good day!
I am watching with great interest the development of JDOM.
There are 2 things I want to ask you about. Here goes:
1. JDOM documents are not build directly, but by using a DOM or SAX
parser and the appropiate adapters. Is there a need for a direct JDOM
Parser from the speed point of view?
2. While building a JDOM document from a DOM document, the internal DTD
gets lost. Is there gonna be a full DTD support in the 1.0 release?
--__--__--
Message: 8
From: "Gary Bentley" <gb at opengroup.org>
To: "Kesav Kumar" <kesavk at voquette.com>, <jdom-interest at jdom.org>
Subject: RE: [jdom-interest] Tomcat and JDOM
Date: Thu, 22 Mar 2001 09:45:39 -0000
The adding to the Tomcat lib dir seems to be better, more reliable and
longer lasting...it also makes my deployment a lot easier as well...
Thanks for the advice though...
G.
-----Original Message-----
From: jdom-interest-admin at jdom.org
[mailto:jdom-interest-admin at jdom.org]On Behalf Of Kesav Kumar
Sent: Wednesday, March 21, 2001 5:30 PM
To: jdom-interest at jdom.org
Subject: RE: [jdom-interest] Tomcat and JDOM
First set your classpath on the local machine which includes
jdom.jar,jaxp.jar and crimson.jar;
Modify the tomcat.bat the line which is set CP=%CP%;%CLASSPATH% to set
CP=%CLASSPATH%;%CP% which makes the system classpath to be first and then
tomcat classes. Make sure that you have clen system classpath.
Kesav Kumar
Software Engineer
Voquette, Inc.
650 356 3740
mailto:kesavk at voquette.com
http://www.voquette.com
Voquette...Delivering Sound Information
-----Original Message-----
From: Gary Bentley [mailto:gb at opengroup.org]
Sent: Wednesday, March 21, 2001 7:39 AM
To: jdom-interest at jdom.org
Subject: RE: [jdom-interest] Tomcat and JDOM
No need to respond...fixed it...
Needed to put the JAR files, jaxp.jar, jdom.jar and crimson.jar in the
$TOMCAT_HOME/lib and ensure that jaxp.jar is overwritten with the newer
version...
Any other info anyone has though would be welcome...
G.
-----Original Message-----
From: jdom-interest-admin at jdom.org
[mailto:jdom-interest-admin at jdom.org]On Behalf Of Gary Bentley
Sent: Wednesday, March 21, 2001 3:10 PM
To: jdom-interest at jdom.org
Subject: [jdom-interest] Tomcat and JDOM
Hi folks,
Probably a simple answer but I'm a bit baffled...
How do I get Tomcat and JDOM 6 to work together? Keep getting:
org.jdom.JDOMException: Error in building: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
Now I can get it to work with JServ...
On Tomcat, I have jaxp.jar, jdom.jar and crimson.jar in the WEB-INF/lib
directory...maybe this is a question for the Tomcat mailing list but I'm
trying here first...
Also, I have expanded the jars into the WEB-INF/classes directory as well...
Now I know that the org.apache.xerces directory is not present (I checked
the Jar)...so why is JDOM looking for it...isn't it supposed to use JAXP by
default now and it should be able to find that...it shoudn't be a class
loader problem since Tomcat is supposed to use a different class loader per
web application...
Cheers (hopefully!),
G.
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--__--__--
Message: 9
From: "Alex Colic" <alex.colic at pop-ware.com>
To: <jdom-interest at jdom.org>
Date: Thu, 22 Mar 2001 09:07:03 -0500
Subject: [jdom-interest] How to check document before parsing it
Hi,
We are using xml as a message packet for one of our network apps. The back
end was not originally designed to work with xml. We have had to customise
it but we presently are not able to get rid of the original message format
of a delimited string. When a critical error occurs the backend can only
send out messages in a delimited string format. My front end needs to do a
check to see if the message it is receiving is a valid xml packet. Is there
a isXML(String) method that I could use that would take a String and pass
back a boolean that the passed String is in xml format?
Any help is appreciated.
Alex
--__--__--
Message: 10
Date: Wed, 21 Mar 2001 12:45:17 -0800
To: jdom-interest at jdom.org
From: Scott Ellsworth <scott at alodar.com>
Subject: [jdom-interest] JDOM vs. Java XML Data Binding
Aleksi Kallio makallio at saunalahti.fi wrote on Mon, 19 Mar 2001 19:01:50
+0200
>What are you opinions on Merlin (ie. JDK 1.4) and its Java XML Data
>Binding? Will it kill JDOM? Will they coexist? Is it even reasonably to
>compare them?
I do not find them reasonable to compare. JDOM is a good tool to do such a
binding before 1.4, but all of my use of the tool is as a means of building
or parsing an XML document. Those documents that are a direct
representation of an object may well end up expressed in the new 1.4 tools,
but most documents I work with are not.
For example, Apple writes out OS X property lists in XML. If I wish to
read such a property list programatically in a Java program, the best way
to do it is likely to read it with JDOM.
A second example: I have a program that generates RuneQuest character
sheets. These are eventually printed from a web browser, and will be done
from pdfs as soon as I learn FOP. I use xalan to generate them from the
core XML format, thus I do not really want them expressed as collections of
objects suited for Java, but as pure structured data to be reformatted for
display in other packages. Thus, the new 1.4 tools will not help me, but
JDOM will.
One of my clients may well end up using it to generate/read a query to be
sent to a rather complicated database. We have not entirely decided yet.
Thus, JDOM and the new tools have very different missions. JDOM exists to
create and interpret disk and memory images of XML, while the new tools in
1.4 are focused on the very important object serialization problem which
has plagued Java from the start. (This limited subset of the overall data
binding problem I suspect they may well have solved, at least in the Swing
domain. The larger scale problem I am less certain of, and do not expect
miracles.)
Scott
Scott Ellsworth
scott at alodar.com
--__--__--
Message: 11
From: "Eric M. Burke" <burke_e at yahoo.com>
To: <jdom-interest at jdom.org>
Subject: RE: [jdom-interest] Validation in SAX/DOMBuilders
Date: Wed, 21 Mar 2001 15:17:42 -0600
I don't think they should be treated differently.
One concern is that some XML parsers will use a
non-standard method of validation that does not
use DTDs or Schemas. In the current JDOM model,
we just tell the parser to "validate", and it
will still work with those parsers.
My second, more immediate concern, is that
this is essentially hard-coding the method of
validation into my Java code. If I write code
today that says "validateDTDs(true)", but a month
from now change my XML data files to use schemas,
I will have to get in there and edit my Java
code, recompile, and re-deploy. I like the
abstraction that the current model employs.
- Eric
>
>
> So when it comes to validation, do you (yes, you, reader...) consider DTD
> validation and schema validation to be separate things, turned on
> separately? For example, when you invoke this method:
>
> public Document build(boolean validate);
>
> in SAXBuilder or DOMBuilder, and send it "true", do you expect that to
> validate both DTDs referenced AND schemas referenced? Just one? Should it
> stay as is, or should it be:
>
> public void validateDTDs(boolean validateDTDs);
> public void validateSchemas(boolean validateSchemas);
> public Document build();
>
> I don't like, fyi,
>
> public Document build(boolean validateDTDs, boolean validateSchemas);
>
> too confusing...
>
> so what do people think?
>
> -Brett
>
> _______________________________________________
> To control your jdom-interest membership:
> http://lists.denveronline.net/mailman/options/jdom-interest/yourad
dr at yourhost.com
--__--__--
Message: 12
Date: Thu, 22 Mar 2001 16:39:43 -0800
From: Jason Hunter <jhunter at collab.net>
To: pys at volga.fr
CC: jdom-interest at jdom.org
Subject: Re: [jdom-interest] XML file corrupted by XMLOutputer
I would suggest you:
a) Try the same remove operation in a standalone app (outside the
servlet environment) because it's likely something fishy is happening
with your servlet output stream.
b) If the corruption still happens, send in the code that reproduces the
problem (even if it only *sometimes* reproduces the problem).
-jh-
pys at volga.fr wrote:
>
> Removing child element from an element using removeContent(Element e) and
> then writing back to the xml file sometimes produces garbage at the end of
> the file for example :
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <messages>
> </messages>
>
> 85019552720">
> <date>19/03/2001&nbsp;&nbsp;17:32</date>
> <texte>message 6</texte>
> </message>
> </messages>
>
> I couldn't figure when exactly this happens. mor often, it happens after
the
> third removing. But sometimes it only happens when removing the last
> element, like in this example. (Not the last in the document, but the last
> when all other elements have been removed, in any order.)
>
> Of course, there is an obvious work arround which consist in making a copy
> of the document without including the removed element, but this is not
very
> satisfying.
>
> Version is Beta 6, used in a servlet, with J2SDK 1.3 and Tomcat 3.1 under
> Win98
> Any idea about what can be going wrong ?
>
> Pierre-Yves Saumont
> Volga Diffusion
> pys at volga.fr
>
> PS : I apologize if it happens that this message was send twice, but I had
a
> server problem while sending it an as I didn't get a copy back in my
> mailbox, I presume it did not get through the first time.
>
> _______________________________________________
> To control your jdom-interest membership:
>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--__--__--
Message: 13
Date: Thu, 22 Mar 2001 16:51:12 -0800
From: Jason Hunter <jhunter at collab.net>
To: JDOM Interest <jdom-interest at jdom.org>
Subject: [jdom-interest] List messages are flowing freely again
As you all probably noticed, posts to this list have been a little
backed up lately but are now coming in droves. We can all thank our
friendly sysadmin DJ for clearing the blockage. Here's what he said in
response to my pestering:
---
It's that darned constipation thing again! :(
Things had been going so well, I thought we'd had the problems licked.
I've cleaned some things up so mail should start flowing again (though
there's enough there that it'll probably take a while to clean up).
I've also done more tweaking of parameters, so maybe THIS TIME it won't
happen again.
---
In the future, if you notice your posts aren't delivered within oh say
two hours, please let me know.
-jh-
3/22 4:51pm PST :-)
--__--__--
Message: 14
Date: Thu, 22 Mar 2001 16:52:56 -0800
From: Jason Hunter <jhunter at collab.net>
To: Stefan ALBOI <sbll at ss.pub.ro>
CC: jdom-interest at jdom.org
Subject: Re: [jdom-interest] JDOM Parser and DTD support
Stefan ALBOI wrote:
>
> 1. JDOM documents are not build directly, but by using a DOM or SAX
> parser and the appropiate adapters. Is there a need for a direct JDOM
> Parser from the speed point of view?
It's not a need, but a native parser might provide a performance
improvement and more easily enable deferred building.
> 2. While building a JDOM document from a DOM document, the internal DTD
> gets lost. Is there gonna be a full DTD support in the 1.0 release?
Yes. You can read in the TODO what's remaining.
-jh-
--__--__--
Message: 15
Date: Thu, 22 Mar 2001 09:11:50 -0500
From: Chad LaJoie <clajoie at vt.edu>
To: jdom-interest at jdom.org
Subject: [jdom-interest] Error with JDom?
I am currently using JDOM to parse external (to my system) RSS
channels. Every time I try to read one I get the following exception
org.jdom.JDOMException: Error on line 1: The root element is required in a
well-formed document.
at org.jdom.input.DOMBuilder.build(DOMBuilder.java:293)
at org.jdom.input.DOMBuilder.build(DOMBuilder.java:342)
at
edu.vt.ward.lexus.widgets.RSSWidget.RSSParser.parse(RSSParser.java:108)
at
edu.vt.ward.lexus.widgets.RSSWidget.RSSParser.updateChannel(RSSParser.java:6
5)
at
edu.vt.ward.lexus.widgets.RSSWidget.RSSChannel.update(RSSChannel.java:543)
Yet when I go and look at the actual RSS file (in this case
http://cnn.com/cnn.rss) it's appears to be just fine. Another gentlemen
the works with me gets the same error when he tries to parse a file on the
local system and again the document is well-formed and have been validated
against the DTD. Has anyone else encountered this and if so what am I
missing here?
For reference here is the code I am using to in my method where the
exception is being encountered.
private RSSChannel parse(URL url) {
try {
DOMBuilder builder = new DOMBuilder();
Document doc = builder.build(url); //this is
line 108
Element root = doc.getRootElement();
.......
}
Chad La Joie "Only a man who can not conquer
IT Specialist his deficiencies feels the need to
IS&C - WARD convince the world he has none"
--__--__--
Message: 16
From: Thomas Koch <Thomas.Koch at atlantec-es.com>
Organization: Atlantec Enterprise Solutions GmbH
Date: Thu, 22 Mar 2001 15:23:41 +0100
To: Ken Rune Helland <kenh at csc.no>, jdom-interest at jdom.org
Subject: Re: [jdom-interest] JDOM 1.0b6 bug in Element.hasChildren()?
Good question. Actually, after looking at Element.java again,
getChildren() uses similar code already. I missed to check
whether objclass was used anywhere else - too much
of a hurry.
Thomas
On Thursday 22 March 2001 12:13, Ken Rune Helland wrote:
> At 11:21 AM 3/22/2001 +0100, Thomas Koch wrote:
> >I believe to have identified a problem with Element.hasChildren()
> >that occurs when Element is subtyped. There is a test for class
> >equality that fails in that case even though it should succeed.
> >
> >See diff below.
> >
> >Thomas
> >
> >
> >*** b6/Element.java Wed Feb 14 20:48:26 2001
> >--- b6-p1/Element.java Thu Mar 22 10:46:43 2001
> >***************
> >*** 742,748 ****
> > while (i.hasNext()){
> > Object obj = i.next();
> > Class objclass = obj.getClass();
> >! if (objclass == Element.class) {
> > return true;
> > }
> > }
> >--- 742,748 ----
> > while (i.hasNext()){
> > Object obj = i.next();
> > Class objclass = obj.getClass();
> >! if (Element.class.isAssignableFrom(objclass)) {
> > return true;
> > }
> > }
>
> Why isnt this just using the instanceof operator?
>
> like:
>
> while (i.hasNext()){
> if (i.next() instanceof Element) {
> return true;
> }
> }
>
> This will return true for Element and all subclasses of element.
> If the second operator to instanceof is a interface it will
> return true for all objects that implements this interface.
>
> Best regards
> KenR
>
>
> _______________________________________________
> To control your jdom-interest membership:
>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourho
>st.com
--__--__--
Message: 17
Date: Thu, 22 Mar 2001 17:08:42 +0100
From: Laurent ROMEO <romeo at agisphere.com>
Organization: AGISphere
To: jdom-interest at jdom.org
Subject: Re: [jdom-interest] insert
--------------1B091024A0EDF98DDEA9165E
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Hi,
Personnally I do the following :
---------------------
// Getting mixed content
Element a = ...
Element c = ...
Element p = a.getParent(); // idem if you get the parent of b element !
java.util.List mixedContent = p.getMixedContent(); // Get the mixed content
of the
parent ( a and c belongs to this List )
// Preparing g
Element b = new Element();
b.addContent( "The middle" );
mixedContent.add( indexOf( c ) , b ); // Javadoc : "The list is live and
modifications to it affect the element's actual content"
------------------------------
Really cool, isn'it ?
Laurent ROMEO.
elephantwalker a écrit :
> don't know this for sure, but is there a way to "insert" and element in a
> particular order?
>
> if I have elements:
>
> <a>
> the beginning
> </a>
> <c>
> the end
> </c>
>
> And I would like to insert <b>the middle</b> in between <a> and <c>, how
is
> it done?
>
> Regards,
>
> Elephantwalker
>
> _______________________________________________
> To control your jdom-interest membership:
>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--
Laurent ROMEO
Directeur Applications
AGISphere
romeo at agisphere.com
(+33)1.47.45.99.99
--------------1B091024A0EDF98DDEA9165E
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<p>Hi,
<p>Personnally I do the following :
<p>---------------------
<br>// Getting mixed content
<br>Element a = ...
<br>Element c = ...
<br>Element p = a.getParent(); // idem if you get the parent
of b element !
<br>java.util.List mixedContent = p.getMixedContent(); // Get the
mixed content of the parent ( a and c belongs to this List )
<p>// Preparing g
<br>Element b = new Element();
<br>b.addContent( "The middle" );
<p>mixedContent.add( indexOf( c ) , b ); // Javadoc : "The list is
live and modifications to it affect the element's actual content"
<br>------------------------------
<br>
<p>Really cool, isn'it ?
<br>
<p>Laurent ROMEO.
<br>
<p>elephantwalker a écrit :
<blockquote TYPE=CITE>don't know this for sure, but is there a way to
"insert"
and element in a
<br>particular order?
<p>if I have elements:
<p><a>
<br> the beginning
<br></a>
<br><c>
<br> the end
<br></c>
<p>And I would like to insert <b>the middle</b> in between <a>
and <c>, how is
<br>it done?
<p>Regards,
<p>Elephantwalker
<p>_______________________________________________
<br>To control your jdom-interest membership:
<br><a
href="http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@y
ourhost.com">http://lists.denveronline.net/mailman/options/jdom-interest/you
raddr at yourhost.com</a></blockquote>
<pre>--
Laurent ROMEO
Directeur Applications
AGISphere
romeo at agisphere.com
(+33)1.47.45.99.99</pre>
</html>
--------------1B091024A0EDF98DDEA9165E--
--__--__--
Message: 18
From: Uwe_Hale at i2.com
Subject: Re: [jdom-interest] insert
To: "elephantwalker" <elephantwalker at home.com>
Cc: jdom-interest at jdom.org, jdom-interest-admin at jdom.org
Date: Thu, 22 Mar 2001 08:55:09 -0600
One way is to get the list of elements and add it at a particular index.
Here is some code I'm using to get around the lack of a setname method.
public static Object changeElementName(Object obj, String name)
{
Element elem = (Element)obj;
Element parentElem = elem.getParent();
List list = parentElem.getChildren();
int index = list.indexOf(elem);
list.remove(index);
list.add(index, elem.getCopy(name));
return list.get(index);
}
Uwe Hale
"elephantwalker"
<elephantwalker at ho To:
<jdom-interest at jdom.org>
me.com> cc:
Sent by: Subject: [jdom-interest]
insert
jdom-interest-admi
n at jdom.org
03/22/01 04:34 AM
don't know this for sure, but is there a way to "insert" and element in a
particular order?
if I have elements:
<a>
the beginning
</a>
<c>
the end
</c>
And I would like to insert <b>the middle</b> in between <a> and <c>, how is
it done?
Regards,
Elephantwalker
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--__--__--
Message: 19
From: philip.nelson at omniresources.com
To: jdom-interest at jdom.org
Subject: RE: [jdom-interest] JDOM friendly conferences?
Date: Thu, 22 Mar 2001 09:54:23 -0600
> Brett and I are speaking on JDOM at the O'Reilly Enterprise Java
> conference later this month. I'm free for a get-together on Tuesday
> night, the 27th. Then I'm speaking at SD West a couple weeks
> later. I
> could be free that Tuesday night too, April 10th.
>
> Phil, do you want to arrange something?
Apologies if you have already received this but I didn't my first post and
it didn't make the list archives.
It's a little late for me to get to the O'Reilly conference. I was worried
that the 4/8-4/12 timeframe might me a little of a travel problem so close
to the holiday but it looks like the airlines are OK. So I can do SDExpo,
but nobody else responded.
The idea is to meet somewhere in the evening near the conference center on
4/10. Any takers?
That day is the start of the Web Services conference but there are not
classes sheduled at that time. There are probably other BOF's going on but
the web site doesn't list what they are. I know last year, the BOF's were
the best part of the show for me.
I will be attending, one way or the other.
--__--__--
Message: 20
From: "elephantwalker" <elephantwalker at home.com>
To: <jdom-interest at jdom.org>
Subject: RE: [jdom-interest] insert
Date: Thu, 22 Mar 2001 08:54:09 -0800
Thanks for all of the posts. Its been awhile since I have used jdom.
-----Original Message-----
From: Uwe_Hale at i2.com [mailto:Uwe_Hale at i2.com]
Sent: Thursday, March 22, 2001 6:55 AM
To: elephantwalker
Cc: jdom-interest at jdom.org; jdom-interest-admin at jdom.org
Subject: Re: [jdom-interest] insert
One way is to get the list of elements and add it at a particular index.
Here is some code I'm using to get around the lack of a setname method.
public static Object changeElementName(Object obj, String name)
{
Element elem = (Element)obj;
Element parentElem = elem.getParent();
List list = parentElem.getChildren();
int index = list.indexOf(elem);
list.remove(index);
list.add(index, elem.getCopy(name));
return list.get(index);
}
Uwe Hale
"elephantwalker"
<elephantwalker at ho To:
<jdom-interest at jdom.org>
me.com> cc:
Sent by: Subject: [jdom-interest]
insert
jdom-interest-admi
n at jdom.org
03/22/01 04:34 AM
don't know this for sure, but is there a way to "insert" and element in a
particular order?
if I have elements:
<a>
the beginning
</a>
<c>
the end
</c>
And I would like to insert <b>the middle</b> in between <a> and <c>, how is
it done?
Regards,
Elephantwalker
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--__--__--
Message: 21
Date: Thu, 22 Mar 2001 10:19:26 -0800
From: Jason Hunter <jhunter at collab.net>
To: Scott Smith <ssmith at summitlogic.com>
CC: JDOM-Interest mailing list <jdom-interest at jdom.org>
Subject: Re: [jdom-interest] Implementation of JAXP TraX Source and
Resultfor
JDOM
As I said, "See the check-in message for details". This is discussed in
there.
-jh-
Scott Smith wrote:
>
> I'm curious. Is this going to get added to jdom itself (not just contrib)
> at some point? This seems to me to be a basic necessity, not an optional
> add-on.
>
> > -----Original Message-----
> > From: Jason Hunter [mailto:jhunter at collab.net]
> > Sent: Thursday, March 22, 2001 5:35 AM
> > To: Laurent Bihanic
> > Cc: JDOM-Interest mailing list
> > Subject: Re: [jdom-interest] Implementation of JAXP TraX Source and
> > Result for JDOM
> >
> >
> > > Please find attached an attempt to implement JAXP 1.1 TRaX
> > source (JDOMSource)
> > > and result (JDOMResult) wrapping JDOM Documents. These
> > classes have been
> > > (lightly) tested with Xalan 2.0.0 and so far are OK.
> >
> > I just added classes based on these to jdom-contrib in the
> > org.jdom.contrib.transform package. See the check-in message for
> > details:
> >
> > http://lists.denveronline.net/lists/jdom-commits/2001-March/00
> > 0537.html
> >
> > > Jason, again, could SAXHandler be made public (maybe in
> > > org.jdom.input.helpers, org.jdom.sax.helpers or something
> > similar) or at least
> > > a protected inner class of SAXbuilder? Once this done,
> > these classes can be
> > > moved anywhere.
> >
> > Done. Others were asking for this too.
> >
> > -jh-
> > _______________________________________________
> > To control your jdom-interest membership:
> > http://lists.denveronline.net/mailman/options/jdom-interest/yo
> uraddr at yourhost.com
> _______________________________________________
> To control your jdom-interest membership:
>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--__--__--
Message: 22
Date: Thu, 22 Mar 2001 10:27:10 -0800
From: Jason Hunter <jhunter at collab.net>
To: Mark Roder <roder at is.com>
CC: "'jdom-interest at jdom.org'" <jdom-interest at jdom.org>
Subject: Re: [jdom-interest] Bug in CDATA reading/writing?
Mark Roder wrote:
>
> Thanks for checking in the new XMLOutputter.java(CVS rev 1.41)
>
> I am noticing a problem that you/someone may be able to track down better
> than I can.
>
> If I construct a outputter with:
> XMLOutputter xmlOut = new XMLOutputter(" ",true);
> And read and then write out a file that contains:
> <Root>
> <ValueOne>This & That</ValueOne>
> <ValueTwo>This <![CDATA[&]]> That</ValueTwo>
>
<LongElem><Tag1>T1</Tag1><Tag2><Tag21>T21</Tag21></Tag2><Tag3>T3</Tag3></Lon
> gElem>
> </Root>
>
> The ValueOne, ValueTwo and LongElem are not indented, but the line before
> them has 2 spaces on it and a newline. Notice it goes
> <Root>\r\n<space><space>\n<ValueOne>.
That's proper behavior. Remember, all whitespace from the original file
is maintained (per the XML spec) and you just asked the outputter to add
an *extra* indent and some *additional* new lines. Since there's
already a lot of new lines in the file, the output isn't terribly pretty
because of the mixing of original and added new lines. Those output
settings are more appropriate if you built the entire document in memory
and there's no pre-existing whitespace for formatting. With a doc from
a file you'll want to setTrimText(true) to see pretty output because
then the outputter can do away with pre-existing whitespace and only add
its own. See the Javadocs where I described the settings for various
kinds of output. The output then is:
<?xml version="1.0" encoding="UTF-8"?>
<Root>
<ValueOne>This & That</ValueOne>
<ValueTwo>This <![CDATA[&]]> That</ValueTwo>
<LongElem>
<Tag1>T1</Tag1>
<Tag2>
<Tag21>T21</Tag21>
</Tag2>
<Tag3>T3</Tag3>
</LongElem>
</Root>
The empty line toward the bottom I'd rather not have there, but it's a
real pain to get rid of (I'll explain the details sometime later if
anyone wants to help fix it), and before worrying about it I wanted to
make sure everything else was OK.
-jh-
--__--__--
Message: 23
From: "Steven D. Keens" <skeens at planetfred.com>
To: "jdom-interest" <jdom-interest at jdom.org>
Date: Thu, 22 Mar 2001 14:25:55 -0500
Subject: [jdom-interest] Why should I have to detach()?
During one of my latest experiences with JDOM I got
an IllegalAddException when calling addContent( Element );
Not seeing any runtime exceptions declared in the docs I
went and looked at the code and found that
IllegalAddException is thrown when the new child element
already has a parent, when adding it to itselt or to a descendant.
I would like to know why? Couldn't addContent() just detach
the new child element automatically from it's parent before
adding it?
The only reason I can see for doing that is to make
the user explicately aware that they are detaching
an element. We had a similar structure in one of our
previous projects and we automatically detached the
child before changing its parent. It was rarely
something that came up and bit us.
--
Steven Keens mailto:skeens at planetfred.com
PlanetFred Inc. http://www.planetfred.com
44 Byward Market, Suite 240, Ottawa, ON, K1N 7A2, Canada
--__--__--
Message: 24
From: Harry Evans <hevans at elite.com>
To: "'jdom-interest at jdom.org'" <jdom-interest at jdom.org>
Subject: RE: [jdom-interest] Doctype entity declaration
Date: Thu, 22 Mar 2001 12:13:17 -0800
I have been working on support for Internal and External Entity declarations
within a DocType declaration.
While this is mostly done, I am struggling with how to handle the output of
these declarations with XMLOutputter.
Should I call DocType.getSerializedForm(), and allow this to write out the
"children" declarations, or handle this explicitly in XMLOutputter?
Right now, XMLOutputter.printDocType(...) and DocType.getSerializedForm()
are basically duplicating the same code. Which is the preferred method of
outputting a DocType? Should both methods be modified, or should this be
standardized to one form or the other? Any ideas?
(I realize that SAXOutputter and DOMOutputter will also require some changes
to handle EntityDeclarations, but I started with XMLOutputter because it is
easier conceptually.)
I would like to resolve this so that I can submit a set of diffs and classes
to the list later this week. (Support for the other declaration types in a
DocType are in the works as well.)
Harry Evans
--__--__--
Message: 25
Date: Thu, 22 Mar 2001 12:41:01 -0800
From: Jason Hunter <jhunter at collab.net>
To: Ken Rune Helland <kenh at csc.no>
CC: Thomas Koch <Thomas.Koch at atlantec-es.com>, jdom-interest at jdom.org
Subject: Re: [jdom-interest] JDOM 1.0b6 bug in Element.hasChildren()?
Ken Rune Helland wrote:
>
> Why isnt this just using the instanceof operator?
>
> like:
>
> while (i.hasNext()){
> if (i.next() instanceof Element) {
> return true;
> }
> }
>
> This will return true for Element and all subclasses of element.
> If the second operator to instanceof is a interface it will
> return true for all objects that implements this interface.
>
> Best regards
> KenR
Just integrated this fix. Thanks, guys.
-jh-
--__--__--
Message: 26
From: philip.nelson at omniresources.com
To: clajoie at vt.edu, jdom-interest at jdom.org
Subject: RE: [jdom-interest] Error with JDom?
Date: Thu, 22 Mar 2001 21:25:00 -0600
I would try to use SAXBuilder and see of the same problem persists. Second,
give use the URL and sample data and maybe we can make more sense of it.
> I am currently using JDOM to parse external (to my system) RSS
> channels. Every time I try to read one I get the following exception
>
> org.jdom.JDOMException: Error on line 1: The root element is
> required in a
> well-formed document.
> at org.jdom.input.DOMBuilder.build(DOMBuilder.java:293)
> at org.jdom.input.DOMBuilder.build(DOMBuilder.java:342)
> at
> edu.vt.ward.lexus.widgets.RSSWidget.RSSParser.parse(RSSParser.
> java:108)
> at
> edu.vt.ward.lexus.widgets.RSSWidget.RSSParser.updateChannel(RS
> SParser.java:65)
> at
> edu.vt.ward.lexus.widgets.RSSWidget.RSSChannel.update(RSSChann
> el.java:543)
>
>
> Yet when I go and look at the actual RSS file (in this case
> http://cnn.com/cnn.rss) it's appears to be just fine.
> Another gentlemen
> the works with me gets the same error when he tries to parse
> a file on the
> local system and again the document is well-formed and have
> been validated
> against the DTD. Has anyone else encountered this and if so
> what am I
> missing here?
>
> For reference here is the code I am using to in my method where the
> exception is being encountered.
>
> private RSSChannel parse(URL url) {
> try {
> DOMBuilder builder = new DOMBuilder();
> Document doc = builder.build(url);
> //this is
> line 108
>
> Element root = doc.getRootElement();
> .......
> }
>
>
> Chad La Joie "Only a man who can not conquer
> IT Specialist his deficiencies
> feels the need to
> IS&C - WARD convince the world he
> has none"
>
> _______________________________________________
> To control your jdom-interest membership:
> http://lists.denveronline.net/mailman/options/jdom-interest/yo
uraddr at yourhost.com
--__--__--
Message: 27
From: philip.nelson at omniresources.com
To: hevans at elite.com, jdom-interest at jdom.org
Subject: RE: [jdom-interest] Doctype entity declaration
Date: Thu, 22 Mar 2001 21:48:40 -0600
> I have been working on support for Internal and External
> Entity declarations
> within a DocType declaration.
>
cool
> While this is mostly done, I am struggling with how to handle
> the output of
> these declarations with XMLOutputter.
>
> Should I call DocType.getSerializedForm(), and allow this to
> write out the
> "children" declarations, or handle this explicitly in XMLOutputter?
>
If you mean, should DocType take a PrintWriter or OutputStream and write to
it I would say that isn't what the classes in org.jdom do IMHO. So I would
say explicitly in the outputters makes sense. If the api you created for
walking the DocType doesn't make it easy, then that could be improved
because that's exactly how others would end up using the class for other
purposes.
> Right now, XMLOutputter.printDocType(...) and
> DocType.getSerializedForm()
> are basically duplicating the same code. Which is the
> preferred method of
> outputting a DocType? Should both methods be modified, or
> should this be
> standardized to one form or the other? Any ideas?
There is a mention about getSerializedForm in the todo. I don't think it
will survive the final cut because of issues of how deep to go and why do it
when we can use outputters to do the same thing. But then there's no
theOutputter(DocType doc) either so ...?
> (I realize that SAXOutputter and DOMOutputter will also
> require some changes
> to handle EntityDeclarations, but I started with XMLOutputter
> because it is
> easier conceptually.)
Yes, makes sense to me.
--__--__--
Message: 28
From: philip.nelson at omniresources.com
To: jdom-interest at jdom.org
Subject: RE: [jdom-interest] Why should I have to detach()?
Date: Thu, 22 Mar 2001 21:59:10 -0600
> I would like to know why? Couldn't addContent() just detach
> the new child element automatically from it's parent before
> adding it?
>
> The only reason I can see for doing that is to make
> the user explicately aware that they are detaching
> an element.
I think that is the reason. Yes you could detach the parent from the child.
But can you automatically detach the child from the parent's content?
Should you? To me this is a little reasonable api reminder to pay
attention. But then, I haven't had a reason to do it myself!
--__--__--
Message: 29
From: philip.nelson at omniresources.com
To: jdom-interest at jdom.org
Subject: RE: [jdom-interest] JDOM vs. Java XML Data Binding
Date: Thu, 22 Mar 2001 22:16:53 -0600
> >What are you opinions on Merlin (ie. JDK 1.4) and its Java XML Data
> >Binding? Will it kill JDOM? Will they coexist? Is it even
> reasonably to
> >compare them?
With the difficulties people are having on 1) what to put in their schemas
2)how to fit their unique business terminology into the language dictated by
industry schemas, and 3) the uncertainty surrounding adoption of schemas,
you have to wonder how good of a plan this is. One friend of mine who is
the ceo of a medium size printing company said there were 75 different xml
"standards" for him to choose from! Would this XML Data Binding api create
an api for my data that I would actually want to use? I think I'll be
skeptical on this api. There wasn't any evidence of activity either. One of
the companies in the JSR has been sold. And, as both are JSR's and don't do
exactly the same thing, I suppose they will both co-exist. But, with luck,
JDOM will be done first....
--__--__--
Message: 30
From: philip.nelson at omniresources.com
To: jdom-interest at jdom.org
Subject: RE: [jdom-interest] JDOM friendly conferences?
Date: Thu, 22 Mar 2001 22:17:55 -0600
> Myself and a coworker might be able to make it to a BoF at
> the SD show,
> so that's two more :-)
>
Better!
I'll see what I can get set up.
--__--__--
Message: 31
Date: Thu, 22 Mar 2001 20:32:40 -0800
From: Jason Hunter <jhunter at collab.net>
To: Chad LaJoie <clajoie at vt.edu>
CC: jdom-interest at jdom.org
Subject: Re: [jdom-interest] Error with JDom?
Sounds like the "Why does passing a document through a socket sometimes
hang the parser?" question in the faq, except this time the parser
complains instead of hanging.
Why are you using DOMBuilder?
-jh-
Chad LaJoie wrote:
>
> I am currently using JDOM to parse external (to my system) RSS
> channels. Every time I try to read one I get the following exception
>
> org.jdom.JDOMException: Error on line 1: The root element is required in a
> well-formed document.
> at org.jdom.input.DOMBuilder.build(DOMBuilder.java:293)
> at org.jdom.input.DOMBuilder.build(DOMBuilder.java:342)
> at
> edu.vt.ward.lexus.widgets.RSSWidget.RSSParser.parse(RSSParser.java:108)
> at
>
edu.vt.ward.lexus.widgets.RSSWidget.RSSParser.updateChannel(RSSParser.java:6
5)
> at
> edu.vt.ward.lexus.widgets.RSSWidget.RSSChannel.update(RSSChannel.java:543)
>
> Yet when I go and look at the actual RSS file (in this case
> http://cnn.com/cnn.rss) it's appears to be just fine. Another gentlemen
> the works with me gets the same error when he tries to parse a file on the
> local system and again the document is well-formed and have been validated
> against the DTD. Has anyone else encountered this and if so what am I
> missing here?
>
> For reference here is the code I am using to in my method where the
> exception is being encountered.
>
> private RSSChannel parse(URL url) {
> try {
> DOMBuilder builder = new DOMBuilder();
> Document doc = builder.build(url); //this is
> line 108
>
> Element root = doc.getRootElement();
> .......
> }
>
> Chad La Joie "Only a man who can not conquer
> IT Specialist his deficiencies feels the need
to
> IS&C - WARD convince the world he has none"
>
> _______________________________________________
> To control your jdom-interest membership:
>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
--__--__--
Message: 32
Date: Thu, 22 Mar 2001 22:53:06 -0800
From: Jason Hunter <jhunter at collab.net>
To: Harry Evans <hevans at elite.com>
CC: "Jdom-Interest at Jdom. Org" <jdom-interest at jdom.org>
Subject: Re: [jdom-interest] Doctype entity declaration
Harry Evans wrote:
>
> I have been working on support for Internal and External Entity
declarations
> within a DocType declaration.
Have you read the commentary I put in TODO recently about this? There's
some questions we need answered.
> While this is mostly done, I am struggling with how to handle the output
of
> these declarations with XMLOutputter.
>
> Should I call DocType.getSerializedForm(), and allow this to write out the
> "children" declarations, or handle this explicitly in XMLOutputter?
>
> Right now, XMLOutputter.printDocType(...) and DocType.getSerializedForm()
> are basically duplicating the same code. Which is the preferred method of
> outputting a DocType?
The standard at the moment is for the object itself to implement
getSerializedForm() and for XMLOutputter to call that method at the
appropriate time. XMLOutputter handles all whitespace issues. This may
not last, as noted in the TODO. But it's a good standard to follow
right now. There's no reason the XMLOutputter doesn't use
doctype.getSerializedForm(), just an oversight.
-jh-
--__--__--
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
End of jdom-interest Digest
More information about the jdom-interest
mailing list