Eclipse Community Forums: Dali » Status of how users with multiple projects should use dali/persistence.xml and <jar-file >

Home » Eclipse Projects » Dali » Status of how users with multiple projects should use dali/persistence.xml and <jar-file >

Status of how users with multiple projects should use dali/persistence.xml and <jar-file > [message #897882]

Wed, 25 July 2012 07:12

Eclipse User

I'm wondering what the status is for Dali having support for referencing multiple projects with entities to be used in a persistence unit - JPA it self uses jar-file references for this but that doesn't really map well at design time.

Any tips/docs on this subject ?

Re: Status of how users with multiple projects should use dali/persistence.xml and <jar-file > [message #898827 is a reply to message #897882]

Fri, 27 July 2012 15:40

Eclipse User

There is no real change in the status in the Juno release, but we have been discussing this use case lately. It seems we need to provide some sort of (design time) project to jar-ref mapping capability where the user can explicitly resolve a jar-ref to a development project. The tricky part would then be providing the Dali editing/validation experience to these dependent JPA projects.

I was thinking we could have a way for the user to create a dependent project and then to identify the owning Dali project, from which the dependent project would inherit the persistence unit from the owner. It would take some work to have a different facet configuration, etc, but it seems feasible. Would also require some tweaks to the validation, but all seems possible.

Let me know if you have any feedback on this. Would be nice to add in this functionality in the near future.

Here is a related enhancement request - https://bugs.eclipse.org/bugs/show_bug.cgi?id=254480.

Neil

[Updated on: Tue, 07 August 2012 10:49] by Moderator

Re: Status of how users with multiple projects should use dali/persistence.xml and <jar-file > [message #900507 is a reply to message #898827]

Tue, 07 August 2012 06:28

Eclipse User

Hi all,

In fact, I thought that using a custom ResourceLocator would be the solution, but I faced another issue while pointing to a file in another project:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=381890

Boris
PS: Neil, your link has an extra point at the end

Previous Topic:	Potentially spurious validation message about attribute mapping?
Next Topic:	JPQL validation errors in named-queries.xml not ignored

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 11:57:35 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter