OW2 Consortium
Search OW2 Mail Archive: 

Advanced Search - Powered by Google


Mail Archive Home | exoplatform List | August 2006 Index

<--  Date Index     <--  Thread Index  -->

Re: [exoplatform] MyFaces support


Hello Kito,

So let me explain more our choices an incoming developments.

1. We had a lot of requests (including you) for supporting JSF MyFaces while we developed based on JSF RI. We can deploy MyFaces portlet in eXo portlet Container in standalone but not with eXo portal 1.x because of conflict with the JSF RI.

2. But we liked (from the early beginning of JSF) the component tree model, rendering and used some of the phases of JSF to build a kind of JSF RI extension in the portal and portlets of eXo Portal 1.1 as you saw. We for example use static inner class for action listener, some exception handlers...Hence, we wished to continue to use that model in eXo Portal 2.0

Therefore our solution to satisfy both 1 and 2 was to extract a "light" subset of JSF to build a framework that we use in eXo Portal 2.0 and also in the portlet that goes with it. That way we can still use a JSF like model and allow our users/customers to use the framework of their choice for their portlets, which is the great advantage of the portlets paradigm btw.

So we will move little by little all our portlets to that framework but it will take some time so for example the future version of eXo ECM (probably starting at 1.3+) will still use the current framework but those portlets will be deployed in the new eXo Portal 2.0. eXo ECM 2.0 will use the new framework

The change is not "drastic" as the model is similar but lighter and more adapted to portal and portlets. And people will be able to use JSF in their own portlet while still almost using it (due to the similar model) in the portal.

HTH

Benjamin


On Aug 31, 2006, at 5:26 PM, kmann@xxxxxxxxxxx wrote:

Quoting Benjamin Mestrallet <benjamin.mestrallet@xxxxxxxxxxxxxxx>:

No beta of Portal 2.0 in september, maybe October...but we want to
make the surprise....and it will be big!

It'll certainly help. It is possible to use the Tomahawk components with
a little bit today with a little bit of tweaking...


The solution is simple, the portal itself does not use JSF anymore
which allows to plug both JSF RI and JSF MyFaces portlet which is not

possible if the portal is built using one of the two.

Hmm.. So, are you removing JSF from the entire portal stack, or are you
simply moving all of the JSF logic into specific portlets that are
bundled with the portal?


It would seem like a pretty drastic change to remove JSF altogether....

On Aug 14, 2006, at 8:04 PM, Kito D. Mann wrote:


-----Original Message-----
From: Gennady Azarenkov
[mailto:gennady.azarenkov@xxxxxxxxxxxxxxx]
Sent: Friday, August 11, 2006 6:28 AM
To: kmann@xxxxxxxxxx; exoplatform@xxxxxxxxxxxxx
Subject: Re: [exoplatform] MyFaces support

hi,
yes, the next version of Portal will solve this prb, AFAIK we
do not have strict timeframe for Portal 2.0, but as Tuan
mentioned some beta could be accessible in September :)

Just out of curiosity, what is your technical approach for solving

this
problem?

----- Original Message -----
From: "Kito D. Mann" <kmann@xxxxxxxxxx>
To: <exoplatform@xxxxxxxxxxxxx>
Sent: Monday, August 07, 2006 6:16 PM
Subject: [exoplatform] MyFaces support


Hello,

As far as I can tell, if you want to deploy a JSF portlet
in eXo portal
1.x,
you must use the JSF RI (since that's what eXo uses, and
the JARs are in
the
common directory, at least in Tomcat). I saw an earlier
e-mail that stated
this would be solved in eXo portal 2.0 (hopefully by
segregating class
loaders). Is there are a target date for eXo portal 2.0?


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann (kmann@xxxxxxxxxx)
Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training,
and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info





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



-- You receive this message as a subscriber of the
exoplatform@xxxxxxxxxxxxx
mailing list.
To unsubscribe: mailto:exoplatform-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws





-- You receive this message as a subscriber of the exoplatform@xxxxxxxxxxxxx mailing list. To unsubscribe: mailto:exoplatform-unsubscribe@xxxxxxxxxxxxx For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help ObjectWeb mailing lists service home page:
http://www.objectweb.org/
wws








<--  Date Index     <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 2006-2007, OW2 Consortium | contact | webmaster.