geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Petersson (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2994) Apache Roller plugin
Date Mon, 09 Apr 2007 13:51:32 GMT


Peter Petersson commented on GERONIMO-2994:

I have now successfully installed Apache Roller on G v2.0 (tomcat) as a plugin :). 

As stated above there exists a issue between G:s activemq-broker modules and hibernates v3.1
property loader (used by Roller) in G v1.2 and the same applies to G v2.0. The workaround
(not loading the activemq-broker) used in G v1.2 dose not seem possible in G v2.0 as Geronimo
wont start up properly  if the activemq-broker module is not loaded. Should G v2.0 be dependent
on a running activemq-broker?

To be able to install plugins from a local maven repository (using a file:///~/.m2/repository/
as path) I had to patch the findArtifact method in  org.apache.geronimo.system.plugin.PluginInstallerGBean
to also check the maven-metadata-local.xml if the lookup of maven-metadata.xml was unsuccessful
(see included patch for details). I don't know if this is this a Maven 2.0 related behavior
or if I have messed up my repository somehow (don't think so).  

For Gernonimo to be able to find the plugins the geronimo-plugins.xml file in the repo has
to contain a default-repository tag like this
Wouldn't it be safe to assume  that the plugins listed in the file resides in the same repository
as this geronimo-plugin.xml file ? and automatically add the current repo if the default-repository
tag is not present? 
This behavior could probably be added to the loadPluginList(URL repo, InputStream in) method
in org.apache.geronimo.system.plugin.PluginInstallerGBean if appropriate.
Including svn patches for work done on the roller plugin, patch needed (in PluginInstallerGBean)
to test install roller on G v2.0 and a modified geronimo-plugins.xml file.

I have also set up and worked on the roller plugin for G v1.2 (as It would actually run) but
have run in to some dependency problems for the roller derby database. Should we include this
embryo in the current roller plugin svn ? If so I think It would require some rearrangements.

What would be required to add a MySql plugin and load it in the same manner as with the derby
database? We could then start experimenting with using the file
for switching databases.

The roller derby db plugin currently fails to install on G v2.0 Jetty with the stack trace
listed below. 
14:17:18,343 WARN  [ExecuteQuery] Method execution failed: 
        at org.apache.geronimo.console.ajax.ProgressMonitor.getProgressInfo(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at javax.servlet.http.HttpServlet.service(
        at javax.servlet.http.HttpServlet.service(
        at org.mortbay.jetty.servlet.ServletHolder.handle(
        at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(
        at org.mortbay.jetty.servlet.ServletHandler.handle(
        at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(
        at org.mortbay.jetty.servlet.SessionHandler.handle(
        at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(
        at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(
        at org.mortbay.jetty.handler.ContextHandler.handle(
        at org.mortbay.jetty.webapp.WebAppContext.handle(
        at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
        at org.mortbay.jetty.handler.HandlerCollection.handle(
        at org.mortbay.jetty.handler.HandlerWrapper.handle(
        at org.mortbay.jetty.Server.handle(
        at org.mortbay.jetty.HttpConnection.handleRequest(
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(
        at org.mortbay.jetty.HttpParser.parseNext(
        at org.mortbay.jetty.HttpParser.parseAvailable(
        at org.mortbay.jetty.HttpConnection.handle(
        at org.mortbay.thread.BoundedThreadPool$

> Apache Roller plugin 
> ---------------------
>                 Key: GERONIMO-2994
>                 URL:
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Plugins
>    Affects Versions: 1.2
>            Reporter: Peter Petersson
>         Assigned To: David Jencks
>            Priority: Minor
>         Attachments: geronimo-plugins.xml, geronimo-web.xml, geronimo-web.xml, plan.xml,
pom.xml, pom.xml,,,,
roller-derbydb-plan-g1_2.xml, roller-mysql-db-plan-1-2.xml, roller_plugin.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:
> The bundle: (until it will be
available directly via roller home)
> Required jars:
> 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(
> Hibernate is expecting a String value (This issue is fixed in hibernate 3.2 with a instanceOf
> 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.

View raw message