Re: Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-30 Thread Sean Doyle
On 6/30/05, Julian Reschke <[EMAIL PROTECTED]> wrote: > Sean Doyle wrote: > >>> The two reasons that I want to save the metadata without the escape > >>>characters are for byte bloat and because there is server-side code > >>>that examines this metadata. > >> > >> > >>That wouldn't be a well-formed

Re: Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-30 Thread Julian Reschke
Sean Doyle wrote: The two reasons that I want to save the metadata without the escape characters are for byte bloat and because there is server-side code that examines this metadata. That wouldn't be a well-formed XML file anymore. Why would you want that? Let me ask a different way - I d

Re: Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-30 Thread Julian Reschke
John Rousseau wrote: This is the second time this question has come up in a week. Shouldn't slide be storing these properties as CDATA elements so that a more generous set of characters can be used? You end up with a different set of escaping problems; is that worth it? Processing XML files

RE: Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-30 Thread Miguel Figueiredo
That would be nice!! Miguel -Original Message- From: John Rousseau [mailto:[EMAIL PROTECTED] Sent: quinta-feira, 30 de Junho de 2005 14:12 To: Slide Users Mailing List Subject: Re: Using proppatch to set properties with XML results in escaped XML in server metadata file Sean Doyle

Re: Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-30 Thread John Rousseau
Sean Doyle wrote: The two reasons that I want to save the metadata without the escape characters are for byte bloat and because there is server-side code that examines this metadata. That wouldn't be a well-formed XML file anymore. Why would you want that? Let me ask a different way - I d

Re: Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-30 Thread Sean Doyle
> > The two reasons that I want to save the metadata without the escape > > characters are for byte bloat and because there is server-side code > > that examines this metadata. > > > That wouldn't be a well-formed XML file anymore. Why would you want that? Let me ask a different way - I do wan

Re: Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-30 Thread Julian Reschke
Sean Doyle wrote: [This is the same message as before - hopefully the formatting is easier to read] Hi - When I use proppatch to set a property on a resource (a collection in this case) that contains XML the server side file contains the following escaped XML sequences in the property:

Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-29 Thread Sean Doyle
[This is the same message as before - hopefully the formatting is easier to read] Hi - When I use proppatch to set a property on a resource (a collection in this case) that contains XML the server side file contains the following escaped XML sequences in the property: .. ..."

Using proppatch to set properties with XML results in escaped XML in server metadata file

2005-06-29 Thread Sean Doyle
Hi - When I use proppatch to set a property on a resource (a collection in this case) that contains XML the server side file contains the following escaped XML sequences in the property: .. ..." success = wdr.proppatchMethod(newPath, "medcommons", metadata, true); Where do I configure/c