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 (asf.osuosl.org: local policy)
Message-ID: <4475F095.3060106@fdar.com>
Date: Thu, 25 May 2006 13:59:49 -0400
From: Ian Roughley <ian@fdar.com>
Reply-To: ian@fdar.com
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Struts Developers List <dev@struts.apache.org>
Subject: Re: DWR/Struts integration: why? (Re: JavaOne Ajax Discussion)
References: <44735B23.4080701@fdar.com>
     <17821.170.201.180.137.1148412700.squirrel@webmail.chiron.lunarpages.com>
     <c6f400460605240646qf72c32eue4666e19e0e2ba31@mail.gmail.com>
     <6821.170.201.180.137.1148480573.squirrel@webmail.chiron.lunarpages.com>
     <c6f400460605240732r1aba5b43l85d7955b71715a0d@mail.gmail.com>
     <35741.170.201.180.137.1148481976.squirrel@webmail.chiron.lunarpages.com>
     <a06230900c09a2660f3e4@192.168.2.102>
     <60803.170.201.180.137.1148486143.squirrel@webmail.chiron.lunarpages.com>
     <a06230904c09a347440c1@192.168.2.110>
    <c6f400460605240932v332e53eaq31b941e5fd208b60@mail.gmail.com>
 <2872.128.146.93.64.1148501118.squirrel@webmail.tracerdigital.com>
 <4475B3CE.4020001@fdar.com> <4475DE20.5010701@tracerdigital.com>
In-Reply-To: <4475DE20.5010701@tracerdigital.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Brian Dittmer wrote:
> Ian Roughley wrote:
>> So, you are saying that your preference would be to include no ajax 
>> integration and leave the framework and let users integrate this as 
>> required - either directly in the HTML or by creating custom themes?
>>
>> /Ian
>>
> No, I definitely would love to see ajax support...I just think it 
> needs to be done right.  Integrating DWR looks like it might get a bit 
> messy.  Taking ideas from DWR, maybe even some of the code and/or the 
> js libs, and building the support directly into SAF2 would be a better 
> option.  That way the look and feel of writing ajax enabled actions is 
> the same as writing other actions.  
But this IS the goal.  The action will be exactly the same as writing 
non-ajax called actions - the data may potentially be populated 
differently.
> This keeps the SAF2 code simple (e.g. you don't need to worry about 
> the glue holding together SAF2 and DWR breaking when a new version of 
> DWR comes out, developers don't need to jump between the DWR codebase 
> and SAF2 codebase) 
We will use DWR under-the-covers to provide the glue - it is mentioned 
here only because it is the dev list and those on the list are most 
likely interested in the enabling technology. The problem found with 
using dojo is that the user is pulled into the dojo source, and way too 
often.  I'm not sure that re-inventing the wheel is a good idea, but we 
will control the integration and upgrades to DWR and work closely with 
Joe to ensure that the are no issues with releases.
> and will be easier for users when configuring their apps (everything 
> is configured in xwork.xml or annotations, no dwr.xml, no servlet 
> extra config in web.xml, etc.).  
This is also the case - my reading the package/action configuration 
there is NO additional DWR configuration on a per action case.  There 
may be an additional web.xml servlet entry, but I think this is acceptable.
> That's just my two cents, I know it's kind of reinventing the wheel 
> but I think it would definitely pay off in the end.
>
> Brian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>

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