[jira] Issue Comment Edited: (GERONIMO-2994) Apache Roller plugin

["Peter Petersson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GERONIMO-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500940 ] 

Peter Petersson edited comment on GERONIMO-2994 at 6/2/07 4:16 AM:
-------------------------------------------------------------------

Hi

Attaching a patch (roller_g20_svn_070602.patch) for the Apache Roller plugin on G v2.0 and a zip bundle (roller12_070602.zip) 
containing everything, including a README.txt file, to get things running on G v1.2. 

Thanks to David Jencks who talked me in to help out with a Roller plugin for Geronimo ;) and provided me with something to work on 
I have come to a point where the plugin is working for Geronimo v1.2/v2.0 (tomcat and jetty) using mysql (or derby)? as database 
back-ends but unfortunately I have not been able to run Roller on G v2.0 although the plugin for G v2.0 works.  
As stated before there exists a issue between G:s activemq-broker modules system properties and hibernates v3.1 property loader 
(used by Roller v3.1). In G v1.2 or earlier this issue can be worked around by not loading the activemq-broker but in 
G v2.0 (tomcat6-j2ee) its not possible to start Geronimo without the activemq-broker running, The G-console won't start 
(anyway I have not found out how to). 
Is it possible?

h4. The next step?
Although the plug-ins are working with the mysql plugin I don't think the way things are set up at the moment was the idea David had 
with using the artifacts_aliases.properties for easy switching database back-ends so when you get time to elaborate on this i will 
try to bend things in that direction, I know you are all quit busy working on Gv2.0 so it can wait until you get some spare time.
Also the current plug-ins are built around rc6 and roller v3.1 has been released so updating would be the next thing to do.  

h4. Geronimo plug-ins from local repository
Geronimo don't like to work on plug-ins from a local repository (using file:///path/.m2/repository/ as path and fetching things using
maven-metadata-local.xml information) so I came up with a small patch to the PluginInstallerGBean::findArtifact method to work around 
this (it's in the jira) but a more ideal setup would probably be to modify the pom:s to install the plugin modules into the repository 
as It would in a production environment anyway. Unfortunately I have just newly begun to use maven so I lack experience in how to set
up such a solution, if anyone could point me to some code or document describing it I would like to try it out.

h4. Mixed snapshot versions
As I have been working with both 1.2 and 2.0 plugin SNAPSHOT artifacts in my local repository I have fond that if the snapshots metadata 
file contains a 2.0-SNAPSHOT version and you expect Geronimo to fetch a 1.2 version (as you have specified it to in the geronimo-plug-ins 
file) you may end up getting hold of 2.0 snapshots (even though you think you have done what you can to prevent it in the plans). 
Is this problem a known fact ? In case of yes what have you G-devs done to avoid it? 

h4. The future looks bright
As the roller-devs have moved on to v3.2 and especially v4.0 with a back end based on JPA dropping the Hibernate-native support all hope on 
getting Roller running on G v2.0 is not yet lost even if the above problem is not resolved. I may check out the code to see where they are going 
and prepare things for a G-plugin when time gives. 
 
Thank you for your time.
 -- Peter Petersson    


 was:
Hi

Attaching a patch (roller_g20_svn_070602.patch) for the Apache Roller plugin on G v2.0 and a zip bundle (roller12_070602.zip) 
containing everything, including a README.txt file, to get things running on G v1.2. 

Thanks to David Jencks who talked me in to help out with a Roller plugin for Geronimo ;) and provided me with something to work on 
I have come to a point where the plugin is working for Geronimo v1.2/v2.0 (tomcat and jetty) using mysql (or derby)? as database 
back-ends but unfortunately I have not been able to run Roller on G v2.0 although the plugin for G v2.0 works.  
As stated before there exists a issue between G:s activemq-broker modules system properties and hibernates v3.1 property loader 
(used by Roller v3.1). In G v1.2 or earlier this issue can be worked around by not loading the activemq-broker but in 
G v2.0 (tomcat6-j2ee) its not possible to start Geronimo without the activemq-broker running, The G-console won't start 
(anyway I have not found out how to). 
Is it possible?

h4. The next step?
Although the plug-ins are working with the mysql plugin I don't think the way things are set up at the moment was the idea David had 
with using the artifacts_aliases.properties for easy switching database back-ends so when you get time to elaborate on this i will 
try to bend things in that direction, I know you are all quit busy working on Gv2.0 so it can wait until you get some spare time.
Also the current plug-ins are built around rc6 and roller v3.1 has been released so updating would be the next thing to do.  

h4. Geronimo plug-ins from local repository
Geronimo don't like to work on plug-ins from a local repository (using _file:///path/.m2/repository/_ as path and fetching things using
maven-metadata-local.xml information) so I came up with a small patch to the PluginInstallerGBean::findArtifact method to work around 
this (it's in the jira) but a more ideal setup would probably be to modify the pom:s to install the plugin modules into the repository 
as It would in a production environment anyway. Unfortunately I have just newly begun to use maven so I lack experience in how to set
up such a solution, if anyone could point me to some code or document describing it I would like to try it out.

h4. Mixed snapshot versions
As I have been working with both 1.2 and 2.0 plugin SNAPSHOT artifacts in my local repository I have fond that if the snapshots metadata 
file contains a 2.0-SNAPSHOT version and you expect Geronimo to fetch a 1.2 version (as you have specified it to in the geronimo-plug-ins 
file) you may end up getting hold of 2.0 snapshots (even though you think you have done what you can to prevent it in the plans). 
Is this problem a known fact ? In case of yes what have you G-devs done to avoid it? 

h4. The future looks bright
As the roller-devs have moved on to v3.2 and especially v4.0 with a back end based on JPA dropping the Hibernate-native support all hope on 
getting Roller running on G v2.0 is not yet lost even if the above problem is not resolved. I may check out the code to see where they are going 
and prepare things for a G-plugin when time gives. 
 
Thank you for your time.
 -- Peter Petersson    

> 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-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
>
>
> 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.