AW: AW: [sdo] Groups - HelperContext Creation - Java Spec - v2 (HelperContextCreation-Java.doc) uploaded

["Barack, Ron" <ron.barack@sap.com>]

Hi Blaise,

 

You're right, if the user specifies a classloader, then we should probably look only there for the referenced classes.  On the otherhand, it would be nice to say something about the default behavior, i.e., in which classloader do the default HC and those created without a specified classloader look?  I'm having trouble formulating a statement here, since I guess it's dependent on the environment (eg, in JavaEE it would be approriate in look in the current threads context, but this wouldn't fit to OSGi).  On the other hand, I don't want to create the impression that static SDOs do not work unless a classloader is supplied.  Maybe we could add a sentence:

 

"A ClassLoader parameter may also be supplied. When a static SDO class is referenced by name, implementations MUST search the supplied ClassLoader for the requested class.  The ClassLoader used by the default HelperContext, and HelperContexts that were created without a specified ClassLoader depends on the implementation and the environment, for instance, when SDO is being used in a Java EE environment, the current thread's contextClassLoader SHOULD be used."

 

which doesn't add anything that's really testable (hence the SHOULD), but defines some expected behaviour... and makes it clear that the default HC is not inconsistent with static SDOs.

 

Best Regards,

Ron

 

---

Von: Blaise Doughan [mailto:blaise.doughan@oracle.com]
Gesendet: Montag, 6. Juli 2009 16:40
An: Barack, Ron
Cc: sdo@lists.oasis-open.org
Betreff: Re: AW: [sdo] Groups - HelperContext Creation - Java Spec - v2 (HelperContextCreation-Java.doc) uploaded

Hi Ron,

Agreed that "generated instance classes" is wrong now that we support annotated interface classes as input.

Do we need to say more than:

"A ClassLoader parameter may also be supplied. When a static SDO class is referenced by name, implementations MUST search the supplied ClassLoader for the requested class."

I think it goes without saying that a ClassLoader includes it's parent class loaders.  I think it is wrong for the spec to imply that implementations may search unrelated ClassLoaders for static SDO classes, do you see a use case for this?

-Blaise


Barack, Ron wrote:

7C3EF93EEBC6EB4A8B4470853DE86566E34C6D@dewdfe18.wdf.sap.corp type="cite">

Hi Blaise,

In section 2.17.1, I do not like the phrase "generated instance classes", since not all static SDOs will be generated.  Could we instead say, 

A ClassLoader parameter may also be supplied.  When a static SDO class is referenced by name, implementations MUST search the supplied ClassLoader for the requested class first.  Implementations MAY search other ClassLoaders, as appropriated for the environment.  For instance, the thread's current context ClassLoader MAY be searched in a JavaEE environment. 

Ron


-----Ursprüngliche Nachricht-----
Von: blaise.doughan@oracle.com [mailto:blaise.doughan@oracle.com] 
Gesendet: Freitag, 3. Juli 2009 19:50
An: sdo@lists.oasis-open.org
Betreff: [sdo] Groups - HelperContext Creation - Java Spec - v2 (HelperContextCreation-Java.doc) uploaded

The document revision named HelperContext Creation - Java Spec - v2
(HelperContextCreation-Java.doc) has been submitted by Mr. Blaise Doughan
to the OASIS Service Data Objects (SDO) TC document repository.  This
document is revision #1 of HelperContextCreation-Java.doc.

Document Description:
This document includes the changes discussed during the conference call on
June 23rd.

View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=33223

Download Document:  
http://www.oasis-open.org/committees/download.php/33223/HelperContextCreation-Java.doc

Revision:
This document is revision #1 of HelperContextCreation-Java.doc.  The
document details page referenced above will show the complete revision
history.


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration

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