RE: [exoplatform] standard or exo portlet

["Kito D. Mann" <kmann@xxxxxxxxxx>]

Luca,

 

What sort of  problems did you have with messages?

 

Also, would you be interested in participating in JSF Central's "In the Trenches" series (http://www.jsfcentral.com/trenches). A suite of 25 JSF portlets would be a great story...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
phone: +1 203-653-2989
fax: +1 203-653-2988

* Sign up for the JSF Central newsletter! http://oi.vresp.com/?fid=ac048d0e17 *

 

---

From: Luca Bernardini [mailto:luca.bernardini@xxxxxxxxxx]
Sent: Monday, March 26, 2007 3:50 AM
To: kmann@xxxxxxxxxx
Cc: brice.revenant@xxxxxxxx; exoplatform@xxxxxxxxxxxxx; 'alamut'
Subject: Re: [exoplatform] standard or exo portlet

We developed about 25 portlet of our "Statim" a B2B e-commerce, using JSF. I think it is a good solution for stay "open".
There are 2 little problems with jsf-messages but afeter patching them, all the rest runs well.

if you want to take a look...
http://www.digisol.it/statimdemo
Luca Bernardini





Kito D. Mann wrote:

If he's targeting eXo 3.x/portal 2.0, I think it'd make sense to use JSF as a web app framework for building portlets (without the eXo extensions).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
* Sign up for the JSF Central newsletter! http://oi.vresp.com/?fid=ac048d0e17 *

 

From: brice.revenant@xxxxxxxx [mailto:brice.revenant@xxxxxxxx]
Sent: Friday, March 23, 2007 7:45 PM
To: exoplatform@xxxxxxxxxxxxx
Cc: alamut
Subject: Re: [exoplatform] standard or exo portlet

Hi,

 

This JSF-based framework is aimed at developing eXo-provided Portlets. It is subject to change in subsequent releases. Reusing it in your own projects means that you run the risk of having to rewrite some code one day.

 

For this reason, this seems preferrable to write pure JSR 168 Portlets. This will make easy the future migration toward the Enterprise WebOS.

 

HTH
-Brice.

--
Brice REVENANT
Bull, Architect of an Open World TM 
phone: +33 (0)4 76 29 74 22
http://www.bull.com

This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

-----alamut <h.siahmed@xxxxxxxxx> wrote: -----

To: exoplatform@xxxxxxxxxxxxx
From: alamut <h.siahmed@xxxxxxxxx>
Date: 22/03/2007 02:45PM
Subject: [exoplatform] standard or exo portlet


Hi my friends, i am a novice in working with portals.
I started by creating simple portlets and am trying now to export such work
to Exo.
According to Exo examples, all the portled extends UIPortlet, they use the
framlework ressources by a different way then the standard one.
i would like to have your viewpoint. In other word, should we follow the Exo
paradigm during developping process or developing standard portlet as
usually.
Thanx in advance.
--
View this message in context: http://www.nabble.com/standard-or-exo-portlet-tf3447565.html#a9614878
Sent from the eXo Platform mailing list archive at Nabble.com.

--
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