jboss-dev-forums

[Jboss-dev-forums] [Design of JBoss Portal] - Re: question about PortletController

[<ju...@jb...>]

this controller is developed to test the portlet container only.

In that case there is no notion of page, all the components are involved in the render.

The goal to have a getRenderList is that the TCKController or the test agent subclass this class to provide their own implementation of the getRenderList based on a specific list of portlets.

For instance the tck will require to have a specific list of portlets to participate in the current request.

You should look also at the CoreController which use the command pattern to implement its logic in order to scale better because it may handle more situations than the simple PortletController.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887007#3887007

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887007

[Jboss-dev-forums] [Design of JBoss Portal] - Re: question about PortletController

[yxyang <nu...@jb...>]

Hi Julien

thanks for your help!  

In the core jboss-service.xml file, i found that the mbean object name is not consistent. 
In the definition of  ThemeService, the object name is defined as "portal:service=ThemeService", but it is refered as "portal:service=ThemeServer" in the servermanager service.

Is this correct?

anonymous wrote : 
  |    < mbean
  |       code="org.jboss.portal.server.impl.ServerManagerImpl"
  |       name="portal:service=ServerManager"
  |       xmbean-dd="org/jboss/portal/server/impl/ServerManagerImpl.xml">
  |       < attribute name="ContainerName" >MyContainer< /attribute>
  |       < depends>portal:service=Hibernate< /depends>
  |       < depends optional-attribute-name="Configuration" proxy-type="attribute">portal:service=Configuration< /depends>
  |       < depends optional-attribute-name="ObjectFactory" proxy-type="attribute">portal:service=ObjectFactory< /depends>
  |       < depends optional-attribute-name="ThemeServer" proxy-type="attribute">portal:service=ThemeServer< /depends>
  |       < depends optional-attribute-name="LayoutServer" proxy-type="attribute">portal:service=LayoutServer< /depends>
  |       < attribute name="InvocationFactoryClassName">org.jboss.portal.core.impl.invocation.CoreInvocationFactory< /attribute>
  |    < /mbean>
  | 

and 

anonymous wrote : 
  |    < mbean
  |       code="org.jboss.portal.theme.impl.ThemeServiceImpl"
  |       name="portal:service=ThemeService"
  |       xmbean-dd="org/jboss/portal/theme/impl/ThemeServiceImpl.xml">
  |    < /mbean>
  | 

regards
Yang

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887204#3887204

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887204