[
https://issues.apache.org/jira/browse/GERONIMO-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514407
]
Peter Petersson commented on GERONIMO-2994:
-------------------------------------------
During my investigation and testing of the artifact aliasing I unfortunately
found out that the openjpa.jdbc.DBDictionary set in roller-tomcat (and
roller-jetty) plans seems to be the one used even after a aliasing switch to a
different database engine. I am not totally sure about this but log messages
indicates that this could be the case. The following is the procedure that lead
me to this conclusion:
* Installing the roller-mysql plugin
* Set the aliasing line
org.apache.geronimo.plugins/roller-derby-database//car=org.apache.geronimo.plugins/roller-mysql-database/2.0-SNAPSHOT/car
in var/config/artifact_aliases.properties.
* Installing the roller-tomcat plugin. This will also pull in the derby
database, initialize and start it. Now roller is running using the derby
database.
* Stopping the roller derby database connector (also stops the roller war).
Starting the roller war also restarts (as expected) the derby connector.
Stopping roller and the roller derby connector before restarting the server.
* Restarting the Geronimo server.
* Starting the roller war and as expected it uses the mysql connector (and the
derby connector is not started).
* The geronimo roller log indicates it used the derby dictionary settings
_[JDBC] Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary"_
and after some usage roller starts throwing database related errors like the
following. _"error in your SQL syntax; check the manual that corresponds to
your MySQL server version for the right syntax to use near TIMESTAMP"_
This unfortunate and at this writing I do not know how to resolve the problem.
Testing are done on the roller-plugin svn #557643 using roller trunk #557441
patched with ROL-1482 and G v2.0 #558093.
> Apache Roller plugin
> ---------------------
>
> Key: GERONIMO-2994
> URL: https://issues.apache.org/jira/browse/GERONIMO-2994
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Plugins
> Affects Versions: 1.2
> Reporter: Peter Petersson
> Assignee: David Jencks
> Priority: Minor
> Attachments: geronimo-plugins.xml, geronimo-plugins.xml,
> geronimo-plugins_070602.xml, geronimo-web.xml, geronimo-web.xml, plan.xml,
> PluginInstallerGBean.patch, pom.xml, pom.xml, roller-custom.properties,
> roller-custom.properties, roller-custom.properties,
> roller-derbydb-plan-g1_2.xml, roller-mysql-db-plan-1-2.xml,
> roller070409.patch, roller12_070602.zip, roller_g20_svn_070602.patch,
> roller_plugin.patch, roller_plugin_070717.patch
>
>
> Have been working on getting Apache Roller running under Geronimo I finally
> got to the point where the roller application seems to be running smoothly in
> Geronimo v1.2 (current snapshot). It would be great to eventually see this
> application as a plugin in G so here are pointers to resources and attached
> plans.
> Apache Roller v3.1 Resources (soon to be released)
> Apache roller home: http://rollerweblogger.org/project/
> The bundle: http://people.apache.org/~snoopdave/apache-roller-3.1/ (until it
> will be available directly via roller home)
> Required jars:
> https://roller.dev.java.net/servlets/ProjectDocumentList?expandFolder=6959&folderID=0
> Path to database create scripts can be found in the bundle above under:
> apache-roller-3.1/webapp/roller/WEB-INF/dbscripts/
> I have tested with the derby database and mysql 5.
> There is currently a issue with G v1.2 and hibernates v3.1 (used by roller
> 3.1) property loader that gets a
>
> FATAL [HibernateRollerImpl] Error initializing Hibernate
> java.lang.ClassCastException: java.util.HashSet
> at
> org.hibernate.util.PropertiesHelper.resolvePlaceHolders(PropertiesHelper.java:88)
>
> Hibernate is expecting a String value (This issue is fixed in hibernate 3.2
> with a instanceOf check)
> Fortunately David Jencks hit this problem in trunk and suggested turning off
> the activemq and activemq-broker modules in config.xml, to test things out,
> and after that everything was running smothly :).
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
