[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [sdo] Revised Proposal for Static SDOs.doc
Hi Blaise,
I was thinking that "null" would mean "normal SDO rules
(for determining if a property is an attribute or element) apply".
With a 2 valued enum, the runtime would have no way of knowing if the programmer
expressed a wish regarding isElement or not.
Since they share the "name" and "uri" properties, maybe
@SdoXmlProperty can be a base type extended by @SdoXmlAttribute and
@SdoXmlElement?
Ron
Von: Blaise Doughan [mailto:blaise.doughan@oracle.com] Gesendet: Dienstag, 24. Februar 2009 14:50 An: Barack, Ron Cc: sdo@lists.oasis-open.org Betreff: Re: [sdo] Revised Proposal for Static SDOs.doc How about dropping @SdoXmlProperty and enhancing @SdoXmlAttribute and @SdoXmlElement? Where do you see the node type being null? @Retention(RetentionPolicy.RUNTIME) @Target(@Target({ElementType.METHOD, ElementType.FIELD}) public @interface SdoXmlElement { String name() default ""; String uri() default ""; } @Retention(RetentionPolicy.RUNTIME) @Target(@Target({ElementType.METHOD, ElementType.FIELD}) public @interface SdoXmlAttribute { String name() default ""; String uri() default ""; } -Blaise Barack, Ron wrote: 7C3EF93EEBC6EB4A8B4470853DE8656674C499@dewdfe18.wdf.sap.corp type="cite"> |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]