Hi Suzan Many thanks for the tip. I temporally solved the problem by avoiding the namespace: path="/data//versicherter". I could migrate to cocoon 2.1.9 if this version solves the problem definitely. Do you know anything about this possibility?
Thx ... Raffaele > -----Ursprüngliche Nachricht----- > Von: Suzan Foster [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 19. Oktober 2006 16:01 > An: [email protected] > Betreff: Re: AW: binding XML (namespace problem) > > Hi Raffaele, > > There are still issues with bindings in the 2.1.8 release with regards > to namespaces. Try omitting the namespace declaration for soap in your > binding definition. > > Merico Raffaele schreef: > > Hi Jeroen > > > > Thanks for your suggestion. But the element gemeldeterLohn is not part > of > > the soap-namespace. It stands as follows in the XML: > > <gemeldeterLohn>....</gemeldeterLohn> > > > > Thx ... Raffaele > > > > > >> -----Ursprüngliche Nachricht----- > >> Von: Jeroen Reijn [mailto:[EMAIL PROTECTED] > >> Gesendet: Donnerstag, 19. Oktober 2006 13:53 > >> An: [email protected] > >> Betreff: RE: binding XML (namespace problem) > >> > >> Hi Merico, > >> > >> the element gemeldeterLohn in your binding file, should it be in the > soap > >> namespace? > >> If so you need to define your fb:value as <fb:value id="lohn" > >> path="soap:gemeldeterLohn"/> > >> > >> Regards, > >> > >> Jeroen Reijn > >> > >> -----Original Message----- > >> From: Merico Raffaele [mailto:[EMAIL PROTECTED] > >> Posted At: Thursday, October 19, 2006 1:25 PM > >> Posted To: Cocoon User List > >> Conversation: binding XML (namespace problem) > >> Subject: binding XML (namespace problem) > >> > >> > >> Dear Community > >> > >> I'm working with cocoon 2.1.8 and I'm fighting with the namespace > >> declaration in the fb:context that looks as follows: > >> > >> <fb:context path="/data/soap:Envelope//versicherter" > >> xmlns:soap="http://www.w3.org/2003/05/soap-envelope";> > >> <fb:value id="lohn" path="gemeldeterLohn"/> > >> </fb:context> > >> > >> If I remove the soap-prefix (also in the XML data) it works fine. > >> Can anybody tell me what's wrong with this declaration of the > namespace. > >> For your support many thanks in advance ... Raffaele > >> > >> --------------------------------------------------------------------- > >> 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] > >> > >> > >> > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
