XOM API for Processing XML with Java

["Orenchak, James" <James.Orenchak AT norcom.de>]

Hi,

I vote for XomParseException.  I'm not crazy about conflicts with core Java
or any other classes!  Using Xom at the beginning would certainly rule out
any possible conflicts.  

Bye the way, could you decide what you're going to call this thing and then
get on with important work, like implementing XSLT Transformations in XOM.
As an old Unix shell scripter, OS/2 REXX writer and desperate Perl hacker,
I'm very comfortable using XSLT.  I cann't wait till a version of XOM comes
out that allows me to easily use XSLT!  I love XOM, but I am missing being
able to use XSLT directly out of XOM.  When can I expect XOM to support XSLT
Tranformations?  


Mit freundlichen Grüßen / Best Regards

James Orenchak 
NorCom Information Technology AG
Solmsstraße 18
D-60486 Frankfurt
Tel + 49 (0) 69 589 96 199         James.Orenchak AT norcom.de
Fax+ 49(0) 69 589 96 111          www.norcom.de

"This email and any attachments contains privileged and confidential
information intended only for the use of the addressee(s). If you are not an
intended recipient of this email, you are hereby notified that any
dissemination, copying or use of information within it is strictly
prohibited. If you received this email in error or without authorisation,
please notify us immediately by reply e-mail and delete the e-mail from your
system. If you need any further assistance, please contact us under
webmaster AT norcom.de"



-----Ursprüngliche Nachricht-----
Von: xom-interest-request AT lists.ibiblio.org
[mailto:xom-interest-request AT lists.ibiblio.org]
Gesendet: Mittwoch, 23. Juli 2003 18:07
An: xom-interest AT lists.ibiblio.org
Betreff: XOM-interest Digest, Vol 6, Issue 13


Send XOM-interest mailing list submissions to
        xom-interest AT lists.ibiblio.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.ibiblio.org/mailman/listinfo/xom-interest
or, via email, send a message with subject or body 'help' to
        xom-interest-request AT lists.ibiblio.org

You can reach the person managing the list at
        xom-interest-owner AT lists.ibiblio.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of XOM-interest digest..."


Today's Topics:

   1. XOM problem (Luc Evers)
   2. Re: XOM problem (Johan Strandberg)
   3. Re: XOM problem (Elliotte Rusty Harold)
   4. Re: Call for Votes: new name for ParseException
      (Elliotte Rusty Harold)
   5. Re: Call for Votes: new name for ParseException (John Cowan)
   6. RE: XOM problem (New, Cecil (GEAE))
   7. Re: Call for Votes: new name for ParseException
      (Elliotte Rusty Harold)
   8. Re: Call for Votes: new name for ParseException (John Cowan)
   9. Re: Call for Votes: new name for ParseException
      (Francois Beausoleil)


----------------------------------------------------------------------

Message: 1
Date: 22 Jul 2003 20:22:45 +0200
From: Luc Evers <luc.evers AT belgacom.net>
Subject: [XOM-interest] XOM problem
To: XOM-interest AT lists.ibiblio.org
Message-ID: <1058898165.5931.7.camel AT localhost.localdomain>
Content-Type: text/plain

Hi,

Before I used Tomcat 4.1.24 and J2sdk1.4.1_01 -> No problem
XOM .jar files were moved to the J2sdk ext directory.

Now I like to use Tomcat 5.04 & J2sdk1.4.2 -> a lot of problems
Tomcat don't work If I copy the XOM .JAR files to the ext directory.
Without this copy, XOM don't work. Even with the correct classpath.

Can you help me?

-> How can I install XOM (xom-1.0d18) ?

 
Best Regards,

Luc,
   


------------------------------

Message: 2
Date: 22 Jul 2003 12:16:55 -0700
From: Johan Strandberg <johan AT acm.org>
Subject: Re: [XOM-interest] XOM problem
To: Luc Evers <luc.evers AT belgacom.net>
Cc: XOM Interest List <xom-interest AT lists.ibiblio.org>
Message-ID: <1058901414.16040.163.camel AT home.strandberg.cc>
Content-Type: text/plain

On Tue, 2003-07-22 at 11:22, Luc Evers wrote:

> Before I used Tomcat 4.1.24 and J2sdk1.4.1_01 -> No problem
> XOM .jar files were moved to the J2sdk ext directory.
> 
> Now I like to use Tomcat 5.04 & J2sdk1.4.2 -> a lot of problems
> Tomcat don't work If I copy the XOM .JAR files to the ext directory.
> Without this copy, XOM don't work. Even with the correct classpath.


Platform?  Windoze I suppose...

Anyway, could you show us the classpath you use now? Does it mention the
jar file itself, or just the directory the jar is in? (Needs to be the
jar itself.)

Have you diff-ed the configuration files between your old and new
Tomcat?


________________________________________________________________________

--j

------------------------------

Message: 3
Date: Wed, 23 Jul 2003 07:55:08 -0400
From: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
Subject: Re: [XOM-interest] XOM problem
To: Luc Evers <luc.evers AT belgacom.net>
Cc: XOM-interest AT lists.ibiblio.org
Message-ID: <p04330101bb4427ccef0a@[192.168.254.4]>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

>Hi,
>
>Before I used Tomcat 4.1.24 and J2sdk1.4.1_01 -> No problem
>XOM .jar files were moved to the J2sdk ext directory.
>
>Now I like to use Tomcat 5.04 & J2sdk1.4.2 -> a lot of problems
>Tomcat don't work If I copy the XOM .JAR files to the ext directory.
>Without this copy, XOM don't work. Even with the correct classpath.
>

Which files specifically do you mean by "XOM .JAR files"? There's 
only one real XOM jar file. The rest of the files in lib may be 
causing conflicts with Tomcat.

Also, Tomcat class loading is tricky., I wouldn't swear that JARs in 
jre/lib/ext are actually loaded when running in Tomcat.
-- 

   Elliotte Rusty Harold
   elharo AT metalab.unc.edu
   Processing XML with Java (Addison-Wesley, 2002)
   http://www.cafeconleche.org/books/xmljava
   http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA

------------------------------

Message: 4
Date: Wed, 23 Jul 2003 08:06:46 -0400
From: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
Subject: Re: [XOM-interest] Call for Votes: new name for
        ParseException
To: xom-interest AT lists.ibiblio.org
Message-ID: <p04330102bb44288219b4@[192.168.254.4]>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 6:24 PM -0500 7/20/03, Bradley S. Huffman wrote:

>XOMParseException. With XOM in the name it's highly unlikely another
>conflict will ever occur.

So I call for a vote and the write-in candidate wins. I don't know. I 
may have to use my veto power on this one. XOMParseException feels 
wrong to me. One reason we have packages is so we don't have to write 
XOMParseException, XOMDocument, XOMNode, XOMText, etc.

Plus, if there's a XOMParseException, I'd sort of expect to see a 
generic XOMException superclass that covers all the exceptions in 
XOM, but I can't really have that because of the distinction between 
checked and runtime exceptions.

For the moment I'm leaning toward XMLParseException. Then again maybe 
I shouldn't do anything at all. This is not the only potential 
conflict. Besides the obvious conflicts with DOM, others include

javax.swing.text.Document
javax.naming.directory.Attribute

ParseException is the only conflict with the core Java classes though.
-- 

   Elliotte Rusty Harold
   elharo AT metalab.unc.edu
   Processing XML with Java (Addison-Wesley, 2002)
   http://www.cafeconleche.org/books/xmljava
   http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA

------------------------------

Message: 5
Date: Wed, 23 Jul 2003 08:43:42 -0400
From: John Cowan <cowan AT mercury.ccil.org>
Subject: Re: [XOM-interest] Call for Votes: new name for
        ParseException
To: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
Cc: xom-interest AT lists.ibiblio.org
Message-ID: <20030723124342.GO2811 AT mercury.ccil.org>
Content-Type: text/plain; charset=us-ascii

Elliotte Rusty Harold scripsit:

> Plus, if there's a XOMParseException, I'd sort of expect to see a 
> generic XOMException superclass that covers all the exceptions in 
> XOM, but I can't really have that because of the distinction between 
> checked and runtime exceptions.

I guess it's too late for this, but is there any hope of my convincing
you that your unchecked exceptions should really be Errors?  Your
contract is to invoke an unchecked exception when the programmer has
blundered, rather than the data being bad.  This is precisely the
contract of Error.

-- 
A poetical purist named Cowan           [that's me:
jcowan AT reutershealth.com]
Once put the rest of us dowan.          [on xml-dev]
    "Your verse would be sweeter        http://www.ccil.org/~cowan
    If it only had metre                http://www.reutershealth.com
And rhymes that didn't force me to frowan."     [overpacked line!] --Michael
Kay

------------------------------

Message: 6
Date: Wed, 23 Jul 2003 08:21:08 -0400
From: "New, Cecil (GEAE)" <cecil.new AT ae.ge.com>
Subject: RE: [XOM-interest] XOM problem
To: Luc Evers <luc.evers AT belgacom.net>, XOM Interest List
        <xom-interest AT lists.ibiblio.org>
