Re: [xmlc] WML and getElementById() bug

At 09:48 AM 7/20/2005 -0700, Justin Akehurst wrote:
>Your fix for WML getElementById() works! Thanks!
>

Great!  Thanks for verifiying.

>When compiling from HEAD, we noticed there is a missing import in
>/xmlc/xmlc/modules/xmlc/src/org/enhydra/xml/lazydom/html/NameNodeListImpl.java
>It is missing the w3c Element class.

Are you sure you got the HEAD?  Here's the imports I see...

package org.enhydra.xml.lazydom.html;
import org.enhydra.apache.xerces.dom.DeepNodeListImpl;
import org.enhydra.apache.xerces.dom.NodeImpl;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;


Element is certainly one of them.  Either you don't have the HEAD or 
whatever tool you are using is lying to you?  Everything builds fine for 
me.  I suggest you try again.

>
>I would be interested in seeing a 2.2.7 official build come out with
>the WML fix in it.

I'd like to address the URL Rewriting issue before releasing.  In the 
meantime, the current HEAD should remain compatible with the eventual 2.2.7 
release.

Jake

>
>Thanks Jacob,
>
>-Justin
>
>
>On 7/20/05, Jacob Kjome <hoju@xxxxxxxx> wrote:
>> Quoting Justin Akehurst <akehurst@xxxxxxxxx>:
>>
>> > Other than the URL rewriting stuff, is CVS HEAD pretty stable for
>> > production use or should we go off of a tag for the WML fixes?
>> >
>>
>> There is no tag yet other than 2.2.6 and previous releases.  Make sure to
>> remember that XMLC now uses ASM2.0 rather than BCel.  There have been some
>> thoughts as to whether to allow for either configuration or dynamic 
discovery
>> of the byte code interpreter of choice, but the current HEAD is 
hardwired to
>> ASM2.0.  This could be a problem if you have an environment that requires
>> ASM1.5.x.  If that's not the case, you should have no worries.  The URL
>> rewriting stuff should be the only issue in question.  So, yes, the HEAD is
>> pretty stable as far as I'm concerned.  Let me know when you test out 
the WML
>> getElementById() fix.
>>
>>
>> Jake
>>
>> > -Justin
>> >
>> > On 7/20/05, Jacob Kjome <hoju@xxxxxxxx> wrote:
>> > > Quoting Justin Akehurst <akehurst@xxxxxxxxx>:
>> > >
>> > > > Thanks, I'm just now getting around to trying this out to see if it
>will
>> > > > work.
>> > > >
>> > >
>> > > Great!  I'd definitely like to have some validation that the fix works.
>> > >
>> > > > Any timeframe on a 2.2.7 release?
>> > > >
>> > >
>> > > Nothing specific.  No one's been clamoring for a release and I've been
>> > hoping
>> > > that David Li would be looking into the issue of XHTML formatting; 
pretty
>> > > printing and otherwise.  But it seems people are awefully busy these
>days!
>> > One
>> > > fix I applied for URL rewriting also seems to be (unexpectedly) 
adversely
>> > > affecting other behavior when utilized and I have to look into that.
>> > >
>> > > Jake
>> > >
>> > > > -Justin
>> > > >
>> > > > On 4/4/05, Jacob Kjome <hoju@xxxxxxxx> wrote:
>> > > > >
>> > > > > Please try building the latest source to see if it solves the
>issue.  I
>> > > > > also fixed VoiceXML in the same way.  Note that the latest source
>uses
>> > ASM
>> > > > > 2.0RC1 rather than BCel (this will be a 2.2.7 feature) and
>requires the
>> > > > > DOM3 xml-apis.jar to be in both the compile and runtime classpath
>(see
>> > the
>> > > > > 2.2.6 release notes for DOM3 stuff).  If you use JDK1.5, then you
>have
>> > no
>> > > > > worries.  If you have anything less than that, then follow the 
2.2.6
>> > > > > release notes.
>> > > > >
>> > > > > After checking out the source, just type:
>> > > > >
>> > > > > ant all-libs
>> > > > >
>> > > > > If you run on a system less than JDK1.5, I suggest you compile 
under
>> > the
>> > > > > same (or older) JDK as your runtime JDK.  For releases, I use
>> > JDK1.3.1_15
>> > > > > just to make sure that XMLC is bytecode-compatible pretty much
>anywhere
>> > you
>> > > > > run it.
>> > > > >
>> > > > > Let me know how it goes!
>> > > > >
>> > > > > Jake
>> > > > >
>> > > > > At 09:55 AM 4/4/2005 -0700, you wrote:
>> > > > >  >Some of the handsets that our company supports can only 
handle WML
>> > > > >  >1.3, and really freak out and do weird things if given any 
XHTML-MP
>> > > > >  >stuff.  We do both, and on a handset by handset basis decide 
which
>> > > > >  >language to serve.
>> > > > >  >
>> > > > >  >-Justin
>> > > > >  >
>> > > > >  >On Apr 4, 2005 9:33 AM, Jacob Kjome <hoju@xxxxxxxx> wrote:
>> > > > >  >>
>> > > > >  >> Thanks for clarifying.  I see another user also confirms 
this.  I
>> > will
>> > > > > try to
>> > > > >  >> look at this sometime this week.  Hopefully version 2.2.7 will
>have
>> > > > this
>> > > > >  >fixed!
>> > > > >  >>
>> > > > >  >> BTW, any reason you aren't using the XHTMLized versions of WML?
>> > Both
>> > > > > the 1.0
>> > > > >  >> and 2.0 WML XHTML dtd's are part of the XMLC XHTML 
distribution.
>> > > > >  >>
>> > > > >  >> Jake
>> > > > >  >>
>> > > > >  >> Quoting Justin Akehurst <akehurst@xxxxxxxxx>:
>> > > > >  >>
>> > > > >  >> > Yes, we were actually experiencing this problem.
>> > > > >  >> > There is no stack trace since the getElementById() method 
just
>> > > > returns
>> > > > >  >> > null instead of the Element.  Using vers. 2.2.5 of xmlc
>> > > > >  >> >
>> > > > >  >> > I had to write a workaround with XPath to get past the 
problem.
>> > > > >  >> >
>> > > > >  >> > This seems to only happen with WML.  Using XHTML it works as
>> > > > expected.
>> > > > >  >> >
>> > > > >  >> > XMLObject xml;  <-- This is an XMLC class compiled with WML.
>> > > > >  >> > String elementId;
>> > > > >  >> > Element node = xml.getElementById(elementId);
>> > > > >  >> > if (node == null) {
>> > > > >  >> >       node = xpathFind(xml, "//*[@id='" + elementId + "']");
>> > > > >  >> > }
>> > > > >  >> >
>> > > > >  >> > xpathFind() is a small helper method that just does an
>> > > > >  >> > XPathAPI.selectSingleNode() call on the xmlobject.
>> > > > >  >> >
>> > > > >  >> > in my options.xmlc file I have this line:
>> > > > >  >> > domFactory="org.enhydra.wireless.wml.WMLDomFactory"
>> > > > >  >> >
>> > > > >  >> > -Justin
>> > > > >  >> >
>> > > > >  >> >
>> > > > >  >> > On Apr 3, 2005 10:11 PM, Jacob Kjome <hoju@xxxxxxxx> wrote:
>> > > > >  >> > >
>> > > > >  >> > > Justin,
>> > > > >  >> > >
>> > > > >  >> > > Are you actually experiencing this or were you just being
>wary
>> > > > > about the
>> > > > >  >> > > mere discussion of the it?  Can you send a stack 
trace?  What
>> > > > > version of
>> > > > >  >> > > XMLC are you using?
>> > > > >  >> > >
>> > > > >  >> > > Jake
>> > > > >  >> > >
>> > > > >  >> > > At 01:53 PM 3/4/2005 -0800, you wrote:
>> > > > >  >> > >  >Hello,
>> > > > >  >> > >  >
>> > > > >  >> > >  >I noticed some traffic in 2002/2003 about how WML's
>XMLObject
>> > has
>> > > > a
>> > > > >  >> > >  >getElementById() method that just returns null, and that
>> > there
>> > > > was a
>> > > > >  >> > >  >patch to fix it (against LazyDOM).
>> > > > >  >> > >  >
>> > > > >  >> > >  >Could someone please fix this?  I am needing this
>> > functionality.
>> > > > >  >> > >  >Ideally I'd like to have it included in a new XMLC 
release.
>> > Also
>> > > > if
>> > > > >  >> > >  >you do come up with a fix, I'd like to get the patch 
to fix
>> > it,
>> > > > so
>> > > > >  >> > >  >that I can continue working as normal.
>> > > > >  >> > >  >
>> > > > >  >> > >  >References:
>> > > > >  >> > >
>>http://mail-archive.objectweb.org/xmlc/2002-07/msg00077.html
>> > > > >  >> > >
>>http://mail-archive.objectweb.org/xmlc/2003-06/msg00003.html
>> > > > >  >> > >  >
>> > > > >  >> > >  >Thanks,
>> > > > >  >> > >  >
>> > > > >  >> > >  >-Justin Akehurst
>> > > > >  >> > >  >
>> > > > >  >> > >  >
>> > > > >  >> > >  >--
>> > > > >  >> > >  >You receive this message as a subscriber of the
>> > > > xmlc@xxxxxxxxxxxxx
>> > > > >  >> > mailing
>> > > > >  >> > >  >list.
>> > > > >  >> > >  >To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
>> > > > >  >> > >  >For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
>> > > > >  >> > >  >ObjectWeb mailing lists service home page:
>> > > > > http://www.objectweb.org/wws
>> > > > >  >> > >
>> > > > >  >> > >
>> > > > >  >> > >
>> > > > >  >> > > --
>> > > > >  >> > > You receive this message as a subscriber of the
>> > xmlc@xxxxxxxxxxxxx
>> > > > >  >mailing
>> > > > >  >> > list.
>> > > > >  >> > > To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
>> > > > >  >> > > For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
>> > > > >  >> > > ObjectWeb mailing lists service home page:
>> > > > http://www.objectweb.org/wws
>> > > > >  >> > >
>> > > > >  >> > >
>> > > > >  >> > >
>> > > > >  >> >
>> > > > >  >> >
>> > > > >  >>
>> > > > >  >>
>> > > > >  >>
>> > > > >  >> --
>> > > > >  >> You receive this message as a subscriber of the
>xmlc@xxxxxxxxxxxxx
>> > > > mailing
>> > > > >  >list.
>> > > > >  >> To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
>> > > > >  >> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
>> > > > >  >> ObjectWeb mailing lists service home page:
>> > http://www.objectweb.org/wws
>> > > > >  >>
>> > > > >  >>
>> > > > >  >>
>> > > > >  >
>> > > > >  >
>> > > > >  >--
>> > > > >  >You receive this message as a subscriber of the 
xmlc@xxxxxxxxxxxxx
>> > > > mailing
>> > > > >  >list.
>> > > > >  >To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
>> > > > >  >For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
>> > > > >  >ObjectWeb mailing lists service home page:
>> > http://www.objectweb.org/wws
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx
>> > mailing
>> > > > list.
>> > > > > To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
>> > > > > For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
>> > > > > ObjectWeb mailing lists service home page:
>http://www.objectweb.org/wws
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> > >
>> > >
>> >
>>
>>
>>
>>
>
>
>--
>You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing
>list.
>To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
>For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws



--
You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing list.
To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws