You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@shale.apache.org by Greg Reddin <gr...@gmail.com> on 2009/04/28 16:27:41 UTC

[ANNOUNCE] Apache Shale To Move To the Attic

This is a heads up for the Shale user community that the Shale PMC has
voted to move the project to the Attic. This means that the Shale
developers (more formally its Project Management Committee) have voted
to retire Shale and move the responsibility for its oversight over to
the Attic project.

The MyFaces community has expressed interest in continuing development
of the Shale-Test module and the Shale PMC will work with MyFaces to
migrate this piece of the codebase.. Look for further announcements to
that regard in the near future.

You can read more about the Apache Attic at http://attic.apache.org.

You can follow the progress of the move at

    https://issues.apache.org/jira/browse/ATTIC-2 if you so wish.

On behalf of the Apache Shale PMC, Thanks!

Greg Reddin

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.

Re : [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Adrian Gonzalez <ad...@yahoo.fr>.
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: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Cyril Bouteille <cy...@travelmuse.com>.
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: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Greg Reddin <gr...@gmail.com>.
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: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Cyril Bouteille <cy...@travelmuse.com>.
It provides the missing C in MVC of JSF for GET requests.  :-) A hook in 
the JSP where you can declare which managed bean should be initialized 
for rendering.
Typically high in your JSP, <s:subview id="name-of-your-bean"> would 
call NameOfYourBean.prerender() event. Each page is in control of what 
beans it needs w/o maintaining any additional mapping file or worry 
about URLs or having to recompile java on changes. It provides you also 
with the flexibility to do conditional initialization with verbatims etc.
I'll check your link, thanks. It looks like the hook is the other 
direction with orchestra where the bean maps to JSPs.

Kito Mann wrote:
> Hello Cyril,
>
> The Orchestra ViewController can definitely handle this. See: 
> http://myfaces.apache.org/orchestra/myfaces-orchestra-core/viewController.html.
>
> I'm not too familiar with the <s:subview> tag -- how does that work?
>
> ---
> Kito D. Mann -- Author, JavaServer Faces in Action
> http://twitter.com/kito99  http://twitter.com/jsfcentral
> http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
> +1 203-404-4848 x3
>
>
> On Tue, Apr 28, 2009 at 5:39 PM, Cyril Bouteille <cyril@travelmuse.com 
> <ma...@travelmuse.com>> wrote:
>
>     Hi Kito, by VC feature I meant essentially the prerender event for
>     processing GET requests. I couldn't see such hook from Orchestra's
>     overview. Does it have such a feature?
>     Writing custom PhaseListeners kicking in logic based on URLs gets
>     a bit old... :) Shale's declarative <s:subview id> is great and
>     much cleaner. Anything else like that out there?
>


Re: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Kito Mann <ki...@virtua.com>.
FYI, I wrote a new blog entry about this:
http://blogs.jsfcentral.com/editorsdesk/entry/shale_in_the_attic
---
Kito D. Mann -- Author, JavaServer Faces in Action
http://twitter.com/kito99  http://twitter.com/jsfcentral
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
+1 203-404-4848 x3


On Fri, May 1, 2009 at 2:28 PM, Kito Mann <ki...@virtua.com> wrote:

> Hello Cyril,
>
> The Orchestra ViewController can definitely handle this. See:
> http://myfaces.apache.org/orchestra/myfaces-orchestra-core/viewController.html
> .
>
> I'm not too familiar with the <s:subview> tag -- how does that work?
>
> ---
> Kito D. Mann -- Author, JavaServer Faces in Action
> http://twitter.com/kito99  http://twitter.com/jsfcentral
> http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
> +1 203-404-4848 x3
>
>
>
> On Tue, Apr 28, 2009 at 5:39 PM, Cyril Bouteille <cy...@travelmuse.com>wrote:
>
>> Hi Kito, by VC feature I meant essentially the prerender event for
>> processing GET requests. I couldn't see such hook from Orchestra's overview.
>> Does it have such a feature?
>> Writing custom PhaseListeners kicking in logic based on URLs gets a bit
>> old... :) Shale's declarative <s:subview id> is great and much cleaner.
>> Anything else like that out there?
>>
>>
>> Kito Mann wrote:
>>
>>> On Tue, Apr 28, 2009 at 12:44 PM, Cyril Bouteille <cyril@travelmuse.com
>>> >wrote:
>>>
>>>
>>>
>>>> This is sad news! Can you please recommend alternative projects for
>>>> migration of deployed View-Controller and Remote features? Thanks.
>>>>
>>>>
>>>
>>>
>>> MyFaces Apache Orchestra has a view controller feature as well, and you
>>> with
>>> JSF 1.2 sometimes a PhaseListener associated with a particular view can
>>> yield similar results:
>>>
>>> <f:view beforePhase="#{myBean.beforePhase}"
>>> afterPhase="#{myBean.afterPhase}">
>>> ...
>>> </f:view>
>>>
>>> The remoting features are a different story, though. JSF 2.0 has most of
>>> the
>>> Shale features (excluding the dialog framework and test framework). It
>>> handles most of the use cases Shale Remoting handles (i.e. resource
>>> mangement) but doesn't allow you to call arbitrary methods in the same
>>> manner.
>>>
>>>
>>>
>>>> Greg Reddin wrote:
>>>>
>>>>
>>>>
>>>>> This is a heads up for the Shale user community that the Shale PMC has
>>>>> voted to move the project to the Attic. This means that the Shale
>>>>> developers (more formally its Project Management Committee) have voted
>>>>> to retire Shale and move the responsibility for its oversight over to
>>>>> the Attic project.
>>>>>
>>>>> The MyFaces community has expressed interest in continuing development
>>>>> of the Shale-Test module and the Shale PMC will work with MyFaces to
>>>>> migrate this piece of the codebase.. Look for further announcements to
>>>>> that regard in the near future.
>>>>>
>>>>> You can read more about the Apache Attic at http://attic.apache.org.
>>>>>
>>>>> You can follow the progress of the move at
>>>>>
>>>>>   https://issues.apache.org/jira/browse/ATTIC-2 if you so wish.
>>>>>
>>>>> On behalf of the Apache Shale PMC, Thanks!
>>>>>
>>>>> Greg Reddin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>
>

Re: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Kito Mann <ki...@virtua.com>.
On Fri, May 1, 2009 at 2:51 PM, Cyril Bouteille <cy...@travelmuse.com>wrote:

>  It provides the missing C in MVC of JSF for GET requests. :-) A hook in
> the JSP where you can declare which managed bean should be initialized for
> rendering.
> Typically high in your JSP, <s:subview id="name-of-your-bean"> would call
> NameOfYourBean.prerender() event. Each page is in control of what beans it
> needs w/o maintaining any additional mapping file or worry about URLs. It
> provides you also with the flexibility to do conditional initialization with
> verbatims etc.
> I'll check your link, thanks. It looks like the hook is the other direction
> with orchestra where the bean maps to JSPs.
>

Ah, I see. Nice. FYI, the phaseListener feature in JSF 1.2 is more
fine-grained than I mentioned; you can reference a specific method via a
method expression for beforePhase and afterPhase. See
http://java.sun.com/javaee/javaserverfaces/1.2_MR1/docs/tlddocs/f/view.html.


>
> Kito Mann wrote:
>
> Hello Cyril,
>
> The Orchestra ViewController can definitely handle this. See:
> http://myfaces.apache.org/orchestra/myfaces-orchestra-core/viewController.html
> .
>
> I'm not too familiar with the <s:subview> tag -- how does that work?
>
> ---
> Kito D. Mann -- Author, JavaServer Faces in Action
> http://twitter.com/kito99  http://twitter.com/jsfcentral
> http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
> +1 203-404-4848 x3
>
>
> On Tue, Apr 28, 2009 at 5:39 PM, Cyril Bouteille <cy...@travelmuse.com>wrote:
>
>> Hi Kito, by VC feature I meant essentially the prerender event for
>> processing GET requests. I couldn't see such hook from Orchestra's overview.
>> Does it have such a feature?
>> Writing custom PhaseListeners kicking in logic based on URLs gets a bit
>> old... :) Shale's declarative <s:subview id> is great and much cleaner.
>> Anything else like that out there?
>>
>> Kito Mann wrote:
>>
>>> On Tue, Apr 28, 2009 at 12:44 PM, Cyril Bouteille <cyril@travelmuse.com
>>> >wrote:
>>>
>>>
>>>
>>>> This is sad news! Can you please recommend alternative projects for
>>>> migration of deployed View-Controller and Remote features? Thanks.
>>>>
>>>>
>>>
>>>
>>> MyFaces Apache Orchestra has a view controller feature as well, and you
>>> with
>>> JSF 1.2 sometimes a PhaseListener associated with a particular view can
>>> yield similar results:
>>>
>>> <f:view beforePhase="#{myBean.beforePhase}"
>>> afterPhase="#{myBean.afterPhase}">
>>> ...
>>> </f:view>
>>>
>>> The remoting features are a different story, though. JSF 2.0 has most of
>>> the
>>> Shale features (excluding the dialog framework and test framework). It
>>> handles most of the use cases Shale Remoting handles (i.e. resource
>>> mangement) but doesn't allow you to call arbitrary methods in the same
>>> manner.
>>>
>>>
>>>
>>>> Greg Reddin wrote:
>>>>
>>>>
>>>>
>>>>> This is a heads up for the Shale user community that the Shale PMC has
>>>>> voted to move the project to the Attic. This means that the Shale
>>>>> developers (more formally its Project Management Committee) have voted
>>>>> to retire Shale and move the responsibility for its oversight over to
>>>>> the Attic project.
>>>>>
>>>>> The MyFaces community has expressed interest in continuing development
>>>>> of the Shale-Test module and the Shale PMC will work with MyFaces to
>>>>> migrate this piece of the codebase.. Look for further announcements to
>>>>> that regard in the near future.
>>>>>
>>>>> You can read more about the Apache Attic at http://attic.apache.org.
>>>>>
>>>>> You can follow the progress of the move at
>>>>>
>>>>>   https://issues.apache.org/jira/browse/ATTIC-2 if you so wish.
>>>>>
>>>>> On behalf of the Apache Shale PMC, Thanks!
>>>>>
>>>>> Greg Reddin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>
>
> --
> [image: TravelMuse Logo] Cyril Bouteille
>  VP, Engineering
>
>  TravelMuse, Inc.
>  4410 El Camino Real, Suite 102
> Los Altos, CA 94022
>  Site: http://www.travelmuse.com (RSS <http://www.travelmuse.com/rss>) | Cyril's
> TravelMuse <http://www.travelmuse.com/profile/?mid=429>
> Blogs: Company<http://www.travelmuse.com/community/blogs/travelmuse-company-blog>(
> RSS<http://www.travelmuse.com/community/blogs/travelmuse-company-blog/feeds/posts>)
> | TravelMusings <http://www.travelmuse.com/community/blogs/travel_musings>(
> RSS <http://www.travelmuse.com/community/blogs/travel_musings/feeds/posts>)
> | Photo <http://www.travelmuse.com/community/blogs/photography> (RSS<http://www.travelmuse.com/community/blogs/photography/feeds/posts>
> )
> Facebook: Page<http://www.new.facebook.com/pages/Los-Altos-CA/TravelMuse/12711960515?ref=ts>|
> App <http://apps.facebook.com/travelmuse/>
> ------------------------------
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited. If you received
> this in error, please contact the sender and delete the material from any
> computer.
>

