Re: [eclipselink-users] Defining persistence.xml programmatically?

[Shaun Smith <shaun.smith@xxxxxxxxxx>]

Hi Dirk,

Dirk Hermanns wrote:

...
What i would like to have even more is, that each bundle has it's own fragment of the persistence.xml file. Each one should contain
only that Entity classes of the osgi bundle itself.

There's currently no support for persistence.xml "fragments" but it is an interesting idea.

Is this possible? The reason behind this is, that i want to modularize my system into osgi bundles. Each bundle has its own
entities, but they are all running in the same database. And i would like to have only one emf, so that i can share the entities
among all bundles.

I understand what you're trying to achieve but there's nothing now.  We'd have to think about and investigate how this could be done.  Can you file an enhancement request for this?

In the attached link you are talking about:
""Just to confirm that in pre 2.0 EclipseLink you do need all of your entities in the same bundle as your persistence.xml for weaving to work""

So will the distribution of entities only work für EclipseLink 2.0? Is there already a release date for 2.0?

Distribution should work pre-2.0.  It's only weaving that will not work across multiple bundles pre-2.0.  You should be able to get something working and when you upgrade to 2.0 weaving will be possible.  The current GA date is December 10th, 2009.  You can find the project calendar here: http://www.google.com/calendar/embed?src="">

    Shaun

Thx a lot,
Dirk

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
  

--

Shaun Smith | Principal Product Manager
Phone: +19055023094
Oracle Server Technologies, Oracle TopLink
ORACLE Canada | 110 Matheson Boulevard West, Suite 100, Mississauga, Ontario | L5R 3P4
Oracle is committed to developing practices and products that help protect the environment