I Agree, I ran into another long term issue recently where I needed to update Attributes on the Root tag, can't do it using XPOINTER in Witango 5 or 5.5, I had to create the root tag manually and fillin the guts.
It looks like they put there energies into implementing XPATH and kept XPOINTER the same for backwards compatibility. There comes a point where so many have created workarounds and fixing the bug breaks the work a rounds. Ben Johansen - http://www.pcforge.com Authorized Witango & MDaemon Reseller Available for Witango Developement -----Original Message----- From: John McGowan [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 9:00 AM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: Old Witango XML Bug Because the code I'm writing has to run on 5 now and on 5.5 later. Having it fixed in 5.5 wouldn't have changed my approach that much, because it still wouldn't work now. I'm just diappointed that the new server doesn't have better support. I thought that all the XML stuff was redone. But the fact that this bug still exists tells me that the @DOM related tags are running the same code they used to. I thought they were going to us an external library like xerces for XML parsing and that would apply to xpointer as well. I guess not.... It's okay.. I worked around it for now. I could swear that when we ran into this bug a long time ago we raised an issue with pervasive or with at the time. (this was a long time ago that we first discovered the bug, it affects attributes named "id" as well as elements. /John Ben Johansen wrote: >Well if you are going to 5.5 why not just go with XPATH ;-) and drop >XPOINTER > > >Ben Johansen - http://www.pcforge.com >Authorized Witango & MDaemon Reseller >Available for Witango Developement > >-----Original Message----- >From: John McGowan [mailto:[EMAIL PROTECTED] >Sent: Wednesday, October 27, 2004 8:12 AM >To: [EMAIL PROTECTED] >Subject: Re: Witango-Talk: Old Witango XML Bug > >Thank you Mike... That's not what I was hoping for... > >/John > >Mike Scally wrote: > > > >>Hi John, >> >>We are running Witango 5.5.003 Liquorice (Win32) and I get the same >>results. >> >>id= >>othertag=Y >> >>Mike. >> >>-----Original Message----- >>From: John McGowan [mailto:[EMAIL PROTECTED] >>Sent: 27 October 2004 15:39 >>To: [EMAIL PROTECTED] >>Subject: Witango-Talk: Old Witango XML Bug >> >>Could someone on this side of the globe help me out with something. >> >>There is a bug that exists up to Witango 5.0. For some reason the DOM >>parser can't seem to find elements named "id" >> >>For example, the following code >> >><@assign Name="domvar" Scope="Local" >>Value=<@Dom Value="<root><id>X</id><othertag>Y</othertag></root>"> >> >> >> >>id=<@ELEMENTVALUE >>OBJECT="domvar" >>SCOPE="Local" >>ELEMENT="root().child(1,id)"> >><br> >>othertag=<@ELEMENTVALUE >>OBJECT="domvar" >>SCOPE="Local" >>ELEMENT="root().child(1,othertag)"> >> >>returns >>id= >>othertag=Y >> >>when it should return >>id= X >>othertag=Y >> >>If someone has a 5.5 server could they please run the test taf attached >>to this message just so I can know if the problem is fixed in 5.5. >> >>Thanks, >>John >> >> >> >> >>________________________________________________________________________ >>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> >> >> >> >>******************************************************************** >>This message is intended only for the use of the person(s) ("the intended >>recipient(s)") to whom it is addressed. It may contain information which is >>privileged and confidential within the meaning of applicable law. If you >>are not the intended recipient, please contact the sender as soon as >>possible. The views expressed in this communication may not necessarily >>be the views held by LGCSB (Local Government Computer Services Board). >> >>Any attachments have been checked by a virus scanner and appear to be >>clean. >>Please ensure that you also scan all messages, as LGCSB does not accept >>any liability for contamination or damage to your systems. >>******************************************************************** >> >>________________________________________________________________________ >>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> >> >> >> >> >________________________________________________________________________ >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > >________________________________________________________________________ >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
