Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <49A03B30.2010306@it-neering.net>
Date: Sat, 21 Feb 2009 18:34:40 +0100
From: Rene Gielen <gielen@it-neering.net>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Struts Developers List <dev@struts.apache.org>
Subject: Re: moving JSON result type into core
References: <e34c19110902190803o1c5777ddu7dfb7698f393c0a3@mail.gmail.com>
In-Reply-To: <e34c19110902190803o1c5777ddu7dfb7698f393c0a3@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

+1 - I love the JSON plugin :)

Wes Wannemacher schrieb:
> Does anyone have any objection to us moving the JSON result type into
> core? It seems to me that it is a good candidate for a core result
> type and I think it would also show that we are striving to provide
> AJAX support. The main motivation for me is that if I wanted to begin
> work on another AJAX plugin, there is this feeling that plugins
> shouldn't depend on each other, yet the JSON plugin seems to be an
> important piece of supporting just about any AJAX/JS framework
> (JQuery, YUI, etc.). Plus, if we make it a part of core, then if
> struts2/xwork changes potentially break compatibility with the JSON
> result type, we'll know, rather than depending on Musachy, Jeromy,
> James or myself (committers on the JSON plugin) to find out the hard
> way.
> 
> So, does anyone object, and why?
> 
> -Wes
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org