Message-ID:
        <B939085A510DAD48BA2A3FDF176501B002CB6D16 AT bwam01msx.ae.ge.com>
Content-Type: text/plain

The standard place for J2EE app libraries is <approot>/WEB-INF/lib

If that doesn't work, then it must be Tomcat classloader issue.

-----Original Message-----
From: Johan Strandberg [mailto:johan AT acm.org]
Sent: Tuesday, July 22, 2003 3:17 PM
To: Luc Evers
Cc: XOM Interest List
Subject: Re: [XOM-interest] XOM problem


On Tue, 2003-07-22 at 11:22, Luc Evers wrote:

> Before I used Tomcat 4.1.24 and J2sdk1.4.1_01 -> No problem
> XOM .jar files were moved to the J2sdk ext directory.
> 
> Now I like to use Tomcat 5.04 & J2sdk1.4.2 -> a lot of problems
> Tomcat don't work If I copy the XOM .JAR files to the ext directory.
> Without this copy, XOM don't work. Even with the correct classpath.


Platform?  Windoze I suppose...

Anyway, could you show us the classpath you use now? Does it mention the
jar file itself, or just the directory the jar is in? (Needs to be the
jar itself.)

Have you diff-ed the configuration files between your old and new
Tomcat?


________________________________________________________________________

--j
_______________________________________________
XOM-interest mailing list
XOM-interest AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/xom-interest

------------------------------

Message: 7
Date: Wed, 23 Jul 2003 09:48:55 -0400
From: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
Subject: Re: [XOM-interest] Call for Votes: new name for
        ParseException
To: John Cowan <cowan AT mercury.ccil.org>
Cc: xom-interest AT lists.ibiblio.org
Message-ID: <p04330103bb44421b1d5f@[192.168.254.4]>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 8:43 AM -0400 7/23/03, John Cowan wrote:

>I guess it's too late for this, but is there any hope of my convincing
>you that your unchecked exceptions should really be Errors?  Your
>contract is to invoke an unchecked exception when the programmer has
>blundered, rather than the data being bad.  This is precisely the
>contract of Error.

That's a new one to me. Where did you get that idea from? It's very 
unusualfor a Java program to throw an Error. Errors almost always 
indicate a failure in the VM that can rarely be predicted or handled, 
e.g. OutOfMemoryError or ClassFormatError. Very few user programs 
should ever throw or even handle errors. The contract of error is not 
that the programmer has blundered. It's that the VM has failed in 
some way.
-- 

   Elliotte Rusty Harold
   elharo AT metalab.unc.edu
   Processing XML with Java (Addison-Wesley, 2002)
   http://www.cafeconleche.org/books/xmljava
   http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA

------------------------------

Message: 8
Date: Wed, 23 Jul 2003 11:18:50 -0400
From: John Cowan <jcowan AT reutershealth.com>
Subject: Re: [XOM-interest] Call for Votes: new name for
        ParseException
To: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
Cc: xom-interest AT lists.ibiblio.org
Message-ID: <20030723151849.GQ15705 AT skunk.reutershealth.com>
Content-Type: text/plain; charset=us-ascii

Elliotte Rusty Harold scripsit:

> That's a new one to me. Where did you get that idea from?  

The 1.4.2 Javadoc for class Error says:

# An Error is a subclass of Throwable that indicates serious problems
# that a reasonable application should not try to catch.

Similarly, the JLS says in section 11.5.2:

# The class Error and its standard subclasses are exceptions from which
# ordinary programs are not ordinarily expected to recover.

JFBP is a component library I wrote where the user writes a small glue class
to
connect the components; you can learn to write glue classes without really
knowing any Java, more or less analogous to shell programming.  If the
components are unable to connect at run time,
the framework throws subclasses of Error to indicate what's wrong.

> unusualfor a Java program to throw an Error. Errors almost always 
> indicate a failure in the VM that can rarely be predicted or handled, 
> e.g. OutOfMemoryError or ClassFormatError. Very few user programs 
> should ever throw or even handle errors. The contract of error is not 
> that the programmer has blundered. It's that the VM has failed in 
> some way.

Not necessarily.  Loading the J2SE 1.4.2 class hierarchy at
http://java.sun.com/j2se/1.4.2/docs/api/overview-tree.html (takes a looong
time to load even over a fast wire), I see the following descendants of
java.lang.Error that don't have those semantics:

java.lang.AssertionError (this is all about programmer faults)
java.nio.charset.CoderMalfunctionError (this indicates an exception in a
  charset decoder or encoder, which is supposed to be "safe code")
