Yup, sounds like a good plan.
Let's get this up on the wiki and then start disecting?
On 21 Nov 2009, at 18:16, Gavin King wrote:
Frankly, a lot of the examples are using approaches that we now
probably no longer recommend. I think rather than just porting all the
examples across, we should redesign some of them, using what we now
think are better approaches.
On Sat, Nov 21, 2009 at 4:06 AM, Pete Muir <pmuir(a)bleepbleep.org.uk> wrote:
> In general, we have too many copies of the booking example and these need to be
merged or removed.
>
> Again, let's make this into a wiki page, and try to rationalize a bit further!
>
> We do need an overall lead on examples, anyone want to take that?
>
> Seam 3 examples
>
> * Blog has become Permalink in Weld
> * Booking (needs overhaul and all booking examples need merging)
> * Contact list (Seam application framework)
> * Numberguess (Drools, should be different to jBPM example)
> * DVDStore (jBPM processes and pageflow)
> * Excel
> * Booking (Groovy)
> * Guicebar
> * Booking (Hibernate)
> * Booking (ICEFaces)
> * IText
> * Booking (JEE5)
> * Booking (JPA)
> * Mail
> * Messages (JSP, remove)
> * Booking (Metawidget)
> * DVDStore (Metawidget)
> * Booking (Nested)
> * Numberguess (Pageflow)
> * OpenId
> * Portal (see portal project)
> * Seampay (Quartz)
> * Seampay (EJB Async)
> * Registration (trivial example for tutorial, so keep)
> * Remoting/*
> * Seambay (JAX-RS)
> * RSS
> * Seambay (old WS, replaced by JAX-RS support, remove)
> * Seamdiscs (Trinidad integration, CRUD, maybe remove)
> * Seamspace (security)
> * Booking (Spring)
> * Tasks (JAX-RS)
> * Todo (jBPM process)
> * UI (testing example, remove)
> * Booking (Wicket)
> * Wiki
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/seam-dev
>
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org