Nabble - Pluto - User

Re: How to invalidate portlet session on logout?

2009-11-18T04:40:06Z

Here is a previous thread on this topic which includes some links as to how uPortal deals with this issue:

http://old.nabble.com/Invalidating-all-portlet-sessions-td18386578.html

-Eric

Brett Randall wrote:

Yes Ate is correct, and also here's a couple of likely links to Jetspeed and Liferay issue trackers where I believe they have dealt with the same requirement you are trying to deal with:

http://issues.apache.org/jira/browse/JS2-582

http://issues.liferay.com/browse/LEP-1466

I've not reviewed those issues, but I can image that the Portal context needs to propagate the session invalidation to the Portlet context.

Brett

On Wed, Nov 18, 2009 at 8:26 PM, Ate Douma <ate@...> wrote:

Portlet 2.0 spec PLT.18.4 (and for that matter the whole of the Portlet spec) *only* talks about the *Portlet* application, not the *Portal* application.
This means, the portlet *container* is required to invalidate the servlet (application) session when the portlet session is invalidated, and this is properly implemented in the Pluto container.
You should not confuse this with the (limited) behavior of the Pluto *Portal* Driver, which primarily purpose is only to serve as testbed for the Pluto container, not a full blown, production ready, portal.
Handling logout *across* portlet applications hosted by the Pluto Portal Driver simply isn't implemented as it not needed for *testing* the Pluto Container itself.

The Pluto Portal Driver, while actually used by some for production purposes, really is not targeted nor maintained for such usages.

If you need such functionality (and/or similar production quality features like persistence, better (session) navigation state/url handling, etc., etc.) you either have to add this yourself or probably better switch using a full blown portal like Apache Jetspeed-2 or others which does provide all such features.

HTH,

Ate

hub wrote:

Brett,
After logout / login I see the same session attributes as I set before in
the portlet session.
I noticed that my, "valueUnbound()" method for attributes in the portlet
session is not called for the cleanup I need to do on logout / "portal
session invalidation". I then set portlet session expiration time to a short
period to check, if valueUnbound() is called at all, ... it is, also on
application shutdown.
The session.invalidate() on logout is run in a jsp in "portal context".
After login with different username I have a different principal in the
portlet session, but same session attributes as set before.

javabrett wrote:

If the HttpSession object is invalidated, the PortletSession object must
also be invalidated by the portlet container.

I read the same here for JSR 168:
http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?pageId=3131

I have set emptySessionPath="true" in server.xml.
running on JBoss GA 4.2.2, Tomcat version is 6.0.20

Thank you
hub

javabrett wrote:

According to Portlet 2.0 spec PLT.18.4:

If the HttpSession object is invalidated, the PortletSession object
must
also be invalidated by the portlet container.

How do you detect that your portlet sessions are not being invalidated?

Brett

On Tue, Nov 17, 2009 at 10:09 PM, hub <felber@...> wrote:

Hello,
How do I invalidate all portlet sessions on logout?

in my logout.jsp in the portal I do the following
<%
session.invalidate();
%>

This invalidates the "portal" session but my portlet sessions are not
invalidated.

smime.p7s (4K) Download Attachment

Re: How to invalidate portlet session on logout?

2009-11-18T02:17:31Z

Brett and Ate,

The Pluto Portal Driver, while actually used by some for production purposes, really is not targeted nor maintained for such usages.
...
If you need such functionality .......add this yourself or probably better switch using a full blown portal like Apache Jetspeed.

I was afraid to hear that ...
Yes, I saw that others using different portal struggeled with similar problems.

Thank you very much
hub

Re: How to invalidate portlet session on logout?

2009-11-18T01:34:42Z

Yes Ate is correct, and also here's a couple of likely links to Jetspeed and Liferay issue trackers where I believe they have dealt with the same requirement you are trying to deal with:

http://issues.apache.org/jira/browse/JS2-582

http://issues.liferay.com/browse/LEP-1466

I've not reviewed those issues, but I can image that the Portal context needs to propagate the session invalidation to the Portlet context.

Brett

On Wed, Nov 18, 2009 at 8:26 PM, Ate Douma <ate@...> wrote:

Portlet 2.0 spec PLT.18.4 (and for that matter the whole of the Portlet spec) *only* talks about the *Portlet* application, not the *Portal* application.
This means, the portlet *container* is required to invalidate the servlet (application) session when the portlet session is invalidated, and this is properly implemented in the Pluto container.
You should not confuse this with the (limited) behavior of the Pluto *Portal* Driver, which primarily purpose is only to serve as testbed for the Pluto container, not a full blown, production ready, portal.
Handling logout *across* portlet applications hosted by the Pluto Portal Driver simply isn't implemented as it not needed for *testing* the Pluto Container itself.

The Pluto Portal Driver, while actually used by some for production purposes, really is not targeted nor maintained for such usages.

If you need such functionality (and/or similar production quality features like persistence, better (session) navigation state/url handling, etc., etc.) you either have to add this yourself or probably better switch using a full blown portal like Apache Jetspeed-2 or others which does provide all such features.

HTH,

Ate

hub wrote:

Brett,
After logout / login I see the same session attributes as I set before in
the portlet session.
I noticed that my, "valueUnbound()" method for attributes in the portlet
session is not called for the cleanup I need to do on logout / "portal
session invalidation". I then set portlet session expiration time to a short
period to check, if valueUnbound() is called at all, ... it is, also on
application shutdown.
The session.invalidate() on logout is run in a jsp in "portal context".
After login with different username I have a different principal in the
portlet session, but same session attributes as set before.

javabrett wrote:

If the HttpSession object is invalidated, the PortletSession object must
also be invalidated by the portlet container.

I read the same here for JSR 168:
http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?pageId=3131

I have set emptySessionPath="true" in server.xml.
running on JBoss GA 4.2.2, Tomcat version is 6.0.20

Thank you
hub

javabrett wrote:

According to Portlet 2.0 spec PLT.18.4:

