Orbeon Forms community mailing list

Loading Resources In "Seperate Deployment"

Classic

List

Threaded

46 messages Options

123

BitByter

Re[4]: Loading Resources In

Hi Markku,

Tuesday, May 8, 2007, 11:41:03 AM, you wrote:

> BitByter, are you also experiencing long XForms filtering times when using
> Separate Deployment? Any idea why it takes so long?

No, I don't notice a significant processing time for the bookcast example in
seperate or integrated deployment. Maybe I should mention that I'm using
client side state-handling as server side state-handling doesn't work within
my web application.

>>> I also noticed that when using an element named <var> the transformation
>>> fails. Think this is due to the fact that the "var" word is a reserved
>>> word in JavaScript. This leads to my next question, could it be possible
>>> use reserved words as element names in the future?

> Any comments on this one?

Not really. Maybe <var> is not part of XHTML or any other defined namespace
in your page?

- bitbyter

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

Markku Laine

Re[4]: Loading Resources In

>> BitByter, are you also experiencing long XForms filtering times when using
>> Separate Deployment? Any idea why it takes so long?
>
> No, I don't notice a significant processing time for the bookcast example in
> seperate or integrated deployment. Maybe I should mention that I'm using
> client side state-handling as server side state-handling doesn't work within
> my web application.

Found the problem/solution! When XHTML 1.1 Doctype is used then the
problem occurs i.e. filtering takes ~14s. When XHTML 1.0 Doctype is used
then filtering takes only ~2s!!!

Try it out and use first:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

And then:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

...and see the difference in processing/filtering time. Could someone
generate a bug report or should/can we use XHTML 1.0 only?

> Not really. Maybe <var> is not part of XHTML or any other defined namespace
> in your page?

The <var> element is defined inside an <xforms:instance> element and it
uses its own namespace (xmlns=""):
<xforms:instance id="data">
<data xmlns="">
<var name="first-name">Markku</var>
</data>
</xforms:instance>

Well, it works fine if I change the element name from <var> to for example
<variable>. I am quite sure that it has something to do with the reserved
words of JavaScript. Also, if I used a different namespace like the one
below, everything worked fine:
<data xmlns:my="">
<var name="first-name">Markku</var>
</data>

So I think there the problem occurs when a reserved word is used in empty
namespace.

Regards

-Markku

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

Markku Laine

Re[4]: Loading Resources In

>> Not really. Maybe <var> is not part of XHTML or any other defined
>> namespace
>> in your page?
>
> So I think there the problem occurs when a reserved word is used in empty
> namespace.

Sorry, works fine. My mistake.

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

Erik Bruchez

Re: Loading Resources In

Administrator

In reply to this post by Markku Laine

.::: Markku :::. wrote:

> Found the problem/solution! When XHTML 1.1 Doctype is used then the
> problem occurs i.e. filtering takes ~14s. When XHTML 1.0 Doctype is used
> then filtering takes only ~2s!!!
>
> Try it out and use first:
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
>
> And then:
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
> "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
>
> ...and see the difference in processing/filtering time. Could someone
> generate a bug report or should/can we use XHTML 1.0 only?

Mmm, this is really surprising. Could it be that some code somewhere
tries to load the public id
(http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd) and that takes a long time?

This is really the only change you are making?

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

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

Markku Laine

Re: Loading Resources In

> Mmm, this is really surprising. Could it be that some code somewhere tries to
> load the public id (http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd) and that
> takes a long time?

Yes, I think so. I faced a similar problem in a project of mine when
SAX parsing XHTML files with different doctype declarations. If I
remember correctly, as a workaround I coded/implemented the
org.xml.sax.ext.EntityResolver2 interface's resolveEntity( ... ) method
which checks whether W3C XHTML doctype is used. If yes, then all XHTML
entities are loaded from an external file xhtml.ent and set to an
InputSource to be returned by the method. Otherwise, the doctype is
processed normally. This worked because entities are now loaded from a
local file instead of from the W3C web site.

> This is really the only change you are making?

Yes. See and test the attachment ops-doctype.war with the latest OPS
Nightly Build. It includes two very simple and valid XHTML documents with
different doctype declarations.

Regards

-Markku

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

ops-doctype.war (9K) Download Attachment

Alessandro Vernet

Re: Re[4]: Loading Resources In

Administrator

In reply to this post by Markku Laine

Hi Markku,

On 5/8/07, .::: Markku :::. <[hidden email]> wrote:

> The <var> element is defined inside an <xforms:instance> element and it
> uses its own namespace (xmlns=""):
> <xforms:instance id="data">
> <data xmlns="">
> <var name="first-name">Markku</var>
> </data>
> </xforms:instance>
>
> Well, it works fine if I change the element name from <var> to for example
> <variable>. I am quite sure that it has something to do with the reserved
> words of JavaScript. Also, if I used a different namespace like the one
> below, everything worked fine:
> <data xmlns:my="">
> <var name="first-name">Markku</var>
> </data>

This is quite surprising. Would you be able to create a small example
that shows the problem and if possible runs in the XForms sandbox? In
this case, I wouldn't think that using the filter should really make a
difference.

Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/

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

123