[ROL-1916] Verify Planet works on Glassfish and prominently point out planet-custom.properties

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0
• Fix Version/s: 5.0
• Component/s: Planet Aggregator

Level of effort

Author: snoopdave
Date: Sat Apr 2 21:52:50 2011
New Revision: 1088146

URL: http://svn.apache.org/viewvc?rev=1088146&view=rev
Log:
Issue ROL-1916: Verify Planet works on Glassfish and prominently point out planet-custom.properties
https://issues.apache.org/jira/browse/ROL-1916

- Corrected cache dir property name in Install Guide
- Made sure JPARollerPlanetPersistenceStrategy uses same logic as non-Roller one

Modified:
   roller/trunk/weblogger-business/src/main/java/org/apache/roller/weblogger/planet/business/jpa/JPARollerPlanetPersistenceStrategy.java
   roller/trunk/weblogger-docs/installguide/generated/html/roller-install-guide.html
   roller/trunk/weblogger-docs/installguide/generated/roller-install-guide.pdf
   roller/trunk/weblogger-docs/installguide/roller-install-guide.odt

• Assignee: David Johnson
• Reporter: David Johnson
• Created: 30/Mar/11 01:55
• Updated: 01/Jan/13 17:53
• Resolved: 02/Apr/11 21:57

Description

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?