xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Initialization problem on Opera 11.01

[Alain C. <ala...@ag...>]

Hello Grégoire,

"//properties" is used to get config properties from a config.xsl file.

I often test with the latest version of Opera and I don't see this 
exception with my own forms.

Can you please send me a test case?

Thanks!

-Alain

Le 11/04/2011 20:02, Grégoire COLBERT a écrit :
> Hi!
>
> I tried my form with Opera 11.01 and it crashes on loading with the
> following report :
>
> ========
>
> <localhost>
>
> XSLTForms Exception
> --------------------------
>
> Error initializing :
>
> <anonymous function: Core.selectSingleNode>([arguments not
> available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:430
> <anonymous function: loadProperties>([arguments not
> available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:130
> <anonymous function: get>([arguments not
> available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:952
> <anonymous function: init>([arguments not
> available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:1546
> initImpl([arguments not available])@https://localhost:8443/:977
> init([arguments not available])@https://localhost:8443/:3
> <anonymous function>([arguments not available])@
>
> Error initially occured at<anonymous function:
> Core.loadNode>([arguments not
> available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:466
> <anonymous function: loadProperties>([arguments not
> available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:130
> <anonymous function: get>([arguments not
> available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:952
> <anonymous function: init>([arguments not
> available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:1546
> initImpl([arguments not available])@https://localhost:8443/:977
> init([arguments not available])@https://localhost:8443/:3
> <anonymous function>([arguments not available])@
>
> TypeError
>
> Cannot convert 'src' to object
>
> ========
>
> A look in "Opera Dragonfly" shows that the problem is the line :
>
>    Core.loadNode(Core.config, Core.selectSingleNode('//properties',
> req.responseXML));
>
> because Core.selectSingleNode returns "null".
>
> What can be wrong with this form?
>
> Thanks for your help!
>
> Grégoire
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Initialization problem on Opera 11.01

[Grégoire C. <gco...@gm...>]

Hi!

I tried my form with Opera 11.01 and it crashes on loading with the
following report :

========

<localhost>
 
XSLTForms Exception
--------------------------
 
Error initializing :
 
<anonymous function: Core.selectSingleNode>([arguments not
available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:430
<anonymous function: loadProperties>([arguments not
available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:130
<anonymous function: get>([arguments not
available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:952
<anonymous function: init>([arguments not
available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:1546
initImpl([arguments not available])@https://localhost:8443/:977
init([arguments not available])@https://localhost:8443/:3
<anonymous function>([arguments not available])@
 
Error initially occured at <anonymous function:
Core.loadNode>([arguments not
available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:466
<anonymous function: loadProperties>([arguments not
available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:130
<anonymous function: get>([arguments not
available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:952
<anonymous function: init>([arguments not
available])@https://localhost:8443/xsltforms/trunk/build/xsltforms.js:1546
initImpl([arguments not available])@https://localhost:8443/:977
init([arguments not available])@https://localhost:8443/:3
<anonymous function>([arguments not available])@
 
TypeError
 
Cannot convert 'src' to object

========

A look in "Opera Dragonfly" shows that the problem is the line :

  Core.loadNode(Core.config, Core.selectSingleNode('//properties',
req.responseXML));

because Core.selectSingleNode returns "null".

What can be wrong with this form?

Thanks for your help!

Grégoire

[Xsltforms-support] "n is undefined" in rev 497 and 498

[Grégoire C. <gco...@gm...>]

Hi!

With revisions 498 and 497, I get "n is undefined" after a submission to
my server (it's ok with 496). The problem is in the
"NodeTestAny.evaluate" function. I fixed it using :

NodeTestAny.prototype.evaluate = function(node) {
    var n = node.localName || node.baseName;
    // return n.substr(0, 10) != "xsltforms_" && node.namespaceURI !=
"http://www.w3.org/2000/xmlns/";
    return (n !== undefined) ? (n.substr(0, 10) != "xsltforms_" &&
node.namespaceURI != "http://www.w3.org/2000/xmlns/") : false;
};

Though the fix is obvious, I wonder if this is theorically possible that
an undefined node reach this function? Since I don't know what you're
trying to do with namespaces, I don't know if this is a test that was
forgotten or something deeper.

Good day to all,
Grégoire

Re: [Xsltforms-support] "n is undefined" in rev 497 and 498

[Grégoire C. <gco...@gm...>]

Le 11/04/2011 11:00, Grégoire COLBERT a écrit :
> Hi!
>
> With revisions 498 and 497, I get "n is undefined" after a submission to
> my server (it's ok with 496). The problem is in the
> "NodeTestAny.evaluate" function. I fixed it using :
>
> NodeTestAny.prototype.evaluate = function(node) {
>     var n = node.localName || node.baseName;
>     // return n.substr(0, 10) != "xsltforms_" && node.namespaceURI !=
> "http://www.w3.org/2000/xmlns/";
>     return (n !== undefined) ? (n.substr(0, 10) != "xsltforms_" &&
> node.namespaceURI != "http://www.w3.org/2000/xmlns/") : false;
> };
>
> Though the fix is obvious, I wonder if this is theorically possible that
> an undefined node reach this function? Since I don't know what you're
> trying to do with namespaces, I don't know if this is a test that was
> forgotten or something deeper.
>
> Good day to all,
> Grégoire
>
"n is undefined" corresponds to text nodes.

Grégoire

Re: [Xsltforms-support] date picker

[COUTHURES A. <ala...@fr...>]

Hi André,

I have now located an issue with FF4: the name() function now returns a 
string always in capital letters for an attribute within an html 
element! An HTML5 feature... I have improved the namespace:: workaround 
for FF4 too.

Before committing again, there is a chance I can also fix something for 
StartML but the exception trace you sent is not enough to locate what 
went wrong: can you please send me a form or a link to it (hopefully 
producing this exception)?

Thanks!

-Alain

Le 11/04/2011 09:16, ac a écrit :
> Hi Alain,
>
>
> Opps, something seems wrong with 498 ...
>
> The previously working form (e.g. FF4) now gives this error:
>
> XSLTForms Exception
> --------------------------
>
> Error evaluating the following XPath expression :
>
> count(//stratml:Value)
>
> TypeError
>
> n is undefined
>
>
>
> And when I click OK, then I get this error:
>
> XSLTForms Exception
> --------------------------
>
> Error initializing :
>
> stringValue(null)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:8244
> ([object Element],[object Array],105,[object
> Array])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1900
> ([object Object],[object
> Element])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:3982
> ([object
> Element])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:4091
> ([object
> Element])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:3968
> ([object HTMLSpanElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1765
> ([object HTMLHeadingElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLDivElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLTableCellElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLTableRowElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLTableSectionElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLTableElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLTableCellElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLTableRowElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLTableSectionElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLTableElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ([object HTMLBodyElement],[object
> Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
> ()@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1712
> ()@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1602
> initImpl()@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/iai2.xml:511
> init()@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/iai2.xml:2
> onload([object
> Event])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/iai2.xml:1
>
>
> TypeError
>
> value is null
>
>
>
> So I have to roll back, if I can as the previous version had been
> patched ...
>
> Regards,
> Andre
>
>
>
>
> Hi Alain, Ivan,
>
> Great!
>
> Ivan, for the record, your patch had apparently fixed the issue.
>
> I have now upgraded to 498.
>
> Thank you both.
>
> Regards,
> Andre
>
>
>
>> Hello André and Ivan,
>>
>> I just discovered that the fix suggested was actually to apply at 3
>> more lines!
>>
>> You can now test with the latest commit.
>>
>> Thank you for your feedbacks!
>>
>> -Alain
>>
>> Le 08/04/2011 21:09, Иван Пономарёв a écrit :
>>> Hello, Andre!
>>>
>>> It seems to me that you are experiencing exactly the same problem
>>> with date picker that has been terrifying us until we found out the
>>> problem in Xsltforms JavaScript and solved it. Apparently Alain did
>>> not have time to assess our bugfix and include it in his code...
>>>
>>> Please see
>>>
>>> http://sourceforge.net/mailarchive/forum.php?thread_name=4D3A0CE5.4020709%40mail.ru&forum_name=xsltforms-support
>>>
>>>
>>> and try out the solution given in the last message of that thread. It
>>> is only about adding ", true" in one method call. Please let us know
>>> if this helps you.
>>>
>>> Regards,
>>>
>>> Ivan Ponomarev
>>>
>>> Fri, 08 Apr 2011 10:53:20 -0400 письмо от ac<ac...@hy...>:
>>>
>>>> Hi Alain,
>>>>
>>>> Sorry about the previous message and forgetting to set the subject and
>>>> set the persona to go through the listserv.
>>>>
>>>>
>>>> Hi Alain,
>>>>
>>>> I hope that you are fine.
>>>>
>>>> Here it is ok, after we have had to work around some issues in
>>>> trying to
>>>> return an xml document in a new browser window, after an XSLTForms
>>>> submission, but managed to get around it with an http submit that
>>>> serializes a large instance model.  Anyway, it is working for us now.
>>>>
>>>> There is still another different issue, as sometimes, the date picker
>>>> increments the selected date by one day.  I tried to get the latest
>>>> XSLTForms from SVN and it did not seem to fix the problem.  I may have
>>>> done something wrong and I am wandering if the issue rings any bell
>>>> for you?
>>>>
>>>> Thank you.
>>>>
>>>> Regards,
>>>> Andre
>>>>
>>>>
>>
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] date picker

[ac <ac...@hy...>]

Hi Alain,


Opps, something seems wrong with 498 ...

The previously working form (e.g. FF4) now gives this error:

XSLTForms Exception
--------------------------

Error evaluating the following XPath expression :

count(//stratml:Value)

TypeError

n is undefined



And when I click OK, then I get this error:

XSLTForms Exception
--------------------------

Error initializing :

stringValue(null)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:8244
([object Element],[object Array],105,[object 
Array])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1900
([object Object],[object 
Element])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:3982
([object 
Element])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:4091
([object 
Element])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:3968
([object HTMLSpanElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1765
([object HTMLHeadingElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLDivElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLTableCellElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLTableRowElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLTableSectionElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLTableElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLTableCellElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLTableRowElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLTableSectionElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLTableElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
([object HTMLBodyElement],[object 
Element],true)@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1782
()@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1712
()@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/xsltforms/xsltforms.js:1602
initImpl()@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/iai2.xml:511
init()@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/iai2.xml:2
onload([object 
Event])@http://www.hyperbase.com/library/hyperform/stratml/asset/xml/iai2.xml:1


TypeError

value is null



So I have to roll back, if I can as the previous version had been 
patched ...

Regards,
Andre




Hi Alain, Ivan,

Great!

Ivan, for the record, your patch had apparently fixed the issue.

I have now upgraded to 498.

Thank you both.

Regards,
Andre



> Hello André and Ivan,
>
> I just discovered that the fix suggested was actually to apply at 3
> more lines!
>
> You can now test with the latest commit.
>
> Thank you for your feedbacks!
>
> -Alain
>
> Le 08/04/2011 21:09, Иван Пономарёв a écrit :
>> Hello, Andre!
>>
>> It seems to me that you are experiencing exactly the same problem
>> with date picker that has been terrifying us until we found out the
>> problem in Xsltforms JavaScript and solved it. Apparently Alain did
>> not have time to assess our bugfix and include it in his code...
>>
>> Please see
>>
>> http://sourceforge.net/mailarchive/forum.php?thread_name=4D3A0CE5.4020709%40mail.ru&forum_name=xsltforms-support
>>
>>
>> and try out the solution given in the last message of that thread. It
>> is only about adding ", true" in one method call. Please let us know
>> if this helps you.
>>
>> Regards,
>>
>> Ivan Ponomarev
>>
>> Fri, 08 Apr 2011 10:53:20 -0400 письмо от ac<ac...@hy...>:
>>
>>> Hi Alain,
>>>
>>> Sorry about the previous message and forgetting to set the subject and
>>> set the persona to go through the listserv.
>>>
>>>
>>> Hi Alain,
>>>
>>> I hope that you are fine.
>>>
>>> Here it is ok, after we have had to work around some issues in
>>> trying to
>>> return an xml document in a new browser window, after an XSLTForms
>>> submission, but managed to get around it with an http submit that
>>> serializes a large instance model.  Anyway, it is working for us now.
>>>
>>> There is still another different issue, as sometimes, the date picker
>>> increments the selected date by one day.  I tried to get the latest
>>> XSLTForms from SVN and it did not seem to fix the problem.  I may have
>>> done something wrong and I am wandering if the issue rings any bell
>>> for you?
>>>
>>> Thank you.
>>>
>>> Regards,
>>> Andre
>>>
>>>
>
>



------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] XSLTForms and xml:lang

[Jens Ø. P. <oe...@gm...>]

Hi Emmanuel,

You are not the only one: in FF4, with 498, our forms hardly show at all.

Best,

Jens

Firefox 3.16:



Firefox 4.0

On Apr 11, 2011, at 12:56 AM, Emmanuel wrote:

> Alain,
> 
> 
> It's not the cache (see screenshot enclosed). I've tested it on two computers. If we're the only ones to report this problem then it must be something with our setup:
> 
> Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0
> 
> We'll use FF3.6 for now.
> Thanks for your help!
> 
> Best regards,
> 
> 
> Emmanuel
> 
> 
> El 10/04/2011 21:53, Alain Couthures escribió:
>> 
>> Emmanuel,
>> 
>> There is no issue yet concerning specifically FireFox 4 support in XSLTForms and the "namespace-test.xml" test case is working successfully on my laptop.
>> 
>> Can you please check again after having cleared the browser cache?
>> 
>> Thanks!
>> 
>> -Alain
>> 
>> Le 10/04/2011 18:32, Emmanuel a écrit :
>>> 
>>> Alain,
>>> 
>>> 
>>> Thanks for your answer.
>>> It works like a charm on Firefox 3.6, which is perfect for us.
>>> 
>>> However, the enclosed test case "namespace-test.xml" fails on Firefox 4 (which XSLTForms might not support at the moment?)
>>> If it may help you, I have also enclosed a slight variation of this test case that works on Firefox 4: "namespace-test-FF4.xml"
>>> Or maybe the test case is wrong? Let me know if I can be of any further help.
>>> 
>>> In any case, my deepest appreciation for your work.
>>> 
>>> Best regards,
>>> 
>>> 
>>> Emmanuel
>> 
> <screenshot.gif>------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev_______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] XSLTForms and xml:lang

[Alain C. <ala...@ag...>]

Emmanuel,

There is no issue yet concerning specifically FireFox 4 support in 
XSLTForms and the "namespace-test.xml" test case is working successfully 
on my laptop.

Can you please check again after having cleared the browser cache?

Thanks!

-Alain

Le 10/04/2011 18:32, Emmanuel a écrit :
> Alain,
>
>
> Thanks for your answer.
> It works like a charm on Firefox 3.6, which is perfect for us.
>
> However, the enclosed test case "namespace-test.xml" fails on Firefox 
> 4 (which XSLTForms might not support at the moment?)
> If it may help you, I have also enclosed a slight variation of this 
> test case that works on Firefox 4: "namespace-test-FF4.xml"
> Or maybe the test case is wrong? Let me know if I can be of any 
> further help.
>
> In any case, my deepest appreciation for your work.
>
> Best regards,
>
>
> Emmanuel

Re: [Xsltforms-support] date picker

[ac <ac...@hy...>]

Hi Alain, Ivan,

Great!

Ivan, for the record, your patch had apparently fixed the issue.

I have now upgraded to 498.

Thank you both.

Regards,
Andre



> Hello André and Ivan,
>
> I just discovered that the fix suggested was actually to apply at 3 
> more lines!
>
> You can now test with the latest commit.
>
> Thank you for your feedbacks!
>
> -Alain
>
> Le 08/04/2011 21:09, Иван Пономарёв a écrit :
>> Hello, Andre!
>>
>> It seems to me that you are experiencing exactly the same problem 
>> with date picker that has been terrifying us until we found out the 
>> problem in Xsltforms JavaScript and solved it. Apparently Alain did 
>> not have time to assess our bugfix and include it in his code...
>>
>> Please see
>>
>> http://sourceforge.net/mailarchive/forum.php?thread_name=4D3A0CE5.4020709%40mail.ru&forum_name=xsltforms-support 
>>
>>
>> and try out the solution given in the last message of that thread. It 
>> is only about adding ", true" in one method call. Please let us know 
>> if this helps you.
>>
>> Regards,
>>
>> Ivan Ponomarev
>>
>> Fri, 08 Apr 2011 10:53:20 -0400 письмо от ac<ac...@hy...>:
>>
>>> Hi Alain,
>>>
>>> Sorry about the previous message and forgetting to set the subject and
>>> set the persona to go through the listserv.
>>>
>>>
>>> Hi Alain,
>>>
>>> I hope that you are fine.
>>>
>>> Here it is ok, after we have had to work around some issues in 
>>> trying to
>>> return an xml document in a new browser window, after an XSLTForms
>>> submission, but managed to get around it with an http submit that
>>> serializes a large instance model.  Anyway, it is working for us now.
>>>
>>> There is still another different issue, as sometimes, the date picker
>>> increments the selected date by one day.  I tried to get the latest
>>> XSLTForms from SVN and it did not seem to fix the problem.  I may have
>>> done something wrong and I am wandering if the issue rings any bell 
>>> for you?
>>>
>>> Thank you.
>>>
>>> Regards,
>>> Andre
>>>
>>>
>
>

Re: [Xsltforms-support] XSLTForms and xml:lang

[Alain C. <ala...@ag...>]

Emmanuel,

The improved workaround for Firefox is now committed.

Thank you for your feedbacks!

-Alain

Le 08/04/2011 00:19, Emmanuel a écrit :
> Alain,
>
> Many thanks for your answer and support. The IE8 problem must be an 
> error on my side.
> Best regards,
>
> Emmanuel
>
> El 07/04/2011 22:23, COUTHURES Alain escribió:
>> Hello Emmanuel,
>>
>> I have located this issue with FireFox: it is due to a workaround for 
>> FireFox not supporting the namespace axis.
>>
>> Please vote at https://bugzilla.mozilla.org/show_bug.cgi?id=94270
>>
>> I have fixed the corresponding workaround and will commit the 
>> modified files as soon as possible.
>>
>> For me, it already worked with both IE8 and IE9....
>>
>> Thanks!
>>
>> -ALain
>>
>> Le 07/04/2011 20:20, Emmanuel a écrit :
>>> And it seems that FF4 does not supportfor the instanceany xml:* 
>>> attribute nor a different namespace...
>>>
>>> El 07/04/2011 18:08, Emmanuel escribió:
>>>> Hello Alain,
>>>>
>>>> Problem found, test case enclosed:
>>>> It occurs even with the last XSLTForms revision and Firefox 3.6 
>>>> when the instance has an xml:lang AND an xml:id attribute.
>>>> If you remove one of them, it works.
>>>>
>>>> It works with Chrome with both attributes. IE8 breaks in both cases.
>>>>
>>>> Wished it had been simpler to solve... Any thoughts welcome.
>>>> Best regards,
>>>>
>>>> Emmanuel
>>>>
>>
>

Re: [Xsltforms-support] date picker

[Alain C. <ala...@ag...>]

Hello André and Ivan,

I just discovered that the fix suggested was actually to apply at 3 more 
lines!

You can now test with the latest commit.

Thank you for your feedbacks!

-Alain

Le 08/04/2011 21:09, Иван Пономарёв a écrit :
> Hello, Andre!
>
> It seems to me that you are experiencing exactly the same problem with date picker that has been terrifying us until we found out the problem in Xsltforms JavaScript and solved it. Apparently Alain did not have time to assess our bugfix and include it in his code...
>
> Please see
>
> http://sourceforge.net/mailarchive/forum.php?thread_name=4D3A0CE5.4020709%40mail.ru&forum_name=xsltforms-support
>
> and try out the solution given in the last message of that thread. It is only about adding ", true" in one method call. Please let us know if this helps you.
>
> Regards,
>
> Ivan Ponomarev
>
> Fri, 08 Apr 2011 10:53:20 -0400 письмо от ac<ac...@hy...>:
>
>> Hi Alain,
>>
>> Sorry about the previous message and forgetting to set the subject and
>> set the persona to go through the listserv.
>>
>>
>> Hi Alain,
>>
>> I hope that you are fine.
>>
>> Here it is ok, after we have had to work around some issues in trying to
>> return an xml document in a new browser window, after an XSLTForms
>> submission, but managed to get around it with an http submit that
>> serializes a large instance model.  Anyway, it is working for us now.
>>
>> There is still another different issue, as sometimes, the date picker
>> increments the selected date by one day.  I tried to get the latest
>> XSLTForms from SVN and it did not seem to fix the problem.  I may have
>> done something wrong and I am wandering if the issue rings any bell for you?
>>
>> Thank you.
>>
>> Regards,
>> Andre
>>
>>

[Xsltforms-support] Another xsltforms-based course, 16-17 June 2011, San Carlos, California

[C. M. Sperberg-M. <cm...@bl...>]

Black Mesa Technologies is pleased to announce a two-day hands-on
introductory course on XForms to take place 16-17 June 2011 in San
Carlos, California. MarkLogic Corporation is generously making a
training room available for the course (but it should be noted that
it's not a MarkLogic course).

The course will be taught using xsltforms.


INTRODUCTION TO XFORMS FOR XML USERS

  San Carlos, California
  16-17 June 2011

This two-day hands-on course introduces XForms as a technology for
building special-purpose XML editors with limited functionality and
correspondingly simple user interfaces.

XForms is built on the model / view / controller idiom, in which the
'model' is a set of XML documents, the 'view' is specified using
XHTML and XForms controls (or 'widgets'), and the 'controller' takes
the form of declarative links between controls in the view and
elements or attributes in the XML documents. With XForms, projects
can develop vocabulary- and task-specific editors which require less
training and provide better task-specific support than full XML
editors; it is thus easier to allow domain experts to examine and
modify XML encoding, and routine tasks can be performed more quickly
and reliably. 

* Topics and syllabus

The course is divided into eight sessions, four to a day:

  Introduction: High-level overview of XForms, background, goals and
  purpose of the XForms spec; “Hello, world” example

  Atomic values and simple structures (1): A simple form; multiple
  submit buttons; enumerated values and vocabulary control;
  conditional relevance; datatypes; validation.

  Atomic values and simple structures (2): Error messages, help,
  hints; validation beyond datatypes; styling the form; adjusting
  for alternate XML structures.

  Multi-part user interfaces: 
  Coding patterns for tabbed interfaces, wizards, user-selected
  alternate views (e.g. summary vs. details, novice vs expert,
  etc.). Multiple instances; dynamic user interfaces.

  Homogeneous repetitions: Handling flat lists; paging through
  records, one record at a time; running off the cliff and how to
  avoid it. Read-only lists; lists of editable items; see-many,
  edit-one interfaces.

  Read-write repetitions, CRUD operations: Special styling for focus
  item; two-pane views. Inserting items; initializing new
  items. Deleting items.

  Mixed content, heterogeneous sequences: Dealing with (flat)
  heterogeneous sequences; dealing with variable-depth
  sequences. Extensions to XForms: tree editors, general mixed-content
  editors. Doing without the extensions: targeted editing in mixed
  content, offloading work to XSLT.

  What next? Individual work and/or Q/A: Where do you go from here?
  Individual work or questions and answers; wrapup.

During the class, students will develop a small XForms application
with a multi-part interface, multiple widget types, and the ability to
add, modify, and delete records in a set. Students will be encouraged
to take their class exercise files with them so that they can continue
to work with them after the class.  


* Prerequisites

Participants should be comfortable editing XML documents and have some
knowledge of HTML markup. Familiarity with XPath and XSLT is helpful
but not required. Programming experience is not required.

Students should bring their own laptops; no classroom machines will be
provided.  The machine must have wifi support, a browser with built-in
support for XSLT (any current version of most major browsers
qualifies) and software the student can use for editing XML documents.


* Who

The course is organized by Black Mesa Technologies LLC and will be
taught by C. M. Sperberg-McQueen.

Michael Sperberg-McQueen is the founder of Black Mesa Technologies. He
has served as co-editor of the XML 1.0 specification, the Text
Encoding Initiative's Guidelines for Text Encoding and Interchange,
and the XML Schema Definition Language (XSD) 1.1 specification; in
2003 he was awarded the XML Cup for contributions to the development
and spread of XML.

MarkLogic Corporation is providing space (for which thanks), but has
no other involvement with the course.


* Logistics

This course will be held from 9:30 a.m. to 5:30 p.m. Thursday and
Friday, 16-17 June 2011, at

    MarkLogic Corporation
    999 Skyway Road, Suite 200
    San Carlos, CA 94070

Thanks to MarkLogic Corporation for hosting the course.

For other logistical information, see the course web site at
http://www.xforms201106.blackmesatech.com/


* Reservations / Info

Space in the course is limited.

To reserve a space, to register, or to ask for more information,
please send email to in...@bl... or call us at
505/747-4224.

An early-bird discount is available for registrations made before 
16 May 2011.


* Announcements of future courses

To receive announcements of future Black Mesa Technologies courses on
XForms and other topics, you can subscribe to
blackmesatech-announce-l.

-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com 
* http://cmsmcq.com/mib                 
* http://balisage.net
****************************************************************

Re: [Xsltforms-support] date picker

[Иван П. <ipo...@ma...>]

Hello, Andre!

It seems to me that you are experiencing exactly the same problem with date picker that has been terrifying us until we found out the problem in Xsltforms JavaScript and solved it. Apparently Alain did not have time to assess our bugfix and include it in his code...

Please see 

http://sourceforge.net/mailarchive/forum.php?thread_name=4D3A0CE5.4020709%40mail.ru&forum_name=xsltforms-support 

and try out the solution given in the last message of that thread. It is only about adding ", true" in one method call. Please let us know if this helps you. 

Regards,

Ivan Ponomarev

Fri, 08 Apr 2011 10:53:20 -0400 письмо от ac <ac...@hy...>:

> Hi Alain,
> 
> Sorry about the previous message and forgetting to set the subject and 
> set the persona to go through the listserv.
> 
> 
> Hi Alain,
> 
> I hope that you are fine.
> 
> Here it is ok, after we have had to work around some issues in trying to 
> return an xml document in a new browser window, after an XSLTForms 
> submission, but managed to get around it with an http submit that 
> serializes a large instance model.  Anyway, it is working for us now.
> 
> There is still another different issue, as sometimes, the date picker 
> increments the selected date by one day.  I tried to get the latest 
> XSLTForms from SVN and it did not seem to fix the problem.  I may have 
> done something wrong and I am wandering if the issue rings any bell for you?
> 
> Thank you.
> 
> Regards,
> Andre
> 
> 
> 
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] date picker

[ac <ac...@hy...>]

Hi Alain,

Sorry about the previous message and forgetting to set the subject and 
set the persona to go through the listserv.


Hi Alain,

I hope that you are fine.

Here it is ok, after we have had to work around some issues in trying to 
return an xml document in a new browser window, after an XSLTForms 
submission, but managed to get around it with an http submit that 
serializes a large instance model.  Anyway, it is working for us now.

There is still another different issue, as sometimes, the date picker 
increments the selected date by one day.  I tried to get the latest 
XSLTForms from SVN and it did not seem to fix the problem.  I may have 
done something wrong and I am wandering if the issue rings any bell for you?

Thank you.

Regards,
Andre

Re: [Xsltforms-support] XSLTForms and xml:lang

[Andre C. <ac...@01...>]

Hi Alain,

I hope that you are fine.

Here it is ok, after we have had to work around some issues in trying to 
return an xml document in a new browser window, after an XSLTForms 
submission, but managed to get around it with an http submit that 
serializes a large instance model.  Anyway, it is working for us now.

There is still another different issue, as sometimes, the date picker 
increments the selected date by one day.  I tried to get the latest 
XSLTForms from SVN and it did not seem to fix the problem.  I may have 
done something wrong and I am wandering if the issue rings any bell for you?

Thank you.

Regards,
Andre

Re: [Xsltforms-support] XSLTForms and xml:lang

[Emmanuel <emm...@ci...>]

Alain,

Many thanks for your answer and support. The IE8 problem must be an 
error on my side.
Best regards,

Emmanuel

El 07/04/2011 22:23, COUTHURES Alain escribió:
> Hello Emmanuel,
>
> I have located this issue with FireFox: it is due to a workaround for 
> FireFox not supporting the namespace axis.
>
> Please vote at https://bugzilla.mozilla.org/show_bug.cgi?id=94270
>
> I have fixed the corresponding workaround and will commit the modified 
> files as soon as possible.
>
> For me, it already worked with both IE8 and IE9....
>
> Thanks!
>
> -ALain
>
> Le 07/04/2011 20:20, Emmanuel a écrit :
>> And it seems that FF4 does not supportfor the instanceany xml:* 
>> attribute nor a different namespace...
>>
>> El 07/04/2011 18:08, Emmanuel escribió:
>>> Hello Alain,
>>>
>>> Problem found, test case enclosed:
>>> It occurs even with the last XSLTForms revision and Firefox 3.6 when 
>>> the instance has an xml:lang AND an xml:id attribute.
>>> If you remove one of them, it works.
>>>
>>> It works with Chrome with both attributes. IE8 breaks in both cases.
>>>
>>> Wished it had been simpler to solve... Any thoughts welcome.
>>> Best regards,
>>>
>>> Emmanuel
>>>
>

Re: [Xsltforms-support] XSLTForms and xml:lang

[COUTHURES A. <ala...@fr...>]

Hello Emmanuel,

I have located this issue with FireFox: it is due to a workaround for 
FireFox not supporting the namespace axis.

Please vote at https://bugzilla.mozilla.org/show_bug.cgi?id=94270

I have fixed the corresponding workaround and will commit the modified 
files as soon as possible.

For me, it already worked with both IE8 and IE9....

Thanks!

-ALain

Le 07/04/2011 20:20, Emmanuel a écrit :
> And it seems that FF4 does not supportfor the instanceany xml:* 
> attribute nor a different namespace...
>
> El 07/04/2011 18:08, Emmanuel escribió:
>> Hello Alain,
>>
>> Problem found, test case enclosed:
>> It occurs even with the last XSLTForms revision and Firefox 3.6 when 
>> the instance has an xml:lang AND an xml:id attribute.
>> If you remove one of them, it works.
>>
>> It works with Chrome with both attributes. IE8 breaks in both cases.
>>
>> Wished it had been simpler to solve... Any thoughts welcome.
>> Best regards,
>>
>> Emmanuel
>>

Re: [Xsltforms-support] XSLTForms and xml:lang

[Emmanuel <emm...@ci...>]

And it seems that FF4 does not supportfor the instanceany xml:* 
attribute nor a different namespace...

El 07/04/2011 18:08, Emmanuel escribió:
> Hello Alain,
>
> Problem found, test case enclosed:
> It occurs even with the last XSLTForms revision and Firefox 3.6 when 
> the instance has an xml:lang AND an xml:id attribute.
> If you remove one of them, it works.
>
> It works with Chrome with both attributes. IE8 breaks in both cases.
>
> Wished it had been simpler to solve... Any thoughts welcome.
> Best regards,
>
> Emmanuel
>
> El 06/04/2011 20:40, COUTHURES Alain escribió:
>> Hello Emmanuel,
>>> We're working on a prototype using MarkLogic, Xsltforms rev. 449 and Firefox 3.6.
>> XSLTForms rev 449 is quite old now. The latest is rev. 497
>>> In one use case, the instance on the client is replaced with another one from the server with an xml:lang attribute.
>>>
>>> The problem is the XPath expressions in the client view don't return elements in the instance with xml:lang.
>>>
>>> I couldn't find documentation on this behavior. Any hint?
>> Could you please send a test case?
>>
>> Thanks!
>>
>> -Alain
>>

Re: [Xsltforms-support] Sending events accross models not possible?

[Grégoire C. <gco...@gm...>]

Le 07/04/2011 17:37, Grégoire COLBERT a écrit :
> Hi!
>
> It seems that it is not possible to send an event from a "model A" to a
> target located inside a "model B". Is it the way XForms is defined, or
> something that is not allowed in XSLTForms but should ultimately work?

My fault! While refactoring my form, I forgot to give the good
"targetid" attribute inside a <xf:dispatch>, while the target had been
moved from a model to another. Sorry for the noise!

Cheers,
Grégoire

[Xsltforms-support] Sending events accross models not possible?

[Grégoire C. <gco...@gm...>]

Hi!

It seems that it is not possible to send an event from a "model A" to a
target located inside a "model B". Is it the way XForms is defined, or
something that is not allowed in XSLTForms but should ultimately work?

As a side question, is "putting everything in a single model" the only
option left?

Thanks!

Grégoire

[Xsltforms-support] Support for @relevant on submission

[Grégoire C. <gco...@gm...>]

Hi Alain,

Latest versions of XSLTForms are good. But what I still miss, though, is
the support of the "relevant" attribute on <xforms:submission>. Is there
something special about it? I would say it's not very different from the
"if" attribute on <xforms:action>, which work fine and are very useful
too. Is there some hidden difficulty in @relevant?

Amicalement,
Grégoire

Re: [Xsltforms-support] XSLTForms and xml:lang

[COUTHURES A. <ala...@ag...>]

Hello Emmanuel,
> We're working on a prototype using MarkLogic, Xsltforms rev. 449 and Firefox 3.6.
XSLTForms rev 449 is quite old now. The latest is rev. 497
> In one use case, the instance on the client is replaced with another one from the server with an xml:lang attribute.
>
> The problem is the XPath expressions in the client view don't return elements in the instance with xml:lang.
>
> I couldn't find documentation on this behavior. Any hint?
Could you please send a test case?

Thanks!

-Alain

[Xsltforms-support] XSLTForms and xml:lang

[Emmanuel d'O. <emm...@ci...>]

Hi,

We're working on a prototype using MarkLogic, Xsltforms rev. 449 and Firefox 3.6.

In one use case, the instance on the client is replaced with another one from the server with an xml:lang attribute.

The problem is the XPath expressions in the client view don't return elements in the instance with xml:lang.

I couldn't find documentation on this behavior. Any hint?

Many thanks in advance,
Regards,


Emmanuel
---- Envoyé avec BlackBerry® d'Orange ----

[Xsltforms-support] Basic XML editor example

[COUTHURES A. <ala...@ag...>]

Hello,

Please find below the XForms example I demonstrated at XML Prague 2011 
for the MarkLogic DemoJam.

It's a very basic XML editor. Only text contents can be modified and 
mixed content is not supported.

Thank you for your feedbacks!

-Alain
------------------------------------------------------------------------
<html xmlns="http://www.w3.org/1999/xhtml" 
xmlns:xf="http://www.w3.org/2002/xforms" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:ev="http://www.w3.org/2001/xml-events">
<head>
<title>Basic XML Editor</title>
<xf:model>
<xf:instance xmlns="">
<xforms-dummy/>
</xf:instance>
<xf:instance xmlns="" id="data-saved">
<data>
<safe>true</safe>
</data>
</xf:instance>
<xf:bind id="nonempty" nodeset=".[local-name() != 'xforms-dummy']"/>
<xf:bind id="notsafe" nodeset="instance('data-saved')/safe" relevant=". 
!= true()"/>
<xf:submission id="save" method="put" replace="none" action="file://">
<xf:message level="modeless" ev:event="xforms-submit-error">Save 
aborted.</xf:message>
<xf:setvalue ref="instance('data-saved')/safe" value="true()" 
ev:event="xforms-submit-done"/>
</xf:submission>
<xf:submission id="load" method="get" serialization="none" 
replace="instance" action="file://">
<xf:setvalue ref="instance('data-saved')/safe" value="true()" 
ev:event="xforms-submit-done"/>
</xf:submission>
<xf:send submission="load" ev:event="xforms-ready"/>
<xf:send submission="save" ev:event="xforms-model-destruct" 
if="instance('data-saved')/safe = false()"/>
</xf:model>
</head>
<body>
<h1>Basic XML Editor</h1>
<xf:trigger>
<xf:label>Load from local disk</xf:label>
<xf:action ev:event="DOMActivate">
<xf:send submission="save" if="instance('data-saved')/safe = false()"/>
<xf:send submission="load"/>
</xf:action>
</xf:trigger>
<xf:submit bind="notsafe" submission="save">
<xf:label>Save to local disk</xf:label>
</xf:submit>
<br/>
<br/>
<xf:group bind="nonempty">
<xf:repeat nodeset="/descendant::*">
<xf:output 
value="substring('&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;',1,3 
* (count(current()/ancestor::*)+1))"/>
<xf:output value="if(*, '-&#xA0;', '')"/>
<xf:output value="local-name()"/>
<xf:repeat nodeset="@*">
<xf:output 
value="substring('&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;',1,3 
* (count(current()/ancestor::*)+1))"/>
<xf:output value="concat('@',local-name())"/>
<xf:input ref="." incremental="true">
<xf:label>: </xf:label>
<xf:setvalue ref="instance('data-saved')/safe" value="false()" 
ev:event="xforms-value-changed"/>
</xf:input>
</xf:repeat>
<xf:output 
value="if(@*,substring('&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;',1,3 
* (count(current()/ancestor::*)+2)),':')"/>
<xf:input ref=".[not(*)]" incremental="true">
<xf:setvalue ref="instance('data-saved')/safe" value="false()" 
ev:event="xforms-value-changed"/>
</xf:input>
</xf:repeat>
</xf:group>
</body>
</html>

[Xsltforms-support] Exception on loading form: Java class xsltforms has no public field or method named "hasXFElement"

[Chester W. <ch...@de...>]

Hello,

When running my form on Firefox 3.6.16 I get the internal error below. The
form works fine on Safari 5.0.4 (Mac OS X 10.6.7)
I don't have a clue about what it is in my form that triggers it---the
reference to .../browse.xhtml:106 is apparently not a line number
because when I move code around in my document it continues to complain
about 106.

XSLTForms Exception
--------------------------

Error initializing :

([object HTMLAppletElement],[object Element],true)@
http://localhost:8888/reminv/build/xsltforms.js:1789
([object HTMLBodyElement],[object Element],true)@
http://localhost:8888/reminv/build/xsltforms.js:1778
()@http://localhost:8888/reminv/build/xsltforms.js:1708
()@http://localhost:8888/reminv/build/xsltforms.js:1602
initImpl()@http://localhost:8888/reminv/browse.xhtml:106
init()@http://localhost:8888/reminv/browse.xhtml:2
onload([object Event])@http://localhost:8888/reminv/browse.xhtml:1


InternalError

Java class xsltforms has no public field or method named "hasXFElement"

Thanks,

Chet Wood