You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Craig L Russell <Cr...@Sun.COM> on 2008/07/18 19:54:02 UTC

Minutes: JDO TCK Conference Call Friday, July 18, 9 am PDT

Attendees: Michael Bouschen, Craig Russell

Agenda:

1. L2 Caching extension. The caching extensions are now checked in. If  
there are any comments, please update the JIRA. Do we need a test  
case? I think not. I can't see how to test this.

2. Richard has a patch for https://issues.apache.org/jira/browse/ 
JDO-582. Not uploaded yet.

3. Working on https://issues.apache.org/jira/browse/JDO-555. Most  
issues are now resolved. Just a couple of tests now fail when running

maven -o -Djdo.tck.security runtck.jdori

The exception mentioned in JDO-555 Craig Russell - 16/Jul/08 03:14 PM  
is still a problem. The ResultObjectFactory constructor requires  
getClassLoader permissions if the user requests a java.util.Map result  
object. So test ResultClassRequirements.testMap in query.conf fails  
with a security violation. Two other security issues are still being  
investigated.

There are some bigger issues when running with security and Windows.  
The result of

springbeans.jarfile = $ 
{pom.getDependencyPath('org.springframework:spring-beans')}

is

springbeans.jarfile=D:/users/michael/.maven/repository 
\org.springframework\jars\spring-beans-2.0.jar

This is an internal Maven call that returns mixed "/" and "\" that  
seems to be confusing Java security policy.

To be continued...

4. An interesting option for a JDO implementation is to use a RESTful  
service like Amazon S3 or memcached for the back end. Some obvious  
issues are transactions, object identity, and query. But having an  
object front end for these would have clear productivity benefits  
compared to a user writing the entire thing by hand (tools are pretty  
simple for accessing data from these services).

Andy suggests using DataNucleus as the starting point for this effort,  
as they have already implemented a number of concrete store managers.  
AI look at DataNucleus store manager interface to see what needs to be  
done to run with a cloud data repository.

Action Items from weeks past:

[Jun 20  2008] AI: Craig reply to Joerg regarding bidirectional  
relationships and possibly update the spec to include the rationale.

[Feb 1 2008] AI  Matthew see what would be needed to update the PMF  
contract to support  ServiceLoader.

[Nov 30 2007] AI Christiaan propose more details on Update/copy by  
query for post-JDO 2.1.

[May 25 2007]  AI everyone download the Grails demo from grails.org   
and check it out. Also look at Grails/Groovy ExpandoMetaClass that   
has the magic to avoid reflection and enhancement.

[May 25 2007] AI Matthew Adams prepare a proposal with just the basics  
of schema synchronization with jdo and orm metadata.

[Aug 11 2006] AI Craig propose some semantics for behavior if user  
tries to add to a list where the ordering element is incorrect.

[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://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


Re: Minutes: JDO TCK Conference Call Friday, July 18, 9 am PDT

Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,

[...]
>
> There are some bigger issues when running with security and Windows. 
> The result of
>
> springbeans.jarfile = 
> ${pom.getDependencyPath('org.springframework:spring-beans')}
>
> is
>
> springbeans.jarfile=D:/users/michael/.maven/repository\org.springframework\jars\spring-beans-2.0.jar 
>
>
> This is an internal Maven call that returns mixed "/" and "\" that 
> seems to be confusing Java security policy.
>
> To be continued...

I figured out when hard coding the path names in the 'grant codbase' 
lines in the security.policy file, I'm able to run with security on 
windows. That means something is going wrong when using properties (like 
${jdo..tck.jdori.jarfile}) in the security.policy file. Even mixing "/" 
and "\" in the path names works, as long as the path names are hard coded.

Any ideas?

Regards Michael

[...]

-- 
*Michael Bouschen*
*Prokurist*

akquinet tech@spree GmbH
Tempelhofer Ufer 23-24, D-10963 Berlin
Bülowstr. 66, D-10783 Berlin

Fon:   +49 30 235 520-33
Fax:   +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url:    www.akquinet.de <http://www.akquinet.de>

akquinet tech@spree GmbH, Berlin
Geschäftsführung: Prof. Dr. Christian Roth, Hendrik Saly, Martin Weber
Amtsgericht Berlin-Charlottenburg HRB 86780
USt.-Id. Nr.: DE 225 964 680

Re: Minutes: JDO TCK Conference Call Friday, July 18, 9 am PDT

Posted by Andy Jefferson <an...@datanucleus.org>.
> 4. ...
> Andy suggests using DataNucleus as the starting point for this effort,
> as they have already implemented a number of concrete store managers.
> AI look at DataNucleus store manager interface to see what needs to be
> done to run with a cloud data repository.

http://www.jpox.org/servlet/wiki/display/ENG/HOWTO+Support+a+new+datastore


-- 
Andy  (DataNucleus - http://www.datanucleus.org)