Hello Habs,
You should have a look at this example to associate a schema to a model:
https://www.w3.org/TR/xforms/#xforms-in-xhtml-00
In your dummy schema, you should try defining co:book, co:magazine as
xsd:string with empty restriction.
Thank you for your feedback!
--Alain
Le 31/10/2016 à 23:02, b...@shroggslodge.freeserve.co.uk a écrit :
Hello Alain - thank you for taking the time to reply.
I haven't tried anything as yet as I did not have any clue as to how
to proceed. With your suggestion, please could you provide me with a
quick example of what you mean to get me underway ?
Regards
Habs
On 31 October 2016 at 21:17, Alain Couthures
<alain.couthu...@agencexml.com <mailto:alain.couthu...@agencexml.com>>
wrote:
Hello Habs,
Because "xsd:string" is the default type, did you try to define a
dummy schema with every complex type considered as atomic string
so XSLTForms cannot complain about missing type declarations?
Thank you for your feedback!
--Alain
Le 31/10/2016 à 10:01, b...@shroggslodge.freeserve.co.uk
<mailto:b...@shroggslodge.freeserve.co.uk> a écrit :
Good morning everyone
I am looking for clarification on how XSLTForms handles instance
documents where elements may contain xsi:type attributes (see
snippet below), with regards to the requirement for and location
of schemas.
Currently I pull in an instance document where this is the case
and XSLTForms is throwing up the error: "Schema for namespace
undefined not defined for type co"
- followed by an exception: "Error dispatching event
'xforms-model-construct' :"
Which has a check box to prevent creating additional dialogues.
If the error dialogue is closed etc, then it goes away the form
continues to load, however if any other action is taken (in my
case I noticed it when moving amongst a repeated set), then the
error occurs again and again. If I check the box to prevent
creating additional dialogues the form stops responding.
(Please accept that I have all the namespaces present and correct.)
Now this error is most likely due to the fact that the instance
document does not refer to a schema and neither does the xform
have a scheme attribute on the 'model' element (or have an inline
schema reference for that matter).
I believe, though I am not sure, that in any case complex types
(elements with child elements etc) are not checked when referring
to schemas in xforms. Only simple types are validated.
For my use it does not matter to check and in any case they are
complex types I am referring to, so I would like to know if the
XSLTForms behaviour allows for 'turning off' schema checking and
if so how to do it please? and if not, what may I try to remove
the error messages at least for complex types ?
Thank you for the insight and comments.
Regards
Habs
Snippet of xml in an instance document:
<catalogue>
.
.
<products>
<product xsi:type="co:book"/>
<uid>2344</uid>
<isbn>432432</isbn>
.
.
</product>
<product xsi:type="co:magazine"/>
<uid>9999</uid>
<author>432432</isbn>
.
.
</product>
</products>
.
.
</catalogue>
------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET andASP.NET <http://ASP.NET> CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
Xsltforms-support mailing list
Xsltforms-support@lists.sourceforge.net
<mailto:Xsltforms-support@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
<https://lists.sourceforge.net/lists/listinfo/xsltforms-support>
------------------------------------------------------------------------------
_______________________________________________
Xsltforms-support mailing list
Xsltforms-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
