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?

I suspect we can't do this natively using XSD, but we can at least mark this as a point that only certain categories of elements can be placed, and domain-aware editor like JBoss Tools can use this. In this case, any suggestions for how to do this "mark"?

Hi Norman, and other XML experts, One of the tasks for Web Beans is to build an XSD. There is an XSD per package, and an root-element per class. Classes can have annotations, such as bindings, which makes them into a bean. This means, for example, that a child element of the class element could be a binding type annotation (it's XML element equivalent), however placing, for example, an annotation which is not, for example, a binding type would be an error. 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?

could be described by XML: <acme:Foo> </acme:Foo> Now, I want to add the binding com.acme.sales.Bar to the Foo class: <acme:Foo> <sales:Bar /> </acme:Foo> In other words, any binding type can be inserted as a child element to a class. So, we need a way to identify this as a point that any binding type can be inserted. Does this explain it better?

Jason T. Greene wrote: > > <xs:element name="bindingElement" type="bindingType"/> > > <xs:complexType name="classType"> >  <xs:sequence> >    <xs:element ref="bindingElement"/> >  </xs:sequence> > </xs:complexType> > > // in the sales namespace > <xs:element name="Bar" substitutionGroup="webbeans:bindingElement"/> > > // in the acme namespace > <xs:element name="Foo" type="classType"/> > > You also want to make bindingElement abstract (abstract=true). -- Jason T. Greene JBoss, a division of Red Hat _______________________________________________ webbeans-dev mailing list webbeans-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/webbeans-dev

Yes, that would be one way to implement it. Though I would properly do this under the ee namespace... On 20 Mar 2009, at 07:14, Nicklas Karlsson wrote: > Back to the issue at hand ;-) > > So. Is my understanding correct that we would have one hand-written > webbeans.xsd somewhere that defines that a beanType can have children > that are constructor parameters, methods and fields and they have > corresponding methodType, fieldType etc that describe them and then > the schema.xsd:s which are generated dynamically just describe the > structure of the classes and refer to wb:beanType, wb:fieldType, > wb:methodType etc? > > On Thu, Mar 19, 2009 at 5:59 PM, Jason T. Greene > <jason.greene(a)redhat.com&gt; wrote: >> Jason T. Greene wrote: >>> >>> <xs:element name="bindingElement" type="bindingType"/> >>> >>> <xs:complexType name="classType"> >>> <xs:sequence> >>> <xs:element ref="bindingElement"/> >>> </xs:sequence> >>> </xs:complexType> >>> >>> // in the sales namespace >>> <xs:element name="Bar" substitutionGroup="webbeans:bindingElement"/> >>> >>> // in the acme namespace >>> <xs:element name="Foo" type="classType"/> >>> >>> >> >> You also want to make bindingElement abstract (abstract=true). >> >> -- >> Jason T. Greene >> JBoss, a division of Red Hat >> _______________________________________________ >> webbeans-dev mailing list >> webbeans-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/webbeans-dev >> > > > > -- > --- > Nik -- Pete Muir http://www.seamframework.org http://in.relation.to/Bloggers/Pete

Pete, my memory is there are 2 or 3 ways to do "inheritance" in XML schemas. I recommend you buy a book on this and read it :) Sent from my iPhone On Mar 19, 2009, at 7:40 AM, Pete Muir <pmuir(a)redhat.com&gt; wrote: > > On 18 Mar 2009, at 04:38, Jason T. Greene wrote: > >> Pete Muir wrote: >>> Hi Norman, and other XML experts, >>> One of the tasks for Web Beans is to build an XSD. There is an >>> XSD per package, and an root-element per class. Classes can have >>> annotations, such as bindings, which makes them into a bean. This >>> means, for example, that a child element of the class element >>> could be a binding type annotation (it's XML element equivalent), >>> however placing, for example, an annotation which is not, for >>> example, a binding type would be an error. >>> 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? >> >> I'm not sure I understand what you want, however it sounds like a >> substitution group. Can you give an example? > > For example in package com.acme > > class Foo { > > > } > > could be described by XML: > > <acme:Foo> > > </acme:Foo> > > Now, I want to add the binding com.acme.sales.Bar to the Foo class: > > <acme:Foo> > <sales:Bar /> > </acme:Foo> > > In other words, any binding type can be inserted as a child element > to a class. So, we need a way to identify this as a point that any > binding type can be inserted. > > Does this explain it better? > >> >> >> -- >> Jason T. Greene >> JBoss, a division of Red Hat > > -- > Pete Muir > http://www.seamframework.org > http://in.relation.to/Bloggers/Pete > > _______________________________________________ > webbeans-dev mailing list > webbeans-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/webbeans-dev

Not fair, Pete, you get paid to be insulted! ;-) On 3/19/09, Pete Muir <pmuir(a)redhat.com&gt; wrote: > s/Pete/Nik/ :-) > > I'm just proxying Nik's questions for some reason here... > > On 19 Mar 2009, at 15:06, Gavin King wrote: > >> Pete, my memory is there are 2 or 3 ways to do "inheritance" in XML >> schemas. I recommend you buy a book on this and read it :) >> >> Sent from my iPhone >> >> On Mar 19, 2009, at 7:40 AM, Pete Muir <pmuir(a)redhat.com&gt; wrote: >> >>> >>> On 18 Mar 2009, at 04:38, Jason T. Greene wrote: >>> >>>> Pete Muir wrote: >>>>> Hi Norman, and other XML experts, >>>>> One of the tasks for Web Beans is to build an XSD. There is an >>>>> XSD per package, and an root-element per class. Classes can have >>>>> annotations, such as bindings, which makes them into a bean. This >>>>> means, for example, that a child element of the class element >>>>> could be a binding type annotation (it's XML element equivalent), >>>>> however placing, for example, an annotation which is not, for >>>>> example, a binding type would be an error. >>>>> 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? >>>> >>>> I'm not sure I understand what you want, however it sounds like a >>>> substitution group. Can you give an example? >>> >>> For example in package com.acme >>> >>> class Foo { >>> >>> >>> } >>> >>> could be described by XML: >>> >>> <acme:Foo> >>> >>> </acme:Foo> >>> >>> Now, I want to add the binding com.acme.sales.Bar to the Foo class: >>> >>> <acme:Foo> >>> <sales:Bar /> >>> </acme:Foo> >>> >>> In other words, any binding type can be inserted as a child element >>> to a class. So, we need a way to identify this as a point that any >>> binding type can be inserted. >>> >>> Does this explain it better? >>> >>>> >>>> >>>> -- >>>> Jason T. Greene >>>> JBoss, a division of Red Hat >>> >>> -- >>> Pete Muir >>> http://www.seamframework.org >>> http://in.relation.to/Bloggers/Pete >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > webbeans-dev mailing list > webbeans-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/webbeans-dev > -- Sent from my mobile device --- Nik