THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
List and describe new manager methods, Struts actions, JSP pages, macros, etc.
...
Changes to RollerFactory
To select a back-end implementation, you set the property 'guice.backend.module' in the Roller configuration file the the class name of a Guice module that specifies the Roller interfaces. The RollerFactory will instantiate that Guice module and will use it to create and inject the Roller implementation specified by that module. Here's the code for RollerFactory.java.
And here's the code for the Guice module for the Hibernate back-end: RollerModule.java.
Changes to the Roller implementation and managers
Roller implementation and all manager implementations use constructor injection. The are all declared as singletons. For example, here's the code for HibernateRollerImpl.java.
...
The Roller version of the database provider uses RollerConfig to configure the database, here's the code:
RollerDatabaseProvider.
Changes to Roller Planet
Roller Planet will use the very same setup as Roller Weblogger. As you'd expect there will be a PlanetFactory and a PlanetModule. There will be a PlanetDatabaseProvider that uses PlanetConfig to get database proerties, etc.
...
Changes to Weblogger's Planet integration
The PlanetFactory uses the Guice back-end specified in the planet.properties file. In Roller we need a special PlanetModule, with a Planet implementation that can read database parameters from the Roller properties file instead of the Planet one.
...
Guice DI is implemented in both Weblogger and Planet and for both the Hibernate and JPA implementations and passing XXX% of tests.
...