> > Anything's possible. ;-) But why would you do that? Sure, it might result in > S2 eventually becoming part of Java EE, but Struts has been pretty > successful over the last 8 years or so without that, as have other > frameworks like Spring and Hibernate. By turning S2 into a JSR, you then end > up with "design by committee", and lose much of the ability to innovate > since you're constrained by what's in the JSR.
S2 based on WW, and we know also JCP also have several big company that spending in this brand, IBM, Oracle, Sun, RedHat, and the user believe that the standard will make the investment more trusted, of course Apache is the most trusted one also in non dejure world. using Apache brand, the movement will still move. i active in Jetspeed long before Jetspeed become JSR 168, and can u imagine what happen if Jetspeed develop a non standard tech, what do you think of pluto? i think the dispatcher mechanism and http and rest tech is the strong point in struts2 and we cannot see JSF model will got this, because different approach in development. my idea is to make new java people and big company that dont want to put their risk can use Struts2. this will make the movement more stronger. F --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
