Re: [Xsltforms-support] XSLTForms browsers compatibility + Some issues using XSLTForms in server side.

[Javier D. <jd...@ge...>]

COUTHURES Alain escribió:
> Hello Javier,
>> Then, to implement the XForms solution, we discovered XSLTForms, and we
>> decided that for us it was the most suitable solution to get XForms
>> work, mainly because we have on our server a xslt layer to adapt our web
>> pages output.
>>   
> Thank you for choosing XSLTForms!
>> After using the examples with several browsers, we concluded that
>> XSLTForms seems to work OK with at least Firefox 3, Internet Explorer 7,
>> Opera and Konqueror.
> I thought Konqueror had not XSLT engine... Are you talking about a
> server side transformation for Konqueror?
Yes, we do a server side transformation of the xsl and konqueror is
capable to process the javascript and the rest of stuff generated by the
xsl.
>>  But we have experienced some problems with Firefox
>> 2. 
> Beta 2 release has been successfully tested with FireFox 2.0.0.17 for
> Windows. FF2 support has been a problem in intermediate work version
> because event management in FireFox has been clearly change since
> FF3.0. Workarounds have been implemented for FF2 support. Can you
> please send me a test case where FF2 support is not correct?
The person that had problems using Firefox 2 had version 2.0.0.10, so no
problem, we have recommended him to update to last 2.0.0.X or 3.X versions.
>> So, in first place, we would like to know if there is any list of
>> browsers that are known to work ok (or no ok) with XSLTForms, to know if
>> we will experience problems with users that have old browsers when are
>> using our new web application.
>>   
> XSLTForms has also been successfully tested with FF 3.0, FF 3.5, IE6
> latest SP, IE7 latest SP, IE8, Safari 4, Opera 10 and Chrome.
Ok, many thanks :)
>> Later, we tried to use the xsl of xsltforms in our server side xslt
>> layer and we experienced some problems that we managed to solve. These
>> problems were mainly that our system (based on Java) wasn't able to load
>> the xsl as it was when we downloaded it from sourceforge, due to using
>> the server side xsl we didn't have defined any processing instruction.
>> Commenting out in xslt all lines with commands like
>> "translate(normalize-space(/processing-instruction('css-conversion')[1]),
>>
>> 'YESNO ', 'yesno')='no'" or
>> "translate(normalize-space(/processing-instruction('xml-stylesheet')[1])",
>>
>> we managed to load the xsl and it seems to work ok in our system. We
>> send you attached to this mail a patch with all changes we have done in
>> your xsl to make it work.
>>   
> In fact, there are more processing-instructions tests in Beta 2
> release... 
Yes, I attached in the previous email the diff with all the
processing-instructions commented.
> But this should not interfere anymore with server side transformation,
> the parameter "baseuri" having been added to permit eXist-db to
> perform the transformation.
Yes, I use the parameter "baseuri", is very useful to locate the
xslforms archive in a directory instead in webapp root directory.

But using baseuri, if I leave uncommented the first
processing-instruction, I get when loading the xsl:

javax.xml.transform.TransformerConfigurationException: No se ha podido
compilar la hoja de estilos
        at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:825)

(No se ha podido compilar la hoja de estilos in spanish means that it
wasn't possible to compile the stylesheet)

The code that is failing is (only fails when we have the processing
instructions):

                                Templates template = null;
                                if( file != null )
                                {
                                        Source xslSource =  new
StreamSource (new File(GRMEntorno.PATH_XSL + GRMEntorno.SEP + file) );
                                        TransformerFactory tFactory =
TransformerFactory.newInstance();
                                        *template =
tFactory.newTemplates( xslSource );*
                                }

¿Are we missing something? I will investigate in eXist-db project how is
dealing with xsls, but I don't see any strange thing in our code...

Best regards,
Javier
>
> Best regards,
>
> -Alain