[seam-dev] Going forward

Mon Jan 9 15:33:23 EST 2012

We're toying with the idea of a 3.2.0 release, which could be done in a 
couple of months and would mostly include bug fixes and other quality 
improvements.  I agree, DeltaSpike will probably be quite a few months 
before any form of complete release is done, and I'm sure that many of 
the modules will require some refactoring as well since deltaspike-core 
isn't a 1:1 port of Solder.

On 09/01/12 23:04, Antoine Sabot-Durand wrote:
> Hello,
>
> Right now Delta Spike project is dealing with very low level core 
> aspect of CDI extension (Solder and CODI core merge mainly). I don't 
> know when we'll have a real version of Delta Spike with all the Seam 
> modules.
>
>
> I've done a lot of dev on Seam Social lately. Unfortunately it was not 
> stable enough to be integrated in 3.1.0.FINAL. So I'm supporting the 
> idea of having a 3.1.1 or even 3.2.0 for me to add my new code to make 
> it available in the coming month and not at the end of the year.
>
> regards,
>
> Antoine SABOT-DURAND
> ---------------------------------------
> Blog : http://www.next-presso.fr
> Twitter ; http://twitter.com/antoine_sd
> LinkedIn : http://fr.linkedin.com/in/antoinesabotdurand
> 06 08 55 34 26
>
>
>
>
> Le 5 janv. 2012 à 09:57, Adrian Gonzalez a écrit :
>
>> Hello Jason,
>>
>> Just my opinion, and it's not worth much (I'm no Seam dev, and I'm 
>> not even using Seam 3 for now - only Seam 2).
>>
>> Anyway, samples are a really high priority : CDI and JSF 2 are quite 
>> tricky - as where Seam 2 and JSF 1.2 ;)
>> I've googled a bit on the internet to find a good JSF/CDI crud 
>> sample, you confbuzz sample was the most promising.
>>
>> I believe starting with really simple crud samples (confbuzz), and 
>> gradually augmenting them is the way to go.
>>
>> And with the pre-requisites :
>>  * stateless is a must - so stateless whenever it's possible.
>>  * GET for readonly and POST for modifications.
>>  *  striving for simplicity
>>
>> Some sample ideas could be :
>> 1 - Simple CRUD : confbuzz.
>> 2 - CRUD with search criteria for list page.
>>     reworking @Inject in Query bean.
>> 3 - CRUD with edit page (create / update).
>>     Firt step in LRC ?
>>     Without a postback to go from list to edit page ?
>> 4 - CRUD with pagination
>> 5 - CRUD with sort
>> 6 - CRUD with delete action in list page
>>     Postback and LRC in list page... Impact on LRC delimitation in 
>> edit page...
>> 7 - CRUD with multiple select in list page.
>> 8 - CRUD with RF dataScroller db pagination / sort / filter sample ?
>>
>> And documenting every bit of it. This would be like another christmas 
>> gift ;)
>>
>> For the rest, I wonder if you shouldn't only correct blocker/major 
>> issues in Seam 3 and direct all your efforts into DeltaSpike.
>>
>> Have a nice day !
>>
>> ------------------------------------------------------------------------
>> *De :* Jason Porter <lightguard.jp at gmail.com 
>> <mailto:lightguard.jp at gmail.com>>
>> *À :* Seam Mailing List <seam-dev at lists.jboss.org 
>> <mailto:seam-dev at lists.jboss.org>>
>> *Envoyé le :* Mercredi 4 Janvier 2012 23h48
>> *Objet :* [seam-dev] Going forward
>>
>> Part of this mail is going to be open thoughts from me, so if you 
>> don't agree, that's fine, it's really open for discussion. I'm 
>> wondering what everyone wants to focus on for Seam 3.2.0. Obviously 
>> we need to support those currently running on Seam 3, and we'll also 
>> continue to work on DeltaSpike. I think eventually we will cut a Seam 
>> 3 release that's based on DeltaSpike Core instead of Solder, which 
>> should make things much easier for people when migration time comes, 
>> or if they want to use MyFaces CODI extensions as well.
>>
>> We currently have 369 issues against Seam 3. I'm not sure how many we 
>> squashed during the Seam 3.1 cycle, but I know it was quite a bit, 
>> maybe 150+. I'd like to hear from the community as well as the module 
>> leads what they feel like we should be working on for this next Seam 
>> development cycle.
>>
>> I know we have said we were going to focus on documentation and 
>> examples, and I still believe that needs to happen. Obviously we need 
>> to do some other dev as well. Maybe a good example though will drive 
>> some of that development. Right now the current examples are very 
>> weak and typically only focus on one or two modules. I have my 
>> Confbuzz example [1] which is up to date with Seam 3.1.0.Final, but 
>> is really lacking features. It could be a good place to start if 
>> nothing else.
>>
>> Does anyone else have any thoughts or a direction they'd like to see 
>> things move?
>>
>> [1] https://github.com/seam/seam-example-confbuzz
>> -- 
>> Jason Porter
>> http://lightguard-jp.blogspot.com <http://lightguard-jp.blogspot.com/>
>> http://twitter.com/lightguardjp
>>
>> Software Engineer
>> Open Source Advocate
>> Author of Seam Catch - Next Generation Java Exception Handling
>>
>> PGP key id: 926CCFF5
>> PGP key available at: keyserver.net <http://keyserver.net/>, 
>> pgp.mit.edu <http://pgp.mit.edu/>
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org <mailto:seam-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org <mailto:seam-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20120110/cf84f1b4/attachment.html 