If the HttpSession object is invalidated, the PortletSession object
must
also be invalidated by the portlet container.

How do you detect that your portlet sessions are not being invalidated?

Brett

On Tue, Nov 17, 2009 at 10:09 PM, hub <felber@...> wrote:

Hello,
How do I invalidate all portlet sessions on logout?

in my logout.jsp in the portal I do the following
<%
session.invalidate();
%>

This invalidates the "portal" session but my portlet sessions are not
invalidated.

Re: How to invalidate portlet session on logout?

2009-11-18T01:26:26Z

Portlet 2.0 spec PLT.18.4 (and for that matter the whole of the Portlet spec) *only* talks about the *Portlet* application, not the *Portal*
application.
This means, the portlet *container* is required to invalidate the servlet (application) session when the portlet session is invalidated, and
this is properly implemented in the Pluto container.
You should not confuse this with the (limited) behavior of the Pluto *Portal* Driver, which primarily purpose is only to serve as testbed
for the Pluto container, not a full blown, production ready, portal.
Handling logout *across* portlet applications hosted by the Pluto Portal Driver simply isn't implemented as it not needed for *testing* the
Pluto Container itself.

The Pluto Portal Driver, while actually used by some for production purposes, really is not targeted nor maintained for such usages.

If you need such functionality (and/or similar production quality features like persistence, better (session) navigation state/url handling,
etc., etc.) you either have to add this yourself or probably better switch using a full blown portal like Apache Jetspeed-2 or others which
does provide all such features.

HTH,

Ate

hub wrote:

> Brett,
> After logout / login I see the same session attributes as I set before in
> the portlet session.
> I noticed that my, "valueUnbound()" method for attributes in the portlet
> session is not called for the cleanup I need to do on logout / "portal
> session invalidation". I then set portlet session expiration time to a short
> period to check, if valueUnbound() is called at all, ... it is, also on
> application shutdown.
> The session.invalidate() on logout is run in a jsp in "portal context".
> After login with different username I have a different principal in the
> portlet session, but same session attributes as set before.
>
>
> javabrett wrote:
>> If the HttpSession object is invalidated, the PortletSession object must
>> also be invalidated by the portlet container.
>>
>
> I read the same here for JSR 168:
> http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?pageId=3131
>
> I have set emptySessionPath="true" in server.xml.
> running on JBoss GA 4.2.2, Tomcat version is 6.0.20
>
>
> Thank you
> hub
>
>
> javabrett wrote:
>> According to Portlet 2.0 spec PLT.18.4:
>>
>> If the HttpSession object is invalidated, the PortletSession object
>> must
>> also be invalidated by the portlet container.
>>
>> How do you detect that your portlet sessions are not being invalidated?
>>
>> Brett
>>
>> On Tue, Nov 17, 2009 at 10:09 PM, hub <felber@...> wrote:
>>
>>> Hello,
>>> How do I invalidate all portlet sessions on logout?
>>>
>>> in my logout.jsp in the portal I do the following
>>> <%
>>> session.invalidate();
>>> %>
>>>
>>> This invalidates the "portal" session but my portlet sessions are not
>>> invalidated.
>>>
>

Re: How to invalidate portlet session on logout?

2009-11-18T01:11:17Z

Brett,
After logout / login I see the same session attributes as I set before in the portlet session.
I noticed that my, "valueUnbound()" method for attributes in the portlet session is not called for the cleanup I need to do on logout / "portal session invalidation". I then set portlet session expiration time to a short period to check, if valueUnbound() is called at all, ... it is, also on application shutdown.
The session.invalidate() on logout is run in a jsp in "portal context". After login with different username I have a different principal in the portlet session, but same session attributes as set before.

javabrett wrote:

If the HttpSession object is invalidated, the PortletSession object must
also be invalidated by the portlet container.

I read the same here for JSR 168:
http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?pageId=3131

I have set emptySessionPath="true" in server.xml.
running on JBoss GA 4.2.2, Tomcat version is 6.0.20

Thank you
hub

javabrett wrote:

According to Portlet 2.0 spec PLT.18.4:

If the HttpSession object is invalidated, the PortletSession object must
also be invalidated by the portlet container.

How do you detect that your portlet sessions are not being invalidated?

Brett

On Tue, Nov 17, 2009 at 10:09 PM, hub <felber@abacus.ch> wrote:

>
> Hello,
> How do I invalidate all portlet sessions on logout?
>
> in my logout.jsp in the portal I do the following
> <%
> session.invalidate();
> %>
>
> This invalidates the "portal" session but my portlet sessions are not
> invalidated.
>

Re: How to invalidate portlet session on logout?

2009-11-17T19:09:07Z

According to Portlet 2.0 spec PLT.18.4:

If the HttpSession object is invalidated, the PortletSession object must also be invalidated by the portlet container.

How do you detect that your portlet sessions are not being invalidated?

Brett

On Tue, Nov 17, 2009 at 10:09 PM, hub <felber@...> wrote:

Hello,
How do I invalidate all portlet sessions on logout?

in my logout.jsp in the portal I do the following
<%
session.invalidate();
%>

This invalidates the "portal" session but my portlet sessions are not
invalidated.

I use objects with implement the HttpSessionBindingListener interface. These
should be called, when the user logs out and the portlet session is
invalidated. I need to do some cleanup for attributes I stored on the
portlet session.

Thank you for helping
Hub

--
View this message in context: http://old.nabble.com/How-to-invalidate-portlet-session-on-logout--tp26388080p26388080.html
Sent from the Pluto - User mailing list archive at Nabble.com.

How to invalidate portlet session on logout?

2009-11-17T03:09:36Z

Hello,
How do I invalidate all portlet sessions on logout?

in my logout.jsp in the portal I do the following
<%
session.invalidate();
%>

This invalidates the "portal" session but my portlet sessions are not invalidated.

I use objects with implement the HttpSessionBindingListener interface. These should be called, when the user logs out and the portlet session is invalidated. I need to do some cleanup for attributes I stored on the portlet session.

Thank you for helping
Hub

java.lang.LinkageError while dispatching events in Pluto 2.0

2009-10-29T08:54:34Z

Hi,

I have problems dispatching events (Pluto 2.0 / JBoss 4.2.2 / Tomcat).
Curiously enough it works, although I get stacktraces. I can send and receive the events.

With the event I dispatch the following object.

public class PortletExchangeInfo implements Serializable {
// jaxb doesnt dispatch HashMap
public ArrayList<String> parameterNames = new ArrayList();
public ArrayList<String[]> parameterValues = new ArrayList();
}

There seams to be a problem getting the JAXB serializer/deserializers.

The exceptions happen in
org.apache.pluto.driver.services.container.EventProviderImpl.createEvent(EventProviderImpl.java:84)
and
org.apache.pluto.driver.services.container.PortletWindowThread.run(PortletWindowThread.java:114)

when calling: JAXBContext jc = JAXBContext.newInstance(clazz);

I get:

FEIN: Unable to inject ch/abacus/flow/web/portlets/PortletExchangeInfo$JaxbAccessorF_parameterNames
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
...
at org.apache.pluto.driver.services.container.PortletWindowThread.run(PortletWindowThread.java:114)
Caused by: java.lang.LinkageError: loader (instance of org/jboss/web/tomcat/service/WebAppClassLoader): attempted duplicate class definition for name: "ch/abacus/flow/web/portlets/PortletExchangeInfo$JaxbAccessorF_parameterNames"
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.lang.ClassLoader.defineClass(ClassLoader.java:465)
...
and

FEIN: Unable to inject ch/abacus/flow/web/portlets/PortletExchangeInfo$JaxbAccessorF_parameterValues
java.lang.reflect.InvocationTargetException
...
at org.apache.pluto.driver.services.container.PortletWindowThread.run(PortletWindowThread.java:114)
Caused by: java.lang.LinkageError: loader (instance of org/jboss/web/tomcat/service/WebAppClassLoader): attempted duplicate class definition for name: "ch/abacus/flow/web/portlets/PortletExchangeInfo$JaxbAccessorF_parameterValues"
...

---------------------------------

and a similar stacktrace from org.apache.pluto.driver.services.container.EventProviderImpl.createEvent

It would be great, if anybody had a clue on this.

Thanks
Hubert

Re: actionURL way to long

2009-10-28T09:57:55Z

unsubscribe

_________________________________________________________
Eric Anderson
Palantir Technologies | Engineering Team Lead
eanderson@... | 520.440.3773
_________________________________________________________

On Oct 28, 2009, at 6:56 AM, hub wrote:

Hello,

It does not have anything to do with public render parameters.
The problem I have with this long url is, that Acrobat Reader refuses to
work with a URL that is 1015 characters long.

The more different portlets I clicked in, the longer the url gets.

Is this the default behaviour? If yes, this is pretty bad :-(

Thank you
Hubert
--
View this message in context: http://www.nabble.com/actionURL-way-to-long-tp26092324p26095045.html
Sent from the Pluto - User mailing list archive at Nabble.com.

smime.p7s (5K) Download Attachment

Re: sample JSR286

2009-10-28T08:32:23Z

It is not possible to make an alone portlet without this inside to Suite.

I have comes with the file pom.xml. It doesn't work me.

Please alone ayundeme wants to deploy to portlet JSR268 in pluto 2.0..

This could make it with the pluto 1.0 since has / she had to plugin. But it cannot spread on to war in 2.0 o'clock the portlet has / she doesn't register I don't eat to make it, alguién dog give me an example been worth of to hello world. Does This version of pluto non work??

2009/8/5 Woonsan Ko <woon_san@...>

Have you looked at the pluto testsuite portlets?
You can download and run it the binary and see JSR 286 portlets here:

http://portals.apache.org/pluto/v20/getting-started.html

You can also look into the sources under the testsuite subproject.

--- On Tue, 8/4/09, lagrimas negras xxx <lagrimasnegras33@...> wrote:

> From: lagrimas negras xxx <lagrimasnegras33@...>

> Subject: sample JSR286
> To: pluto-user@...
> Date: Tuesday, August 4, 2009, 3:03 PM

> Please somebody can spend a portlet JSR 286
> of example. Simple hello World
>

Re: actionURL way to long

2009-10-28T06:55:56Z

Hello,

It does not have anything to do with public render parameters.
The problem I have with this long url is, that Acrobat Reader refuses to work with a URL that is 1015 characters long.

The more different portlets I clicked in, the longer the url gets.

Is this the default behaviour? If yes, this is pretty bad :-(

Thank you
Hubert

actionURL way to long

2009-10-28T03:26:17Z

Hello,

A Url created with renderResponse.createActionURL() (jsr-286) is m u c h too long. Below is a sample url.
Why is this so? It looks linke all portlets are contained in this url. For some tools like acrobat reader, this kind of URL is too long, it refuses to connect to.
How can I avoid this? Could it have to do with public render parameters?

Thanks for your help
Hubert

/pluto/portal/__actestsuite0x2MenuPortlet!2255103%7C0/__pmtestsuite0x2MenuPortlet!2255103%7C0_view/__pmtestsuite0x2XFormsPortlet!2255103%7C6_view/__pmtestsuite0x2StartWorkflowPortlet!2255103%7C3_view/__pmtestsuite0x2WorkflowPortlet!2255103%7C4_view/__pmtestsuite0x2MyStartedWorkflowsPortlet!2255103%7C5_view/__pmtestsuite0x2MyWorkflowsPortlet!2255103%7C1_view/__wstestsuite0x2MenuPortlet!2255103%7C0_normal/__wstestsuite0x2XFormsPortlet!2255103%7C6_normal/__wstestsuite0x2StartWorkflowPortlet!2255103%7C3_normal/__wstestsuite0x2WorkflowPortlet!2255103%7C4_normal/__wstestsuite0x2MyStartedWorkflowsPortlet!2255103%7C5_normal/__wstestsuite0x2MyWorkflowsPortlet!2255103%7C1_normal/__rptestsuite0x2WorkflowPortlet!2255103%7C4_command/viewworkflow/__rptestsuite0x2XFormsPortlet!2255103%7C6_param_XFormsPortlet/karotest/__rptestsuite0x2MyStartedWorkflowsPortlet!2255103%7C5_param_MyStartedWorkflowsPortlet/karotest/__rptestsuite0x2WorkflowPortlet!2255103%7C4_id/5762/__rptestsuite0x2MyStartedWorkflowsPortlet!2255103%7C5_id/5762/__rptestsuite0x2WorkflowPortlet!2255103%7C4_view/viewworkflow/__rptestsuite0x2MyStartedWorkflowsPortlet!2255103%7C5_command/viewworkflow/__sp_render-action/home?

Shorten URL

2009-10-27T07:18:08Z

Hi all,

is there a way to get rid of the "/portal" in the URL? And if it's
possible please tell me how.
I tried to use UrlRewrite to forward /hello to /pluto/portal/hello,
but this does not work since pluto does not react after a forward.

Thanks in advance,
Armin

understanding pluto-default-theme

2009-10-08T06:52:17Z

Hi,
I would like to understand, what exactly happens in the "pluto-default-theme.jsp"
Where do variables like "currentPage.portletIds" or "portlet" come from? What else is accessible? Is there any documentation available?

What I would like to do is:
For all portlets on a page using the same theme, I want to check the name of the portlet and decide at runtime wether it will be placed on portal page or not.
Is this possible at all and how do you do this?

I noticed that a "porlet" variable looks like for example "testsuite.MenuPortlet!2255103|0".
Is it possible to work with Portletnames only? (MenuPortlet).

Unfortunately I did not find any documentation or samples about this.
Any help would be appreciated

Thanx
Hubert

Re: sample JSR286

2009-08-05T06:23:55Z

Have you looked at the pluto testsuite portlets?
You can download and run it the binary and see JSR 286 portlets here:

http://portals.apache.org/pluto/v20/getting-started.html

You can also look into the sources under the testsuite subproject.

--- On Tue, 8/4/09, lagrimas negras xxx <lagrimasnegras33@...> wrote:

> From: lagrimas negras xxx <lagrimasnegras33@...>
> Subject: sample JSR286
> To: pluto-user@...
> Date: Tuesday, August 4, 2009, 3:03 PM
> Please somebody can spend a portlet JSR 286
> of example. Simple hello World
>

sample JSR286

2009-08-04T06:03:14Z

Please somebody can spend a portlet JSR 286 of example. Simple hello World

plugin eclipse pluto 2.0

2009-08-04T03:40:43Z

Hello, you know a plugin it eclipse for pluto 2.0

Re: Using ServletRequestAttributeListener(s) in Pluto

2009-07-30T17:53:30Z

This is a portlet spec issue. The 1.0 portlet spec does not define a way
to get behavior similar to ServletRequestAttributeListener. The fact
that Pluto uses a cross-context call to a special servlet to initiate
portlet rendering is an implementation detail that cannot be relied upon
when writing a 'portlet'. However if you have a
ServletRequestAttributeListener in the web.xml for your portlet
application and directly target a servlet of your own your listener
should be triggered.

-Eric

michael freedman wrote:

> Seems that in at least Pluto 1.x, if you register a
> ServletRequestAttributeListener with your web application you are
> never called because Pluto relies on cross context dispatching --
> These listeners are maintained in the servletContext hence with cross
> context there are two involved (pluto's and the portlet app). In this
> case we run into a mismatch where Pluto's context/listeners are used
> rather and the portlet apps. I.e. The request is received/managed by
> the Pluto context (the one that doesn't have the apps listeners
> registered -- context is transferred to the portlet app and the
> portlet app removed the request attribute, the removal is actually
> handled by the request instance in the Pluto context and hence the
> Pluto listeners are called not the portlet app.
>
> Anyone ever figure a way around this? Or is this one of those
> (generic) servlet gotchas related to cross context?
> -Mike-

smime.p7s (4K) Download Attachment

Using ServletRequestAttributeListener(s) in Pluto

2009-07-30T15:45:48Z

Seems that in at least Pluto 1.x, if you register a
ServletRequestAttributeListener with your web application you are never
called because Pluto relies on cross context dispatching -- These
listeners are maintained in the servletContext hence with cross context
there are two involved (pluto's and the portlet app). In this case we
run into a mismatch where Pluto's context/listeners are used rather and
the portlet apps. I.e. The request is received/managed by the Pluto
context (the one that doesn't have the apps listeners registered --
context is transferred to the portlet app and the portlet app removed
the request attribute, the removal is actually handled by the request
instance in the Pluto context and hence the Pluto listeners are called
not the portlet app.

Anyone ever figure a way around this? Or is this one of those (generic)
servlet gotchas related to cross context?
-Mike-

In early version of Pluto other servlet in portlet war cannot share HttpSession with portlet?

2009-07-15T19:19:31Z

Hi,

Our client reported a bug that in rather early version of Pluto, other
servlet in portlet war cannot see the same HttpSession object as
portlet can see.

This is because when request reached to portlet war from portal, the
request contextpath is still pointing to portal, but for other servlets
in portlet war, surely the contextpath is just portlet war's path.

People told me that in later Pluto this is issue is fixed, but I read the
new Pluto (1.1.6) back-and-forth still cannot see how this issue is
fixed?

I would really appreciate if anything could give me a pointer (a hint is
good enough)?

Thanks very much for helps, Lisheng

Re: Supplied Maven script for one or multiple portlets?

2009-07-02T07:17:46Z

Glen Mazza wrote:
> Hello, is the Maven script on the deploying page
> (http://portals.apache.org/pluto/v20/deploying.html) meant for just one
> portlet, or will it work for multiple portlets within the same WAR as well.
> It's artifactId (HelloWorldPortlet) implies it should only be used for one
> portlet but the testsuite and pluto-portal WARs both contain multiple
> portlets so I'm unsure.

The artifactId of the example configuration shown should be regarded as just that: an example :)

The deployment always concerns a full portlet (web) *application*, meaning you can combine multiple portlet definitions (all defined in one
portlet.xml) to be deployed as a single set.

It is comparable to deploying a plain web application for which you can define multiple servlets in one web.xml

Regards,

Ate

>
> Thanks,
> Glen
>

Re: Supplied Maven script for one or multiple portlets?

2009-07-02T07:13:21Z

The deployment is for the entire WAR so you can have as many portlets as
you would like in one webapp.

-Eric

Glen Mazza wrote:

> Hello, is the Maven script on the deploying page
> (http://portals.apache.org/pluto/v20/deploying.html) meant for just one
> portlet, or will it work for multiple portlets within the same WAR as well.
> It's artifactId (HelloWorldPortlet) implies it should only be used for one
> portlet but the testsuite and pluto-portal WARs both contain multiple
> portlets so I'm unsure.
>
> Thanks,
> Glen
>
>

smime.p7s (4K) Download Attachment

Supplied Maven script for one or multiple portlets?

2009-07-02T07:08:10Z

Hello, is the Maven script on the deploying page (http://portals.apache.org/pluto/v20/deploying.html) meant for just one portlet, or will it work for multiple portlets within the same WAR as well. It's artifactId (HelloWorldPortlet) implies it should only be used for one portlet but the testsuite and pluto-portal WARs both contain multiple portlets so I'm unsure.

Thanks,
Glen

Re: How to configure "portal driver 2.0"

2009-07-02T07:03:54Z

The Pluto portal driver incorporates the pluto-testsuite.war's portlets, so you might be able glean from the Pluto portal driver how it should be incorporating your portlets by default.

I doubt you would want to put the pluto portal driver (the "driver" is the webapp hosting the portlets, right?) in your portlet's WEB-INF folder, or even reference the portal within your portlet WAR. On the contrary, you might want to modify the pluto portal driver's WAR to incorporate your WAR's portlets, just as it presently incorporates the testsuite WAR's.

Alternatively, the Pluto portal driver's webapp has an Admin page where you can dynamically incorporate portals from your portal WAR--so that's another option for you. The bottom of the deploying page can show you how to make that addition persistent: http://portals.apache.org/pluto/v20/deploying.html

I think the embedding page you're referencing is for if you want to create Portal generation software like Jetspeed, not really your purposes here. Also, Jetspeed has a Portal/Portlet tutorial that might help you:
http://portals.apache.org/jetspeed-2/tutorial/index.html

Glen

Alvim wrote:

Hi,

I'm trying to embed a portlet JSR 268 (2.0) into a simple WAR following the FAQ:

http://portals.apache.org/pluto/faq.html#simple-embed

And following the "embedding instructions" for Pluto 2.0:

http://portals.apache.org/pluto/v20/embedding.html

But the instruction doesn't inform about how to configure the pluto portal driver (v. 2.0)... So I tried to copy the following JARs to my app WEB-INF/lib :

- pluto-portal-driver-impl-2.0.0.jar
- spring-*.jar (the 4 Spring JARs that Pluto 2.0 have in tomcat/lib)

The app throws an exception in the filter initialized:

26069 [main] INFO org.apache.pluto.driver.PortalStartupListener - Starting up Pluto Portal Driver. . .
01/07/2009 12:04:38 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener
java.lang.NullPointerException
at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:111)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3830)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)

Anyone could help me to configure appropriate Pluto Portal Driver JARs in my app? Thanks a lot!

Paulo Alvim
Brazil

Paulo Alvim
Diretor de Tecnologia
Powerlogic SA
55 (31) 3555-0050

Re: How to configure "portal driver 2.0"

2009-07-01T08:26:15Z

I think is probably a missing Spring file (I don't know Spring). The PortalStartupListener line is:

   LOG.debug(" [1a] Loading DriverConfiguration. . . ");
        DriverConfiguration driverConfiguration = (DriverConfiguration)
                springContext.getBean("DriverConfiguration");

Paulo Alvim
Diretor de Tecnologia
Powerlogic SA
55 (31) 3555-0050

----- Mensagem original -----
De: "Paulo César Alvim Ottoni" <alvim@...>
Para: pluto-user@...
Enviadas: Quarta-feira, 1 de Julho de 2009 12:20:45 (GMT-0300) Auto-Detected
Assunto: How to configure "portal driver 2.0"

Hi,

I'm trying to embed a portlet JSR 268 (2.0) into a simple WAR following the FAQ:

http://portals.apache.org/pluto/faq.html#simple-embed

And following the "embedding instructions" for Pluto 2.0:

http://portals.apache.org/pluto/v20/embedding.html

But the instruction doesn't inform about how to configure the pluto portal driver (v. 2.0)... So I tried to copy the following JARs to my app WEB-INF/lib :

- pluto-portal-driver-impl-2.0.0.jar
- spring-*.jar (the 4 Spring JARs that Pluto 2.0 have in tomcat/lib)

The app throws an exception in the filter initialized:

26069 [main] INFO org.apache.pluto.driver.PortalStartupListener - Starting up Pluto Portal Driver. . .
01/07/2009 12:04:38 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener
java.lang.NullPointerException
    at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:111)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3830)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost..java:525)

Anyone could help me to configure appropriate Pluto Portal Driver JARs in my app? Thanks a lot!

Paulo Alvim
Brazil

Paulo Alvim
Diretor de Tecnologia
Powerlogic SA
55 (31) 3555-0050

Re: "Web application descriptor must be a valid web.xml" build error

2009-07-01T08:23:59Z

No--same error even if I do that, even if I delete the file. Maybe it's requiring a 2.4 web.xml (I'm relying on a tutorial sample--I can upgrade it.) I'll look into entering a (Maven, apparently) JIRA for a better error message--I need to know whether it can't find the web.xml, or it can but there's something wrong with the file. The troubleshooting you do in each case is very different.

Thanks,
Glen

Woonsan Ko wrote:

Hi Glen,

I see the element definition in the dtd specified in your web.xml as follows:

<!ELEMENT web-app (icon?, display-name?, description?, distributable?,
context-param*, filter*, filter-mapping*, listener*, servlet*,
servlet-mapping*, session-config?, mime-mapping*, welcome-file-list?,
error-page*, taglib*, resource-env-ref*, resource-ref*, security-constraint*,
login-config?, security-role*, env-entry*, ejb-ref*, ejb-local-ref*)>

So, I think you should move down welcome-file-list after servlet-mapping.

Regards,

Woonsan

--- On Tue, 6/30/09, Glen Mazza <glen.mazza@gmail.com> wrote:

> From: Glen Mazza <glen.mazza@gmail.com>
> Subject: "Web application descriptor must be a valid web.xml" build error
> To: pluto-user@portals.apache.org
> Date: Tuesday, June 30, 2009, 4:55 PM
>
> Hello, I'm repeatedly getting a "Web application descriptor
> must be a valid
> web.xml" error while trying to build a sample
> HelloWorldPortlet following
> the online docs here[1], using the pom.xml supplied and
> following the folder
> structure on that page (i.e. having the web.xml in
> "HelloWorldPortlet\src\main\java\webapp\WEB-INF"
> directory.) Partial
> stacktrace is below.
>
> Eclipse is showing that the web.xml is at least
> well-formed:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD
> Web Application
> 2.3//EN"
>    "http://java.sun.com/dtd/web-app_2_3.dtd">
>
> <web-app id="HelloWorldID">
>
>    <display-name>HelloWorldPortlet</display-name>
>
>    <welcome-file-list>
>
> <welcome-file>index.html</welcome-file>
>    </welcome-file-list>
>
> <servlet>
>
> <servlet-name>HelloWorldPortlet</servlet-name>
>
> <servlet-class>org.apache.pluto.container.driver.PortletServlet</servlet-class>
> <init-param>
>
> <param-name>portlet-name</param-name>
>
> <param-value>HelloWorldPortlet</param-value>
> </init-param>
>
> <load-on-startup>1</load-on-startup>
> </servlet>
>
> <servlet-mapping>
>
> <servlet-name>HelloWorldPortlet</servlet-name>
>
> <url-pattern>/PlutoInvoker/HelloWorldPortlet</url-pattern>
> </servlet-mapping>
> </web-app>
>
> But even if I delete this web.xml or use another web.xml
> that I know works
> (one from Pluto's portal or testsuite WAR file) I still get
> this same
> error--so I can't tell if there's a problem with the
> web.xml or simply that
> it can't find the web.xml. Any hints? Also, is
> this a Maven war plugin or
> Pluto plugin issue--if the latter, I'll enter a JIRA for
> the error message
> to distinguish between "bad web.xml" and "can't find the
> web.xml" so users
> with the latter problem don't need to spend time trying to
> fix their web.xml
> when that's not the problem.
>
> Thanks,
> Glen
>
> [1] http://portals.apache.org/pluto/v20/deploying.html
>
> C:\eclipse\workspace\HelloWorldPortlet>mvn clean install
> -e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building HelloWorldPortlet
> [INFO] task-segment: [clean, install]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] [pluto2:assemble {execution: default}]
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Web application descriptor must be a valid web.xml
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Web
> application
> descript
> or must be a valid web.xml
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:703)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:540)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:519)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:371)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:332)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:181)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> --
> View this message in context: http://www.nabble.com/%22Web-application-descriptor-must-be-a-valid-web.xml%22-build-error-tp24273382p24273382.html
> Sent from the Pluto - User mailing list archive at
> Nabble.com.
>
>

How to configure "portal driver 2.0"

2009-07-01T08:20:40Z

Hi,

I'm trying to embed a portlet JSR 268 (2.0) into a simple WAR following the FAQ:

http://portals.apache.org/pluto/faq.html#simple-embed

And following the "embedding instructions" for Pluto 2.0:

http://portals.apache.org/pluto/v20/embedding.html

But the instruction doesn't inform about how to configure the pluto portal driver (v. 2.0)... So I tried to copy the following JARs to my app WEB-INF/lib :

- pluto-portal-driver-impl-2.0.0.jar
- spring-*.jar (the 4 Spring JARs that Pluto 2.0 have in tomcat/lib)

The app throws an exception in the filter initialized:

26069 [main] INFO org.apache.pluto.driver.PortalStartupListener - Starting up Pluto Portal Driver. . .
01/07/2009 12:04:38 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener
java.lang.NullPointerException
    at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:111)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3830)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)

Anyone could help me to configure appropriate Pluto Portal Driver JARs in my app? Thanks a lot!

Paulo Alvim
Brazil

Paulo Alvim
Diretor de Tecnologia
Powerlogic SA
55 (31) 3555-0050

Re: "Web application descriptor must be a valid web.xml" build error

2009-06-30T08:14:22Z

Hi Glen,

I see the element definition in the dtd specified in your web.xml as follows:

<!ELEMENT web-app (icon?, display-name?, description?, distributable?,
context-param*, filter*, filter-mapping*, listener*, servlet*,
servlet-mapping*, session-config?, mime-mapping*, welcome-file-list?,
error-page*, taglib*, resource-env-ref*, resource-ref*, security-constraint*,
login-config?, security-role*, env-entry*, ejb-ref*, ejb-local-ref*)>

So, I think you should move down welcome-file-list after servlet-mapping.

Regards,

Woonsan

--- On Tue, 6/30/09, Glen Mazza <glen.mazza@...> wrote:

> From: Glen Mazza <glen.mazza@...>
> Subject: "Web application descriptor must be a valid web.xml" build error
> To: pluto-user@...
> Date: Tuesday, June 30, 2009, 4:55 PM
>
> Hello, I'm repeatedly getting a "Web application descriptor
> must be a valid
> web.xml" error while trying to build a sample
> HelloWorldPortlet following
> the online docs here[1], using the pom.xml supplied and
> following the folder
> structure on that page (i.e. having the web.xml in
> "HelloWorldPortlet\src\main\java\webapp\WEB-INF"
> directory.) Partial
> stacktrace is below.
>
> Eclipse is showing that the web.xml is at least
> well-formed:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD
> Web Application
> 2.3//EN"
>    "http://java.sun.com/dtd/web-app_2_3.dtd">
>
> <web-app id="HelloWorldID">
>
>    <display-name>HelloWorldPortlet</display-name>
>
>    <welcome-file-list>
>
> <welcome-file>index.html</welcome-file>
>    </welcome-file-list>
>
> <servlet>
>
> <servlet-name>HelloWorldPortlet</servlet-name>
>
> <servlet-class>org.apache.pluto.container.driver.PortletServlet</servlet-class>
> <init-param>
>
> <param-name>portlet-name</param-name>
>
> <param-value>HelloWorldPortlet</param-value>
> </init-param>
>
> <load-on-startup>1</load-on-startup>
> </servlet>
>
> <servlet-mapping>
>
> <servlet-name>HelloWorldPortlet</servlet-name>
>
> <url-pattern>/PlutoInvoker/HelloWorldPortlet</url-pattern>
> </servlet-mapping>
> </web-app>
>
> But even if I delete this web.xml or use another web.xml
> that I know works
> (one from Pluto's portal or testsuite WAR file) I still get
> this same
> error--so I can't tell if there's a problem with the
> web.xml or simply that
> it can't find the web.xml. Any hints? Also, is
> this a Maven war plugin or
> Pluto plugin issue--if the latter, I'll enter a JIRA for
> the error message
> to distinguish between "bad web.xml" and "can't find the
> web.xml" so users
> with the latter problem don't need to spend time trying to
> fix their web.xml
> when that's not the problem.
>
> Thanks,
> Glen
>
> [1] http://portals.apache.org/pluto/v20/deploying.html
>
> C:\eclipse\workspace\HelloWorldPortlet>mvn clean install
> -e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building HelloWorldPortlet
> [INFO] task-segment: [clean, install]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] [pluto2:assemble {execution: default}]
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Web application descriptor must be a valid web.xml
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Web
> application
> descript
> or must be a valid web.xml
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:703)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:540)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:519)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:371)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:332)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:181)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> --
> View this message in context: http://www.nabble.com/%22Web-application-descriptor-must-be-a-valid-web.xml%22-build-error-tp24273382p24273382.html
> Sent from the Pluto - User mailing list archive at
> Nabble.com.
>
>

