Re: Dijit Calendar usage in Struts 1.3
On Sun, Dec 28, 2008 at 6:43 PM, Frank W. Zammetti fzli...@omnytex.comwrote: Ilan wrote: NB: http://docs.dojocampus.org/dijit/form/DateTextBox is what looks suitable. Again. I am just asking if there are any recommended practices when adding a Digit widgit to a Struts 1.3 jsp/view There really isn't... there's conceptually no difference between adding Dojo or anything else to a Struts 1.x application and adding it to a non-Struts application... S1 has no inherent knowledge of GUI widgets so it's all up to you. There aren't really even any recognized best-practices (yet) around RIA development in general, although many of us can point out things you probably should or shouldn't do when we see it. Well this is how I added the calendar widgit. bean:define id=deliveryDate name=transactionCaptureForm property=deliveryDate/ input class=urEdf2TxtEnblDojoDate type=text name=deliveryDate id=deliveryDate value=%= deliveryDate % dojoType=dijit.form.DateTextBox required=true / So.. is there something wrong with doing it this way? -- Ilan
Re: Hi.. some advice please.
2008/12/29 Paweł Wielgus poulw...@gmail.com Hi Ilan, i'm using struts 1.x for about 6 years inside 3 big web apps, one of those is public and have no problems with performance. All of them are constantly developed and gain new functionalities all the time. S1 has anything that i need, but s2 makes it easier - that's the main difference for me. Thats good to know. Thanks for the confirmation that Struts 1.3 is not obsolete and provides all that I need with good performance. As for ajax i don't undersand the need for dojo plugin, Well actually my primary concern (before AJAX) is a solid internationalised datepicker... And Dojo seems to provide a very nice one in its Dijit namespace. What do you use for a datepicker? Thanks, Ilan Best greetings, Paweł Wielgus.
Dijit Calendar usage in Struts 1.3
On Sat, Dec 27, 2008 at 10:01 PM, Martin Gainty mgai...@hotmail.com wrote: Wes is right on Struts support for legacy 1.x development 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 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 I looked at the AjaxParts Calendar and the Dojo Calendar and the Dojo Calendar looks signficantly better. Are there any best practices to follow when adding a Dijit Widigt to a Struts 1.3 jsp/view ? Thanks, Ilan
Re: Dijit Calendar usage in Struts 1.3
On Sun, Dec 28, 2008 at 11:13 AM, Ilan ilan.pille...@gmail.com wrote: On Sat, Dec 27, 2008 at 10:01 PM, Martin Gainty mgai...@hotmail.comwrote: Wes is right on Struts support for legacy 1.x development 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 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 I looked at the AjaxParts Calendar and the Dojo Calendar and the Dojo Calendar looks signficantly better. Are there any best practices to follow when adding a Dijit Widigt to a Struts 1.3 jsp/view ? NB: http://docs.dojocampus.org/dijit/form/DateTextBox is what looks suitable. Again. I am just asking if there are any recommended practices when adding a Digit widgit to a Struts 1.3 jsp/view Thanks, Ilan
Hi.. some advice please.
Hi, I am working quickly against the grain at the enterprise I work at. We are using SAP's WebDynpro technology for the public internet facing site through which we use to work with our customers and enable B2B between our customers. It connects directly via internal web service calls to SAP R3, Siebel, BW etc etc that wrap facade enterprise beans. We have run into significant performance issues for certain highly used areas in the site and I am working on an alternative using Struts 1.3. I have some momentum and have been given the green light to design and implement one aspect of the current site. As always there are some naysayers that are calling for JSF, Spring etc. But at the moment I have the momentum. I have several challenges/constraints. (1) The SAP J2EE engine currently in production (for a while still) implements the servlet 2.3 and the jsp 1.2 specifcation - but we are using the 1.4_2 jdk. (2) I have very limited time so do not have time to evaluate every option. (3) I have already done 70% of the work and have my authentication, actions, actionforms etc all working 100% correctly. Struts 2 is not a viable option due to (1) above. I only glanced at JSF etc; but I believe from what I have read that Struts 1.3 is flexible, extendible. I understand that Struts 1.3 is still the most popular MVC framework and I am assuming this is because it provides everything one could need to produce a high performance J2EE web site and that this is proven. Are these assumptions correct? I have one naysayer claiming that Struts 1.3 is obsolete. I provided the IT Director with the current sites using Struts from the wiki and the article from FAQ saying its not obsolete. 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! Thanks, Ilan
Re: Hi.. some advice please.
Yeah.. The reason is because we currently are running the Netweaver SAP 7.0 J2EE and R3 release. To update the entire environment of many clustered servers etc etc is a massive undertaking and the Powers-That-Be keep talking about when they are going to do and shifting the move further down the horizon. If I was making the calls it would be #1 priority. But, as of yet, I don't yet have enough influence to impose my opinion. I am hoping it will happen by the end of 2009 but I am not holding my breath. -- Ilan On Sat, Dec 27, 2008 at 9:15 PM, James Carr james.r.c...@gmail.com wrote: Why are you still using java 1.4??? I mean really? On Sat, Dec 27, 2008 at 1:11 PM, Ilan ilan.pille...@gmail.com wrote: Hi, I am working quickly against the grain at the enterprise I work at. We are using SAP's WebDynpro technology for the public internet facing site through which we use to work with our customers and enable B2B between our customers. It connects directly via internal web service calls to SAP R3, Siebel, BW etc etc that wrap facade enterprise beans. We have run into significant performance issues for certain highly used areas in the site and I am working on an alternative using Struts 1.3. I have some momentum and have been given the green light to design and implement one aspect of the current site. As always there are some naysayers that are calling for JSF, Spring etc. But at the moment I have the momentum. I have several challenges/constraints. (1) The SAP J2EE engine currently in production (for a while still) implements the servlet 2.3 and the jsp 1.2 specifcation - but we are using the 1.4_2 jdk. (2) I have very limited time so do not have time to evaluate every option. (3) I have already done 70% of the work and have my authentication, actions, actionforms etc all working 100% correctly. Struts 2 is not a viable option due to (1) above. I only glanced at JSF etc; but I believe from what I have read that Struts 1.3 is flexible, extendible. I understand that Struts 1.3 is still the most popular MVC framework and I am assuming this is because it provides everything one could need to produce a high performance J2EE web site and that this is proven. Are these assumptions correct? I have one naysayer claiming that Struts 1.3 is obsolete. I provided the IT Director with the current sites using Struts from the wiki and the article from FAQ saying its not obsolete. 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! Thanks, Ilan - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: Hi.. some advice please.
On Sat, Dec 27, 2008 at 9:21 PM, Wes Wannemacher w...@wantii.com wrote: 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. Hi.. I did point that out. I also see the next maintenance release is for 25th January. I have saved the JIRA link and I think that does counter this guy. -- Ilan -Wes - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: Hi.. some advice please.
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
