cancel
Showing results for 
Search instead for 
Did you mean: 

How does Alfresco convert the xsd to a web form?

karljj1
Champ in-the-making
Champ in-the-making
Hi,

I have spent some time looking at Alfresco and decided that it did not meet my requirements, However I really liked the ability to convert an xsd file into a web form. Could someone offer me some advice on how Alfresco does this?

I know it uses Chiba to render the converted form but what does it use to convert the xsd to an xform?

I have looked at a few things out their that do this such as eclipse with the visual forms plugin, wdsl2xform and xsd2gui however they either fail to do the conversion or only partially convert the file. They never seem to create the buttons for insertion/deletion which is what I really need.

Any help would be great.

Here is my xsd file which works in Alfresco.

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSche… elementFormDefault="qualified">
<xs:element name="EventList">
<xs:complexType>
<xs:sequence>
<xs:element name="ExerciseName" type="xs:string"/>
<xs:element name="ExerciseDescription" type="xs:string"/>
<xs:element name="Events" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="EventName" type="xs:string"/>
<xs:element name="EventDescription" type="xs:string"/>
<xs:element name="Incidents" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="IncidentName" type="xs:string"/>
<xs:element name="IncidentDescription" type="xs:string"/>
<xs:element name="Injects" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="InjectName" type="xs:string"/>
<xs:element name="InjectDescription" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
1 REPLY 1

adrianpj
Champ in-the-making
Champ in-the-making
xforms.js plays an important role in XForms rendering.

The Web browser page downloads (via AJAX) the XForms generated by xsd2xforms , and it is interpreted by xforms.js.

I think Chiba is used in server-side just to handle events and some other non-visual stuff.