Attendees: Michelle Caisse, Richard Schilling, Michael Bouschen, Craig
Russell
Agenda:
1. Enhancer specification text. A few last issues:
a. Can you specify a class name or only the file name (path) of a
class? The advantage of having file and directory names is that it
reinforces the fact that the enhancer works on the byte codes, not
classes. The advantage of class names is usability for some use cases.
So what exactly are the use cases?
b. Can you specify resources vs. files: What is the use case for
specifying a resource name instead of a file or directory name?
c. Should the setOptions API be called setNonstandardOptions? If only
nonstandard options are in the list, this might make it clear that the
standard options are not going to be found here.
d. Enhancement on the fly is enabled by Java 6 instrumentation. How
can this feature be exploited? AI Richard look at Java 6 feature and
discuss on dev alias.
e. Must metadata come from exactly the same location (e.g. jar file,
file system) as the class to be enhanced? The metadata Chapter 18
already specifies a search order for metadata. Should this description
be used for the enhancer as well, with the addition of how to
translate parameters into a metadata search list? And should the
context class loader or just the class loader passed to the enhancer
be used to find metadata files?
2. Other issues
none.
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[May 25 2007] AI Matthew Adams prepare a proposal with just the basics
of schema synchronization with jdo and orm metadata.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
