xsltforms-support Mailing List for XSLTForms (Page 104)
Brought to you by:
alain-couthures
Menu
▾
▴
xsltforms-support — XSLTForms support list
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(9) |
Jul
(16) |
Aug
(5) |
Sep
(43) |
Oct
(36) |
Nov
(58) |
Dec
(43) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(79) |
Feb
(81) |
Mar
(107) |
Apr
(93) |
May
(85) |
Jun
(54) |
Jul
(64) |
Aug
(54) |
Sep
(45) |
Oct
(53) |
Nov
(34) |
Dec
(77) |
| 2011 |
Jan
(56) |
Feb
(53) |
Mar
(52) |
Apr
(66) |
May
(44) |
Jun
(16) |
Jul
(28) |
Aug
(5) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(46) |
| 2012 |
Jan
(16) |
Feb
(38) |
Mar
(47) |
Apr
(45) |
May
(41) |
Jun
(41) |
Jul
(72) |
Aug
(17) |
Sep
(10) |
Oct
(16) |
Nov
(29) |
Dec
(30) |
| 2013 |
Jan
(25) |
Feb
(13) |
Mar
(20) |
Apr
(25) |
May
(34) |
Jun
(8) |
Jul
(12) |
Aug
(9) |
Sep
(21) |
Oct
(19) |
Nov
(6) |
Dec
(2) |
| 2014 |
Jan
(14) |
Feb
(8) |
Mar
(7) |
Apr
(13) |
May
(33) |
Jun
(13) |
Jul
(6) |
Aug
(5) |
Sep
(5) |
Oct
(34) |
Nov
(7) |
Dec
|
| 2015 |
Jan
(1) |
Feb
(6) |
Mar
(17) |
Apr
(12) |
May
(10) |
Jun
(18) |
Jul
(31) |
Aug
(9) |
Sep
(3) |
Oct
(6) |
Nov
(19) |
Dec
(1) |
| 2016 |
Jan
(18) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
|
Jun
(17) |
Jul
(7) |
Aug
|
Sep
(3) |
Oct
(6) |
Nov
(3) |
Dec
|
| 2017 |
Jan
(5) |
Feb
(17) |
Mar
(4) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(8) |
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(4) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(13) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(15) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2021 |
Jan
(9) |
Feb
(26) |
Mar
(17) |
Apr
|
May
(7) |
Jun
(18) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(2) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(10) |
Feb
|
Mar
(7) |
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(11) |
Nov
(8) |
Dec
(5) |
| 2024 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Alex B. <rho...@ya...> - 2009-11-25 03:52:30
|
Hi Alain,
Thanks very much for your response. I checked the latest code from svn and copied the latest files from trunk/build into my project. I tried adding the xmlns="" in beta 2 and in both with and without with the current build in trunk.
Unfortunately I still seem to be having problems submitting data successfully; I was wondering whether I could just run my latest code by you and see if I can get some advice?
I'm testing the submissions on MarkLogic 4.1 this time (the target db for this project). As before, I'm having success submitting using Internet Explorer 8; however, for some reason, Chrome and Firefox 3.5 are still throwing errors. I haven't tried Opera since.
IE8 shows the response returned by the xquery and writes the XML document to the collection.
Chrome displays a submit error in the debug log:
0 -> Submit put - undefined - http://localhost:8005/crv/basic-crud/savehttpput.xqy - true
91 -> NETWORK_ERR: XMLHttpRequest Exception 101
Firefox 3.5 also displays an error in the log
0 -> Submit put - undefined - http://localhost:8005/crv/basic-crud/savehttpput.xqy - true
125 -> Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXMLHttpRequest.send]
I'm pasting in the xq code, the xml instance and the form markup - if there's anything you can spot, I'd really appreciate any thoughts you may have; thanks very much in advance :)
The XQuery:xqueryversion"1.0-ml";declarefunctionlocal:updateNode(){let$form-data:= xdmp:get-request-body()/node()return$form-data};xdmp:document-insert
<
<
{
</
The XML instance:<?xml version="1.0" encoding="UTF-8"?><itemxmlns=""></item>
The XForm markup:<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<?xsltforms-options debug="yes"?><htmlxmlns="http://www.w3.org/1999/xhtml"xmlns:xf="http://www.w3.org/2002/xforms"xmlns:ev="http://www.w3.org/2001/xml-events"><head><title>XSLTForms - Basic Submission PUT example</title><xf:model><xf:instanceid="default"src="test-instance.xml"/><xf:submissionid="save"method="put"action="http://localhost:8005/xqueries/savehttpput.xqy"><xf:togglecase="case-busy"ev:event="xforms-submit"/><xf:togglecase="case-submit-done"ev:event="xforms-submit-done"/><xf:togglecase="case-submit-error"ev:event="xforms-submit-error"/></xf:submission></xf:model></head><body><xf:inputref="/item/name"><xf:label>Name: </xf:label></xf:input></html><xf:submitclass="store"submission="save"><xf:label>Save</xf:label></xf:submit><xf:switch><xf:caseid="ready"/><xf:caseid="case-busy"><p>Waiting for results from server...</p></xf:case><xf:caseid="case-submit-error"><p>Submit error</p></xf:case><xf:caseid="case-submit-done"><p>Submit
done</p></xf:case></xf:switch></body><name>simple doc content</name>
("xml-doc-name-here.xml", item>{local:updateNode()}</item>,xdmp:default-permissions(),"collection-name-here"), result>xdmp:get-request-body()/node()}result>
|
|
From: COUTHURES A. <ala...@ag...> - 2009-11-24 21:01:36
|
Hi Alex, With beta release 2, xmlns="" should be present in the instance source file. It's no more required with the latest SVN build. My tests with your test case ar OK with IE7, FF3, Chrome and Opera. Thank you for posting your tests results again. Best regards, -Alain > Hi, > > I've been working with XSLTForms and have noticed that there's a fair amount of inconsistency between the submission process across different browsers. I've set up the most simplistic example I can and I wanted to post to the group to see whether anyone could offer any advice. > > Here's the simple XML instance (1.xml): > <?xml version="1.0" encoding="UTF-8"?> > <item> > <name>Simple instance</name> > </item> > > And here's the XForm (submit.xml): > <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?> > <?xsltforms-options debug="yes"?> > <html > xmlns="http://www.w3.org/1999/xhtml" > xmlns:xf="http://www.w3.org/2002/xforms" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > xmlns:ev="http://www.w3.org/2001/xml-events"> > <head> > <title>XSLTForms - Basic Submission [post] example</title> > <xf:model> > <xf:instance id="default" src="1.xml" /> > <xf:submission id="save" method="post" action="http://localhost:8080/exist/rest/db/edit/save-new.xq" ref="instance('default')"> > <xf:toggle case="case-busy" ev:event="xforms-submit"/> > <xf:toggle case="case-submit-done" ev:event="xforms-submit-done"/> > <xf:toggle case="case-submit-error" ev:event="xforms-submit-error"/> > </xf:submission> > </xf:model> > </head> > <body> > > <xf:input ref="/item/name"> > <xf:label>Name: </xf:label> > </xf:input> > <xf:submit class="store" submission="save"> > <xf:label>Save</xf:label> > </xf:submit> > > <xf:switch> > <xf:case id="ready"/> > <xf:case id="case-busy"> > <p>Waiting for results from server...</p> > </xf:case> > <xf:case id="case-submit-error"> > <p>Submit error</p> > </xf:case> > <xf:case id="case-submit-done"> > <p>Submit done</p> > </xf:case> > </xf:switch> > </body> > </html> > > I've been testing the submission process with eXist 1.4 and I'm using beta 2 of XSLTForms - all tests so far have been conducted using Windows XP. These are the results I'm getting with the following browsers: > > Internet Explorer 8 - successfully saves the document/instance to a collection *and* displays the response (without replace="all") even being required.. > > Chrome - reports a submit error but *does* save the document/instance to a collection. > > Firefox 3.5.x - reports a submit error and does not save the document/instance. From looking at the submission in Firebug, it would appear that it isn't even sending the instance with the request. > > Opera 10.01 - reports a submit error and does not save the document/instance. > > For what it's worth, I've used the same XForm markup and achieved a successful submission using the firefox plugin and the nightly build of ubiquity-xforms with Firefox 3.5.x > > Do these results tally with anyone else's findings? It would be great to at least get the submission process working with Firefox as it has such a large market share. Can anyone offer me any advice based on my posting? > > Would there be any benefit in trying the same tests with a nightly build? Can I send more specific console/debug information to help out with this? > > Many thanks in advance, > A > > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Alex B. <rho...@ya...> - 2009-11-24 16:37:21
|
Hi,
I've been working with XSLTForms and have noticed that there's a fair amount of inconsistency between the submission process across different browsers. I've set up the most simplistic example I can and I wanted to post to the group to see whether anyone could offer any advice.
Here's the simple XML instance (1.xml):
<?xml version="1.0" encoding="UTF-8"?>
<item>
<name>Simple instance</name>
</item>
And here's the XForm (submit.xml):
<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<?xsltforms-options debug="yes"?>
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:xf="http://www.w3.org/2002/xforms"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ev="http://www.w3.org/2001/xml-events">
<head>
<title>XSLTForms - Basic Submission [post] example</title>
<xf:model>
<xf:instance id="default" src="1.xml" />
<xf:submission id="save" method="post" action="http://localhost:8080/exist/rest/db/edit/save-new.xq" ref="instance('default')">
<xf:toggle case="case-busy" ev:event="xforms-submit"/>
<xf:toggle case="case-submit-done" ev:event="xforms-submit-done"/>
<xf:toggle case="case-submit-error" ev:event="xforms-submit-error"/>
</xf:submission>
</xf:model>
</head>
<body>
<xf:input ref="/item/name">
<xf:label>Name: </xf:label>
</xf:input>
<xf:submit class="store" submission="save">
<xf:label>Save</xf:label>
</xf:submit>
<xf:switch>
<xf:case id="ready"/>
<xf:case id="case-busy">
<p>Waiting for results from server...</p>
</xf:case>
<xf:case id="case-submit-error">
<p>Submit error</p>
</xf:case>
<xf:case id="case-submit-done">
<p>Submit done</p>
</xf:case>
</xf:switch>
</body>
</html>
I've been testing the submission process with eXist 1.4 and I'm using beta 2 of XSLTForms - all tests so far have been conducted using Windows XP. These are the results I'm getting with the following browsers:
Internet Explorer 8 - successfully saves the document/instance to a collection *and* displays the response (without replace="all") even being required..
Chrome - reports a submit error but *does* save the document/instance to a collection.
Firefox 3.5.x - reports a submit error and does not save the document/instance. From looking at the submission in Firebug, it would appear that it isn't even sending the instance with the request.
Opera 10.01 - reports a submit error and does not save the document/instance.
For what it's worth, I've used the same XForm markup and achieved a successful submission using the firefox plugin and the nightly build of ubiquity-xforms with Firefox 3.5.x
Do these results tally with anyone else's findings? It would be great to at least get the submission process working with Firefox as it has such a large market share. Can anyone offer me any advice based on my posting?
Would there be any benefit in trying the same tests with a nightly build? Can I send more specific console/debug information to help out with this?
Many thanks in advance,
A
|
|
From: COUTHURES A. <ala...@ag...> - 2009-11-23 20:56:52
|
Hello, > we have changed the constructURI javascript function to create > relative uris correctly This javascript function was already modified but the query string was not removed. Thank you for pointing at this! I have just fixed this in the last SVN commit. Best regards, -Alain |
|
From: Javier D. <jd...@ge...> - 2009-11-20 11:27:54
|
Hello,
we have changed the constructURI javascript function to create relative
uris correctly:
constructURI : function(uri) {
if (!uri.match(/:\/\//)) {
var relativ = document.location.href;
var pos = relativ.indexOf("?");
relativ = relativ.substring(0,pos);
pos = 0;
if (uri.indexOf("/")==0) {
for (i=0;i<3;++i){
pos = relativ.indexOf("\/",pos);
++pos;
}
uri = relativ.substring(0,--pos)+uri;
}else {
uri = relativ.replace(/[^\/]+$/,"") + uri;
}
}
return uri;
}
If uri starts with /, we generate the url with the
"protocol://host:port/" + uri, and if not, we do the same you were doing
but taking out the query part of the uri.
I hope it may be useful for anybody.
Best Regards,
Javier
Javier Díaz escribió:
> Hello,
> My answer, below.
>
> COUTHURES Alain escribió:
>> Hello Javier,
>>> Hello,
>>>
>>> I have a xform with the following submission:
>>>
>>> <xf:submission id="s01" method="post" replace="all"
>>> action="*/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM*">
>>> <xf:message level="modeless"
>>> ev:event="xforms-submit-error">Submit error.</xf:message>
>>> </xf:submission>
>>>
>>> That is get through the following url:
>>>
>>> https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms
>>>
>>> When I use the submit that triggers the action of above, I get that
>>> the page that is requested is:
>>>
>>> https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/*/nucleo?FILE=pruebas/entornoReq.xml&GEREMIAS_RESPUESTA=whitehtml&XML=XFORM
>>>
>>> *¿Is this a bug or a feature?
>> This is clearly not yet supported to have an action attribute value
>> starting with / ... Have a look at constructURI method of Core class
>> to add this feature (this should not be difficult in fact!) and I
>> will integrate your fix in XSLTForms.
> Ok, I will investigate with constructURI.
>
> But I think the behaviour of the construction of the uri is also a bit
> strange in the case that action does not start with / and is a
> relative one. I mean, I you have an url like this:
>
> https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms
>
> to construct the relative path to send a submit should be used taking
> out the query part of the url, in this case
> "?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms", so the
> url constructed (without taking into account the initial /) should be,
> from:
>
> nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM
>
> the following:
>
> https://tuerca:8080/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM
>
> or in case you have subdirectories, from
> "https://tuerca:8080/subdir1/subdir2/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM",
> the absolute uri of
> "nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM"
> should be:
>
> "https://tuerca:8080/subdir1/subdir2/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM"
> _
> _In this last example, if we had as relative uri
> "/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM",
> the absolute uri should be:
>
> "https://tuerca:8080/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM"
>
> Am I missing something? I will try to change constructURI to have this
> behaviour, I suppose it fits better with RFC 3986
> <http://tools.ietf.org/html/rfc3986> (see section 5.2).
>
> Best Regards,
> Javier
>>
>> Thanks!
>>
>> -Alain
>>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
|
|
From: Javier D. <jd...@ge...> - 2009-11-13 10:10:26
|
Hello, I am trying to use a xml template to insert new elements in a repeat structure using origin (as it can be seen in http://en.wikibooks.org/wiki/XForms/Insert_with_Origin) I mean, instead of (seen in a example of xsltforms): <xforms:action ev:event="DOMActivate"> <xforms:insert nodeset="transaction" position="after" at="last()"/> <xforms:setvalue ref="transaction[last()]/date" value="substring-before(now(), 'T')"/> <xforms:setvalue ref="transaction[last()]/amount" value="'0.00'"/> <xforms:setvalue ref="transaction[last()]/withdraw">true</xforms:setvalue> <xforms:setvalue ref="transaction[last()]/desc"/> </xforms:action> something like this: <xforms:action ev:event="DOMActivate"> <xforms:insert nodeset="transaction" position="after" at="last()" origin="instance('template')/transaction"/> </xforms:action> I haven't found any example with origin, so I'm not sure if it is possible to do this now with xsltforms... Best Regards, Javier |
|
From: COUTHURES A. <ala...@ag...> - 2009-11-12 09:52:50
|
Hello again, > I see in the example you have provided that there is an complexType: > <xsd:schema targetNamespace="http://commerce.example.com/payment"> > <xsd:simpleType name="ccnumber"> > <xsd:restriction base="xsd:string"> > > <xsd:pattern value="\d{14,18}"/> > </xsd:restriction> > </xsd:simpleType> > <xsd:element name="payment"> > <xsd:complexType> > <xsd:sequence> > <xsd:element name="number" type="my:ccnumber" minOccurs="0"/> > <xsd:element name="expiry" type="xsd:gYearMonth" minOccurs="0"/> > </xsd:sequence> > > <xsd:attribute name="method" type="xsd:string"/> > </xsd:complexType> > </xsd:element> > </xsd:schema> > > What do you refer with "Only simpleType is supported"? > Bindings are required to associated types to element. In this example, the complexType is not interpreted by XSLTForms ! > By the way, is there any place where I can see which parts of xsltforms > are yet noy fully implemented? > Sorry, not yet. Commercial support is proposed if you are in a hurry ! Best regards, -Alain |
|
From: Javier D. <jd...@ge...> - 2009-11-12 09:47:02
|
COUTHURES Alain escribió: > Hello, >> I am trying to use schemas in model with xsltforms and I it is >> impossible to me to make it work. >> >> I also don't find any example in xsltforms using schema. Is this feaute >> totally implemented in xsltforms? > No this feature is not yet fully implemented. Only simpleType is > supported. I see in the example you have provided that there is an complexType: <xsd:schema targetNamespace="http://commerce.example.com/payment"> <xsd:simpleType name="ccnumber"> <xsd:restriction base="xsd:string"> <xsd:pattern value="\d{14,18}"/> </xsd:restriction> </xsd:simpleType> <xsd:element name="payment"> <xsd:complexType> <xsd:sequence> <xsd:element name="number" type="my:ccnumber" minOccurs="0"/> <xsd:element name="expiry" type="xsd:gYearMonth" minOccurs="0"/> </xsd:sequence> <xsd:attribute name="method" type="xsd:string"/> </xsd:complexType> </xsd:element> </xsd:schema> What do you refer with "Only simpleType is supported"? >> If yes, does have anybody an example >> that works with xsltforms? >> > You can have a look at > http://www.agencexml.com/xforms-tests/testsuite/XForms1.1/Edition1/Chapt02/2.3.a.xhtml > Thank you for the example. By the way, is there any place where I can see which parts of xsltforms are yet noy fully implemented? > > Best regards, > > -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2009-11-12 09:28:25
|
Hello, > I am trying to use schemas in model with xsltforms and I it is > impossible to me to make it work. > > I also don't find any example in xsltforms using schema. Is this feaute > totally implemented in xsltforms? No this feature is not yet fully implemented. Only simpleType is supported. > If yes, does have anybody an example > that works with xsltforms? > You can have a look at http://www.agencexml.com/xforms-tests/testsuite/XForms1.1/Edition1/Chapt02/2.3.a.xhtml Best regards, -Alain |
|
From: Javier D. <jd...@ge...> - 2009-11-12 09:16:03
|
Hello, I am trying to use schemas in model with xsltforms and I it is impossible to me to make it work. I also don't find any example in xsltforms using schema. Is this feaute totally implemented in xsltforms? If yes, does have anybody an example that works with xsltforms? For example, I have found this example in internet, and doesn't works with xsltforms: http://xforms-examples.googlecode.com/svn/trunk/05-validation/55-load-schema/ With schema in model i'm referring in using in model something like this: <xf:model id="test" schema="data-types.xsd"> <xf:instance src="instance-data.xml"/> </xf:model> Best regards, Javier |
|
From: Javier D. <jd...@ge...> - 2009-11-10 17:21:46
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello,<br>
My answer, below.<br>
<br>
COUTHURES Alain escribió:
<blockquote cite="mid:4AF...@ag..." type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
Hello Javier,
<blockquote cite="mid:4AF...@ge..." type="cite">Hello,<br>
<br>
I have a xform with the following submission:<br>
<br>
<tt><xf:submission id="s01" method="post" replace="all" action="<b>/nucleo?FILE=pruebas/entornoReq.xml&amp;GRM_RESPUESTA=whitehtml&amp;XML=XFORM</b>"><br>
<xf:message level="modeless"
ev:event="xforms-submit-error">Submit error.</xf:message><br>
</xf:submission></tt><br>
<br>
That is get through the following url:<br>
<br>
<tt><a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms">https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms</a><br>
<br>
</tt>When I use the submit that triggers the action of above, I get
that the page that is requested is:<br>
<br>
<tt><a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/">https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/</a><b>/nucleo?FILE=pruebas/entornoReq.xml&GEREMIAS_RESPUESTA=whitehtml&XML=XFORM<br>
<br>
</b></tt>¿Is this a bug or a feature?<br>
</blockquote>
This is clearly not yet supported to have an action attribute value
starting with / ... Have a look at constructURI method of Core class to
add this feature (this should not be difficult in fact!) and I will
integrate your fix in XSLTForms.<br>
</blockquote>
Ok, I will investigate with constructURI.<br>
<br>
But I think the behaviour of the construction of the uri is also a bit
strange in the case that action does not start with / and is a relative
one. I mean, I you have an url like this:<br>
<br>
<tt><a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms">https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms</a><br>
<br>
</tt>to construct the relative path to send a submit should be used
taking out the query part of the url, in this case "<tt><a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms">?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms</a></tt>",
so the url constructed (without taking into account the initial /)
should be, from: <br>
<br>
<tt>nucleo?FILE=pruebas/entornoReq.xml&amp;GRM_RESPUESTA=whitehtml&amp;XML=XFORM</tt><br>
<br>
the following:<br>
<br>
<tt><a class="moz-txt-link-freetext"
href="https://tuerca:8080/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM">https://tuerca:8080/nucleo?FILE=pruebas/entornoReq.xml&amp;GRM_RESPUESTA=whitehtml&amp;XML=XFORM</a></tt><br>
<br>
or in case you have subdirectories, from
<a class="moz-txt-link-rfc2396E"
href="https://tuerca:8080/subdir1/subdir2/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM">"https://tuerca:8080/subdir1/subdir2/nucleo?FILE=pruebas/entornoReq.xml&amp;GRM_RESPUESTA=whitehtml&amp;XML=XFORM"</a>,
the absolute uri of
"nucleo?FILE=pruebas/entornoReq.xml&amp;GRM_RESPUESTA=whitehtml&amp;XML=XFORM"
should be:<br>
<br>
<tt><a class="moz-txt-link-rfc2396E"
href="https://tuerca:8080/subdir1/subdir2/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM">"https://tuerca:8080/subdir1/subdir2/nucleo?FILE=pruebas/entornoReq.xml&amp;GRM_RESPUESTA=whitehtml&amp;XML=XFORM"</a></tt><br>
<u><br>
</u>In this last example, if we had as relative uri
"/nucleo?FILE=pruebas/entornoReq.xml&amp;GRM_RESPUESTA=whitehtml&amp;XML=XFORM",
the absolute uri should be:<br>
<tt><br>
<a class="moz-txt-link-rfc2396E"
href="https://tuerca:8080/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM">"https://tuerca:8080/nucleo?FILE=pruebas/entornoReq.xml&amp;GRM_RESPUESTA=whitehtml&amp;XML=XFORM"</a><br>
<br>
</tt>Am I missing something? I will try to change constructURI to have
this behaviour, I suppose it fits better with <a
href="http://tools.ietf.org/html/rfc3986">RFC 3986</a> (see section
5.2).<br>
<br>
Best Regards,<br>
Javier<br>
<blockquote cite="mid:4AF...@ag..." type="cite"><br>
Thanks!<br>
<br>
-Alain<br>
<br>
</blockquote>
</body>
</html>
|
|
From: COUTHURES A. <ala...@ag...> - 2009-11-10 14:12:12
|
Hello Javier, > Hello, > > I have a xform with the following submission: > > <xf:submission id="s01" method="post" replace="all" > action="*/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM*"> > <xf:message level="modeless" > ev:event="xforms-submit-error">Submit error.</xf:message> > </xf:submission> > > That is get through the following url: > > https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms > > When I use the submit that triggers the action of above, I get that > the page that is requested is: > > https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/*/nucleo?FILE=pruebas/entornoReq.xml&GEREMIAS_RESPUESTA=whitehtml&XML=XFORM > > *¿Is this a bug or a feature? This is clearly not yet supported to have an action attribute value starting with / ... Have a look at constructURI method of Core class to add this feature (this should not be difficult in fact!) and I will integrate your fix in XSLTForms. Thanks! -Alain |
|
From: Claudius T. <cla...@ya...> - 2009-11-10 14:10:51
|
I use eXist and this helped me:
<xsl:processing-instruction name="xml-stylesheet">href="/exist/rest//db/xsltforms/xsltforms.xsl" type="text/xsl"</xsl:processing-instruction>
Claudius
|
|
From: Javier D. <jd...@ge...> - 2009-11-10 13:14:49
|
Hello Claudius, the port you are using doesn't matters of using http or https, the web is working ok with this protocol and port. My problem is only related about xsltforms processing relative urls, that it seems it is not getting the base uri of the server (or maybe I'm doing something wrong with xsltforms). Best Regards, Javier Claudius Teodorescu escribió: > Hi, > > For https requests don't you need to address port 8443? > > Claudius > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Javier D. <jd...@ax...> - 2009-11-10 13:14:23
|
Hello Claudius, the port you are using doesn't matters of using http or https, the web is working ok with this protocol and port. My problem is only related about xsltforms processing relative urls, that it seems it is not getting the base uri of the server (or maybe I'm doing something wrong with xsltforms). Best Regards, Javier Claudius Teodorescu escribió: > Hi, > > For https requests don't you need to address port 8443? > > Claudius > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Claudius T. <cla...@ya...> - 2009-11-10 12:39:49
|
Hi,
For https requests don't you need to address port 8443?
Claudius
|
|
From: Javier D. <jd...@ge...> - 2009-11-10 12:32:21
|
COUTHURES Alain escribió: > Hello Javier, >> Hello, >> >> I have noticed that "... Loading ..." message can be >> internationalized with files "messages.properties" and >> "messages_<lang>.properties". >> >> But I see that in spanish one, "messages_es.properties" it has >> "status = ... Loading ...", that is the english message. I think it >> should be translated to spanish, >> indicating for example "... Cargando ...". > Thank you! I have changed this in the SVN repository. >> I also noticed that in my case is always loaded the english version, >> whereas other people is corrected loaded the spanish version with >> "Cargando" (I have changed it locally). >> >> I think the reason is that to decide the languaje to use, is taking >> into account the user-agent instead the accept-language header. >> >> In my case, that is choosing english version: >> >> User-Agent |Mozilla/5.0 (X11; U; Linux i686; *en-US*; rv:1.9.0.14) >> Gecko/2009091913 Mandriva/1.9.0.14-0.1mdv2009.1|| (2009.1) >> Firefox/3.0.14| >> Accept >> |text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8| >> Accept-Language |*es-es*,es;q=0.8,en-gb;q=0.6,en-us;q=0.4,en;q=0.2| >> >> >> And in a case where is choosed the spanish one: >> >> User-Agent |Mozilla/5.0 (X11; U; Linux i686; *es-ES*; rv:1.9.0.10) >> Gecko/2009042513 Ubuntu/8.04 (hardy) Firefox/3.0.10||| >> Accept >> |text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8| >> Accept-Language |*es-es*,es;q=0.8,en-us;q=0.5,en;q=0.3| >> >> >> It would be great to get the correct one, although I can survive with >> english localized version :) > Unfortunately, it doesn't seem possible to access "Accept-Language" > directly in Javascript. A server page might be used to interpret it > instead of returning the requested file (URL rewriting can do the trick). Oh, I see. Maybe a workaround for xsltforms is to set a parameter like "basedir" that indicates the language to enable that the server that receives the request can analize the "Accept-Language" header and forward the preferred languaje to the xsl. But don't worry, in my case I will use the easy way, as we have all the web page in spanish, we will put as english message properties file the spanish one. >> >> And finally, I have detected that inside the xsltforms.xsl, in >> templates "xforms:itemset" and "xhtml:html | html" there are two >> "Loading" messages. Do these messages appear in any moment? Should I >> change it to spanish version? (I want only to appear spanish messages). > The "Loading" in "xhtml:html | html" is displayed just before the > message found in the properties file. > > The "Loading" in "xforms:itemset" is used to initialize this itemset > while downloading the corresponding values. This message is not yet > customizable. > > You can, of course, change both, if you want. > > Best regards, > > -Alain |
|
From: Javier D. <jd...@ge...> - 2009-11-10 12:30:14
|
Hello,
I have a xform with the following submission:
<xf:submission id="s01" method="post" replace="all"
action="*/nucleo?FILE=pruebas/entornoReq.xml&GRM_RESPUESTA=whitehtml&XML=XFORM*">
<xf:message level="modeless"
ev:event="xforms-submit-error">Submit error.</xf:message>
</xf:submission>
That is get through the following url:
https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/pai-ip.xml&GRM_RESPUESTA=xsltforms
When I use the submit that triggers the action of above, I get that the
page that is requested is:
https://tuerca:8080/nucleo?FILE=pruebas/javi/xforms/*/nucleo?FILE=pruebas/entornoReq.xml&GEREMIAS_RESPUESTA=whitehtml&XML=XFORM
*¿Is this a bug or a feature?
If it is working correctly, ¿hoy can I force in "action" to get a
relative link, without the server? (https://tuerca:8080/ in my case)
Best regards,
Javi
|
|
From: COUTHURES A. <ala...@ag...> - 2009-11-09 19:52:09
|
Hello Javier, > Hello, > > I have noticed that "... Loading ..." message can be internationalized > with files "messages.properties" and "messages_<lang>.properties". > > But I see that in spanish one, "messages_es.properties" it has "status > = ... Loading ...", that is the english message. I think it should be > translated to spanish, > indicating for example "... Cargando ...". Thank you! I have changed this in the SVN repository. > I also noticed that in my case is always loaded the english version, > whereas other people is corrected loaded the spanish version with > "Cargando" (I have changed it locally). > > I think the reason is that to decide the languaje to use, is taking > into account the user-agent instead the accept-language header. > > In my case, that is choosing english version: > > User-Agent |Mozilla/5.0 (X11; U; Linux i686; *en-US*; rv:1.9.0.14) > Gecko/2009091913 Mandriva/1.9.0.14-0.1mdv2009.1|| (2009.1) > Firefox/3.0.14| > Accept |text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8| > Accept-Language |*es-es*,es;q=0.8,en-gb;q=0.6,en-us;q=0.4,en;q=0.2| > > > And in a case where is choosed the spanish one: > > User-Agent |Mozilla/5.0 (X11; U; Linux i686; *es-ES*; rv:1.9.0.10) > Gecko/2009042513 Ubuntu/8.04 (hardy) Firefox/3.0.10||| > Accept |text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8| > Accept-Language |*es-es*,es;q=0.8,en-us;q=0.5,en;q=0.3| > > > It would be great to get the correct one, although I can survive with > english localized version :) Unfortunately, it doesn't seem possible to access "Accept-Language" directly in Javascript. A server page might be used to interpret it instead of returning the requested file (URL rewriting can do the trick). > > And finally, I have detected that inside the xsltforms.xsl, in > templates "xforms:itemset" and "xhtml:html | html" there are two > "Loading" messages. Do these messages appear in any moment? Should I > change it to spanish version? (I want only to appear spanish messages). The "Loading" in "xhtml:html | html" is displayed just before the message found in the properties file. The "Loading" in "xforms:itemset" is used to initialize this itemset while downloading the corresponding values. This message is not yet customizable. You can, of course, change both, if you want. Best regards, -Alain |
|
From: Javier D. <jd...@ge...> - 2009-11-06 09:42:25
|
Hello, I have noticed that "... Loading ..." message can be internationalized with files "messages.properties" and "messages_<lang>.properties". But I see that in spanish one, "messages_es.properties" it has "status = ... Loading ...", that is the english message. I think it should be translated to spanish, indicating for example "... Cargando ...". I also noticed that in my case is always loaded the english version, whereas other people is corrected loaded the spanish version with "Cargando" (I have changed it locally). I think the reason is that to decide the languaje to use, is taking into account the user-agent instead the accept-language header. In my case, that is choosing english version: User-Agent |Mozilla/5.0 (X11; U; Linux i686; *en-US*; rv:1.9.0.14) Gecko/2009091913 Mandriva/1.9.0.14-0.1mdv2009.1|| (2009.1) Firefox/3.0.14| Accept |text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8| Accept-Language |*es-es*,es;q=0.8,en-gb;q=0.6,en-us;q=0.4,en;q=0.2| And in a case where is choosed the spanish one: User-Agent |Mozilla/5.0 (X11; U; Linux i686; *es-ES*; rv:1.9.0.10) Gecko/2009042513 Ubuntu/8.04 (hardy) Firefox/3.0.10||| Accept |text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8| Accept-Language |*es-es*,es;q=0.8,en-us;q=0.5,en;q=0.3| It would be great to get the correct one, although I can survive with english localized version :) And finally, I have detected that inside the xsltforms.xsl, in templates "xforms:itemset" and "xhtml:html | html" there are two "Loading" messages. Do these messages appear in any moment? Should I change it to spanish version? (I want only to appear spanish messages). Best Regards, Javier |
|
From: Javier D. <jd...@ge...> - 2009-11-05 11:57:17
|
COUTHURES Alain escribió: > Hello Javier, >> activating debug mode in xslt compilation, this error appeared: >> >> com.sun.org.apache.bcel.internal.generic.ClassGenException: ICONST >> can be used only for value between -1 and 5: 7 >> at >> com.sun.org.apache.bcel.internal.generic.ICONST.<init>(ICONST.java:81) >> at >> com.sun.org.apache.xalan.internal.xsltc.compiler.Step.translatePredicates(Step.java:412) >> at >> com.sun.org.apache.xalan.internal.xsltc.compiler.Step.translate(Step.java:237) >> at >> com.sun.org.apache.xalan.internal.xsltc.compiler.AbsoluteLocationPath.translate(AbsoluteLocationPath.java:101) >> at >> com.sun.org.apache.xalan.internal.xsltc.compiler.CastExpr.translate(CastExpr.java:229) >> at >> com.sun.org.apache.xalan.internal.xsltc.compiler.FunctionCall.translate(FunctionCall.java:710) > It seems this exception is already known as a possible bug: > http://marc.info/?l=xalan-dev&m=117629991417675&w=2 > > Are you using the latest Xalan version ? I'm using the Xalan version that comes with the sun jvm. In my case, it is: $ java -server -version java version "1.6.0_15" Java(TM) SE Runtime Environment (build 1.6.0_15-b03) Java HotSpot(TM) Server VM (build 14.1-b02, mixed mode) It is one of the latest java 1.6 versions (the last is 1.6.17), so maybe is a different bug, I suppose the one you indicated is old enough to be solved. >> >> Then, I tried to simplify the processing-instruction commands, using >> an extra variable and it seems that Xalan can process the xsl and it >> seems it works ok. >> 25,26c25 >> < <xsl:variable name="pivaluebck" >> select="/processing-instruction('xml-stylesheet')"/> >> < <xsl:variable name="pivalue" >> select="translate(normalize-space($pivaluebck[1]), ' ', '')"/> >> --- >> > <xsl:variable name="pivalue" >> select="translate(normalize-space(/processing-instruction('xml-stylesheet')[1]), >> ' ', '')"/> >> >> ¿Is it possible to make a change in xsltforms xsl like this to al the >> proccessing-instruction lines to be able to use it with Xalan? > There are already workarounds in XSLTForms like the one you found for > other XSLT engines problems. So, I will change this in XSLTForms as > you suggest. I will contact you again when it will be committed. Many thanks :) I will try it as soon as you change it. >> >> In addition, I have seen that you have some processing-instruction >> lines duplicated (css-conversion and xsltforms-options ones). Taking >> in account that the processing instructions you have are global, and >> are located in the top of xml document if defined, maybe is better to >> retrieve its value at the beginning of the document (I completely >> ignore if this can affect to your xsl, it is only a suggestion). > Instead of global variables, I prefer having local variables defined > and used in the corresponding source component (if you have a look at > the SVN repository, you will see that the xsltforms.xsl file is > generated from many source components!). Oh, I didn't know you split the xsl in several pieces, a good idea if it gets too long :) > > Best regards, > > -Alain > |
|
From: COUTHURES A. <ala...@ag...> - 2009-11-05 09:01:25
|
Hello Javier, > activating debug mode in xslt compilation, this error appeared: > > com.sun.org.apache.bcel.internal.generic.ClassGenException: ICONST can > be used only for value between -1 and 5: 7 > at > com.sun.org.apache.bcel.internal.generic.ICONST.<init>(ICONST.java:81) > at > com.sun.org.apache.xalan.internal.xsltc.compiler.Step.translatePredicates(Step.java:412) > at > com.sun.org.apache.xalan.internal.xsltc.compiler.Step.translate(Step.java:237) > at > com.sun.org.apache.xalan.internal.xsltc.compiler.AbsoluteLocationPath.translate(AbsoluteLocationPath.java:101) > at > com.sun.org.apache.xalan.internal.xsltc.compiler.CastExpr.translate(CastExpr.java:229) > at > com.sun.org.apache.xalan.internal.xsltc.compiler.FunctionCall.translate(FunctionCall.java:710) It seems this exception is already known as a possible bug: http://marc.info/?l=xalan-dev&m=117629991417675&w=2 Are you using the latest Xalan version ? > > Then, I tried to simplify the processing-instruction commands, using > an extra variable and it seems that Xalan can process the xsl and it > seems it works ok. > 25,26c25 > < <xsl:variable name="pivaluebck" > select="/processing-instruction('xml-stylesheet')"/> > < <xsl:variable name="pivalue" > select="translate(normalize-space($pivaluebck[1]), ' ', '')"/> > --- > > <xsl:variable name="pivalue" > select="translate(normalize-space(/processing-instruction('xml-stylesheet')[1]), > ' ', '')"/> > > ¿Is it possible to make a change in xsltforms xsl like this to al the > proccessing-instruction lines to be able to use it with Xalan? There are already workarounds in XSLTForms like the one you found for other XSLT engines problems. So, I will change this in XSLTForms as you suggest. I will contact you again when it will be committed. > > In addition, I have seen that you have some processing-instruction > lines duplicated (css-conversion and xsltforms-options ones). Taking > in account that the processing instructions you have are global, and > are located in the top of xml document if defined, maybe is better to > retrieve its value at the beginning of the document (I completely > ignore if this can affect to your xsl, it is only a suggestion). Instead of global variables, I prefer having local variables defined and used in the corresponding source component (if you have a look at the SVN repository, you will see that the xsltforms.xsl file is generated from many source components!). Best regards, -Alain |
|
From: Javier D. <jd...@ge...> - 2009-11-05 08:30:55
|
Hello Alain,
activating debug mode in xslt compilation, this error appeared:
com.sun.org.apache.bcel.internal.generic.ClassGenException: ICONST can
be used only for value between -1 and 5: 7
at
com.sun.org.apache.bcel.internal.generic.ICONST.<init>(ICONST.java:81)
at
com.sun.org.apache.xalan.internal.xsltc.compiler.Step.translatePredicates(Step.java:412)
at
com.sun.org.apache.xalan.internal.xsltc.compiler.Step.translate(Step.java:237)
at
com.sun.org.apache.xalan.internal.xsltc.compiler.AbsoluteLocationPath.translate(AbsoluteLocationPath.java:101)
at
com.sun.org.apache.xalan.internal.xsltc.compiler.CastExpr.translate(CastExpr.java:229)
at
com.sun.org.apache.xalan.internal.xsltc.compiler.FunctionCall.translate(FunctionCall.java:710)
Then, I tried to simplify the processing-instruction commands, using an
extra variable and it seems that Xalan can process the xsl and it seems
it works ok.
25,26c25
< <xsl:variable name="pivaluebck"
select="/processing-instruction('xml-stylesheet')"/>
< <xsl:variable name="pivalue"
select="translate(normalize-space($pivaluebck[1]), ' ', '')"/>
---
> <xsl:variable name="pivalue"
select="translate(normalize-space(/processing-instruction('xml-stylesheet')[1]),
' ', '')"/>
¿Is it possible to make a change in xsltforms xsl like this to al the
proccessing-instruction lines to be able to use it with Xalan?
In addition, I have seen that you have some processing-instruction lines
duplicated (css-conversion and xsltforms-options ones). Taking in
account that the processing instructions you have are global, and are
located in the top of xml document if defined, maybe is better to
retrieve its value at the beginning of the document (I completely ignore
if this can affect to your xsl, it is only a suggestion).
Best Regards,
Javier
COUTHURES Alain escribió:
> Hello Javier,
>> 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 );*
>> }
> It sounds like a Xalan problem... Did you already have a look at posts
> concerning similar problems :
> http://stackoverflow.com/questions/1235121/java-problem-loading-stylesheet
> , http://dev.eclipse.org/newslists/news.eclipse.webtools/msg18031.html ?
>
> Best regards,
>
> -Alain
|
|
From: COUTHURES A. <ala...@ag...> - 2009-11-05 08:13:28
|
Hello,
Here are some recent links concerning XSLTForms:
* a huge OASIS invoice example:
http://spec.cenbii.eu/Tools/invoice-example/invoice-xform-xsltForms.xml
* at W3C TPAC: http://www.w3.org/2009/11/04-tpac-minutes.html and
http://www.w3.org/2009/Talks/11-04-steven-backplane/
* XForms vs. Web Forms:
http://groups.google.com/group/openweb-group/browse_thread/thread/873d75bf62a48204/1f13db737922708e?hide_quotes=no
So, it seems XSLTForms is well known now!
Best regards,
-Alain
|
|
From: COUTHURES A. <ala...@ag...> - 2009-11-03 19:55:11
|
Hello Javier,
> 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 );*
> }
It sounds like a Xalan problem... Did you already have a look at posts
concerning similar problems :
http://stackoverflow.com/questions/1235121/java-problem-loading-stylesheet
, http://dev.eclipse.org/newslists/news.eclipse.webtools/msg18031.html ?
Best regards,
-Alain
|
97 messages has been excluded from this view by a project administrator.
