On Apr 21, 2009, at 7:49 AM, Lee jackie wrote:
hi, everybody
I want to customerize the JetSpeed to apply to a group of new
component
model, and I config the container.impl = *** to refer to to my
ContainerImpl
class, and restart the tomcat to test it. But I found JetSpeed still
to use
the default container implementation
org.apache.pluto.PortletContainerImpl, How could I to make the
modification
effective, thanks!
jackie
Sounds like more of a jetspeed-dev mailing list question
Anyway I don't think that property is used anymore
See the jetspeed-spring.xml Spring configuration:
<!-- Pluto Portlet Container -->
<bean id="Pluto" class="org.apache.pluto.PortletContainerImpl" />
<!-- Desktop Pluto Portlet Container -->
<bean id="DesktopPluto"
class="org.apache.jetspeed.container.DesktopPortletContainerImpl">
<constructor-arg index='0'>
<value>/desktop</value>
</constructor-arg>
<constructor-arg index='1'>
<value>/action</value>
</constructor-arg>
<constructor-arg index='2'>
<value>/portlet</value>
</constructor-arg>
</bean>
<!-- Jetspeed 2's wrapper around Pluto -->
<!-- settings for this bean will start the underlying pluto
portlet container -->
<bean id="org.apache.pluto.PortletContainer"
class="org.apache.jetspeed.container.JetspeedPortletContainerWrapper"
init-method="start"
destroy-method="shutdown">
<constructor-arg>
<ref bean="Pluto" />
</constructor-arg>
<constructor-arg>
<value>${portal.name}</value>
</constructor-arg>
<constructor-arg>
<ref bean="ServletConfig" />
</constructor-arg>
<constructor-arg>
<ref bean="Engine" />
</constructor-arg>
<property name="requestFactory">
<ref bean="ServletRequestFactory" />
</property>
<property name="responseFactory">
<ref bean="ServletResponseFactory" />
</property>
</bean>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
