Presentation Framework update

[julien1]

I would like to integrate the current PF code in 2.6 trunk as it is difficult to access the modules from the current PF branch.

Once it is done, it will be possible to use the web module in order to make the classic presentation client rely on it instead of the "server" module that will make it more reusable. I have migrated the useful stuff from the server module (i.e the parameter & body parsing code) to the web module with the proper test cases.

[julien1]

I am going to try to use SVN external to create a composite project made of 2.6 + the presentation framework.

[theute]

That would be preferred :)

[claprun]

Yeah, I would also prefer a change like that to occur after 2.6.3 is released...

[julien1]

I have started it there : http://anonsvn.jboss.org/repos/portal/branches/presentation/

It compiles the portal core using "build -Dgroups=core", the two modules presentation and core-presentation don't compile yet.

Later, core-presentation will be integrated into 2.6.x and presentation will be modularized it (when I'll need it in portlet container module)

[julien1]

So now it downloads and compiles although the presentation and core-presentation needs to be compiled manually. I have not tested it works yet.

I have started it there : http://anonsvn.jboss.org/repos/portal/branches/presentation/

It compiles the portal core using "build -Dgroups=core", the two modules presentation and core-presentation don't compile yet.

Later, core-presentation will be integrated into 2.6.x and presentation will be modularized it (when I'll need it in portlet container module)

[julien1]

I wanted to mention that one role of the PF is to be a backbone for the management of events between the different components in the various tiers. I.e an event could be sent from a portlet to other portlets using JSR 286 API but the creation of messages could happen in the portlet container or in the user agent done by a javascript API. It would be the same for the consumption of messages that could happen in the portlet container or in the user agent.

That kind of message management is similar to the Bayeux protocol (http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html).