javax.xml.parsers.FactoryConfigurationError (the parser factory given in the
  system properties doesn't exist or is broken)
javax.xml.transform.TransformerFactoryConfigurationError (same story, but
for
  a transformation factory)

Indeed, it seems to me that the subclasses of nu.xom.XMLException are all
essentially very like assertion failures, which throw Errors as shown above.

-- 
Is a chair finely made tragic or comic? Is the          John Cowan
portrait of Mona Lisa good if I desire to see
jcowan AT reutershealth.com
it? Is the bust of Sir Philip Crampton lyrical,         www.ccil.org/~cowan
epical or dramatic?  If a man hacking in fury
www.reutershealth.com
at a block of wood make there an image of a cow,
is that image a work of art? If not, why not?               --Stephen
Dedalus

------------------------------

Message: 9
Date: Wed, 23 Jul 2003 11:59:59 -0400
From: "Francois Beausoleil" <fbos AT users.sourceforge.net>
Subject: Re: [XOM-interest] Call for Votes: new name for
        ParseException
To: "John Cowan" <jcowan AT reutershealth.com>,    "Elliotte Rusty Harold"
        <elharo AT metalab.unc.edu>
Cc: xom-interest AT lists.ibiblio.org
Message-ID: <20030723160000.2559774969 AT smtp.us2.messagingengine.com>
Content-Type: text/plain; charset="ISO-8859-1"

I would beg to differ.  Errors should be reserved for things which break
the whole application.  When you receive an Error, we have a catastrophic
failure and we cannot continue.

If a document is malformed, the application can recover by rejecting the
document and/or asking the user to correct the document.  Exceptions are
more appropriate in this case.

Hope that helps,
François

On Wed, 23 Jul 2003 11:18:50 -0400, "John Cowan"
<jcowan AT reutershealth.com> said:
> Elliotte Rusty Harold scripsit:
> 
> > That's a new one to me. Where did you get that idea from?  
> 
> The 1.4.2 Javadoc for class Error says:
> 
> # An Error is a subclass of Throwable that indicates serious problems
> # that a reasonable application should not try to catch.
> 
> Similarly, the JLS says in section 11.5.2:
> 
> # The class Error and its standard subclasses are exceptions from which
> # ordinary programs are not ordinarily expected to recover.
> 
> JFBP is a component library I wrote where the user writes a small glue
> class to
> connect the components; you can learn to write glue classes without
> really
> knowing any Java, more or less analogous to shell programming.  If the
> components are unable to connect at run time,
> the framework throws subclasses of Error to indicate what's wrong.
> 
> > unusualfor a Java program to throw an Error. Errors almost always 
> > indicate a failure in the VM that can rarely be predicted or handled, 
> > e.g. OutOfMemoryError or ClassFormatError. Very few user programs 
> > should ever throw or even handle errors. The contract of error is not 
> > that the programmer has blundered. It's that the VM has failed in 
> > some way.
> 
> Not necessarily.  Loading the J2SE 1.4.2 class hierarchy at
> http://java.sun.com/j2se/1.4.2/docs/api/overview-tree.html (takes a
> looong
> time to load even over a fast wire), I see the following descendants of
> java.lang.Error that don't have those semantics:
> 
> java.lang.AssertionError (this is all about programmer faults)
> java.nio.charset.CoderMalfunctionError (this indicates an exception in a
>   charset decoder or encoder, which is supposed to be "safe code")
> javax.xml.parsers.FactoryConfigurationError (the parser factory given in
> the
>   system properties doesn't exist or is broken)
> javax.xml.transform.TransformerFactoryConfigurationError (same story, but
> for
>   a transformation factory)
> 
> Indeed, it seems to me that the subclasses of nu.xom.XMLException are all
> essentially very like assertion failures, which throw Errors as shown
> above.
> 
> -- 
> Is a chair finely made tragic or comic? Is the          John Cowan
> portrait of Mona Lisa good if I desire to see          
> jcowan AT reutershealth.com
> it? Is the bust of Sir Philip Crampton lyrical,        
> www.ccil.org/~cowan
> epical or dramatic?  If a man hacking in fury          
> www.reutershealth.com
> at a block of wood make there an image of a cow,
> is that image a work of art? If not, why not?               --Stephen
> Dedalus
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest
> 
Developer of Java Gui Builder
http://jgb.sourceforge.net/

------------------------------

_______________________________________________
XOM-interest mailing list
XOM-interest AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/xom-interest


End of XOM-interest Digest, Vol 6, Issue 13
*******************************************