Portlet Factory, Version 6.1.2

---

 

Choosing builder base classes and interfaces

Depending on how your builder acts on the WebApp, you need to extend or implement a specific base class or interface for your generation class and specify an appropriate GenHandler class in the builder definition. The following table lists the three ways of implementing a builder:

Builder Behavior	Specify GenHandler in Builder Definition	Base Class or Interface for the Builder Generation Class
Adds elements to a page using a Page Location input.	WebAppControlGenHandler	Implement WebAppControlBuilder and override the doBuilderCall() method.
If builder does not use a Page Location input. Adds elements to pages without taking a Page Location input Does not add any elements to a page.	WebAppGenHandler	Implement WebAppBuilder and override the doBuilderCall() method.
Adds elements to a page by writing directly to the XML describing the page in the WebApp. Note: This is not a common case.	WebAppControlGenHandler	Extend BaseWebAppControlBuilder and override the handleControl() method.

Keep these implementations in mind when you create the builder definition and generation class for your own builder.

The list below enumerates the fully-qualified class names for each of the classes and interfaces mentioned in the table above.

• com.bowstreet.builders.webapp.foundation.WebAppControlBuilder

• com.bowstreet.builders.webapp.foundation.WebAppBuilder

• com.bowstreet.builders.webapp.foundation.BaseWebAppControlBuilder

Parent topic: About adding elements to pages in the web application

---

Library | Support |