No. The "XML" fragment you have sent is invalid XML, and so no XSLT processor will be able to read it.
Paul On Wed, May 7, 2008 at 2:08 PM, Stadelmann Josef <[EMAIL PROTECTED]> wrote: > Thanks Paul, > > can I do that with an XSL / XSLT approach? > > Josef > > > -----Ursprüngliche Nachricht----- > Von: Paul Fremantle [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 7. Mai 2008 14:59 > > > An: [email protected] > Betreff: Re: encoding of SOAP responses > > > If you read the XML spec http://www.w3.org/TR/2006/REC-xml-20060816/ > > You will see that [] \ ^ and a number of other characters are not > supported within XML tag names. > > I suggest you change your format to be: > <e:code n="1"> > > Paul > > > On Wed, May 7, 2008 at 1:46 PM, Stadelmann Josef > <[EMAIL PROTECTED]> wrote: > > Hello Paul, > > hello AXIS2 (J/C) experts > > hello XML, XSL, XSLT, LIBXML2, encoding experts! > > > > I have to pass the following result back top my client also receive it at > the server later? > > > > Regarding encoding (better allowed and non-allowed characters) I have to > transive > > the following XML between client and server out from a larger legacy > integration. > > > > :<b:root xmlns:b="SPS-Payload" xmlns:c="COL" xmlns:d="WS" xmlns:e="field"> > > <c:col> > > <d:wsout> > > <e:SELECT/> > > <e:CODE[1]>XXX</e:CODE[1]> > > <e:TARGET>FKT_PUTCODES</e:TARGET> > > <e:OBJEKT[1]>AVT</e:OBJEKT[1]> > > <e:CODE>3X</e:CODE> > > <e:TEXT[1]>ZDK / BMWP</e:TEXT[1]> > > <e:OBJEKT>AVT</e:OBJEKT> > > </d:wsout> > > </c:col> > > </b:root> > > > > this should now be converted to a OMElement and without "[" and "]" it > works. > > however - today - I was told that "[" and "]" are used very frequently > indexing fields. > > > > I was further told - today - that we have "<" amd ">" and that we carry > "&" as well as a few others. > > According W3C Specs I can find how to substitute "&", "<" ">" and a few > more but not "[" and "]" > > > > The interesting thing is that I get field-name field-value pairs in to > AXIS2/C hash tables, then > > create an OMModel from it, then serialize this model to what you see > above, and pass this > > XML string from C Legacy code through JNI back to my Java Axis2 > Web-Service. > > > > And only then, when this string is again converted into an OMElement, > AXIS2/C raises > > an exception. > > > > I agree that certain characters can be parsed while others must be > substituted before > > parsing by an XML reader/parser occures, I ask the following: > > > > 1. What is the prefered way to substitute this "forbiddent" characters > using hopefully AXIS2/C > > and or AXIS2/J AXIOM AXUTIL SW components? > > > > 2. Is XSLT technic the rigth thing to do it; I am still a novice in this > regards. > > > > 3. Would it be possible that "[" and "]" would not lead to an exception > if I would tell AXIS2/J > > webservice server to use for this deserialization a different encoding > schema? > > > > 4. How would you best transive over AXIS2 a PS formatted document? > > > > 5. How would you best transive over AXIS2 a LaTex document? > > > > 6. Binary as MTOM OK? > > > > > > Very thanksfull for a ASAP answer. > > Josef.Stadelmann > > @axa-winterthur.ch > > > > > > > > -----Ursprüngliche Nachricht----- > > Von: Paul Fremantle [mailto:[EMAIL PROTECTED] > > Gesendet: Mittwoch, 13. Februar 2008 18:42 > > An: [email protected] > > Betreff: Re: encoding of SOAP responses > > > > > > > > > > Do you mean you need to use the same encoding as the client sent? > > > > Paul > > > > On Feb 13, 2008 5:35 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > Hello Rushikesh and Paul, > > > > > > > > > > > > thank you very much for your answers. Unfortunately my question was not > > > precise enough. I am not consuming a web service, but offering it. Can I > > > determine the encoding of the SOAP responses my server delivers at > runtime > > > depending on a parameter transmitted in the SOAP Header of the request > also? > > > > > > > > > > > > Thanks for your help, > > > > > > Jan > > > > > > > > -- > > Paul Fremantle > > Co-Founder and VP of Technical Sales, WSO2 > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [EMAIL PROTECTED] > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
