roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Johnson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ROL-1916) Verify Planet works on Glassfish and prominently point out planet-custom.properties
Date Sat, 02 Apr 2011 21:58:05 GMT

    [ https://issues.apache.org/jira/browse/ROL-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015083#comment-13015083
] 

David Johnson commented on ROL-1916:
------------------------------------

The properties below are only needed for the (unreleased) standalone version of Planet Roller.

> output.dir=/usr/local/planet/webapp 
> template.dir=/usr/local/planet/webapp/WEB-INF/templates 

I made some changes to ensure that Planet uses the same properties as Roller for database
configuration, verified that the the install guide is correct on this topic and verified that
planet works on Glassfish 3.1.

> Verify Planet works on Glassfish and prominently point out planet-custom.properties
> -----------------------------------------------------------------------------------
>
>                 Key: ROL-1916
>                 URL: https://issues.apache.org/jira/browse/ROL-1916
>             Project: Roller
>          Issue Type: Bug
>          Components: Planet Aggregator
>    Affects Versions: 5.0
>            Reporter: David Johnson
>            Assignee: David Johnson
>             Fix For: 5.0
>
>
> From Peter Evans:
> > Still with the roller.properties, it needs a big warning sign in there for
> > planet. saying
> > "DONT FORGET YOUR planet-custom.properties!"
> >
> > ERROR 2011-03-29 22:50:39,970 RomeFeedFetcher:getRomeFetcherCache - Planet
> > cache directory is not writable: /var/planet/cache
> >
> > There's some other stuff in the planet.properties that might need some
> > discussion, for example:
> > output.dir=/usr/local/planet/webapp
> > template.dir=/usr/local/planet/webapp/WEB-INF/templates
> >
> > Anyway, attempting to turn on planet, gets my favourite show stopper:
> >
> > INFO  2011-03-29 23:05:14,737 WebloggerFactory:bootstrap -    Version:
> > 5.0.0-RC4
> > INFO  2011-03-29 23:05:14,738 WebloggerFactory:bootstrap -    Revision:
> > r1075074
> > INFO  2011-03-29 23:05:14,738 WebloggerImpl:initialize - Initializing Roller
> > Weblogger business tier
> > FATAL 2011-03-29 23:05:14,740 JPAPropertiesManagerImpl:initialize - Failed
> > to initialize runtime configuration properties.Please check that the
> > database has been upgraded!
> > java.lang.ClassCastException:
> > org.apache.roller.weblogger.pojos.RuntimeConfigProperty cannot be cast to
> > org.apache.roller.weblogger.pojos.RuntimeConfigProperty
> >       at
> > org.apache.roller.weblogger.business.jpa.JPAPropertiesManagerImpl.getProperties(JPAPropertiesManagerImpl.java:127)
> >       at
> > org.apache.roller.weblogger.business.jpa.JPAPropertiesManagerImpl.initialize(JPAPropertiesManagerImpl.java:77)
> >
> >   Once this error happens, that is fatal until one destroys the database and
> > starts all over again!
> >   Which is magnificent.
> >
> >   now, its asking about the database being upgraded, but how?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message