Right now you need to have both the jdo and the repository.xml mappings. It is a pain =/

A cleaner JDO implementation based around the OTM is under development, but won't be advertised in a release until post 1.0. It is probably the highest priority post-1.0 objective and stubs and partial implementations are in place now.

the PersistenceBrokerFactory.defaultPersistenceBroker().clearCache(); call just flushes the cache for demonstration purposes. There is no JDO api specification for clearing the cache =)

-Brian

On Wednesday, November 12, 2003, at 05:05 PM, Gus Heck wrote:

Wait... Do I need to do this to use JDO... or is this covered by the .jdo files? The tutorial has this line that says:

TODO: Put information about the .jdo files

Unfortunately by the time the tutorial gets to JDO it has implemented all the other API's so I am having difficulty figuring out what parts of the previous work are required to use JDO.

Also I notice that the tutorial section on JDO has this line:



Which is clearly not part of the JDO API. This appears to mean that I will depend on the non-JDO OJB persistance framework. Is there a way around this?

-Gus


Gus Heck wrote:


This is probably a terribly noob question, but is there a good way to generate my object mappings for the repository.xml? Seems like a lot of tedium to do it for more than one or two classes.

-Gus


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



Reply via email to