"Web application descriptor must be a valid web.xml" build error

2009-06-30T07:55:21Z

Hello, I'm repeatedly getting a "Web application descriptor must be a valid web.xml" error while trying to build a sample HelloWorldPortlet following the online docs here[1], using the pom.xml supplied and following the folder structure on that page (i.e. having the web.xml in "HelloWorldPortlet\src\main\java\webapp\WEB-INF" directory.) Partial stacktrace is below.

Eclipse is showing that the web.xml is at least well-formed:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app id="HelloWorldID">

<display-name>HelloWorldPortlet</display-name>

<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>

<servlet>
<servlet-name>HelloWorldPortlet</servlet-name>
<servlet-class>org.apache.pluto.container.driver.PortletServlet</servlet-class>
<init-param>
<param-name>portlet-name</param-name>
<param-value>HelloWorldPortlet</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>HelloWorldPortlet</servlet-name>
<url-pattern>/PlutoInvoker/HelloWorldPortlet</url-pattern>
</servlet-mapping>
</web-app>

But even if I delete this web.xml or use another web.xml that I know works (one from Pluto's portal or testsuite WAR file) I still get this same error--so I can't tell if there's a problem with the web.xml or simply that it can't find the web.xml. Any hints? Also, is this a Maven war plugin or Pluto plugin issue--if the latter, I'll enter a JIRA for the error message to distinguish between "bad web.xml" and "can't find the web.xml" so users with the latter problem don't need to spend time trying to fix their web.xml when that's not the problem.

Thanks,
Glen

[1] http://portals.apache.org/pluto/v20/deploying.html

C:\eclipse\workspace\HelloWorldPortlet>mvn clean install -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building HelloWorldPortlet
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [pluto2:assemble {execution: default}]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Web application descriptor must be a valid web.xml
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Web application descript
or must be a valid web.xml
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:703)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:540)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)

[Pluto 2.0.0] Spring portlet

2009-06-25T07:40:30Z

Hi,

I tested spring portlet taked from
http://code.google.com/p/spring-portlet-sample/.

Everythinks looks working very well, except the fact that images are
not displayed. When I look into the code, I found that
request.getContextPath() in a jsp returns the context path of the
container (pluto) instead of contextPath of the portlet. When I
replaced by renderRequest.getContextPath(), it works well.

Is it an expected behavior or a bug of pluto-2.0.0?

Regards.
KT.

RE: what is pageregistry.xml file? why it is not coming with pluto 1.1.6

2009-06-18T06:22:20Z

I am trying to integrate JOSSO 1.8 into pluto to implement SSO feature.
but the tutorial i used for that, suggest the change in tag <fragment> int pageregistry.xml file.
It is not coming with pluto 1.1.6, but comes with older version.
please suggest what can i do to tackle that problem?

Pluto 2.0.0 And weblogic - Do all tck test succeed ?

2009-06-18T06:05:14Z

Hi,

Does any one succed running pluto with Weblogic?

On my side, the test "DispatcherRequestTest" failed.

PLT 16.3.1 - checkPathInfo
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

PLT 16.3.1 - checkRequestURI
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

PLT 16.3.1 - checkGetRequestURI
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

PLT 16.3.1 - checkContextPath
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

PLT 16.3.1 - checkGetContextPath
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

PLT 16.3.1 - checkServletPath
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

