[jdom-interest] unsubscribe

Alex Iskold alex.iskold at thesmallworlds.com
Mon Mar 3 23:31:18 PST 2003 

unsubscribe

----- Original Message -----
From: <jdom-interest-request at jdom.org>
To: <jdom-interest at jdom.org>
Sent: Tuesday, March 04, 2003 2:04 AM
Subject: jdom-interest digest, Vol 1 #1144 - 5 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: jdom b8 jdk 1.4.1 patch (MarkW)
>    2. Parsing extended characters: jdom1.8/tomcat 4.0.6/axis1.0/windows98
(Helen.Watchorn at transwareplc.com)
>    3. Error in my previous email title : jdom B8 and using JDK 1.4.1 (SE)
<eom> (Helen.Watchorn at transwareplc.com)
>    4. Re: How to use importNode in JDOM (Alex Rosen)
>    5. SAXBuilder problems... (Bob.Breitling at rrd.com)
>
> --__--__--
>
> Message: 1
> From: "MarkW" <mark.wilson at wilsoncom.de>
> To: "'Jdom-Interest'" <jdom-interest at jdom.org>
> Subject: RE: [jdom-interest] jdom b8 jdk 1.4.1 patch
> Date: Mon, 3 Mar 2003 09:15:38 +0100
>
> Hello,
> > This is just ridiculous. Download the code from CVS and use it.
> A version with the StringBuffer problem should IMHO be available without
> having to access via CVS.
> What do you do when trying out something for the first time? : you use
> what=B4s easily available and that is at the moment a version which does
> not work with the current version of java.
>
> > Beta 8's dead and gone.
> Then the link to the beta 8 milestone build should be killed.
>
> - Mark
>
> > -----Original Message-----
> > From: jdom-interest-admin at jdom.org=20
> > [mailto:jdom-interest-admin at jdom.org] On Behalf Of Elliotte=20
> > Rusty Harold
> > Sent: Sunday, March 02, 2003 9:46 PM
> > To: 'Jdom-Interest'
> > Subject: RE: [jdom-interest] jdom b8 jdk 1.4.1 patch
> >=20
> >=20
> > This is just ridiculous. Download the code from CVS and use it. A lot=20
> > more things have been fixed besides this problem. There's no reason=20
> > to fork the code here.
> >=20
> > Let's be clear: there have been exactly no JDOM releases to date,=20
> > just betas. There's nothing special about 1.0b8 that indicates you=20
> > should be using it, in fact, just the opposite. If it works for you,=20
> > great. If not, then move up to the current CVS version. If you find a=20
> > problem there, it's worth fixing. Beta 8's dead and gone.
> > --=20
> >=20
> > +-----------------------+------------------------+-------------------+
> > | Elliotte Rusty Harold | elharo at metalab.unc.edu | Writer/Programmer |
> > +-----------------------+------------------------+-------------------+
> > |           Processing XML with Java (Addison-Wesley, 2002)          |
> > |              http://www.cafeconleche.org/books/xmljava             |
> > | http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA  |
> > +----------------------------------+---------------------------------+
> > |  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
> > |  Read Cafe con Leche for XML News: http://www.cafeconleche.org/    |
> > +----------------------------------+---------------------------------+
> > _______________________________________________
> > To control your jdom-interest membership:
> > http://lists.denveronline.net/mailman/options/jdom-interest/yo
> uraddr at yourhost.com
>
>
> --__--__--
>
> Message: 2
> To: jdom-interest at jdom.org
> From: Helen.Watchorn at transwareplc.com
> Date: Mon, 3 Mar 2003 10:11:45 +0000
> Subject: [jdom-interest] Parsing extended characters: jdom1.8/tomcat
4.0.6/axis1.0/windows98
>
> Hi -
>
> I have written a web service that allows the user to enter in keywords,=
>  in
> order to search through XML metadata files, and if found to return a
> learning object. The user may enter keywords that contain extended
> characters, ie =E9 or =ED. The XML metadata files don't declare their e=
> ncoding,
> so by default they are UTF-8. I run the web service using Forte v.4.
>
> I URL.encode all keywords to UTF-8 and pass these keywords to my servle=
> t.
> When I run my servlet I get NULL when I add the line
> request.getCharacterEncoding() therefore I added the line,
> request.setEncoding("UTF-8") at the start of my processRequest() method=
> .
> But then the servlet file wouldn't compile in Forte or at the command l=
> ine.
> [Q.1 Why is this?] I found a workaround where you convert the incoming
> String to a byteArray and then re-write that to a String with UTF-8
> encoding, thus solving the compile problem.
>
> [Q.2] My real problem is that the UTF-8 encoded keyword never matches a=
> ny
> text in the XML metadata file when the keyword contains an extended
> character, [the XML file definitely contains the phrase in question]. T=
> he
> character doesn't display itself correctly in the DOS Command box, but =
> from
> my reading that's because of the underlying code page that I'm using (w=
> hich
> is cp850) so I'm not unduly concerned about the display issue.
>
> I don't know where else to fix or change encoding setup so that extende=
> d
> characters  are matched - is it Tomcat? JDOM? Axis? Windows98?
>
> Any ideas or insights, greatly appreciated.
> Helen
>
> =
>
>
>
> --__--__--
>
> Message: 3
> To: jdom-interest at jdom.org
> From: Helen.Watchorn at transwareplc.com
> Date: Mon, 3 Mar 2003 10:19:33 +0000
> Subject: [jdom-interest] Error in my previous email title : jdom B8 and
using JDK 1.4.1 (SE) <eom>
>
>
> --__--__--
>
> Message: 4
> Date: Mon, 03 Mar 2003 08:32:46 -0700
> From: "Alex Rosen" <arosen at novell.com>
> To: <jdom-interest at jdom.org>, <brett at newInstance.com>,
> <raju at noospherics.com>
> Subject: Re: [jdom-interest] How to use importNode in JDOM
>
> Use clone() or detach() - see the JDOM FAQ.
>
> Alex
>
> >>> "Raju Mukherjee" <raju at noospherics.com> 3/2/2003 1:43:49 PM >>>
> Hi Brett,
>
> I read you article in developer works on importing a childNode or
> Element from one document to another document using DOM.
> http://www-106.ibm.com/developerworks/xml/library/x-tipmvdom.html
>
> I wnat to do the same with JDOM. couldn't figure out how to do that.
> This is what i am trying to do:
>
> a) I have a template.xml
>
>     <root>
>         <element1>
>             <child1/>
>             <child2/>
>         </element>
>     </root>
> b) I want to create a new xml from the template.xml . Also a outside
> process result will tell be how mant <element1> should the new document
> have under <root>
> c) So if the outside process ask me to add 2 such <element1> child
> under the new xml file's <root>, I would have to take the template of
> <element1> from the "template.xml" and add that 2 times under <root> to
> get my new xml file.
> ---------------basically adding row to a database.
>
> You have nicely show that using w3c.dom.Node....but how would I do it
> in JDOM.
>
> Any help is appreciated.
>
> Raju
>
> --__--__--
>
> Message: 5
> To: jdom-interest at jdom.org
> From: Bob.Breitling at rrd.com
> Date: Mon, 3 Mar 2003 09:44:17 -0600
> Subject: [jdom-interest] SAXBuilder problems...
>
> Hello,
>
> I'm trying to use a SAXBuilder object to build a XML document from an URL
> In my case the URL is to a FileMaker Pro 5.5 Web companion running on
> another computer on my local network.  If I access the same URL with my
web
> browser (Netscape 7.02) I get feed back a document.  From my Java program
I
> always get a JDOM exception thrown.
>
> After writing several test programs that try to open a URL I am getting a
> lot of FileNotFound exceptions.  It is almost as though the test programs
> and the SAXBuilder.build(URL) calls are not waiting for the FileMaker DB
> long enough.  None of this is making a lot of sense though.
>
> If I take the data returned to the browser and feed it into JDOM, I get a
> Document object instantiated so if I could get the URL to work I believe I
> would get back a parsable XML document.  The JDOM exception seems to be
> related to not getting anything back and not getting back an invalid XML
> data stream.
>
> The most burning question is how can the browser use the same URL and get
> back an XML document and my SAXBuilder code and my test programs that use
> URL and URLConnections and java.io.* classes to read the URL all fail?
>
> Thanks is advance for any insight into this problem.
>
> Bob Breitling
> RRDonnelley & Sons
>
>
>
>
> --__--__--
>
> _______________________________________________
> 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