You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@shale.apache.org by Adrian Gonzalez <ad...@yahoo.fr> on 2009/04/29 00:07:12 UTC
Re : [ANNOUNCE] Apache Shale To Move To the Attic
You should take a serious look at seam (at least read all the documentation if you need to change your codebase) before taking another framework on top of jsf.
http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/
The framework is very powerfull (but complicated, and you should do perf. benchmarks).
To use it with facelets / ajax4jsf / richfaces.
conversation management
get functionnality and page actions
remoting (proprietary protocol)
powerfull navigation with exception handling
good jpa (urgh... hibernate) integration
validation with Hibernate Validator (this is a goog one !)
security (authentication / authz)
spring integration if need be
and much more...
________________________________
De : Cyril Bouteille <cy...@travelmuse.com>
À : Greg Reddin <gr...@gmail.com>
Cc : "user@shale.apache.org" <us...@shale.apache.org>
Envoyé le : Mardi, 28 Avril 2009, 23h31mn 13s
Objet : Re: [ANNOUNCE] Apache Shale To Move To the Attic
Hi Greg, what features of Seam do you feel match Shale's VC or Remoting?
I also understand ajax4jsf to be returning only HTML fragments per architecture. We've a lot of Shale Remoting function returning JSON and I'm not sure how we would do that in RichFaces...
We do have a couple of outstanding bugs with Shale and unfortunately not much time to contribute :-( , so folks like me will have to migrate to some other framework that's still actively maintained.
Greg Reddin wrote:
> On Tue, Apr 28, 2009 at 11:44 AM, Cyril Bouteille <cy...@travelmuse.com> wrote:
>
>> This is sad news! Can you please recommend alternative projects for
>> migration of deployed View-Controller and Remote features? Thanks.
>>
>
> Just my viewpoint: probably your best bet would be to migrate to Seam
> and/or ajax4jsf.
>
> But if you just don't feel like leaving Shale... This doesn't mean the
> code is going to disappear. The code will be housed in the Apache
> Attic svn. I'm not sure about existing releases, but I doubt they will
> be removed from Maven repos, etc. If you feel like the code needs
> further improvement feel free to start it back up at Google Code or
> elsewhere. The only caveat to forking is that ASF still holds the
> Apache Shale trademark so you'd have to come up with a different name.
>
> Thanks,
> Greg
>
Re : Re : [ANNOUNCE] Apache Shale To Move To the Attic
Posted by Adrian Gonzalez <ad...@yahoo.fr>.
I'm not used to Shale dialogs.
Perhaps using jpdl ? (and not jbpm !) (jpdl = page flows)
http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/jbpm.html
We've used jpdl once 1.5 year ago, there where issues concerning exception handling (not done at pages.xml).
But it has surely be resolved since.
________________________________
De : "mario.buonopane@accenture.com" <ma...@accenture.com>
À : user@shale.apache.org
Envoyé le : Mercredi, 29 Avril 2009, 9h32mn 10s
Objet : RE: Re : [ANNOUNCE] Apache Shale To Move To the Attic
Hi, how can migrate Shale dialogs in seam?
Mario
-----Original Message-----
From: Adrian Gonzalez [mailto:adr_gonzalez@yahoo.fr]
Sent: 29 aprile 2009 00.07
To: user@shale.apache.org
Subject: Re : [ANNOUNCE] Apache Shale To Move To the Attic
You should take a serious look at seam (at least read all the documentation if you need to change your codebase) before taking another framework on top of jsf.
http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/
The framework is very powerfull (but complicated, and you should do perf. benchmarks).
To use it with facelets / ajax4jsf / richfaces.
conversation management
get functionnality and page actions
remoting (proprietary protocol)
powerfull navigation with exception handling
good jpa (urgh... hibernate) integration
validation with Hibernate Validator (this is a goog one !)
security (authentication / authz)
spring integration if need be
and much more...
________________________________
De : Cyril Bouteille <cy...@travelmuse.com>
À : Greg Reddin <gr...@gmail.com>
Cc : "user@shale.apache.org" <us...@shale.apache.org>
Envoyé le : Mardi, 28 Avril 2009, 23h31mn 13s
Objet : Re: [ANNOUNCE] Apache Shale To Move To the Attic
Hi Greg, what features of Seam do you feel match Shale's VC or Remoting?
I also understand ajax4jsf to be returning only HTML fragments per architecture. We've a lot of Shale Remoting function returning JSON and I'm not sure how we would do that in RichFaces...
We do have a couple of outstanding bugs with Shale and unfortunately not much time to contribute :-( , so folks like me will have to migrate to some other framework that's still actively maintained.
Greg Reddin wrote:
> On Tue, Apr 28, 2009 at 11:44 AM, Cyril Bouteille <cy...@travelmuse.com> wrote:
>
>> This is sad news! Can you please recommend alternative projects for
>> migration of deployed View-Controller and Remote features? Thanks.
>>
>
> Just my viewpoint: probably your best bet would be to migrate to Seam
> and/or ajax4jsf.
>
> But if you just don't feel like leaving Shale... This doesn't mean the
> code is going to disappear. The code will be housed in the Apache
> Attic svn. I'm not sure about existing releases, but I doubt they will
> be removed from Maven repos, etc. If you feel like the code needs
> further improvement feel free to start it back up at Google Code or
> elsewhere. The only caveat to forking is that ASF still holds the
> Apache Shale trademark so you'd have to come up with a different name.
>
> Thanks,
> Greg
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
RE: Re : [ANNOUNCE] Apache Shale To Move To the Attic
Posted by ma...@accenture.com.
Hi, how can migrate Shale dialogs in seam?
Mario
-----Original Message-----
From: Adrian Gonzalez [mailto:adr_gonzalez@yahoo.fr]
Sent: 29 aprile 2009 00.07
To: user@shale.apache.org
Subject: Re : [ANNOUNCE] Apache Shale To Move To the Attic
You should take a serious look at seam (at least read all the documentation if you need to change your codebase) before taking another framework on top of jsf.
http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/
The framework is very powerfull (but complicated, and you should do perf. benchmarks).
To use it with facelets / ajax4jsf / richfaces.
conversation management
get functionnality and page actions
remoting (proprietary protocol)
powerfull navigation with exception handling
good jpa (urgh... hibernate) integration
validation with Hibernate Validator (this is a goog one !)
security (authentication / authz)
spring integration if need be
and much more...
________________________________
De : Cyril Bouteille <cy...@travelmuse.com>
À : Greg Reddin <gr...@gmail.com>
Cc : "user@shale.apache.org" <us...@shale.apache.org>
Envoyé le : Mardi, 28 Avril 2009, 23h31mn 13s
Objet : Re: [ANNOUNCE] Apache Shale To Move To the Attic
Hi Greg, what features of Seam do you feel match Shale's VC or Remoting?
I also understand ajax4jsf to be returning only HTML fragments per architecture. We've a lot of Shale Remoting function returning JSON and I'm not sure how we would do that in RichFaces...
We do have a couple of outstanding bugs with Shale and unfortunately not much time to contribute :-( , so folks like me will have to migrate to some other framework that's still actively maintained.
Greg Reddin wrote:
> On Tue, Apr 28, 2009 at 11:44 AM, Cyril Bouteille <cy...@travelmuse.com> wrote:
>
>> This is sad news! Can you please recommend alternative projects for
>> migration of deployed View-Controller and Remote features? Thanks.
>>
>
> Just my viewpoint: probably your best bet would be to migrate to Seam
> and/or ajax4jsf.
>
> But if you just don't feel like leaving Shale... This doesn't mean the
> code is going to disappear. The code will be housed in the Apache
> Attic svn. I'm not sure about existing releases, but I doubt they will
> be removed from Maven repos, etc. If you feel like the code needs
> further improvement feel free to start it back up at Google Code or
> elsewhere. The only caveat to forking is that ASF still holds the
> Apache Shale trademark so you'd have to come up with a different name.
>
> Thanks,
> Greg
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.