OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sdo message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: AW: [sdo] Revised Proposal for Static SDOs.doc


Title: Revised Proposal for Static SDOs.doc
Hi Blaise,
 
Embarrassing mistake here:  annotations do not allow "extends" clauses.  In that case, I have a slight preference for the proposal as it is currently written up, since it allows the user to either make something an element explicitly or to allow SDO to decide itself.  That said, I really don't want to hold up accepting this proposal based on this issue.  If this is the only thing that is hold you back from supporting the proposal, let me know and I will replace my @SdoXmlElement and @SdoXmlProperty with the annotations you have specified.
 
For everyone else, the proposal was reviewed and discussed at the vF2F, I think there is consensus here.  I'd like to resolve ISSUE 22 (as well as ISSUE 13, ISSUE 25, ISSUE 28 and ISSUE 29) at Tuesday's meeting.
 
Ron
  


Von: Barack, Ron [mailto:ron.barack@sap.com]
Gesendet: Dienstag, 24. Februar 2009 15:05
An: Blaise Doughan
Cc: sdo@lists.oasis-open.org
Betreff: 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

Hi Ron,

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">

<<Proposal for Static SDOs.doc>>

Hi Everyone,

Attached is a new proposal in which I've tried to incorporate all the comments I got during the F2F on Friday.  Blaise, I've broken out @SdoXmlElement seperately rather than keeping it a part of @SdoXmlProperty because annotations don't allow default values to be null, and I think implementations need to distinguish whether the user has actually said anything or not.  Otherwise, we'd need a three-valued enum, and I just think that's too ugly.

Comments welcome, maybe we can discuss this on Tuesday's call.


Ron


--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]