Re: xml serializing
Re: xml serializing
- Subject: Re: xml serializing
- From: Jeff Schmitz <email@hidden>
- Date: Wed, 30 Jan 2008 14:47:12 -0600
I don't know if you'd call it "on top". I downloaded the libraries to
a different place, and then updated the WOLips config (actually I just
used the woswitch script that popped up on the message list, but I
think that's pretty much what it did).
I did have xalan and xercesImpl in the webobjects extensions from when
I was playing around trying to fix my previous problem, but I removed
them and restarted and I still get the same thing. I am of course
using the jdom related jars built into my woa bundle as referenced in
my previous problem (jdom-1.0, jaxen-jdom, jaxen-core and saxpath),
but I need to keep those.
On Jan 30, 2008, at 1:39 PM, Chuck Hill wrote:
Did you install that on top of 5.4? Is there anything in /Library/
Java/Extensions or /Library/WebObjects/Extensions that might have a
newer version of XML "stuff"?
Chuck
On Jan 30, 2008, at 11:19 AM, Jeff Schmitz wrote:
I'm seeing this using WO 5.3 on Leopard. I haven't tried it yet
deployed on Tiger/5.3.
On Jan 30, 2008, at 1:11 PM, Chuck Hill wrote:
On Jan 30, 2008, at 9:06 AM, Jeff Schmitz wrote:
Using the NSXmlOutputStream class as described in Practical
Webobjects and passing in a key value, e.g.
xml_stream.writeObject(first(), "first")
I'm getting output with a structure that doesn't match what is
shown in the book. For example, here is a snippet of my output:
<string id="7" xml:space="preserve">jeff</string>
<string idRef="7" key="first"/>
Note the extra level of indirection where the key value is in its
own element that has a reference to another element that contains
the associated key data.
According to the book, and Apple's own documentation, I would
have expected something more like:
<string id="7" key="first" xml:space="preserve">jeff</string>
I'm thinking the format I'm getting is going to make any XSL I
write a little more complicated, and it also worries me that in
the future this format could change, breaking all my xsl's. Any
idea why this might be?
My first, and only, guess is a difference in versions between the
libraries used waaay back when that was written and what you have
installed on your machine. Which WO version? Hopefully there is
some way to control how this gets generated. XSL is annoying
enough for the easy version.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve
specific problems.
http://www.global-village.net/products/practical_webobjects
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden