You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Weaver, Scott" <we...@ugs.com> on 2007/10/30 16:52:54 UTC
Did we remove support for root portal applications.
Did we remove support for "/" portlet applications? Looks like it
because now I get errors when trying to register just "/" for my portlet
app. Also, the contextPath init parameter for the
JetspeedContainerServlet is completely ignored. This is a requirement
for me. What were the reasons for removing support for this?
Thanks,
-scott
RE: Did we remove support for root portal applications.
Posted by "Weaver, Scott" <we...@ugs.com>.
I manually changed the DB to "/" for my portlet app. This used to work
fine prior to 2.1.3, but now every time I restart Jetspeed, the entry in
WEB_APPLICATION get reset.
When I have my web.xml setup like this, I don't get any errors BUT it
registers the context path to "/salescentre" instead of "/"
<servlet>
<description>MVC Servlet for Jetspeed Portlet
Applications</description>
<display-name>Jetspeed Container</display-name>
<servlet-name>JetspeedContainer</servlet-name>
<servlet-class>org.apache.jetspeed.container.JetspeedContainerServlet</s
ervlet-class>
<init-param>
<param-name>contextName</param-name>
<param-value>salescentre</param-value>
</init-param>
<init-param>
<param-name>contextPath</param-name>
<param-value>/</param-value>
</init-param>
<load-on-startup>100</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>JetspeedContainer</servlet-name>
<url-pattern>/container/*</url-pattern>
</servlet-mapping>
If I change it to this:
<servlet>
<description>MVC Servlet for Jetspeed Portlet
Applications</description>
<display-name>Jetspeed Container</display-name>
<servlet-name>JetspeedContainer</servlet-name>
<servlet-class>org.apache.jetspeed.container.JetspeedContainerServlet</s
ervlet-class>
<init-param>
<param-name>contextName</param-name>
<param-value>/</param-value>
</init-param>
<init-param>
<param-name>contextPath</param-name>
<param-value>/</param-value>
</init-param>
<load-on-startup>100</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>JetspeedContainer</servlet-name>
<url-pattern>/container/*</url-pattern>
</servlet-mapping>
I then get this error:
java.lang.IllegalStateException: Invalid paName "/". paName cannot be
null nor can it begin nor end with any slashes.
at
org.apache.jetspeed.util.descriptor.PortletApplicationWar.validatePortle
tApplicationName(PortletApplicationWar.java:169)
at
org.apache.jetspeed.util.descriptor.PortletApplicationWar.<init>(Portlet
ApplicationWar.java:132)
at
org.apache.jetspeed.tools.pamanager.PortletApplicationManager.startPA(Po
rtletApplicationManager.java:431)
at
org.apache.jetspeed.tools.pamanager.PortletApplicationManager.startPA(Po
rtletApplicationManager.java:419)
at
org.apache.jetspeed.tools.pamanager.PortletApplicationManager.startPortl
etApplication(PortletApplicationManager.java:194)
at
org.apache.jetspeed.container.JetspeedContainerServlet.attemptStart(Jets
peedContainerServlet.java:173)
at
org.apache.jetspeed.container.JetspeedContainerServlet.access$2(Jetspeed
ContainerServlet.java:159)
at
org.apache.jetspeed.container.JetspeedContainerServlet$1.run(JetspeedCon
tainerServlet.java:144)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
I tried manually changing the DB to "/" for my portlet app. This used
to work fine prior to 2.1.3, but now every time I restart Jetspeed, the
entry in WEB_APPLICATION get reset.
I think will look at fix this issue if no has any issues with it.
-scott
> -----Original Message-----
> From: Ate Douma [mailto:ate@douma.nu]
> Sent: Tuesday, October 30, 2007 12:09 PM
> To: Jetspeed Developers List
> Subject: Re: Did we remove support for root portal applications.
>
> Weaver, Scott wrote:
> > Did we remove support for "/" portlet applications? Looks like it
> > because now I get errors when trying to register just "/" for my
portlet
> > app. Also, the contextPath init parameter for the
> > JetspeedContainerServlet is completely ignored. This is a
requirement
> > for me. What were the reasons for removing support for this?
> >
> I have no idea if/why this would have been done, and I don't recall
any
> discussion about it either.
> I have deployed the portal under / but never tried doing so for a pa.
> What kind of errors do you get and can you pinpoint it to a certain
area
> where it fails (e.g. deployer, invoker etc.)
>
> Ate
>
> >
> >
> > Thanks,
> >
> > -scott
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Did we remove support for root portal applications.
Posted by Ate Douma <at...@douma.nu>.
Weaver, Scott wrote:
> Did we remove support for "/" portlet applications? Looks like it
> because now I get errors when trying to register just "/" for my portlet
> app. Also, the contextPath init parameter for the
> JetspeedContainerServlet is completely ignored. This is a requirement
> for me. What were the reasons for removing support for this?
>
I have no idea if/why this would have been done, and I don't recall any discussion about it either.
I have deployed the portal under / but never tried doing so for a pa.
What kind of errors do you get and can you pinpoint it to a certain area where it fails (e.g. deployer, invoker etc.)
Ate
>
>
> Thanks,
>
> -scott
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org