[phpsoa] Re: Randomly appearing strings when working with CDATA

2007-03-12 Thread cdouglas

Is there a way I can email it to you since I can't post it here?


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
phpsoa group.
To post to this group, send email to phpsoa@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.co.uk/group/phpsoa?hl=en
-~--~~~~--~~--~--~---



[phpsoa] Re: Randomly appearing strings when working with CDATA

2007-03-12 Thread simonslaws



On 12 Mar, 15:43, cdouglas [EMAIL PROTECTED] wrote:
 Is there a way I can email it to you since I can't post it here?

Hi Chris

If the data is sensitive/confidential it's better not to send it out
to me. I'll mail you directly and I'll get you to describe the general
shape of the data.

Regards

Simon


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
phpsoa group.
To post to this group, send email to phpsoa@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.co.uk/group/phpsoa?hl=en
-~--~~~~--~~--~--~---



[phpsoa] Re: Randomly appearing strings when working with CDATA

2007-03-12 Thread simonslaws



On 12 Mar, 17:35, cdouglas [EMAIL PROTECTED] wrote:
 An example XML doc structure pulled from the CDATA section of the
 parent xml doc is:

 applicationData
parameterSet
   group name=group1
  parameter name=param1Value/parameter
   /group
  group name=group2
 parameter name=param2value/parameter
  /group
  group name=group3
group name=group4
 parameter name=param4value/parameter
/group
 /group
 /parameterSet
 /applicationData

 An group section is here that demonstrates the issue.  The issue
 occurs 3 times just in this small section, this is typical.
 I am currently running the following commands to clean it up before
 processing.

 $cdata = str_replace(![CDATA[,,$cdata);
 $cdata = str_replace(]],,$cdata);

  gro]]![CDATA[up name=callFlow
 group name=message
 parameter name=allowY/parameter
 /group
 group name=talk
 parameter name=maxDuration600/
 parameter
 /group
 group name=acceptance
 group name=allowMethods
 parameter name=DTMFY/
 parameter
 ]]![CDATA[parameter
 name=VoiceN/parameter
 parameter name=passiveY/
 parameter
 parameter name=PulseN/
 parameter
 /group
 group name=cp
 parameter name=allowY/
 parameter
 /group
 /group
 group name=messages
 parameter name=userDefinedN/
 pa]]![CDATA[rameter
 parameter name=talkOverlayN/
 parameter
 parameter name=talkRandomN/
 parameter
 /group
 /group

Hi Chris

Thanks for that. I tried this by creating a document with 20 or so
ApplicationData elements in CDATA sections and didn't see the effect
you are seeing (am running with the AVOCET branch at the moment). The
places you are seeing the CDATA markers are really strange and it
lookes like they are valid in as much that the CDATA section is
terminated and then started up again. I wonder if this is a buffering
thing somewhere. I.e something reads part of a CDATA secton and sends
a CDATA event which SDO uses to create a CDATA section. As only part
of the CDATA has been read the next part gets put in a separate CDATA
section. Anyhow just thinking aloud as I don't see any references to
this kind of thing in a quick web search. I need to investigate
further!

Regards

Simon


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
phpsoa group.
To post to this group, send email to phpsoa@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.co.uk/group/phpsoa?hl=en
-~--~~~~--~~--~--~---