Is the following still true?
# Atom Publishing Protocol (APP) - this is an incomplete and untested
# implementation of an unfinished IETF specification.
# Intended only for interoperability testing. DO NOT ENABLE IN PRODUCTION!
webservices.atomprotocol.enabled=false
Note, this is in -custom (copied from elsewhere into -custom and editted)
and yet:
globalConfig.rol has "Enable Atom Publishing Protocol" as checked.
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?
