Limitations of strutscx

Hey List, (last e-mail was sent with wrong e-mail account)

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



Petition an Adobe fuer FrameMaker / Macintosh - mitmachen!
http://www.PetitionOnline.com/fmforosx/petition.html
##########################################################

                +++

Hartmut Kern M.A.

Projekt Informationstechnologie

Max- Planck-Institut für Wissenschaftsgeschichte
Wilhelmstraße 44
D-10117 Berlin
- Germany -

tel: +49 (0) 30 22 66 7 - 341
fax: +49 (0) 30 22 66 7 - 340
web:  http://www.mpiwg-berlin.mpg.de
e-mail: [email protected]

             +++