Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » externalize eclipselink.target-database property
externalize eclipselink.target-database property [message #513702] Wed, 10 February 2010 16:32 Go to next message
brad Mising name is currently offline brad Mising name
Messages: 17
Registered: February 2010
Junior Member
Hey guys, what is the best way to externalize the "eclipselink.target-database" property in persistence.xml. We would like to distribute the same ear for multiple databases, but don't want to build a different ear for each database type. What do you guys think? Thanks
-Brad
Re: externalize eclipselink.target-database property [message #513717 is a reply to message #513702] Wed, 10 February 2010 17:53 Go to previous messageGo to next message
Tom Eugelink is currently offline Tom Eugelink
Messages: 806
Registered: July 2009
Senior Member
On 2010-02-10 22:32, brad wrote:
> Hey guys, what is the best way to externalize the
> "eclipselink.target-database" property in persistence.xml. We would like
> to distribute the same ear for multiple databases, but don't want to
> build a different ear for each database type. What do you guys think?
> Thanks
> -Brad

I do the whole config by code instead of XML.
Re: externalize eclipselink.target-database property [message #513940 is a reply to message #513717] Thu, 11 February 2010 12:57 Go to previous messageGo to next message
brad Mising name is currently offline brad Mising name
Messages: 17
Registered: February 2010
Junior Member
We are looking to make it editable by our users so it would benefit us to keep it in the xml file.
-Brad
Re: externalize eclipselink.target-database property [message #513956 is a reply to message #513940] Thu, 11 February 2010 14:02 Go to previous message
Tom Eugelink is currently offline Tom Eugelink
Messages: 806
Registered: July 2009
Senior Member
On 11-2-2010 18:57, brad wrote:
> We are looking to make it editable by our users so it would benefit us
> to keep it in the xml file.
> -Brad

Well, naturally mine is editable by sysadmin as well; it's also in a configuration file, just not in the one in the BM jar. It's totally external to the application (in /etc even). Because of the configuration-by-code I can put it where ever I want, fetch the value and configure.

Tom
Previous Topic:Mapping entity property to stored functioncall - possible?
Next Topic:maven static weaving plugin
Goto Forum:
  


Current Time: Wed Apr 16 00:23:21 EDT 2014

Powered by FUDForum. Page generated in 0.05804 seconds