On 17 Mar 2009, at 01:09, Dan Allen wrote:
Therefore, we can increase the "type safety" of the XSD by
restricting the category of child elements that can be placed in the
class element. However, I don't know how to do this in XSD - any
pointers?
Assuming you know all the possible elements up front, this is done
with a <xs:choice> and/or <xs:sequence>. However, I suspect what you
are saying is that there could be elements that aren't known at the
time the XSD is generated.
Yes, I need to restrict the "category/class/type" of elements, not the
elements themselves. The actual elements which can go there aren't
known at xsd creation time.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than
a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a
message if
you feel that it did not reach my attention.
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete