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 > >
