Limitations of strutscx
itgroup <[email protected]>
| Newsgroups | gmane.comp.java.strutscx.user |
|---|---|
| Message-ID | <[email protected]> |
Hey List, I am working with strutscx for a while. My question is bind to my new project. (See Attachments) As an overview: There is another way of xml than in the strutscx-demo: a snapshot: <xs:element name="section"> <xs:complexType> <xs:sequence> <xs:element ref="heading"/> <xs:element ref="par" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="section" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> This are real documents with sections in sections. I found that there would be a systematic problem, when I use it with castor. Am I wrong or have I to define so many variables in InfoVo as sections or paragraphs in this sections? Please contact me if I didn't could explain my problem in a understandible way. Best Regards Hartmut Kern
vlp_entries_template01_01.xsd
(application/text, 4.1 KB) - not displayed