Re: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Kito Mann <ki...@virtua.com>.
Hello Cyril,

The Orchestra ViewController can definitely handle this. See:
http://myfaces.apache.org/orchestra/myfaces-orchestra-core/viewController.html
.

I'm not too familiar with the <s:subview> tag -- how does that work?

---
Kito D. Mann -- Author, JavaServer Faces in Action
http://twitter.com/kito99  http://twitter.com/jsfcentral
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
+1 203-404-4848 x3


On Tue, Apr 28, 2009 at 5:39 PM, Cyril Bouteille <cy...@travelmuse.com>wrote:

> Hi Kito, by VC feature I meant essentially the prerender event for
> processing GET requests. I couldn't see such hook from Orchestra's overview.
> Does it have such a feature?
> Writing custom PhaseListeners kicking in logic based on URLs gets a bit
> old... :) Shale's declarative <s:subview id> is great and much cleaner.
> Anything else like that out there?
>
>
> Kito Mann wrote:
>
>> On Tue, Apr 28, 2009 at 12:44 PM, Cyril Bouteille <cyril@travelmuse.com
>> >wrote:
>>
>>
>>
>>> This is sad news! Can you please recommend alternative projects for
>>> migration of deployed View-Controller and Remote features? Thanks.
>>>
>>>
>>
>>
>> MyFaces Apache Orchestra has a view controller feature as well, and you
>> with
>> JSF 1.2 sometimes a PhaseListener associated with a particular view can
>> yield similar results:
>>
>> <f:view beforePhase="#{myBean.beforePhase}"
>> afterPhase="#{myBean.afterPhase}">
>> ...
>> </f:view>
>>
>> The remoting features are a different story, though. JSF 2.0 has most of
>> the
>> Shale features (excluding the dialog framework and test framework). It
>> handles most of the use cases Shale Remoting handles (i.e. resource
>> mangement) but doesn't allow you to call arbitrary methods in the same
>> manner.
>>
>>
>>
>>> Greg Reddin wrote:
>>>
>>>
>>>
>>>> This is a heads up for the Shale user community that the Shale PMC has
>>>> voted to move the project to the Attic. This means that the Shale
>>>> developers (more formally its Project Management Committee) have voted
>>>> to retire Shale and move the responsibility for its oversight over to
>>>> the Attic project.
>>>>
>>>> The MyFaces community has expressed interest in continuing development
>>>> of the Shale-Test module and the Shale PMC will work with MyFaces to
>>>> migrate this piece of the codebase.. Look for further announcements to
>>>> that regard in the near future.
>>>>
>>>> You can read more about the Apache Attic at http://attic.apache.org.
>>>>
>>>> You can follow the progress of the move at
>>>>
>>>>   https://issues.apache.org/jira/browse/ATTIC-2 if you so wish.
>>>>
>>>> On behalf of the Apache Shale PMC, Thanks!
>>>>
>>>> Greg Reddin
>>>>
>>>>
>>>>
>>>>
>>>
>

Re: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Cyril Bouteille <cy...@travelmuse.com>.
Hi Kito, by VC feature I meant essentially the prerender event for 
processing GET requests. I couldn't see such hook from Orchestra's 
overview. Does it have such a feature?
Writing custom PhaseListeners kicking in logic based on URLs gets a bit 
old... :) Shale's declarative <s:subview id> is great and much cleaner. 
Anything else like that out there?

