On Wed, Jan 5, 2011 at 06:43, Jozef Hartinger <jharting(a)redhat.com> wrote:
For Seam REST there are several minor code changes planned. Besides,
there is some work to be done docs+examples but this can be postponed.
The most challenging part is implementing headless facelets rendering
which may or may not get into the next release based on how it goes.
Otherwise, Jan 21 seems OK from my point of view.
Btw, talking about facelets, isn't anyone planning on implementing the
same thing? I mean backporting the Renderer component from Seam 2. This
component allows facelets to be rendered outside of the JSF lifecycle.
Certainly, we’ll need this component outside of REST - at least for
mail, excel and pdf modules. Since I am not a JSF expert, any help in
this area would be appreciated.
J.
Jozef, this has been talked about in the past and we never found
anyone to take it, nor have we found a good way of doing this. JSF is
not very friendly at all when it comes to starting w/o the normal
ServletContextListener. Another option would be work that Cody is
doing in Mail to support Velocity / FreeMarker, or even the Seam
Render project that Lincoln has.
On 01/04/2011 12:07 PM, Shane Bryzak wrote:
> I hope everyone had a restful end of year break. Now that we're into
> the new year I'd like to make it a top priority to prepare a beta
> release for Seam 3. To do this, we're first going to need at least a
> beta release for every single Seam module - the good news though for
> module leads, is if your module is already at Beta1 or higher, you don't
> need to do anything ;-)
>
> What I'd like to do is start off with a simple status check from each of
> the module leads for each of the modules that are still in alpha. To
> the best of my knowledge this includes the following modules:
>
> Seam Catch (Alpha3)
> Seam International (Alpha 3)
> Seam JMS (Alpha 1)
> Seam REST (Alpha 2)
> Seam Security (Alpha2)
> Seam Servlet (Alpha 2)
>
> If your module is in the above list, can you please describe what is
> still required to be done to get your module to a beta release, and
> roughly how long you think it will take. I'll start with the security
> module:
>
> Currently the security module is in good shape, however I'm expecting to
> make some further changes to the authenticator API to allow better
> integration between the external authentication module and the core
> security beans, such as Identity. I estimate that this work will take
> approximately 2 weeks (so should be roughly completed by the 18th of
> Jan) after which I'll release beta 1.
>
> Once we have an update from all module leads then we can start setting
> target release dates. Ideally I would like to get the beta released
> before the end of this month, ideally around the 21st.
>
> Thanks,
> Shane
>
>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
seam-dev(a)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
PGP key id: 926CCFF5
PGP key available at:
keyserver.net,
pgp.mit.edu