Change Xregistey to use embaded database.
-----------------------------------------
Key: AIRAVATA-14
URL: https://issues.apache.org/jira/browse/AIRAVATA-14
Project: Airavata
Issue Type: Task
Components: XRegistry
Reporter: Raminderjeet Singh
Based on the following discussion we agreed to remove mysql dependency and move
to Apache Derby.
---->
I agree with Patanachai and Simon's observations. But I see good support for
Derby integration. I am fully supportive with an assumption that it will bring
down the initial configuration steps. I want to focus on other aspects of
Airavata but will add JIRA tasks for the components which will need Derby
integration. Soliciting volunteers in advance to close them.
Suresh
On Jul 5, 2011, at 1:58 PM, Raminderjeet Singh wrote:
+1 for bundling embedded database. Its really easy to have some samples if we
want and easy for someone to evaluate also.
Thanks
Raminder
On Jul 5, 2011, at 1:54 PM, Thilina Gunarathne wrote:
+1 for bundling Derby or something similar which would work out of the box
at least for the simple cases. Apache ODE also follows the same path, where
they have Derby in-build making the WAR deployment to work out of the box.
Looking at how ODE does the config may be a good idea, since Airavata also
uses ODE..
thanks,
Thilina
On Tue, Jul 5, 2011 at 12:58 PM, Marlon Pierce <[email protected]>wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It would still probably be good for things to work "out of the box" with
a simple in-memory db.
Marlon
On 7/5/11 12:46 PM, [email protected] wrote:
Hi,
I agree with Simon. From what I see in the svn, I think there is no
compile-time dependency.
For all messaging modules, you can just remove MySQL dependency from the
POM
file.
It will not interfere with package building.
And as Ross said, we require a user need to download and install MySQL
library, if MySQL Driver class is presented in the configuration file.
On Tue, Jul 5, 2011 at 4:32 AM, Simon Courtenage <[email protected]
wrote:
I don't think there is a compile-time dependency. Rather it's a config
dependency - JRC, for example, require that an entry to the mysql jdbc
library be present in the config file. The config file is read by an
attributes class, which can be queried for the name of the jdbc
connector.
So, as far as the JCS (sorry, I said JRC in my original email) code is
concerned, at compile time, there is no dependency on mysql-connector.
But
realistically, at run-time, there is. And the comment in the code
reflects
that.
See the config file for JCS here:
http://jakarta.apache.org/jcs/JDBCDiskCache.html
Simon
On Sun, Jul 3, 2011 at 10:24 PM, Suresh Marru <[email protected]>
wrote:
On Jul 3, 2011, at 3:23 AM, Simon Courtenage wrote:
Quite a few apache projects have dependencies on the official mysql
java
jdbc connector, in the sense that their product requires it to connect
to
mysql databases. Tomcat is one, for example, as is, I believe, JRC
(the
source code for JRC has a comment that mentions
org.gjt.mm.mysql.driver,
which is an old precursor of the official mysql jdbc driver). So does
airavata need to be different?
Hello Simon,
Thank you for chiming in. No Airavata need not be different, I am
asking
out of ignorance. Do you know how these projects handle the GPL license
of
the official mysql-connector? I tried to poke around but could not find
a
concrete example. Can you please pass a reference which has a pom
dependency
of this jar (either compile or run time)?
Suresh
Simon Courtenage
On Sun, Jul 3, 2011 at 3:32 AM, Suresh Marru <[email protected]>
wrote:
Hi All,
One of our incubation goals [1] is to resolve the the incompatible
license
dependencies. AFAIK, the biggest or only incompatible dependency is
the
mysql-connector-jave which is GPL. Suggestions for alternatives?
Cheers,
Suresh
[1] - http://wiki.apache.org/incubator/AiravataProposal
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
