Eclipse Community Forums: Gemini » Best practice

Home » Eclipse Projects » Gemini » Best practice - gemini jpa

Best practice - gemini jpa [message #913445]

Sat, 15 September 2012 13:21

Eclipse User

Hi together,

right now i am wondering about the best practice using gemini jpa and
how other projects are using it.

Question to projects that already use gemini:
How are you using gemini jpa?
- Did you turn off dynamic weaving?
- Or did you change the startorder of the bundles a way, that gemini jpa
does not have to re-resolve the persistence unit?
- Or are you handling the re-resolving internally?

Would be really interesting for me. Then i get an idea what will be best
practice and how i can use it.

Thanks a lot for any hints and discussions...
Best,
Florian

Re: Best practice - gemini jpa [message #928563 is a reply to message #913445]

Sun, 30 September 2012 15:19

Eclipse User

For my Eclipse RCP and e4 Apps;

Quote:

Did you turn off dynamic weaving?

Yeah. I turn it off completely and always set the -DREFRESH_BUNDLES=false property.

Quote:

Or did you change the startorder of the bundles a way, that gemini jpa
does not have to re-resolve the persistence unit?

I tried and always do, but not sure if it helps.

Quote:

Or are you handling the re-resolving internally?

Never tried, but the Eclipse Extension Point handling is hard to change. Things may be a lot easier with e4.

Previous Topic:	Gemini DBAccess 1.1.0 Milestone 3
Next Topic:	Performance and concurrency of calls into services

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 07 21:13:24 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter