> -----Original Message----- > From: Joe Germuska [mailto:[EMAIL PROTECTED] ==////== > > > By no means do I consider myself the authority to answer these, but > here are some responses based on my understanding and my interest in > how things go. In summary, really a lot of these questions are > premature based on the likely pace of development, and as always, the > community is going to set the direction based on who steps up to > participate in the coding. That said, here are point-by-points... >
I agree some of these questions are premature. I felt the urge to ask with some kind of quasi-journalistic verge, because it is better to have clarity of where Java web technology is going. > >1) Is the WebWork name going to exist still? > > I don't think so. > > >2) Is the Struts name going to be annexed with WebWork? > > I don't think so. > So in fact WebWork is going to be subsumed under Struts umbrella. That is fine, but I wonder is this going to upset the WebWorkers? > >3) A users has invested his or her hard-earned cash in `WebWork' in > >Action book. > >Will contents of this tome still be relevant in Struts? > > Substantially yes, although of course there will be package naming > changes and whatever changes seem to make for a better framework. > > >4) In fact there are a number of such books on the markets > e.g Struts Receipes > >and Struts Cookbook. Are these book becoming irrevelant or > still revelant? > >Have the book publishers lost a dosh of cash, then ? > > I think that no publisher expects to be making a lot from tech books > for very long after they are published; things just change too fast. > In any case, that's not my concern, and it wouldn't be even if I had > written one of those books ;-) > If you go to conferences then one of the selling points for users is to buy the book that goes with the latest technology. So I believe it is of concern to the potential users, if not directly the publishers themselves. > >5) What architectural components are going to be replaced in Struts ? > >( And conversely in Webwork?) > > TBD > I assume, then, that the next Struts will probably follow the FrontController design pattern. However is this true, or is it going to be a new architecture? > >6) What happens to the custom tag libraries like HTML or HTML-EL? > > TBD > > >7) Will Struts users suddenly now have to learn OGNL thing? > > That seemed to be on the roadmap. It also didn't seem to be > a big burden. > > >8) How will the Webwork Integration affect popular Struts extensions > >such as the Validator or Tiles? > > Both are (or are being adapted to be) able to run without Struts. > Therefore, they should be usable or not as is deemed of use to the > community. Odds seem good that some kind of adapters will be > available. > Fair enough > >9) A Girl named Geraldine (or A Guy named Gerald if you are so > >inclined) has invested in > >heavily Spring supported Struts Actions, and has read your recent > >announcement and > >she proclaims "What Do I Do Now?!" > > > >( Spring support AOP already, so does it fit with the > WebWork interceptors? ) > > Well, as always, there's no reason to jump to the new thing if it > doesn't serve your needs. Are there things that you really find > harder than they should be now that you have this Struts-and-Spring > framework in place? If not, why switch? If so, help map the path > from where you are to where you want to be and you'll be more able to > ensure continuity! (See also 11 below.) > I guess you're right. If there's an itch, it will be probably be scratched. The other side of the coin is that of simplification. One of the short falls of Struts and Java web is you already find yourself hand-injecting or binding stuff altogether. If the next version of Struts is able to simplify development then that will be a big-win. > > >10) "What does WebWork really bring to the Struts party? " > >"What is the different between that and this new Struts Ti that I > >have been hearing about?" > > The main difference between this and Struts Ti is that rather than > including WebWork as a dependency, it will be included in the > distribution. This allows for more efficient management of > interrelationships between the core and the layers that Ti was > offering to bring above and beyond what WebWork already has. > Good > >11) What will be the typically code that the application developer > >writes for Struts 2.x? > >Will it be Struts Action, Chains of Commands, or Interceptor? > > I imagine that all of them will be usable. The differences are > pretty superficial really. I imagine that we will try to leave the > plug-in point for control logic as wide open as possible. There are > many ways to skin that cat and no need to insist on the one-true-way. > > >12) When do you expect Struts 2.x to "go live"? > > Peter! You've been around here long enough to know better! ;-) > Yep, I know, just trying my luck. See top reply > Joe > > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com > "Narrow minds are weapons made for mass destruction" -The Ex > -- Peter Pilgrim :: J2EE Software Development Operations/IT - Credit Suisse First Boston, Floor 15, 5 Canada Square, London E14 4QJ, United Kingdom Tel: +44-(0)207-883-4497 ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.csfb.com/legal_terms/disclaimer_external_email.shtml ============================================================================== --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
