-Source Java Consultant
Creator, Tapestry: Java Web Components
http://howardlewisship.com
-Original Message-
From: Christian Essl [mailto:[EMAIL PROTECTED]
Sent: Monday, March 08, 2004 4:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [HiveMind] nested schemas
Thanks for the hint
]
Subject: Re: [HiveMind] nested schemas
Thanks for the hint on schema-id!
I've added it now. Checking and complaining early :).
I removed the configuration-id and service-id atts and have just
schema-id.
However I still want to access schemas even if they don't
provide an id.
Therefore in my current
Essl [mailto:[EMAIL PROTECTED] Sent: Friday, March
05, 2004 10:35 PM
To: [EMAIL PROTECTED]
Subject: [HiveMind] nested schemas
I think I have solved my problem with a element content definition based
on another schema. (I include the patch).
To do that I had to modify the core. There is now
: [HiveMind] nested schemas
I'm a little nervous about the use of configuration-id or service-id ... why not
schema-id.
Recently, schema was, effectively, promoted to first-class status (a schema's id is
qualified with
the module id and may be referenced from other modules).
--
Howard M. Lewis Ship
-Source Java Consultant
Creator, Tapestry: Java Web Components
http://howardlewisship.com
-Original Message-
From: Christian Essl [mailto:[EMAIL PROTECTED]
Sent: Friday, March 05, 2004 10:35 PM
To: [EMAIL PROTECTED]
Subject: [HiveMind] nested schemas
I think I have solved my
I was just wondering if it is much work to make it possible to reference a
schema from within an element. Something like:
element ..
.
content schema-id=
or service-id=
or configuration-id=..
parentMethod=../
/element
The content tag would