[seam-dev] Seam module spotlight series

Shane Bryzak sbryzak at redhat.com
Mon Apr 11 17:53:42 EDT 2011


Brian,  I think you're up next!  Do you think you could have something 
prepared by next weekend?

Also, it would be great if everyone could make an effort to publicise 
these posts by tweeting about it, etc.


On 12/04/11 06:04, Jason Porter wrote:
> I could, haven't yet though.
>
> On Mon, Apr 11, 2011 at 12:26, José Rodolfo Carrijo de Freitas 
> <jose.freitas at softplan.com.br <mailto:jose.freitas at softplan.com.br>> 
> wrote:
>
>     Nice, are you going to post in TSS ? or another big it news website?
>
>     *De:*seam-dev-bounces at lists.jboss.org
>     <mailto:seam-dev-bounces at lists.jboss.org>
>     [mailto:seam-dev-bounces at lists.jboss.org
>     <mailto:seam-dev-bounces at lists.jboss.org>] *Em nome de *Jason Porter
>     *Enviada em:* sábado, 9 de abril de 2011 15:08
>     *Para:* Shane Bryzak
>     *Cc:* seam-dev at lists.jboss.org <mailto:seam-dev at lists.jboss.org>
>     *Assunto:* Re: [seam-dev] Seam module spotlight series
>
>     Attached is the markdown file for the first entry.
>
>     On Fri, Apr 1, 2011 at 20:36, Shane Bryzak <sbryzak at redhat.com
>     <mailto:sbryzak at redhat.com>> wrote:
>
>     Guys,
>
>     I'd like to start up a weekly Seam module spotlight.  Basically, each
>     week I'd like one of you to write up an article that we can publish on
>     in.relation.to <http://in.relation.to> that shows off the best
>     features of your module.
>     Preferably the article would be use-case centric, as opposed to the
>     feature-centric style that we generally write with in the reference
>     documentation.  For example, if I was writing a blog post about the
>     persistence module I would make the point that if you're writing POJO
>     beans to implement your business layer that I would not have
>     transaction
>     support by default, and that is where the transaction features of the
>     persistence module come in.  I'd also explain how it could be
>     useful in
>     other container environments, such as Tomcat or even Java SE.
>
>     This style of writing is more likely to get your readers to a point
>     where they understand why your module is as cool as we say it is, as
>     they can relate its coolness in terms of real life use cases.  Whereas
>     explaining things from a feature point of view might leave some
>     confused
>     as to how they can actually *use* that feature in their own projects.
>
>     Anyway, I'm looking for a brave volunteer to go first.  Ideally
>     we'd get
>     the first spotlight article published by the end of next week (before
>     the 9th) so that should leave enough time to put together an
>     informative
>     article.
>
>     Shane
>     _______________________________________________
>     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
>
>
>
>
>     -- 
>     Jason Porter
>     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>
>
>
>
>
> -- 
> Jason Porter
> 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>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110412/71a984fc/attachment-0001.html 


More information about the seam-dev mailing list