xsltforms-support Mailing List for XSLTForms (Page 38)
Brought to you by:
alain-couthures
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: Adam M. <Ada...@gm...> - 2012-11-30 00:59:26
|
Hello fans of XsltForms, and Alain in particular :) I was just testing with r562, and I noticed that when an element is marked as *required* and it has no value (node.value === ""), the node is given the *notvalid* property, but this doesn't translate into the corresponding HTML control element receiving the *xforms-invalid* attribute (it continues on with *xforms-valid* attribute). I found new code at the start of *XsltForms_control.prototype.changeProp()*which seems to be responsible for this. The effect of the new code seems to be that *notvalid* is taken to be false when the new value is empty and there's been no validation error. It seems as if the code is at odds with itself a bit here -- one part of the code gives the node the *notvalid*property, but other code overrides that. Consider a node with all the following properties: *** has an empty value (node.value === '') *** has property *required* * * *has attribute *xsi:nil='true'* (automatically set via a bind when the value is empty) * has corresponding type that specializes *xs:string* to require min-length = 1 The control for such a node seems to retain *xforms-valid* attribute because of the new code in *XsltForms_control.prototype.changeProp()*. If * XsltForms_control.prototype.changeProp()* only returned *XsltForms_browser.getBoolMeta(node, prop)* (as before) then the control would receive the attribute * xforms-invalid*. Should the new code in *XsltForms_control.prototype.changeProp()* be changed to consider *xsi:nil* ? A node which is *nil*, but is also required - can surely not be considered valid. Please let me know your thoughts on this. Thanks very much for all your work on this excellent project :) /Adam |
From: Alain C. <ala...@ag...> - 2012-11-27 21:11:50
|
Hello Mark, > I'm about to find out if the list supports PDF attachments... > > We have made some minor changes to the xsltforms JS and XSL (using > label instead of span in a list of radio buttons/checkboxes). Please send me these patches, I can integrate them in the next build if you agree. > > We have identified two more sets of changes we would like to make so > that screen-readers make sense to the user, but our JS/XSL/framework > knowledge isn't really up to it. > > Examples and explanations are attached (possibly). I can see what to do with these explanations but missing ids should be generated with the same algorithm. Thanks! -Alain |
From: Alain C. <ala...@ag...> - 2012-11-27 21:03:04
|
Hello Ihe, > Could somebody explain what the inner and outer attributes of setnode do. > > It's like with .innerHTML and .outerHTML: @inner will replace the node content and @outer will replace the node itself. -Alain |
From: Ihe O. <ihe...@gm...> - 2012-11-27 13:11:08
|
Could somebody explain what the inner and outer attributes of setnode do. I set up and ran the example in CSM's message and it didn't do anything?. On Thu, Nov 22, 2012 at 10:31 PM, Stephen Cameron <ste...@gm...> wrote: > Hi Ihe, > > There is also an non-standard 'setnode' XPath action that is useful in this > scenario. > > there is an example form here: > http://www.mail-archive.com/xsl...@li.../msg00331.html > > but I've used it thus: > > <xf:setnode ref="instance('xform')" > outer="transform(instance('built_schema'),'xslt/generator_1.0.xsl')"/> > > Cheers > > > On Fri, Nov 23, 2012 at 1:31 AM, Ihe Onwuka <ihe...@gm...> wrote: >> >> I need to do transformations, both pre and post on data in my XForms >> instance. Actually I could transform before loading but I need to >> transform after the user edits the XForm as well. >> >> I've come across bits and bobs suggesting you can load a stylesheet >> into an instance. Could somebody direct me to where I can get more >> info on how to accomplish this. >> >> Also are such transforms XSLT 1.0 or 2.0. I am running XSLTForms from >> eXist. >> >> thanks >> >> >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Mark B. <ma...@te...> - 2012-11-26 15:31:30
|
I'm about to find out if the list supports PDF attachments… We have made some minor changes to the xsltforms JS and XSL (using label instead of span in a list of radio buttons/checkboxes). We have identified two more sets of changes we would like to make so that screen-readers make sense to the user, but our JS/XSL/framework knowledge isn't really up to it. Examples and explanations are attached (possibly). Any comments, hints/tips on how to implement these, or even someone prepared to do it? Thanks Mark On 19 Nov 2012, at 22:01, Stephen Cameron <ste...@gm...> wrote: > Hi Mark, > yes, this is important and has been in the back of my mind for a while > http://webguide.gov.au/accessibility-usability/accessibility/ > I hope you can have some success! > > On Mon, Nov 19, 2012 at 11:02 PM, Mark Barratt <ma...@te...> wrote: > We are making some forms (with xsltforms, of course) for a site where the requirement is for everything to conform to WAI AA accessibility. > > Out of the box the xsltforms framework doesn't deliver conformance. > > We are working on making it conform. Does anyone else here have some experience (we are quite new to the framework and we are mainly designers not developers) that they would like to share? > > We will share our experience when (if?) we have got it conforming, of course. > > > -- > Mark Barratt > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Florent G. <li...@fg...> - 2012-11-25 15:11:59
|
Alain Couthures wrote: Hi, >> By the way, have you considered migrating to (or having an >> alternative version for) Saxon CE? > There is an issue for Saxon CE as main XSLT engine for > XSLTForms: browsers don't want adjacent text nodes in generated > SCRIPT elements. Even if XSLTForms could easily be modified > for this, performance is not good. Thanks for the details. Too bad for the performance issue. But maybe if there was a version using CE, it would be a good use case for Saxonica to invest time in performance tuning? ;-) Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ |
From: Jens Ø. P. <oe...@gm...> - 2012-11-25 09:17:43
|
Hi Alain, Dropping the file in the "data" collection, noting its name in "examples.xml" and giving it an @id is all you need to display the form. I remove your pi as well, since it could confuse, but that is not necessary. The only exception is "hello2.xml" where I have changed the location of the external instance. Obviously, I could simply have scanned the files in the collection and have displayed them as a list, but I wanted to have the possibility to add information and note urls and paths to other files, as well as to group (not really used yet) and sort the examples, and it seemed easier in this (slightly redundant) way. In "form.xq", I have a function to add elements to the forms. I add some css, mainly to supply a margin, add a description (not really used yet), and I add buttons to open the forms and instances in eXide. In the eXist-db documentation, for instance in the Demo, it is standard to have the ability to open (and alter) queries and data files, and I wished to make this possible with your forms as well. I would be more than pleased if I could add any suggestions you might have to the app before the final release of eXist-db. I think a more systematic presentation of xforms should be made, something in the manner of the betterform feature explorer, but obviously that takes more time. Cheers, Jens On Nov 24, 2012, at 11:22 PM, Alain Couthures <ala...@ag...> wrote: > Hi Jens, > > Thank you for creating the XSLTForms Demo. > > Could you please confirm that after adding the source file for a new example, the examples.xml file is the only one to be updated? > > And I wonder why you added an hidden anchor for eXide? > > Cheers, > > -Alain > > Le 23/11/2012 10:32, Jens Østergaard Petersen a écrit : >> Hi, >> >> This morning a release candidate for the 2.0 version of eXist-db has been made available for download. >> >> XSLTForms is installed by default (rev 559) as a library in /db/apps/, as well as the first draft of an XSLTForms Demo. >> >> Please assist in making the XSLTForms Demo show more XSLTForms features. >> >> I copy below Wolfgang Meier's announcement of the release. >> >> Cheers, >> >> Jens >> >> > |
From: Alain C. <ala...@ag...> - 2012-11-24 22:22:27
|
Hi Jens, Thank you for creating the XSLTForms Demo. Could you please confirm that after adding the source file for a new example, the examples.xml file is the only one to be updated? And I wonder why you added an hidden anchor for eXide? Cheers, -Alain Le 23/11/2012 10:32, Jens Østergaard Petersen a écrit : > Hi, > > This morning a release candidate for the 2.0 version of eXist-db has been made available for download. > > XSLTForms is installed by default (rev 559) as a library in /db/apps/, as well as the first draft of an XSLTForms Demo. > > Please assist in making the XSLTForms Demo show more XSLTForms features. > > I copy below Wolfgang Meier's announcement of the release. > > Cheers, > > Jens > > |
From: Alain C. <ala...@ag...> - 2012-11-24 21:00:16
|
Hi Florent, > >> Because the XSLT engine is the one of the browser, this is XSLT 1.0. > By the way, have you considered migrating to (or having an alternative version for) Saxon CE? There is an issue for Saxon CE as main XSLT engine for XSLTForms: browsers don't want adjacent text nodes in generated SCRIPT elements. Even if XSLTForms could easily be modified for this, performance is not good. As an engine for the transform() function, the performance issue might be acceptable but I did not succeed in using the API for this use case... -Alain |
From: Florent G. <li...@fg...> - 2012-11-24 15:00:26
|
Alain Couthures wrote: Hi Alain, > Because the XSLT engine is the one of the browser, this is XSLT 1.0. By the way, have you considered migrating to (or having an alternative version for) Saxon CE? Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ |
From: Jens Ø. P. <oe...@gm...> - 2012-11-23 09:32:32
|
Hi, This morning a release candidate for the 2.0 version of eXist-db has been made available for download. XSLTForms is installed by default (rev 559) as a library in /db/apps/, as well as the first draft of an XSLTForms Demo. Please assist in making the XSLTForms Demo show more XSLTForms features. I copy below Wolfgang Meier's announcement of the release. Cheers, Jens ### On Nov 23, 2012, at 10:03 AM, Wolfgang Meier <wol...@ex...> wrote: A release candidate for the 2.0 version is now available for download from Sourceforge: https://sourceforge.net/projects/exist/files/Stable/2.0/ The purpose of this release is to test the setup a last time and give documentation authors a chance to see how the final thing will look like. As you will certainly recognize, a lot has changed on the surface compared to the tech preview: the new launcher integrates with the desktop and installs a system tray icon (on those systems which support it, i.e. Windows, Mac and some Unix flavors). The dashboard is now the central hub of eXist-db and replaces the old home screen, featuring a range of plugins and apps. The entire web content has been modularized and moved into self-contained, installable apps. Creating your own apps should be rather painless using eXide's app wizard. We'll be happy to hear any issues you find. At this point, we're in particular interested to get feedback on * does the installer work properly for you? Is it too large and shall we disable some extensions? Right now it has most extension modules enabled, including xslfo and content extraction, which adds a lot to its size. We consider providing a stripped-down alternative with just the bare minimum. * do the fallbacks we built into the launcher work on those systems which do not support the Java desktop integration? * is installing/deinstalling packages via the package manager reliable on all systems? The release candidate has been verified to work properly with Java 6 and 7 (some problems reported with OpenJDK 6). We are heading for a mid-December release of 2.0 final. Happy Testing, Wolfgang |
From: Stephen C. <ste...@gm...> - 2012-11-22 22:31:40
|
Hi Ihe, There is also an non-standard 'setnode' XPath action that is useful in this scenario. there is an example form here: http://www.mail-archive.com/xsl...@li.../msg00331.html but I've used it thus: <xf:setnode ref="instance('xform')" outer="transform(instance('built_schema'),'xslt/generator_1.0.xsl')"/> Cheers On Fri, Nov 23, 2012 at 1:31 AM, Ihe Onwuka <ihe...@gm...> wrote: > I need to do transformations, both pre and post on data in my XForms > instance. Actually I could transform before loading but I need to > transform after the user edits the XForm as well. > > I've come across bits and bobs suggesting you can load a stylesheet > into an instance. Could somebody direct me to where I can get more > info on how to accomplish this. > > Also are such transforms XSLT 1.0 or 2.0. I am running XSLTForms from > eXist. > > thanks > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Alain C. <ala...@ag...> - 2012-11-22 21:24:11
|
Hello Ihe, > I need to do transformations, both pre and post on data in my XForms > instance. Actually I could transform before loading but I need to > transform after the user edits the XForm as well. > > I've come across bits and bobs suggesting you can load a stylesheet > into an instance. Could somebody direct me to where I can get more > info on how to accomplish this. Have a look at http://www.agencexml.com/xsltforms/survey.xml This is a new example I just added to demonstrate CSV submission with XSLT preprocessing. > > Also are such transforms XSLT 1.0 or 2.0. I am running XSLTForms from eXist. Because the XSLT engine is the one of the browser, this is XSLT 1.0. Thank you for you feedbacks! -Alain |
From: Ihe O. <ihe...@gm...> - 2012-11-22 14:31:35
|
I need to do transformations, both pre and post on data in my XForms instance. Actually I could transform before loading but I need to transform after the user edits the XForm as well. I've come across bits and bobs suggesting you can load a stylesheet into an instance. Could somebody direct me to where I can get more info on how to accomplish this. Also are such transforms XSLT 1.0 or 2.0. I am running XSLTForms from eXist. thanks |
From: Alex B. <ale...@gm...> - 2012-11-20 11:27:15
|
Dear Alain, Thank you for improving xforms. The option which you have added into xfoms works fine! With best regards, Alexander 2012/11/11 Alain Couthures <ala...@ag...> > Hi Alex, > > I have now added a new option for that: > > <?xsltforms-options required-position="left"?> > > It will be effective for all required controls with a label in the current > form. > > As for other options, this one can be added in a config.xsl file. > > Thank you for your feedbacks! > > -Alain > > Le 12/10/2012 15:32, Alain Couthures a écrit : > >> Hi Alex and all, >> >> This can probably be managed by a config option. Would it be an >> interesting way to proceed? >> >> Thank you for your point of views! >> >> -Alain >> >> Le 10/10/2012 13:15, Alex Bozhenko a écrit : >> >>> Does it possible to put >>> <span class="xforms-required-icon">***</span> >>> after >>> <label class="xforms-label"> >>> (if label exist for this input), but not after >>> <span class="value"> >>> ? >>> >> >> ------------------------------**------------------------------** >> ------------------ >> Don't let slow site performance ruin your business. Deploy New Relic APM >> Deploy New Relic app performance management and know exactly >> what is happening inside your Ruby, Python, PHP, Java, and .NET app >> Try New Relic at no cost today and get our sweet Data Nerd shirt too! >> http://p.sf.net/sfu/newrelic-**dev2dev<http://p.sf.net/sfu/newrelic-dev2dev> >> ______________________________**_________________ >> Xsltforms-support mailing list >> Xsltforms-support@lists.**sourceforge.net<Xsl...@li...> >> https://lists.sourceforge.net/**lists/listinfo/xsltforms-**support<https://lists.sourceforge.net/lists/listinfo/xsltforms-support> >> >> > |
From: Alain C. <ala...@ag...> - 2012-11-19 12:26:20
|
Hello Mark, Could you please elaborate with some examples? I figure that there are missing attributes for the generated HTML elements, is that right? Probably, the XSLT stylesheet will be more concerned that the Javascript part... Are you familiar with XSLT? Thanks! -Alain Le 19/11/2012 13:02, Mark Barratt a écrit : > We are making some forms (with xsltforms, of course) for a site where the requirement is for everything to conform to WAI AA accessibility. > > Out of the box the xsltforms framework doesn't deliver conformance. > > We are working on making it conform. Does anyone else here have some experience (we are quite new to the framework and we are mainly designers not developers) that they would like to share? > > We will share our experience when (if?) we have got it conforming, of course. > > > -- > Mark Barratt > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Mark B. <ma...@te...> - 2012-11-19 12:18:29
|
We are making some forms (with xsltforms, of course) for a site where the requirement is for everything to conform to WAI AA accessibility. Out of the box the xsltforms framework doesn't deliver conformance. We are working on making it conform. Does anyone else here have some experience (we are quite new to the framework and we are mainly designers not developers) that they would like to share? We will share our experience when (if?) we have got it conforming, of course. -- Mark Barratt |
From: Alain C. <ala...@ag...> - 2012-11-11 06:38:27
|
Hi Alex, I have now added a new option for that: <?xsltforms-options required-position="left"?> It will be effective for all required controls with a label in the current form. As for other options, this one can be added in a config.xsl file. Thank you for your feedbacks! -Alain Le 12/10/2012 15:32, Alain Couthures a écrit : > Hi Alex and all, > > This can probably be managed by a config option. Would it be an > interesting way to proceed? > > Thank you for your point of views! > > -Alain > > Le 10/10/2012 13:15, Alex Bozhenko a écrit : >> Does it possible to put >> <span class="xforms-required-icon">*</span> >> after >> <label class="xforms-label"> >> (if label exist for this input), but not after >> <span class="value"> >> ? > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Alain C. <ala...@ag...> - 2012-11-08 06:50:53
|
Hello Peter, The @value content is not a valid XPath expression. Should it be: concat('http://{myserver}/some-service.php?u=' ,instance('read-val')/value/u) ?? Did you try with the @instance attribute instead of @targetref? Because of the cross-domain restriction, XSLTForms tries to use JSONP when the requested domain is different from the domain from which the form came. IE8 comes with a debugger but I don't remember if there is a Network profiler. Did you give it a try? Thank you for your feedbacks! -Alain Le 07/11/2012 13:35, peter winstanley a écrit : > Hello List > > I have a draft xform with a submission: > > <xf:submission id="test-submit" method="get" replace="instance" targetref="instance('service-response-instance')" serialization="none" mode="synchronous" mediatype="text/xml"> > <xf:resource value="concat('http://{myserver}/some-service.php?u=' ,instance('read-val'))value/u"/> > </xf:submission> > > > In Firefox 16 this gives me a submission to http://{myserver}/some-service.php?u=12345 which seems correct > but with IE7 it gives me a submission error that I am still trying to diagnose, and on IE8 it gives an error and the submission is http://{myserver}/some-service.php?u=12345&callback=jsoninst > > Any thoughts/ideas? > > Cheers > > Peter > > ____________________________________________________________ > FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! > Visit http://www.inbox.com/photosharing to find out more! > > > |
From: Alain C. <ala...@ag...> - 2012-11-08 06:39:52
|
Hi Elias, Is it possible for you to send me a test form? Thanks! -Alain Le 05/11/2012 23:29, Elias Mazur a écrit : > Hi Alain. > > I added a prefix on the instance as you suggested and still gives me > the same message. From what I understand, xsi:type allows you to bind > an element outside the default namespace. My instance starts with the > <Document> element and it defines the instance namespace xsi and > xsi:schemaLocation which should resolve xsi:type , at least I think > that's the theory behind it. It validates fine, but I can't get it to > work with XSLTForms. Any suggestion is greatly appreciated. > > Thanks > Elias > > On Thu, Nov 1, 2012 at 11:20 AM, Alain Couthures > <ala...@ag... <mailto:ala...@ag...>> > wrote: > > Hello Elias, > > Welcome to XSLTForms support list! > > I suspect a namespace issue: there is no prefix in your example > and XForms assumes that the default namespace to be its own. > > Is it possible for you to add a prefix in your instance, at least > just for test purposes? > > Thank you for your feedbacks! > > -Alain > > Le 01/11/2012 16:09, Elias Mazur a écrit : >> Hi. >> >> I'm trying to create an instance that has an xsi:type attribute. >> The instance defines the xsi namespace and xsi:schemaLocation at >> the root element as follows: >> >> <Document xmlns="urn:hl7-org:v3" >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >> xsi:schemaLocation="urn:hl7-org:v3 >> http://localhost:8080/exist/rest/db/studydata/schemas/StudyDesign.xsd" >> classCode="DOCCLIN" moodCode="EVN"> >> >> and the node that is breaking is the <effectiveTime> with the >> xsi:type attribute: >> >> <component3 typeCode="COMP"> >> <substanceAdministration classCode="SBADM" moodCode="DEF"> >> <effectiveTime xsi:type="PIVL_TS"> >> <period value="1" unit="day"/> >> </effectiveTime> >> <routeCode code="xxxx" displayName="ORAL" codeSystem="1.22.3.3"/> >> <doseQuantity value="0.625" unit="mg"/> >> <consumable typeCode="CSM" xsi:nil="true"/> >> </substanceAdministration> >> </component3> >> >> The XML validates fine against the instance schema in the xsi >> definition using XML spy as well as the xquery validate eXist >> functions (JAXP, JAXV and JING). Environment is eXist database, >> Xquery. >> >> Problem: when I try to create the instance as follows: >> >> <xf:model id="hl7-message"> >> <xf:instance id="sd-model" >> src="http://localhost:8080/exist/rest/db/studydata/instances/studydesign-model.xml" >> /> >> </xf:model> >> >> I get a "Message from webpage" pop error message (see attached): >> >> "Type PIVL_TS not defined in namespace >> http://www.w3.org/2002/xforms" >> >> The complex type PIVL_TS is defined in one of the schemas >> included in "StudyDesign.xsd" defined in xsi:schemaLocation. >> >> Any help is appreciated. >> >> Thanks >> Elias >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> >> >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... <mailto:Xsl...@li...> >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
From: peter w. <p....@in...> - 2012-11-07 12:35:54
|
Hello List I have a draft xform with a submission: <xf:submission id="test-submit" method="get" replace="instance" targetref="instance('service-response-instance')" serialization="none" mode="synchronous" mediatype="text/xml"> <xf:resource value="concat('http://{myserver}/some-service.php?u=' ,instance('read-val'))value/u"/> </xf:submission> In Firefox 16 this gives me a submission to http://{myserver}/some-service.php?u=12345 which seems correct but with IE7 it gives me a submission error that I am still trying to diagnose, and on IE8 it gives an error and the submission is http://{myserver}/some-service.php?u=12345&callback=jsoninst Any thoughts/ideas? Cheers Peter ____________________________________________________________ FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more! |
From: Elias M. <eli...@gm...> - 2012-11-05 22:29:11
|
Hi Alain. I added a prefix on the instance as you suggested and still gives me the same message. From what I understand, xsi:type allows you to bind an element outside the default namespace. My instance starts with the <Document> element and it defines the instance namespace xsi and xsi:schemaLocation which should resolve xsi:type , at least I think that's the theory behind it. It validates fine, but I can't get it to work with XSLTForms. Any suggestion is greatly appreciated. Thanks Elias On Thu, Nov 1, 2012 at 11:20 AM, Alain Couthures < ala...@ag...> wrote: > Hello Elias, > > Welcome to XSLTForms support list! > > I suspect a namespace issue: there is no prefix in your example and XForms > assumes that the default namespace to be its own. > > Is it possible for you to add a prefix in your instance, at least just for > test purposes? > > Thank you for your feedbacks! > > -Alain > > Le 01/11/2012 16:09, Elias Mazur a écrit : > > Hi. > > I'm trying to create an instance that has an xsi:type attribute. The > instance defines the xsi namespace and xsi:schemaLocation at the root > element as follows: > > <Document xmlns="urn:hl7-org:v3" xmlns:xsi=" > http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:hl7-org:v3 > http://localhost:8080/exist/rest/db/studydata/schemas/StudyDesign.xsd" > classCode="DOCCLIN" moodCode="EVN"> > > and the node that is breaking is the <effectiveTime> with the xsi:type > attribute: > > <component3 typeCode="COMP"> > <substanceAdministration classCode="SBADM" moodCode="DEF"> > <effectiveTime xsi:type="PIVL_TS"> > <period value="1" unit="day"/> > </effectiveTime> > <routeCode code="xxxx" displayName="ORAL" codeSystem="1.22.3.3"/> > <doseQuantity value="0.625" unit="mg"/> > <consumable typeCode="CSM" xsi:nil="true"/> > </substanceAdministration> > </component3> > > The XML validates fine against the instance schema in the xsi definition > using XML spy as well as the xquery validate eXist functions (JAXP, JAXV > and JING). Environment is eXist database, Xquery. > > Problem: when I try to create the instance as follows: > > <xf:model id="hl7-message"> > <xf:instance id="sd-model" src=" > http://localhost:8080/exist/rest/db/studydata/instances/studydesign-model.xml" > /> > </xf:model> > > I get a "Message from webpage" pop error message (see attached): > > "Type PIVL_TS not defined in namespace > http://www.w3.org/2002/xforms" > > The complex type PIVL_TS is defined in one of the schemas included in > "StudyDesign.xsd" defined in xsi:schemaLocation. > > Any help is appreciated. > > Thanks > Elias > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today:http://p.sf.net/sfu/appdyn_sfd2d_oct > > > > _______________________________________________ > Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > |
From: Immanuel N. <imm...@go...> - 2012-11-05 12:42:42
|
Hi Dan, Since I was not able to replicate the hello2 example from http://exist-db.org/exist/xforms/hello2.xml (see above) I am now trying to get your example 1.8 running http://www.danmccreary.com/xrx/beginners-guide/beginners-guide-to-xrx.xhtml#ex.edit.xq Unfortunately, this doesn't work, too. I copied and pasted example 1.8 under /db/apps/terms/edit/edit.xq Did some corrections, namely replaced xmlns:xs="http://www.w3.org/2001/<acronym>XML</acronym>Schema" by xmlns:xs="http://www.w3.org/2001/XMLSchema" copied and pasted *Example 1.10. /db/apps/terms/edit/next-id.xml* *Example 1.11. /db/apps/terms/edit/save-new.xq* Because $file in edit.xq refers to a file named "new-instance.xml", I created a file /db/apps/terms/data/new-instance.xml with the following content: ** *<term>* * <id></id>* * <term-name>my name</term-name>* * <definition></definition>* * <publish-status-code></publish-status-code>* *</term>* ** *Now I was able to load edit.xq?new=true and it was displayed as expected.* *However, when I pushed the Save button, nothing happened. Hence, something is wrong either with XSLTform.xsl or with the example.* Again I tried to understand what is (supposed to) going on with the submission element. First of all I don't understand why the instance attribute has the value "my-task". My guess is that it should point to an existing instance in the model. Yet there is no instance named "my-task", but only one named "save-data". Therefore I changed the value of the instance attribute in the submission element accordingly. Still pushing the safe button didn't yield any effect. Then I read about Alain'2 comment that "AVT for XForms submission is not supported". But that didn't help me any further. It would be great to have a working example! - Immanuel 2012/11/1 Dan McCreary <dan...@gm...> > Hi Immanuel, > > Perhaps you should consider using HTTP POST and creating a save.xq > similar to the one in the Beginner's Guide. The problem with PUT is > that you must make sure that you have write access and this opens up > security concerns. HTTP POST allows you to use the request:get-data() > to get the incoming data file and then do an xmldb:store() > > Here is the submission line: > > <xf:submission id="save" method="post" action="{if ($new='true') then > ('save-new.xq') else ('update.xq')}" instance="my-task" > replace="all"/> > > > http://www.danmccreary.com/xrx/beginners-guide/beginners-guide-to-xrx.xhtml#d0e733 > > - Dan > > On Wed, Oct 31, 2012 at 6:06 PM, Immanuel Normann > <imm...@go...> wrote: > > Hi, > > > > I still try to understand how submission put and get works. Exist-db > comes > > with the example > > exist/webapp/xforms/hello2.xml (I assume it is known to you?! see > > http://exist-db.org/exist/xforms/hello2.xml). > > > > This example works basically as one expects. In order to learn from it I > > made copy to > > > > /db/my-hello.xml > > > > and changed only two paths in that file to fit to my setting: > > > > <xf:submission id="put-to-db" method="put" replace="none" > > resource="../rest/db/xforms-example-hello2.xml"> > > > > to > > > > <xf:submission id="put-to-db" method="put" replace="none" > > resource="/exist/rest/db/xforms-example-my-hello.xml"> > > > > and > > > > > > <xf:submission id="get-from-db" method="get" replace="instance" > > > resource="../rest/db/xforms-example-hello2.xml?_query=/person&_wrap=no"> > > > > to > > <xf:submission id="get-from-db" method="get" replace="instance" > > > resource="/exist/rest/db/xforms-example-my-hello.xml?_query=/person&_wrap=no"> > > > > And this is my problem: > > > > Let's say the initial content of > /exist/rest/db/xforms-example-my-hello.xml > > is > > > > <person> > > <name>Otto</name> > > </person> > > > > When I go to http://localhost:8080/exist/rest/db/my-hello.xmleverything is > > displayed as in the hello2 example. > > > > Now I type in the text: Anna > > and push the button: Safe > > > > This changes /exist/rest/db/xforms-example-my-hello.xml to: > > > > <person> > > <name>Anna</name> > > <name>Otto</name> > > <name/> > > <name/> > > <test/> > > <name/> > > </person> > > > > Actually this is the same effect as in the hello2 example. The first > > question here: why is > > > > <name/> > > <name/> > > <test/> > > <name/> > > > > added? I would expect only a change to > > > > <person> > > <name>Anna</name> > > <name>Otto</name> > > </person> > > > > But even more strange is the effect of the following interaction: > > > > Let's start again with > > > > <person> > > <name>Otto</name> > > </person> > > > > Now I type again the text: Anna > > but push then the button: Refresh from DB > > > > Still the content of xforms-example-my-hello.xml is (as expected): > > > > <person> > > <name>Otto</name> > > </person> > > > > However, when I type again: Anna > > And then push the button: Safe > > > > Then the content of xforms-example-my-hello.xml is: > > > > <exist:result> > > <name>Anna</name> > > </exist:result> > > > > That's not I would expect. Instead I would expect again: > > > > <person> > > <name>Anna</name> > > <name>Otto</name> > > </person> > > > > For me the behaviour of submission is thus rather unpredictable. Or do > you > > have an explanation? I would be very happy to learn how this submission > > really works. > > > > Immanuel > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_sfd2d_oct > > _______________________________________________ > > Xsltforms-support mailing list > > Xsl...@li... > > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > > > > -- > Dan McCreary > NoSQL Evangelist > office: (952) 931-9198 > cell: (612) 986-1552 > |
From: William V. <wi...@bi...> - 2012-11-03 19:06:04
|
The exact error message is this: HTTP ERROR 400 Problem accessing /exist/rest//db/NanoXFServer/input.xml. Reason: Error while serializing XML: java.io.FileNotFoundException: C:\bin\eXist\tools\wrapper\bin\config.xsl (The system cannot find the file specified) I found a workaround using XQuery to avoid the server-side transform and it worked well. It receives the XForm name as a parameter and returns it: xquery version "1.0"; declare namespace exist="http://exist.sourceforge.net/NS/exist"; declare option exist:serialize "method=xhtml media-type=application/xml process-xsl-pi=no"; let $q := request:get-parameter('form', '') let $form := doc($q) return $form Someone in the exist-open mailing list is having a similar problema> http://sourceforge.net/mailarchive/forum.php?thread_name=CAHM8cTfFc%2BxmuA0M1Eyo4tXaW3uWxCqs8Hn6U3wg%3D4MRRmM-Bw%40mail.gmail.com&forum_name=exist-open El 2012-10-31 17:27, Dan McCreary escribió: > Hi Bill, > > I am using the latest version of XSLTForms on eXist 2.0 and I did > find > that some of the javascript within the HTML files had to have the > ampersand character escaped or my loader ant tasks would not run > correctly. This was only in the code for the Tiny editor as I > recall. > > - Dan > > On Wed, Oct 31, 2012 at 3:13 PM, William Velasquez > <wi...@bi...> wrote: >> Hi, >> >> Has anybody used the latest version of XSLTForms with eXist 2.0 >> beta? >> >> I'm just testing the examples and getting errors accesing config.xsl >> in >> the local disk. >> >> When I change the PI in the XForm to the full path of XSLTForms in >> the >> eXist server, the form begins to load, but a message box with null >> reference error appers. >> >> Thanks everybody, >> >> >> Bill >> >> >> PD: Para quienes hablan Español, estoy escribiendo el libro de >> XForms >> en Wikibooks http://es.wikibooks.org/wiki/XForms Todos sus aportes >> son >> bien recibidos. >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
From: Elias M. <eli...@gm...> - 2012-11-01 15:27:44
|
Hi Alain. Thanks for the quick reply. Yes I can add a prefix in the instance. I'll do that and let you know. But, if you re-define xmlns within the root element of the instance, shouldn't it be the default namespace from that point on? We were using MozzIE before we decided to go XSLTForms and it seemed to work fine. Thanks again. Elias On Thu, Nov 1, 2012 at 11:20 AM, Alain Couthures < ala...@ag...> wrote: > Hello Elias, > > Welcome to XSLTForms support list! > > I suspect a namespace issue: there is no prefix in your example and XForms > assumes that the default namespace to be its own. > > Is it possible for you to add a prefix in your instance, at least just for > test purposes? > > Thank you for your feedbacks! > > -Alain > > Le 01/11/2012 16:09, Elias Mazur a écrit : > > Hi. > > I'm trying to create an instance that has an xsi:type attribute. The > instance defines the xsi namespace and xsi:schemaLocation at the root > element as follows: > > <Document xmlns="urn:hl7-org:v3" xmlns:xsi=" > http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:hl7-org:v3 > http://localhost:8080/exist/rest/db/studydata/schemas/StudyDesign.xsd" > classCode="DOCCLIN" moodCode="EVN"> > > and the node that is breaking is the <effectiveTime> with the xsi:type > attribute: > > <component3 typeCode="COMP"> > <substanceAdministration classCode="SBADM" moodCode="DEF"> > <effectiveTime xsi:type="PIVL_TS"> > <period value="1" unit="day"/> > </effectiveTime> > <routeCode code="xxxx" displayName="ORAL" codeSystem="1.22.3.3"/> > <doseQuantity value="0.625" unit="mg"/> > <consumable typeCode="CSM" xsi:nil="true"/> > </substanceAdministration> > </component3> > > The XML validates fine against the instance schema in the xsi definition > using XML spy as well as the xquery validate eXist functions (JAXP, JAXV > and JING). Environment is eXist database, Xquery. > > Problem: when I try to create the instance as follows: > > <xf:model id="hl7-message"> > <xf:instance id="sd-model" src=" > http://localhost:8080/exist/rest/db/studydata/instances/studydesign-model.xml" > /> > </xf:model> > > I get a "Message from webpage" pop error message (see attached): > > "Type PIVL_TS not defined in namespace > http://www.w3.org/2002/xforms" > > The complex type PIVL_TS is defined in one of the schemas included in > "StudyDesign.xsd" defined in xsi:schemaLocation. > > Any help is appreciated. > > Thanks > Elias > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today:http://p.sf.net/sfu/appdyn_sfd2d_oct > > > > _______________________________________________ > Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > |