Re: OGNL performance detrimental to Struts 2
Tonight I was looking at abstracting away OGNL from xwork. (I was pretty far before I gave up for the night, about a half dozen OGNL references in xwork that I'll have to look at a little closer) So I took a look at what it would take to integrate MVEL. First, the lack of javadoc is a little disappointing. (There wasn't a single line of javadoc comment that I could find) Secondly, the integration guide isn't very extensive, just some basic examples. Based on these 2 items alone, it may not be as trivial as advertised to figure out how to integrate MVEL into XWork. On the other hand OGNL is not without it's issues. :) I'll probably look at it a bit later when I'm farther with xwork, but that's my take on it thus far for what it's worth. Tom Chris Brock wrote: Don't dare me. I'm pretty ambitious. I wrote MVEL 1.0 in three days. Don Brown-2 wrote: I'd like it to be possible for a Struts developer to swap in a new EL, perhaps MVEL, if they didn't like OGNL for some reason. If you can create a patch to make that happen, I would consider it my early Christmas present :) Don Chris Brock wrote: Why do you think it would be so terribly difficult? What does MVEL not support that is currently supported by OGNL that would not be fixable by a few tweaks to MVEL's syntax? Generally, MVEL's API architecture follows the same pattern as OGNL, supports type coercion, conversion, projections, etc. Not to mention that MVEL is now an active project and OGNL is not, and of course the performance advantage in MVEL which is only getting better by the day. Don Brown-2 wrote: If you can find a way to completely replace OGNL by MVEL, I'd be very interested to see it. :) Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: documentation problems
Thanks for pointing these out, but please feel free to take the next step and correct them. By editing the original Confluence pages, found at http://cwiki.apache.org/confluence/display/WW, these snippet errors can be corrected. The reason so many are broken is that the pages were pointing to XWork 1, so I turned off those prefixes, which broke the snippets. All we need to do is point the snippets to XWork 2. The snippet plugin works by allowing the administrator to set allowed "prefixes" that snippets can have. For our instance, the following prefixes are defined: Prefix URL struts2/http://svn.apache.org/repos/asf/struts/struts2/trunk/ com.opensymphony.xwork2. http://svn.opensymphony.com/svn/xwork/trunk/src/java/com/opensymphony/xwork2/ org.apache.struts2. http://svn.apache.org/repos/asf/struts/struts2/trunk/core/src/main/java/org/apache/struts2/ org.apache.struts2.views.tiles. http://svn.apache.org/repos/asf/struts/struts2/trunk/plugins/tiles/src/main/java/org/apache/struts2/views/tiles/ org.apache.struts2.sitegraph. http://svn.apache.org/repos/asf/struts/struts2/trunk/plugins/sitegraph/src/main/java/org/apache/struts2/sitegraph/ xwork2/ http://svn.opensymphony.com/svn/xwork/trunk/ people/ http://people.apache.org/ org.apache.struts2.sitemesh. http://svn.apache.org/repos/asf/struts/struts2/trunk/plugins/sitemesh/src/main/java/org/apache/struts2/sitemesh/ openejb3/ http://svn.apache.org/repos/asf/incubator/openejb/trunk/openejb3/ Take the case of the validation.html page. There are several snippets that use the "xwork/" prefix, so it should be updated to "xwork2/". Most of the errors will probably be just that easy. See also: http://confluence.atlassian.com/display/CONFEXT/Snippet+Plugin Don Musachy Barroso wrote: Macro snippet errors: http://struts.apache.org/2.x/docs/validation.html http://struts.apache.org/2.x/docs/type-conversion.html http://struts.apache.org/2.x/docs/localization.html http://struts.apache.org/2.x/docs/action-chaining.html http://struts.apache.org/2.x/docs/interceptors.html http://struts.apache.org/2.x/docs/chain-result.html http://struts.apache.org/2.x/docs/stream-result.html http://struts.apache.org/2.x/docs/ajax-theme.html Broken: http://struts.apache.org/2.x/S2PLUGINS/spring-plugin.html (on http://struts.apache.org/2.x/docs/guides.html) http://struts.apache.org/2.x/S2PLUGINS/plexus-plugin.html (on http://struts.apache.org/2.x/docs/guides.html) http://struts.apache.org/2.x/S2PLUGINS/home.html(on http://struts.apache.org/2.x/docs/guides.html) http://struts.apache.org/2.x/S2PLUGINS/tiles-result.html (on http://struts.apache.org/2.x/docs/result-types.html) http://struts.apache.org/2.x/apidocs/index.html (on http://struts.apache.org/2.x/docs/guides.html) http://struts.apache.org/2.x/S2WIKI/home.html (on http://struts.apache.org/2.x/docs/home.html) Small error here: http://struts.apache.org/2.x/docs/portlet-configuration.html regards musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
documentation problems
Macro snippet errors: http://struts.apache.org/2.x/docs/validation.html http://struts.apache.org/2.x/docs/type-conversion.html http://struts.apache.org/2.x/docs/localization.html http://struts.apache.org/2.x/docs/action-chaining.html http://struts.apache.org/2.x/docs/interceptors.html http://struts.apache.org/2.x/docs/chain-result.html http://struts.apache.org/2.x/docs/stream-result.html http://struts.apache.org/2.x/docs/ajax-theme.html Broken: http://struts.apache.org/2.x/S2PLUGINS/spring-plugin.html (on http://struts.apache.org/2.x/docs/guides.html) http://struts.apache.org/2.x/S2PLUGINS/plexus-plugin.html (on http://struts.apache.org/2.x/docs/guides.html) http://struts.apache.org/2.x/S2PLUGINS/home.html(on http://struts.apache.org/2.x/docs/guides.html) http://struts.apache.org/2.x/S2PLUGINS/tiles-result.html (on http://struts.apache.org/2.x/docs/result-types.html) http://struts.apache.org/2.x/apidocs/index.html (on http://struts.apache.org/2.x/docs/guides.html) http://struts.apache.org/2.x/S2WIKI/home.html (on http://struts.apache.org/2.x/docs/home.html) Small error here: http://struts.apache.org/2.x/docs/portlet-configuration.html regards musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Tag reorganization
Yeah, but given the problems that most people have at some stage of debugging with the tags, I thought there would be more traffic ;-) /Ian Mitchell James wrote: That's the wonderful or terrible thing about successful OSS projects, you are kidding yourself if you think even 5% of the users are even on a mailing list, much less that they will read every post. -- James Mitchell 678.910.8017 On Dec 29, 2006, at 8:09 AM, Ian Roughley wrote: If we go the from route, then it should be a simple global find and replace. I am surprised at such a large use of the tags though. I've asked more than a couple of times if anyone was using them, and there was never a response. /Ian Shekhar Yadav wrote: We are using 2.0.1 and we are using form/div with ajax based theme. Is it going to be major problem for us to migrate to new tags. If so what are you recommendations, we are in process of building and only half way through. I don't want to create 250 screens with tags that are going to be outdated by the time we release the app. - Shekhar -Original Message- From: Ian Roughley [mailto:[EMAIL PROTECTED] Sent: Thursday, December 28, 2006 7:36 AM To: Struts Developers List Subject: Re: [proposal] Tag reorganization I'm torn - I like the fact that we are getting the ajax code out of the base, but especially for webwork->s2 upgrades there is going to be more work. The other thing is that 2.0.2 is still beta, and frankly I don't think there is that many people using the tags at the moment, so this would be a good time to make the change. /Ian David H. DeWolf wrote: That's what I'm imagining too. . .and we're agreeing that this incompatibility is a pill we have to swallow. Ian Roughley wrote: I think I am missing something here - how will the tags be invoked? It will need to be a new tld with a new name space, right? Something like rather than - so there will be a compatibility issue, but all the functionality will be moved forward. /Ian David H. DeWolf wrote: Ted Husted wrote: Don mentioned a separate tag library, so that would indicate another prefix, but there'd be no reason why the internal tag syntax would change. To keep the codebase manageable, I believe we do need to make this change, and I'd rather make it now while we are in our first beta series than after the first Struts 2 GA. The plugin model might also open the door to other AJAX implementations of the same tags. I agree. I like it, but just wanted to make sure we think through the compatibility changes before we make a decision. In essence we're saying that this change is more important than backwards compat of this one tag and we're willing to live with those repercussions. I'm on board with that. -T. On 12/27/06, David H. DeWolf <[EMAIL PROTECTED]> wrote: Ok, as long as we keep the tag prefixes and tag names once they are abstracted from the plugin. At one point we talked about having a simple version which is extended by the dojo version and added additional (dojo-specific) featuers. It seems like the current names would be more likely be used for the core tags - not the dojo-enhanced ones. Ted Husted wrote: A struts-dojo plugin shouldn't change the tag syntax. It should just be a matter of adding the JAR, as we do for Spring, and JasperReports, and Tiles, so forth. On 12/27/06, David H. DeWolf <[EMAIL PROTECTED]> wrote: Nope, that's the one I'm talking about. I got the impression we were going to keep it as is and thus break backwards compatibility in 2.0.2 -- and then mess with it again it when we create the plugin. . . David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EM
Re: [S2] XWork Status Quo
I am willing and spending lots of my free time on Struts 2, XWork and (still) WebWork 2.2.X. to bring this projects to high quality products as lots of the other developers are doing, but I need more feedback to get more of the envolved developers in. There are some open issues in Jira where I call for feedback, but did not get any input. My perspective is that we are creating and maintaining the framework that we *want* to use to create our own applications. Experience has proven that we can create a better framework by working together than any of us can create working apart. We work hard to make the framework accessible to other developers, in the hope that some of those developers will join us. We distribute the framework to the general public, but the general public is not our customer. Our customers are the volunteers who contribute back to the framework. The general public are prospective customers, some of which become customers by working with other users on the mailing lists, filing issues, submitting patches, and helping to make the framework better. We tag a build "General Availability" when we feel that the bits hold no surprises and the product is ready for the general public to put into production. Note that we don't mark it "final" or "stable", or in any way say that we are done. We just say it's ready for public consumption. If we help people on the lists, if we apply patches that people submit, if we invite contributors to join us, if we create a safe place where people can discuss and improve the product, then quality take cares if itself. And, best of all, we don't have to do all the work ourselves. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] XWork Status Quo
On 1/1/07, Alexandru Popescu <[EMAIL PROTECTED]> wrote: Before the merge, I was spending a lot of my spare time contributing to WW and on the XWork side along with Rainer, Jason, and occasionally a couple of more guys. The direction was clear for everybody and everybody knew where we are heading to. Then, WebWork was the major consumer of XWork, and since they share the OpenSymphony infrastructure, XWork, essentially, remained a subproject of WebWork. But, since XWork 2 and Struts 2 do not share the same infrastructure, we cannot treat XWork like it is a subproject of Struts 2. The situation seems confused because XWork 2 is now a project without a list, and therefore without a visible, public community. If XWork adopts the usual project infrastructure, so that it stand on its own, I believe we will see greater clarity and, consequently, greater involvement. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] XWork Status Quo
On 12/31/06, Rainer Hermanns <[EMAIL PROTECTED]> wrote: Thoughts? I think the way to address any problems with XWork involvement is to followup on Patrick's post and create the usual project infrastructure: A user list, a dev list, and a commits lists for the automatic posts from Subversion, JIRA, and Confluence. I also think it would be helpful if we distributed the bits and let the community decide if the they are GA or not. It's fine to have a roadmap, but a roadmap is artificial. The map is not the land. If the community tells us the bits are ready for primetime, then we should not let a roadmap stand in the way of a "General Availability" release. Documentation is a great way to build community, but we don't deploy documentation. Meanwhile, the quickest way to destroy community is to never create a production-ready release, which is what is happening now. So, please, lets setup the usual lists for XWork, and dub the next XWork 2 distribution XWork 2.0.3. Then we can distribute it with Struts 2.0.3, and let the community tell us if the bits are ready for primetime or not. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] XWork Status Quo
Happy new year guys. :-) WebWork just like any other open-source project follows the open-source spirits. It is very much driven by the community itself. Features are often implemented when they are substantial enough, it doesn't matter if it originated from users, commiters or the project leads themself. Discussions are normally done until an agreement reach prior to having them implemented. I'd say opensymphony is very much like ASF minus the rigid rules. Just want to say that from my experience its been both fun and educational at the same time working under the lead of Pat/Jason/Rainer with the community. Jason might be at times a bit harsh at words but he is very much most of the time accurately true. Cheers guys. :-) Don Brown <[EMAIL PROTECTED]> wrote: To fight philosophy with philosophy ;), the goal of Struts 2 has been pretty much the same since we started: to simplify web development to create a more developer-friendly framework. We've been following the Struts Ti plan [1] roughly since late 2005. WebWork was brought on board as it was the perfect, solid and proven framework that these ideas could be built upon. The current driving goal of Struts 2 is to get a GA release out. Yes, we've implemented some pretty core changes and resolved a lot of the rough spots [2] in WebWork 2, and now it is time to get them out to the wider public. Following such progress can be difficult, particularly because of the organization structure of Struts and Apache projects in general. In WebWork, you had two project leads that directed efforts. In Struts, you have a group of committers on the Project Management Committee (PMC), each with an equal voice in determining where the project is going. As expected, each PMC member has their own idea of where the project should go, so direction and conflicts are more difficult to discern and resolve. That said, I'm very confident that we are all on board to get Struts 2 out and make it the best framework available. All I can tell you is to follow the dev mailing list and get involved in the discussions. That is the best way to keep abreast of the changes and directions, as well as move the project to where you want it to go. If you see a change you don't like, speak up! Your voice is just as important as anyone else's, and the more talented people we have behind the project, the better. Don [1] http://wiki.apache.org/struts/StrutsTi [2] http://wiki.apache.org/struts/RoughSpots Alexandru Popescu wrote: > First of all Happy New Year to everyone! and then a bit of a > philosophical email - something related to previous post by Rainer and > something that bothered me for the last couple of months. > > Before the merge, I was spending a lot of my spare time contributing > to WW and on the XWork side along with Rainer, Jason, and occasionally > a couple of more guys. The direction was clear for everybody and > everybody knew where we are heading to. During the merge and > afterwards, I got very confused... I've seen lots of emails in the > form: "hey I've thought about this incredible idea, how does it > sound?... oh by the way I have already implemented it... (and as a > side note it changes everything you knew about the underlying > pieces)". At this point I have stepped back a bit and I have started > to just watch because I HAD NO IDEA where we want to go - and not the > generic answers. There are lots of discussions about alphas, betas, > GAs, etc releases but I haven't seen a single one that would qualify > itself to be promoted to final users. > > Now I see Rainer asking for help and I tend to see the reasons why. > And as always I would be happy to help, but I frankly would like to > see what the intentions are. Because, once again, I would like to > understand why I would put my efforts behind it - and hopefully not > just to create a couple of alphas, betas, etc. > > BR, > > ./alex > -- > .w( the_mindstorm )p. > :: OSS Evangelist :: > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Send instant messages to your online friends http://uk.messenger.yahoo.com
Re: [S2] XWork Status Quo
To fight philosophy with philosophy ;), the goal of Struts 2 has been pretty much the same since we started: to simplify web development to create a more developer-friendly framework. We've been following the Struts Ti plan [1] roughly since late 2005. WebWork was brought on board as it was the perfect, solid and proven framework that these ideas could be built upon. The current driving goal of Struts 2 is to get a GA release out. Yes, we've implemented some pretty core changes and resolved a lot of the rough spots [2] in WebWork 2, and now it is time to get them out to the wider public. Following such progress can be difficult, particularly because of the organization structure of Struts and Apache projects in general. In WebWork, you had two project leads that directed efforts. In Struts, you have a group of committers on the Project Management Committee (PMC), each with an equal voice in determining where the project is going. As expected, each PMC member has their own idea of where the project should go, so direction and conflicts are more difficult to discern and resolve. That said, I'm very confident that we are all on board to get Struts 2 out and make it the best framework available. All I can tell you is to follow the dev mailing list and get involved in the discussions. That is the best way to keep abreast of the changes and directions, as well as move the project to where you want it to go. If you see a change you don't like, speak up! Your voice is just as important as anyone else's, and the more talented people we have behind the project, the better. Don [1] http://wiki.apache.org/struts/StrutsTi [2] http://wiki.apache.org/struts/RoughSpots Alexandru Popescu wrote: First of all Happy New Year to everyone! and then a bit of a philosophical email - something related to previous post by Rainer and something that bothered me for the last couple of months. Before the merge, I was spending a lot of my spare time contributing to WW and on the XWork side along with Rainer, Jason, and occasionally a couple of more guys. The direction was clear for everybody and everybody knew where we are heading to. During the merge and afterwards, I got very confused... I've seen lots of emails in the form: "hey I've thought about this incredible idea, how does it sound?... oh by the way I have already implemented it... (and as a side note it changes everything you knew about the underlying pieces)". At this point I have stepped back a bit and I have started to just watch because I HAD NO IDEA where we want to go - and not the generic answers. There are lots of discussions about alphas, betas, GAs, etc releases but I haven't seen a single one that would qualify itself to be promoted to final users. Now I see Rainer asking for help and I tend to see the reasons why. And as always I would be happy to help, but I frankly would like to see what the intentions are. Because, once again, I would like to understand why I would put my efforts behind it - and hopefully not just to create a couple of alphas, betas, etc. BR, ./alex -- .w( the_mindstorm )p. :: OSS Evangelist :: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] XWork Status Quo
First of all Happy New Year to everyone! and then a bit of a philosophical email - something related to previous post by Rainer and something that bothered me for the last couple of months. Before the merge, I was spending a lot of my spare time contributing to WW and on the XWork side along with Rainer, Jason, and occasionally a couple of more guys. The direction was clear for everybody and everybody knew where we are heading to. During the merge and afterwards, I got very confused... I've seen lots of emails in the form: "hey I've thought about this incredible idea, how does it sound?... oh by the way I have already implemented it... (and as a side note it changes everything you knew about the underlying pieces)". At this point I have stepped back a bit and I have started to just watch because I HAD NO IDEA where we want to go - and not the generic answers. There are lots of discussions about alphas, betas, GAs, etc releases but I haven't seen a single one that would qualify itself to be promoted to final users. Now I see Rainer asking for help and I tend to see the reasons why. And as always I would be happy to help, but I frankly would like to see what the intentions are. Because, once again, I would like to understand why I would put my efforts behind it - and hopefully not just to create a couple of alphas, betas, etc. BR, ./alex -- .w( the_mindstorm )p. :: OSS Evangelist :: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax tags in 2.0.3 (was Struts 2.0.2 status - Ready to roll)
Actually, the result would be something like since the new tag library couldn't share the same prefix (except in JSP, of course). Technically, I suppose the Velocity directives could pick whatever name they want, but you'd want to be consistent. Don Patrick Lightbody wrote: +1 I think in general the concept of "themes" for the AJAX stuff was a mistake. Instead, let's do stuff like: And make those tags part of an external plugin. That way we don't make migration from WebWork impossible, but we also fix a mistake we made with WebWork by trying to stuff too much functionality in to themes. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=56165&messageID=111480#111480 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
