I'm trying to use the xforms genereated by this tool in Chiba (I think you know this project :-)). Following the sample, If I deploy 'purchaseOrder.xhtml' in Chiba-3.0.2b2 I get the following error
org.chiba.xml.xforms.exception.XFormsBindingException: datatype 'tns:purchaseOrderType' is unknown
But If I deploy "purchaseOrder_chiba.xhtml", it works.
Looking at the generation scripts, I only find
/tags/stable/demos/purchaseOrder/purchaseOrder.sh
that generates "purchaseOrder.xhtml" but not "purchaseOrder_chiba.xhtml"., soy I guess that this last one has been generated by hand.
So, the forms generated by this engine, are they compaible with Chiba? If not, which are the changes I have to do for making them compatible?
Thanks a lot
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, I'm just know reading the readme.txt and there is the answer
This is purchaseOrder.xsd from Chiba SVN.
The generated form cannot be directly used in Chiba, as the instance contains type declarations, which are unknown to Chiba. There is also slightly modified version in purchaseOrder_chiba.xhtml, which should work in Chiba too.
So, I see it is a Chiba problem, I will jump to the Chiba's forum :-)
You have to remove all xsi:type attributes from the instance, where type is not XML Schema type. xsi:type is required in SOAP messages, that's why it is generated by wsdl2xforms. In my case I used slightly modified version of Chiba, that doesn't give error in this case. I can send you a patch, if you like.
I'm not 100% sure though, that suppressing the error message would be the correct behaviour in this case. But including complexType schema definitions for those types in XForms output file would be nontrivial task.
One option could be to generate xsi:type attributes only from wsdl2xforms and not from schema2xforms. This is not the final solution, but would make first use experience bit smoother.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply, I will try to take a deeper look at this tool and Chiba next week.
By the way, do you think that the Orbeon integrates better with your tool than Chiba? Or that Orbeon is "better" (it's always hard to know what this word means) than Chiba?
Thanks a lot
Isi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This should certainly be no Orbeon bashing but i can't see why you think Orbeon to be more stable - probably you should have a look at the latest Chiba code (in SVN NOT b2). We've worked hard on conformance testing and ourstanding issue with the standard and we are currently passing 98% of the normative XForms 1.1 test suite. The remaining fails (less than 10 tests) are partly issues with the test suite itself which we have submitted to the WG and have been clarified in the meantime.
I agree that we still have a documentation weakness but we are working on that too. Watch out for our next release which we are preparing right now and hopefully will become available later this month or at worst until midth of Feb.
And of course Chiba is supporting xsi:type in instances. We heavily use that in projects.
Maybe it's also of interest to mention that we are now 4 people here working on Chiba instead of 2 as was the case for long years.
Joern
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi:
I'm trying to use the xforms genereated by this tool in Chiba (I think you know this project :-)). Following the sample, If I deploy 'purchaseOrder.xhtml' in Chiba-3.0.2b2 I get the following error
org.chiba.xml.xforms.exception.XFormsBindingException: datatype 'tns:purchaseOrderType' is unknown
But If I deploy "purchaseOrder_chiba.xhtml", it works.
Looking at the generation scripts, I only find
/tags/stable/demos/purchaseOrder/purchaseOrder.sh
that generates "purchaseOrder.xhtml" but not "purchaseOrder_chiba.xhtml"., soy I guess that this last one has been generated by hand.
So, the forms generated by this engine, are they compaible with Chiba? If not, which are the changes I have to do for making them compatible?
Thanks a lot
Sorry, I'm just know reading the readme.txt and there is the answer
This is purchaseOrder.xsd from Chiba SVN.
The generated form cannot be directly used in Chiba, as the instance contains type declarations, which are unknown to Chiba. There is also slightly modified version in purchaseOrder_chiba.xhtml, which should work in Chiba too.
So, I see it is a Chiba problem, I will jump to the Chiba's forum :-)
Thanks
Isi
PD: I found the clue at https://chiba-project.org/trac/ticket/411
You have to remove all xsi:type attributes from the instance, where type is not XML Schema type. xsi:type is required in SOAP messages, that's why it is generated by wsdl2xforms. In my case I used slightly modified version of Chiba, that doesn't give error in this case. I can send you a patch, if you like.
I'm not 100% sure though, that suppressing the error message would be the correct behaviour in this case. But including complexType schema definitions for those types in XForms output file would be nontrivial task.
One option could be to generate xsi:type attributes only from wsdl2xforms and not from schema2xforms. This is not the final solution, but would make first use experience bit smoother.
Thanks for the reply, I will try to take a deeper look at this tool and Chiba next week.
By the way, do you think that the Orbeon integrates better with your tool than Chiba? Or that Orbeon is "better" (it's always hard to know what this word means) than Chiba?
Thanks a lot
Isi
I would say, that Orbeon seems more stable, has working business model and seems to evolve faster. And they certainly have better documentation.
I haven't really tested wsdl2xforms with Orbeon, but I'm hoping to it in november-december.
This should certainly be no Orbeon bashing but i can't see why you think Orbeon to be more stable - probably you should have a look at the latest Chiba code (in SVN NOT b2). We've worked hard on conformance testing and ourstanding issue with the standard and we are currently passing 98% of the normative XForms 1.1 test suite. The remaining fails (less than 10 tests) are partly issues with the test suite itself which we have submitted to the WG and have been clarified in the meantime.
I agree that we still have a documentation weakness but we are working on that too. Watch out for our next release which we are preparing right now and hopefully will become available later this month or at worst until midth of Feb.
And of course Chiba is supporting xsi:type in instances. We heavily use that in projects.
Maybe it's also of interest to mention that we are now 4 people here working on Chiba instead of 2 as was the case for long years.
Joern
Hi tambetm,
Pls send me Chiba patch which not raise error in xsi:type since i also have the same issue.
Thanks
CH
I put Validator.patch under Files.