Hi Werner,
Yes, Mike is in the loop. Please enjoy your chat :-)
regards,
-Linda
On 4/20/2011 1:30 PM, Werner Keil wrote:
> According to the Java.net project page he is a committing member, so he should be aware of these threads.
>
> -------- Original-Nachricht --------
>> Datum: Wed, 20 Apr 2011 21:38:52 +0200
>> Von: "Werner Keil" <werner.keil_at_gmx.net>
>> An: linda.demichiel_at_oracle.com
>> CC: jsr338-experts_at_jpa-spec.java.net
>> Betreff: [jsr338-experts] Re: improved SQL result set mapping
>
>> Linda/all,
>>
>> I don't know, if Mike Keith is also in the EG, but he's always been
>> involved in EclipseLink, the RI at Eclipse among other projects there.
>>
>> I shall meet him in person tomorrow and on Friday at Great Indian
>> Developer Summit. While not a real EG meeting it seems like a great opportunity to
>> hava a chat about some aspects or current questions in the EG.
>>
>> If there's any discussion item beyond what has been communicated recently,
>> please reply. Sorry that I haven't been as vocal, I was especially
>> involved in preparing 3 presentations, including Java EE 7 where JSR-338, at least
>> from a Bird's eye perspective (crow's nest of the Cloud Treader ;-) is of
>> course also a key topic.
>>
>> Kind Regards,
>> Werner
>>
>> -------- Original-Nachricht --------
>>> Datum: Wed, 20 Apr 2011 10:03:17 +0200
>>> Von: "Rainer Kwesi Schweigkoffer" <kwesi_at_sap.com>
>>> An: Linda DeMichiel <linda.demichiel_at_oracle.com>
>>> CC: jsr338-experts_at_jpa-spec.java.net
>>> Betreff: [jsr338-experts] Re: improved SQL result set mapping
>>> Hi Linda, all,
>>>
>>> Linda DeMichiel, am 19 Apr 2011 hast Du um 11:22 zum Thema
>>> "[jsr338-experts] Re: improved SQL result set mapp" geschrieben :
>>>
>>>>>>>> @Target(value={})
>>>>>>>> @Retention(value=RUNTIME)
>>>>>>>> public @interface ConstructorResult {
>>>>>>>> Class targetClass();
>>>>>>>> ColumnResult[] columns();
>>>>>>>> }
>>>>>>> One could think of EntityResult[] entities here as well. This
>> would
>>>>>>> impose a restriction on the ordering of constructor parameters
>>>>>>> (entities either first or last), however, I think one could live
>>> with
>>>>>>> that. Unfortunately, annotations may not inherit from each other.
>>>>>
>>>>> Any opinion on the above ?
>>>> I think I would prefer to defer the issue pending any requests.
>>> Actually, my point here is that constructor expressions in JPQL allow
>>> for entities as arguments, and I would find it quite helpful for users
>>> if similar constructs would be defined with as similar functional range
>>> as possible throughout the spec. Users already have to face intricacies
>>> like e.g.
>>>
>>> Native SQL queries -> positional parameters
>>> Stored procedures -> positional and named parameters
>>> JPQL queries -> positional and named parameters
>>> Criteria queries -> named and unnamed parameters
>>>
>>> Wouldn't want to open up another one here as well...
>>>
>>> Best regards
>>> Rainer
>>>
>>> ---
>>> Rainer Schweigkoffer SAP AG Walldorf
>>> Business Solution & Technology TD Core JS&I
>>> Technology Development Dietmar-Hopp-Allee 16
>>> Java Server Core D-69190 Walldorf
>>> JEE Implementation Group phone: +49 6227 7 45305
>>> Building 3, I.3.14 fax: +49 6227 7 821177
>>> rainer.schweigkoffer_at_sap.com
>>>
>>> Sitz der Gesellschaft/Registered Office: Walldorf, Germany
>>> Vorstand/SAP Executive Board: Werner Brandt, Angelika Dammann,
>>> Bill McDermott (Co-CEO), Gerhard Oswald, Vishal Sikka,
>>> Jim Hagemann Snabe (Co-CEO)
>>> Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory
>>> Board: Hasso Plattner
>>> Registergericht/Commercial Register Mannheim No HRB 350269
>>>
>>> Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige
>>> vertrauliche Informationen enthalten. Sollten Sie diese E-Mail
>>> irrtuemlich erhalten haben, ist Ihnen eine Verwertung des Inhalts,
>>> eine Vervielfaeltigung oder Weitergabe der E-Mail ausdruecklich
>>> untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die
>>> empfangene E-Mail. Vielen Dank.
>>>
>>> This e-mail may contain trade secrets or privileged, undisclosed, or
>>> otherwise confidential information. If you have received this e-mail
>>> in error, you are hereby notified that any review, copying, or
>>> distribution of it is strictly prohibited. Please inform us
>>> immediately and destroy the original transmittal. Thank you for your
>>> cooperation.
>>>
>>>
>> --
>> NEU: FreePhone - kostenlos mobil telefonieren und surfen!
>> Jetzt informieren: http://www.gmx.net/de/go/freephone
>