RE:JDOM problem

> This simply isn't true. Subclasses of the standard JDOM classes can > use different storage models than their superclasses. > [...] JDOM can be implemented as a wrapper around other models. How do you do that without having the subclass carry all the (unused) fields from the superclass's storag

RE:JDOM problem

At 1:52 PM -0500 12/9/03, Joseph Kesselman wrote: I still haven't seen realworld evidence that JDOM actually adds much convenience. I've taught DOM and JDOM both numerous times. It's become obvious to me that most developers take a long time to understand DOM if they ever do. JDOM works for them

RE:JDOM problem

At 1:52 PM -0500 12/9/03, Joseph Kesselman wrote: We agree that we disagree. "Only one implementation" means JDOM can't be implemented as a wrapper around other models, which means that unless *everything* you're doing is built around JDOM you have to pay the overhead of copying the data out of s

RE:JDOM problem

We're getting pretty far afield here, so this will probably be my last post on the topic. If the community Really Wants to hear it debated... and if so we should probably find a more appropriate venue. >In practice, the single implementation means JDOM code is more >portable, not less. We ag

DO NOT REPLY [Bug 24886] - XML 1.1 NameChar >= 10000 not recognized

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24579] - [XML 1.0] - E27: Must reject non-shortest forms in UTF-8

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 6878] - XHTML Serializer doctype should be html instead of HTML

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

DO NOT REPLY [Bug 6878] - XHTML Serializer doctype should be html instead of HTML

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

Re: Incorrect/Old XHTML SystemID in org.apache.xml.serialize.HTMLdtd.java

Hello Michael, The second bug [1] you mentioned is actually reported in Bugzilla. Now I remember that I fixed both of these bugs on a local copy of CVS back in the winter (before I was a Xerces committer). I'll see if I've still got those patches around. They were fairly straightforward fixes, so

DO NOT REPLY [Bug 25365] New: - validations against schemas fail

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE:JDOM problem

At 8:47 AM -0500 12/9/03, Joseph Kesselman wrote: By all means, look at it -- but realize that you're buying nonportability of your code in exchange for whatever advantages it might or might not offer. In practice, the single implementation means JDOM code is more portable, not less. DOM code w

RE:JDOM problem

JDOM is not a W3C specification. It's in competition with the W3C DOM. Some of us have strong philosophical objections to JDOM, since its implementation as classes rather than interfaces imposes some serious problems when trying to integrate it with other code. (Basically, there is only one

Re: Incorrect/Old XHTML SystemID in org.apache.xml.serialize.HTMLdtd.java

Also, the root-element name specified in the DOCTYPE in HTMLSerializer is hardcoded to "HTML" (ie. upper-case). For XHTML it should be lower-case. I know that I can get around the previous problem with SystemID by setting it using OutputFormat.setDoctype(), but I don't see a way to workaround

Incorrect/Old XHTML SystemID in org.apache.xml.serialize.HTMLdtd.java

I have noticed that the DOCTYPE used when serializing XHTML using XHTMLSerializer is not the same as that specified on the w3c site - http://www.w3.org/TR/xhtml1/#dtds . It is using a systemID of "http://www.w3.org/TR/WD-html-in-xml/DTD/xhtml1-strict.dtd"; when it should be "http://www.w3.org/T

Re: patch for bug 25347

Hi Kohosuke, I have committed patches for bug no 24124 and 25347 into main trunk. Thanks for the same. Regards, Venu Kohsuke Kawaguchi wrote: See http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25347 for the bug report and please accept the patch to fix this problem: http://nagoya.apache.org/b

RE:JDOM problem

Hi .. Newbie question ... While I was browsing through the JDOM element interface I didn't see any apis as getelementsbytagname ... is there any specific reason for not including such an API. Please point me out for any other such difference between w3c DOM and JDOM specs Excuses if my wordings