| DB setup problems & project status [message #1751] |
Mon, 25 August 2008 12:21  |
Eclipse User |
|
|
|
Originally posted by: Marius.NightLabs.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everybody,
I want to test maynstall and see if it is suitable for our provisioning
needs, but in order to do so I need to provide a property file
describing the data source for EclipseLink.
In the version from CVS there is no configuration file registered under
the key "MaynstallConfigFile". There exists only an obsolete
registration to a non-existing file under the key
"MaynstallHibernateConfigFile".
I was searching around on the EclipseLink Wiki and on the Maynstall Wiki
in order to find information on how to provide this information exactly,
but wasn't successful. I'd be very thankful if somebody can provide an
existing configuration file or point me to a truly helpful Wiki page
(not like the ones filled up with UI-screenshots).
Furthermore I hope the project is still under development. I've noticed
that there seems to be no active development going on from the project
members -- no commits for quite some time -- but contributed fixes are
applied. So how about the future plans and the development on this
project? Is there a publicly visible release plan? If not, when do you
plan to release the first stable?
Thanks in advance for any helpful comment! :-)
Marius Heinzmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIstwfuSHKxXSCvdcRAqilAJwJod3ZCfTvkYs602ZkuHhiyIrJGgCg n9xK
IBXvlAgX8Gl8OZX853E9Z0A=
=b9P9
-----END PGP SIGNATURE-----
|
|
|
|
| Re: DB setup problems & project status [message #1766 is a reply to message #1758] |
Wed, 03 September 2008 10:35  |
| Eclipse User |
|
|
|
Originally posted by: tim._NOSPAM_genuitec.com
Hi Marius,
Yes, we're out here, though the news group has been quite quiet so we've been
quite bad about staying on top of it. My apologies!
Regarding getting up and going with the configuration file, what you essentially
have to do is configure a JPA bundle containing EclipseLink and leverage the
Maynstall extension to map in the properties file that defines the configuration
for JPA.
The key properties to have in the mapped file are:
# Settings for MySQL
eclipselink.jdbc.driver=com.mysql.jdbc.Driver
eclipselink.jdbc.password=password
eclipselink.jdbc.write-connections.max=10
eclipselink.jdbc.write-connections.min=10
eclipselink.jdbc.url=jdbc:mysql://servername/dbname?
autoReconnectForPools=true&blobSendChunkSize=2048000& ;jdbcCompliantTruncation=fal
se&autoCommit=false
eclipselink.jdbc.user=username
eclipselink.jdbc.read-connections.max=40
eclipselink.jdbc.read-connections.min=40
eclipselink.target-database=MySQL4
We had initially started the Maynstall project built on top of Hibernate and at
the time we updated Maynstall to work with EclipseLink, EclipseLink was at such
an early stage that we weren't able to have a full exemplary setup due to
licensing issues at the time. Since then EclipseLink has clearly progressed and
we could certainly tidy up some of the getting started steps for Maynstall.
Regarding the project itself, we are looking at reviving the project a bit now
since during work with the p2 re-architecture of provisioning in Eclipse, some
fundamental changes will ultimately need to work into Maynstall. As p2 is now
stable and shipped with Eclipse 3.4, we are at a better place to continue evolving the Maynstall technology.
Cheers,
Tim
|
|
|
| Re: DB setup problems & project status [message #564148 is a reply to message #1751] |
Wed, 27 August 2008 07:21 |
| Eclipse User |
|
|
|
Originally posted by: Marius.NightLabs.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Huhu,
is there anybody out there? :-)
Regards
M. Heinzmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFItTjSuSHKxXSCvdcRAiXgAKCWJFgoQyOI3oNrhEnWF1vuUgxLEQCg xSN8
FxUj2xMr8lKxhmrCirbe1uY=
=FJfS
-----END PGP SIGNATURE-----
|
|
|
| Re: DB setup problems & project status [message #564196 is a reply to message #1758] |
Wed, 03 September 2008 10:35 |
| Eclipse User |
|
|
|
Hi Marius,
Yes, we're out here, though the news group has been quite quiet so we've been
quite bad about staying on top of it. My apologies!
Regarding getting up and going with the configuration file, what you essentially
have to do is configure a JPA bundle containing EclipseLink and leverage the
Maynstall extension to map in the properties file that defines the configuration
for JPA.
The key properties to have in the mapped file are:
# Settings for MySQL
eclipselink.jdbc.driver=com.mysql.jdbc.Driver
eclipselink.jdbc.password=password
eclipselink.jdbc.write-connections.max=10
eclipselink.jdbc.write-connections.min=10
eclipselink.jdbc.url=jdbc:mysql://servername/dbname?
autoReconnectForPools=true&blobSendChunkSize=2048000& ;jdbcCompliantTruncation=fal
se&autoCommit=false
eclipselink.jdbc.user=username
eclipselink.jdbc.read-connections.max=40
eclipselink.jdbc.read-connections.min=40
eclipselink.target-database=MySQL4
We had initially started the Maynstall project built on top of Hibernate and at
the time we updated Maynstall to work with EclipseLink, EclipseLink was at such
an early stage that we weren't able to have a full exemplary setup due to
licensing issues at the time. Since then EclipseLink has clearly progressed and
we could certainly tidy up some of the getting started steps for Maynstall.
Regarding the project itself, we are looking at reviving the project a bit now
since during work with the p2 re-architecture of provisioning in Eclipse, some
fundamental changes will ultimately need to work into Maynstall. As p2 is now
stable and shipped with Eclipse 3.4, we are at a better place to continue evolving the Maynstall technology.
Cheers,
Tim
|
|
|
Powered by
FUDForum. Page generated in 0.04546 seconds
Home