On Sat, Dec 27, 2008 at 10:01 PM, Martin Gainty <mgai...@hotmail.com> wrote:
> If you're thinking your UI layer will need Ajax controls (or any type of > asynchronous behaviour) > you will need to adopt and implement Struts 2.x so you can define and > implement Dojo Ajax Unfotunately I do not have the option to use Struts 2.x as our production environment implements the 2.3 servlet specifcation and 1.2 JSP specification and this will be the case for at least the majority of 2009. I need to have a production ready implementation of the one area of our current site using a Web MVC framework by Jan 16 2009. > controls generally supported by declaration of head tag with theme > attribute set to ajax as in this example > <s:head theme="ajax"> > Underneath the UI layer you will need to match Struts (version 2) > Dojo-plugin to Dojo (v 1.2) and then Dojo support for the ActiveX control > performing the actual transport work IE uses XMLHttpRequest (version 2.x) > http://api.dojotoolkit.org/jsdoc/dojo/1.2/dojo._xhrObj/.switch/1.1.1 > Hmmm... We do not use ActiveX in our systems as many of customers (behind corporate internet access) disallow ActiveX. Is ActiveX a requirement for Strut 2 and Dojo interaction on IE? IE6 sp2 is the official supported platform for the customer. Again this is not a decision under my control. I suspect its still used in corporates more than IE7 is. Also when looking at performance documentation with Dojo it seems some custom building is necessary in order to achieve performance? > As far as MVC there are 3 implementations that I currently know of > 1)Spring MVC where everything in the bottom-most entities are createed > using BeanFactories > http://static.springframework.org/spring/docs/2.0.x/reference/mvc.html > memory (Spring can gobble near and far heap at an astounding rate) > > I/O (how many config files can be read in and tracked by Factory) > > CustomDispatcher calls Spring classes first then others second (FIlters and > Servlets) > Does this mean that Spring has a lower performance in terms of speed than Struts 1.3? Performance is the highest priority (although it must be maintainable). If Spring performs worse that Struts 1.3 then ugg. And the heap eating sounds worrying too since we get large traffic. > > 2)Rails which means you have to download, build Rails binary onto Apache > 2.x which opens up a whole new set of resource challenges when so many of > these processes are called..More info on RubyOnRails available at > http://rubyonrails.org > Although we do use Apache in our QA and Dev environments we use a Foundry hardware solution on Production. I am assuming this would mean even more resource challenges? > > 3)Struts is actually the lightest implementation with the fewest parts > earliest implementations actually did'nt define their own TagLibs defaulting > to using standard JSTL and a very light implementation to pass thru > back-end-process requests to previously mapped Action configurations defined > in struts-config.xml > http://wiki.apache.org/struts/AjaxStruts > Well sounds like what I have got 70% running already. And the performance improvements over Web Dynpro has been dramatic! Lightest implementation sounds to me like something I could hug. I am looking for light, flexible, extendible and maintable. Thanks for your input! -- Ilan > HTH > Martin > ______________________________________________ > Disclaimer and confidentiality note > Everything in this e-mail and any attachments relates to the official > business of Sender. This transmission is of a confidential nature and Sender > does not endorse distribution to any party other than intended recipient. > Sender does not necessarily endorse content contained within this > transmission. > > > > > > Subject: Re: Hi.. some advice please. > > From: w...@wantii.com > > To: user@struts.apache.org > > Date: Sat, 27 Dec 2008 14:21:02 -0500 > > > > On Sat, 2008-12-27 at 21:11 +0200, Ilan wrote: > > [snip] > > > My 2 questions are as follows: > > > (1) Is JavaWebParts the best option for the use of a datepicker? (This > is my > > > last design decision and then I just have slog.) > > > (2) Is JavaWebParts the best option for AJAX with 1.3? > > > (3) Does anyone have good links saying why Struts 1.3 is a good > decision for > > > a MVC architecture that is high performing and maintable and > > > flexible/extendible enough to be a suitable for a production system > that > > > will be around for long time. > > > > > > I would appreciate any thoughts, comments or answers! > > > > > > I don't know about the specifics of datepickers, but as to struts 1.x > > obsolescence, I would point out that 1.x is actively developed. In fact, > > there was a new release on 12/04/08. Many of us developers work on the > > 2.x series, but there are quite a few guys (Paul, Nils-Helge, Niall, > > James, etc.) that work to continue supporting the many 1.x users. > > > > -Wes > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > > For additional commands, e-mail: user-h...@struts.apache.org > > > > _________________________________________________________________ > It's the same Hotmail(R). If by "same" you mean up to 70% faster. > > http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_broad1_122008 >
