On Fri, Aug 22, 2008 at 12:47 PM, Gabriel Belingueres
<[EMAIL PROTECTED]> wrote:
> The scenario where S2 would become a JCP approved JSR is pretty much scary 
> IMO:
>
> 1) It means it exists a Reference Implementation of S2, or that S2 is
> build upon a RI of something else.
> 2) Any vendor can come up with their own flavors and extensions of the
> JSR, which brings more FUD than solutions.
>
> Instead, I'd like to see S2 building functionality upon itself more like:
>
> 1) the "flow" concept (like Spring WF)
> 2) improving validation framework (validating against JSR 303 compliant 
> POJOs)i
>
> or other things that are not framework specific but useful, like
> having a repository of themes for changing the L&F of the apps. Think
> having to develop a new app, your customer pick a design from
> www.oswd.org and you have to create a new theme for that particular
> design. If you could just find that theme already built THAT would be
> a time saver.

I don't disagree, but this is an interesting read along a similar topic:

http://adactio.com/journal/1498

Matt

>
> 2008/8/22, Wendy Smoak <[EMAIL PROTECTED]>:
>> On Thu, Aug 21, 2008 at 11:31 PM, Frans Thamura <[EMAIL PROTECTED]> wrote:
>>
>> > is it possible that S2 become part of JCP?
>> > java server action framework
>> > right now only component framework there
>> > any idea?
>>
>> While I cringe every time I hear someone say that they chose JSF
>> because "It's the standard" there's no way I would want to see Struts
>> 2 attempt the JCP.  It wouldn't be Struts 2 by the time you came out
>> the other end, and, well... what Martin said. ;)
>>
>> --
>> Wendy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to