Kito Mann wrote:
> On Tue, Apr 28, 2009 at 12:44 PM, 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.
>>     
>
>
> MyFaces Apache Orchestra has a view controller feature as well, and you with
> JSF 1.2 sometimes a PhaseListener associated with a particular view can
> yield similar results:
>
> <f:view beforePhase="#{myBean.beforePhase}"
> afterPhase="#{myBean.afterPhase}">
> ...
> </f:view>
>
> The remoting features are a different story, though. JSF 2.0 has most of the
> Shale features (excluding the dialog framework and test framework). It
> handles most of the use cases Shale Remoting handles (i.e. resource
> mangement) but doesn't allow you to call arbitrary methods in the same
> manner.
>
>   
>> Greg Reddin wrote:
>>
>>     
>>> This is a heads up for the Shale user community that the Shale PMC has
>>> voted to move the project to the Attic. This means that the Shale
>>> developers (more formally its Project Management Committee) have voted
>>> to retire Shale and move the responsibility for its oversight over to
>>> the Attic project.
>>>
>>> The MyFaces community has expressed interest in continuing development
>>> of the Shale-Test module and the Shale PMC will work with MyFaces to
>>> migrate this piece of the codebase.. Look for further announcements to
>>> that regard in the near future.
>>>
>>> You can read more about the Apache Attic at http://attic.apache.org.
>>>
>>> You can follow the progress of the move at
>>>
>>>    https://issues.apache.org/jira/browse/ATTIC-2 if you so wish.
>>>
>>> On behalf of the Apache Shale PMC, Thanks!
>>>
>>> Greg Reddin
>>>
>>>
>>>       


Re: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Kito Mann <ki...@virtua.com>.
On Tue, Apr 28, 2009 at 12:44 PM, 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.


MyFaces Apache Orchestra has a view controller feature as well, and you with
JSF 1.2 sometimes a PhaseListener associated with a particular view can
yield similar results:

<f:view beforePhase="#{myBean.beforePhase}"
afterPhase="#{myBean.afterPhase}">
...
</f:view>

The remoting features are a different story, though. JSF 2.0 has most of the
Shale features (excluding the dialog framework and test framework). It
handles most of the use cases Shale Remoting handles (i.e. resource
mangement) but doesn't allow you to call arbitrary methods in the same
manner.

>
>
> Greg Reddin wrote:
>
>> This is a heads up for the Shale user community that the Shale PMC has
>> voted to move the project to the Attic. This means that the Shale
>> developers (more formally its Project Management Committee) have voted
>> to retire Shale and move the responsibility for its oversight over to
>> the Attic project.
>>
>> The MyFaces community has expressed interest in continuing development
>> of the Shale-Test module and the Shale PMC will work with MyFaces to
>> migrate this piece of the codebase.. Look for further announcements to
>> that regard in the near future.
>>
>> You can read more about the Apache Attic at http://attic.apache.org.
>>
>> You can follow the progress of the move at
>>
>>    https://issues.apache.org/jira/browse/ATTIC-2 if you so wish.
>>
>> On behalf of the Apache Shale PMC, Thanks!
>>
>> Greg Reddin
>>
>>
>
> --
> Cyril Bouteille
> VP, Engineering
> TravelMuse, Inc.
>
>

Re: [ANNOUNCE] Apache Shale To Move To the Attic

Posted by Cyril Bouteille <cy...@travelmuse.com>.
This is sad news! Can you please recommend alternative projects for 
migration of deployed View-Controller and Remote features? Thanks.

Greg Reddin wrote:
> This is a heads up for the Shale user community that the Shale PMC has
> voted to move the project to the Attic. This means that the Shale
> developers (more formally its Project Management Committee) have voted
> to retire Shale and move the responsibility for its oversight over to
> the Attic project.
>
> The MyFaces community has expressed interest in continuing development
> of the Shale-Test module and the Shale PMC will work with MyFaces to
> migrate this piece of the codebase.. Look for further announcements to
> that regard in the near future.
>
> You can read more about the Apache Attic at http://attic.apache.org.
>
> You can follow the progress of the move at
>
>     https://issues.apache.org/jira/browse/ATTIC-2 if you so wish.
>
> On behalf of the Apache Shale PMC, Thanks!
>
> Greg Reddin
>   

-- 
 Cyril Bouteille
VP, Engineering
TravelMuse, Inc.