I _don't_ want to filter my queries. Can I give the native implementation a try?
Would that be the CVS Head or would it be a different branch?
Thanks.
Charlie
Brian McCallister wrote:
You need both if you are using the JDORI plugin. It is annoying =(
The native JDO impl I am working on for OJB will allow you to just use the OJB mappings as the .jdo files will only be used for (optional in OJB but not for spec-compliant JDO) bytecode enhancement process. This JDO impl is *far* from ready for use yet (well, actually it works great as long as you don't want to filter your queries as JDOQL isn't implemented yet).
-Brian
On Apr 14, 2004, at 8:06 AM, Nicolas Arni-Bloch wrote:
Hi all,
I want to try JDO with OJB but I have some misunderstood.
I am not very clear about where to put the MetaData for the mapping ? In the repository.xml or in the XXX.jdo ?
I look in the tutorial5 and I see that information for the mapping are stored in the Product.jdo.
So should we put this information in the .jdo and in the repository.xml ?
My second question is : with the JDO should we use the ManageableCollection interface for the collection or not. I have try the jdo implementation with a single class and its work. But I try with 1..n relation and it doesn't ?
Is some body as code example for using JDO with OJB ?
Nicolas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
