Page History

...

As it stands today it's only benefits are that it 1) allows a customizer to easily switch out Roller manager classes and replace them with his or her their own implementations and 2) make it possible for RollerFactory to instantiate other Roller-dependent classes created by folks who are customizing Roller.

...

List and describe new manager methods, Struts actions, JSP pages, macros, etc.

Changes to

...

Roller Weblogger bootstrapping

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.

• RollerFactory.java
• RollerModule.java - JPA version
• RollerModule.java - Hibernate version

...

Roller implementation and all manager implementations use constructor injection. The are all declared as singletons.

• JPARollerImpl.java.
• HibernateRollerImpl.java.

Changes to Roller Planet bootstrapping

Roller Planet uses the very same setup as Roller Weblogger. As you'd expect there is a PlanetFactory, which uses a PlanetModule to initialize Guice and create injected instances.

• PlanetFactory.java
• PlanetModule.java - JPA version
• PlanetModule.java - Hibernate version

Planet implementation and all manager implementations use constructor injection. The are all declared as singletons.

• JPAPlanetImpl.java.
• HibernatePlanetImpl.java.

Changes to Roller Weblogger's Planet integration

The PlanetFactory uses the Guice back-end specified in the planet.properties file. In To use Planet in Roller we need simply provide a special different PlanetModule, one with a Planet implementation that can read reads database parameters from the Roller properties file instead of the Planet one.

...