AW: Limitations of strutscx

Hi Hartmut Kern,

Sorry fort the late respond on your question. - Did you solve the problem
meanwhile? Otherwise please give us more input on the problem you like to
solve.

Regards,

Berny



-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]] Im Auftrag von Hartmut
Kern
Gesendet: Mittwoch, 8. September 2004 15:14
An: [email protected]
Betreff: [Strutscx-user] 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




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php