PLT 16.3.1 - checkGetServletPath
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

PLT 16.3.1 - checkQueryString
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

PLT 16.3.1 - checkGetQueryString
Ensure that included attribute 'javax.servlet.include.path_info' is
available in servlet request.
Assertion failed: got javax.servlet.include.path_info: {null},
expected: {/checkRequestURI,/checkContextPath,/checkServletPath,/checkQueryString}

Is a bug or a bad config on my side? Thanks for any help.

Regards.
KT.

Hello World portlet

2009-06-09T12:12:56Z

I am trying to create a Hello World portlet in Pluto before I go on to more advanced portlets. I have looked at the tutorial from onjava.com and looked at a previous post on nabble on uploading the .war file to Pluto, and other tutorials (including from ibm.com) that I have found on the internet, but still have trouble.

I have downloaded and installed the pluto-current-bundle (version 2.0) from the download site. The directory structure for HelloWorld is typical for web applications. My HelloWorld class is located in WEB-INF/classes. I have the web.xml and portlet.xml properly done and located in WEB-INF. I do not know what else is necessary to complete the portlet.

All the tutorials I have found are for Pluto 1.0 and have completed the same steps in Pluto 2.0.

Can somebody please let me know what else I need to do to get a simple Hello World portlet working?

Thanks.

RE: How to skip LOG IN page into pluto

2009-06-09T06:15:18Z

I am new to portal elopement & using Apache Pluto to deploy my portlet application.
i wan to skip Pluto log in page where we put User name : Pluto & password : Pluto . i.e. when i put url like http://localhost:8080/pluto/portal directly pluto portal page should be shown where my portlet app resides.
any way is there to get rid of Pluto log in page.

OR

can i use that login page as my personal login for my app.

please rep

[ANNOUNCE] Apache Portals Jetspeed 2.2.0, Pluto 2.0.0, Applications 1.0 releases

2009-05-28T10:24:36Z

The Apache Portals team is proud to announce the major release of a suite of new Portal projects, all aligned to the new Portlet API 2.0 specification (JSR-286):

* Version 2.2.0 of the Jetspeed Enterprise Portal

* Version 2.0.0 of the Pluto Container

* Version 1.0 of several new Portals Applications

More information about the Apache Portals Project itself and its projects can be found here:

http://portals.apache.org

http://portals.apache.org/jetspeed-2

http://portals.apache.org/pluto

http://portals.apache.org/applications

Jetspeed is an Open Portal Platform and Enterprise Portal, written in open source to the Java Portlet API standard under the Apache license. Version 2.2.0 is a major update from the 2.1.3 release.

New Features and improvements in Version 2.2.0:

* Portlet API 2.0 Support and Compliance

* Inter-Portlet Communication via Events

* New High Speed Preferences Database Storage

* New Extensible Security Model with LDAP Synchronization

* Improved Documentation including 5 New Guides (Users Guide, Admin Guide, Developers Guide, Build Guide, Deploy Guide)

* New Improved Administrative Portlets

* New Skins

* New Maven-2 Custom Build

* Improved integration support for popular web development frameworks like Wicket, Spring MVC, JSF, and Struts

Full details can be found in the Jetspeed 2.2.0 release notes:

http://portals.apache.org/jetspeed-2/release-notes.html

A demo of Jetspeed is running live at Apache Zones. Login with username/password admin/j2:

http://portals.zones.apache.org/jetspeed/portal/

http://portals.zones.apache.org/jetspeed/desktop/

Pluto Container is the Reference Implementation of th Java Portlet Specifications 1.0 and 2.0.

Pluto 2.0.0 is fully compliant with the latest 2.0 specification, also known as JSR-286,

as well as the 1.0 specification, known as JSR-168.

Full details can be found in the Pluto 2.0.0 release notes:

http://portals.apache.org/pluto/v20/release-notes.html

Apache Portals Applications (APA) is a new collaborative software development project existing under the Apache Portals project. APA is dedicated to providing robust, full-featured, commercial-quality, and freely available Portlet Applications under the Apache license developed at the Apache Software Foundation. The APA project releases 1.0 versions of the following Portlet Applications and components, all targetted at the Portlet Specification 2.0 (JR-286):

* Gems - A collection of reusable portlets including Flash, Google Maps, File, Event and Browser portlets.

* Database Browser - A portlet application dedicated to the development and database portlet development including scrollable lists and data entry forms

* Demo - A portlet application dedicated to learning Java and Groovy portlet programming and tutorials, as well as some helpful weather and bookmark portlets

* RSS - A portlet application dedicated to the development of RSS portlet features

* Web Content - A portlet application dedicated to the development of Web Content rewriting and IFrame based web content.

* Logging - Apache Portals Applications Logging, (APA Logging), is a utility library used to setup and deploy logging to portlet applications

Source and binary distributions, including standard and full demo installers for Jetspeed-2 Portal, are available from:

http://portals.apache.org/jetspeed-2/download.html

http://portals.apache.org/pluto/download.html

http://portals.apache.org/applications/download.html

Validating the release

The release has been signed by Vivek Kumar, Carsten Ziegeler, and David Taylor, the release managers for

this release. The public key can be found in the KEYS file in the download

area. Download the KEYS file only from the Apache website.

http://www.apache.org/dist/portals/jetspeed-2/KEYS

http://www.apache.org/dist/portals/pluto/KEYS

http://www.apache.org/dist/portals/applications/KEYS

Instructions on how to validate the release can be found here:

http://www.apache.org/dev/release-signing.html#check-integrity

Reporting Issues

In case you encounter an issue, we would appreciate if you can report it through our issue tracking system:

http://issues.apache.org/jira/browse/JS2

http://issues.apache.org/jira/browse/PLUTO

http://issues.apache.org/jira/browse/APA

We hope you enjoy using Apache Portals! If you have any questions, please consult:

* The web site: http://portals.apache.org/

* The mailing lists: http://portals.apache.org/mail-lists.html

David Sean Taylor

On behalf of the Apache Portals Team