Bridge
interface is to be implemented by an external (to the bridge service manager) bridge service
@author amyk
Instances of this class is stateless and multi-thread safe. They are reentrant.
All the marshal operation generates fragments.
Subject to change without notice. @since JAXB 2.0 EA1 @author Kohsuke Kawaguchi
Instances of this class is stateless and multi-thread safe. They are reentrant.
All the marshal operation generates fragments.
Subject to change without notice. @since JAXB 2.0 EA1 @author Kohsuke Kawaguchi
Bridge
interface is used by a portlet to execute a JSF artifact. Its lifecycle follows the pattern used by other web components such as portlets or servlets, namely: init
: one time (per portlet) initialization. Usually invoked during portlet init
but may also occur lazily. Context is passed to the Bridge at initialization via PortletContext
attributes. See method description for details. doFacesRequest
: called for each portlet request that is to be handled by Faces. Must only be called after the bridge has been initialized. destroy
: called to destroy this bridge instance. Usually invoked during portlet destroy
but may also occur earlier if the portlet decides to reclaim resources. Portlet developers are encouraged to allow deployers an ability to configure the particular Bridge implementation it uses within a given deployment. This ensures a best fit solution for a given application server, portlet container, and/or Faces environment. The specifics for this configuation are undefined. Each portlet can define a preferred mechanism. Subclasses of {@link GenericFacesPortlet} automatically inherit this behavior as it recognizes a definedportlet initialization parameter.
Implementations of this Bridge
interface are required to have a code
constructor.
Defines a bridge between server and client side.
It contains a set of {@link Command}.
Commands are executed by the client side in order to update the DOM.
There is only one Bridge objet per session.
The current bridge object is serialized in current xul page via a set of tag (xfc namespace).
You can get the current Bridge instance with XulUtils.getBridge() method.
@author kito31 @version $Id: Bridge.java,v 1.3 2005/11/06 17:54:59 kito31 Exp $
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|