Re: Is this the appropriate mailing list for questions about the Tiles 2 sandbox project?
Greg Reddin ha scritto: On 12/29/06, Stone, Sam [EMAIL PROTECTED] wrote: Is this the appropriate mailing list for questions about the Tiles 2 sandbox project? For now yes. Tiles will soon have its own top-level project and when that happens you can ask questions there. But it will likely be a few weeks before all that is set up. And there is another issue, some of us (me included) are on holidays, so if you notice some delay (or no answer at all) is for this reason. I hope to become fully functional starting from 2nd January. Ciao Antonio P.S.: BTW, have a good end and a good start (of year) :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tiles 2 - how to get more error info?
Stone, Sam ha scritto: Am getting ServletException while including page (see EX. 1 below). How can I get more specific information? My insert looks as follows: tiles:insertDefinition name=site.login ignore=true/ ... org.apache.tiles.taglib.ContainerTagSupport TRAS0014I: The following exception was logged org.apache.tiles.TilesException: ServletException while including page. I think that now (in the HEAD) the error is logged with more detail. Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to do this with latest Tiles 2 API?
Stone, Sam ha scritto: Using the API from Sep 2006 I was able to access externally an attribute from a tiles definition as follows: String sTilesDefName = (String) request.getAttribute(tile_name); TilesContext tilesContext = new ServletTilesContext(session.getServletContext(), request, response); ComponentDefinition componentDefinition = TilesUtil.getDefinition(sTilesDefName, tilesContext); String sMyAtribute = (String) componentDefinition.getAttribute(myAttribute); I can't quite figure out how to do this using the current Tiles 2 API. Well... you can't! At least, not the easy way that it was. If you want to manage definitions and attributes directly you have to create a container, probably extending the BasicTilesContainer class, or get the container and cast it to BasicTilesContainer class (dangerous), that accesses the definitions factory. Anyway what's your exact requirement? Why do you need to access the definition? Probably you don't need to access them, but only to render or verify if the definition is there. Antonio - 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] Struts 2.0.2 status - Ready to roll
On 12/30/06, Ted Husted [EMAIL PROTECTED] wrote: OK, I'll get ready to roll another release then. I've updated the release notes with the latest changes, and I'm preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: On 12/30/06, Ted Husted [EMAIL PROTECTED] wrote: OK, I'll get ready to roll another release then. I've updated the release notes with the latest changes, and I'm preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1. Just FYI, the assembly module's pom has the wrong XWork version number in it, so the build fails. (That should be controlled with a property in the parent pom; I'll fix it after you tag 2.0.2.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
I looked again at a clean checkout and found the reference. The assembly POM in my usual working copy was missing the XWork stanza. I'm not sure when I did that or why. The other thing is why do we get the Embedded error: C:\projects\Apache\struts2-clean\assembly\..\target\site isn't a directory. prompt on a clean build. Every artifact in the assembly seems to generate this error. Creating the directory cures the problem, but only until the next clean build. Is it a Windows issue? -Ted. On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: I can't even find the XWork reference in the POM assembly. :) Why don't you go ahead and fix the parent POM, and then we'll tag it. -Ted. On 12/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: On 12/30/06, Ted Husted [EMAIL PROTECTED] wrote: OK, I'll get ready to roll another release then. I've updated the release notes with the latest changes, and I'm preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1. Just FYI, the assembly module's pom has the wrong XWork version number in it, so the build fails. (That should be controlled with a property in the parent pom; I'll fix it after you tag 2.0.2.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: I looked again at a clean checkout and found the reference. The assembly POM in my usual working copy was missing the XWork stanza. I'm not sure when I did that or why. The other thing is why do we get the Embedded error: C:\projects\Apache\struts2-clean\assembly\..\target\site isn't a directory. prompt on a clean build. Every artifact in the assembly seems to generate this error. Creating the directory cures the problem, but only until the next clean build. I don't see that error, and I'm on Windows. C:\projects\Apache\struts2-clean\assembly\..\target\site would be the path to the top-level generated website. The instructions say 'mvn clean install site -P all,pre-assembly', so with 'site' in there, all the websites should get generated under their respective modules' target/site directories. (And I have other uncommitted changes in the assembly module, so just fixing the version in assembly/pom.xml is the best idea for now.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
I can't even find the XWork reference in the POM assembly. :) Why don't you go ahead and fix the parent POM, and then we'll tag it. -Ted. On 12/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: On 12/30/06, Ted Husted [EMAIL PROTECTED] wrote: OK, I'll get ready to roll another release then. I've updated the release notes with the latest changes, and I'm preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1. Just FYI, the assembly module's pom has the wrong XWork version number in it, so the build fails. (That should be controlled with a property in the parent pom; I'll fix it after you tag 2.0.2.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
I was leaving site out. Thanks! -Ted. On 12/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: I looked again at a clean checkout and found the reference. The assembly POM in my usual working copy was missing the XWork stanza. I'm not sure when I did that or why. The other thing is why do we get the Embedded error: C:\projects\Apache\struts2-clean\assembly\..\target\site isn't a directory. prompt on a clean build. Every artifact in the assembly seems to generate this error. Creating the directory cures the problem, but only until the next clean build. I don't see that error, and I'm on Windows. C:\projects\Apache\struts2-clean\assembly\..\target\site would be the path to the top-level generated website. The instructions say 'mvn clean install site -P all,pre-assembly', so with 'site' in there, all the websites should get generated under their respective modules' target/site directories. (And I have other uncommitted changes in the assembly module, so just fixing the version in assembly/pom.xml is the best idea for now.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Formatting rules
Antonio Did you ever get to put the eclipse formatter on the wiki? thanks musachy Antonio Petrelli wrote: Ted Husted ha scritto: * http://struts.apache.org/releases.html#Coding In practice, we would like the code to pass our Checkstyle configuration. * http://svn.apache.org/viewvc/struts/maven/trunk/build/ Thank you Ted, now I know how many mistakes I made :-) I will try to prepare an Eclipse formatter file ASAP to put it in the wiki. Ciao Antonio - 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] Struts 2.0.2 status - Ready to roll
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: I was leaving site out. Thanks! I'm having trouble with 'mvn install -Pall' (svn trunk, with the version set at 2.0.2.) The struts-all build is failing because it can't find 'struts2-config-browser-plugin'. To make it work, I dropped into plugins and ran mvn install, then built again from the top. I thought we had decided not to have a combined Struts 2 jar, correct? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
Yes, we decided that a combined struts-all.jar wasn't useful. From clean checkout against a clean repository, I had to install the plugins first, and then run the usual assembly commands, same as you. I added a note to the wiki page. -Ted. On 12/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: I was leaving site out. Thanks! I'm having trouble with 'mvn install -Pall' (svn trunk, with the version set at 2.0.2.) The struts-all build is failing because it can't find 'struts2-config-browser-plugin'. To make it work, I dropped into plugins and ran mvn install, then built again from the top. I thought we had decided not to have a combined Struts 2 jar, correct? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
For now, I'll just delete it from the library before I sign it, to avoid confusion. Then, we can take it out all together for Struts 2.0.3. -Ted. On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: Yes, we decided that a combined struts-all.jar wasn't useful. From clean checkout against a clean repository, I had to install the plugins first, and then run the usual assembly commands, same as you. I added a note to the wiki page. -Ted. On 12/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote: I was leaving site out. Thanks! I'm having trouble with 'mvn install -Pall' (svn trunk, with the version set at 2.0.2.) The struts-all build is failing because it can't find 'struts2-config-browser-plugin'. To make it work, I dropped into plugins and ran mvn install, then built again from the top. I thought we had decided not to have a combined Struts 2 jar, correct? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Tag reorganization
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 dojo:select ... / from s:select theme=ajax ... / 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 dojo:select ... / rather than s:select theme=ajax ... / - 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: [EMAIL PROTECTED]
WW-1583
WW-1583 was closed, but I don't see the change on svn head. regards musachy - 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)
On 12/31/06, Musachy Barroso [EMAIL PROTECTED] wrote: Don Brown wrote: This reminds me - what about moving all the ajax tags to a plugin for 2.0.3? Now I'm confused :), weren't you working on this already? Yes, but we were also talking about branching and doing that in Struts 2.1.0. -Ted. - 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)
Oh that's true. Enough for this year. Happy new year every one! musachy Ted Husted wrote: On 12/31/06, Musachy Barroso [EMAIL PROTECTED] wrote: Don Brown wrote: This reminds me - what about moving all the ajax tags to a plugin for 2.0.3? Now I'm confused :), weren't you working on this already? Yes, but we were also talking about branching and doing that in Struts 2.1.0. -Ted. - 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: Ajax tags in 2.0.3 (was Struts 2.0.2 status - Ready to roll)
The basic idea is to get rid of the ajax theme, and create a dojo-specific tag library. Therefore, we'd keep certain ajax features like client-side validation in the main tags, but move dojo-specific tags like div, date picker, anchor, etc out into their own tag library. IMO, basing a tag library/theme on a toolkit like dojo is much preferred over basing on a technology. Don Ted Husted wrote: On 12/31/06, Musachy Barroso [EMAIL PROTECTED] wrote: Don Brown wrote: This reminds me - what about moving all the ajax tags to a plugin for 2.0.3? Now I'm confused :), weren't you working on this already? Yes, but we were also talking about branching and doing that in Struts 2.1.0. -Ted. - 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: Ajax tags in 2.0.3 (was Struts 2.0.2 status - Ready to roll)
+1 On 12/31/06, Don Brown [EMAIL PROTECTED] wrote: The basic idea is to get rid of the ajax theme, and create a dojo-specific tag library. Therefore, we'd keep certain ajax features like client-side validation in the main tags, but move dojo-specific tags like div, date picker, anchor, etc out into their own tag library. IMO, basing a tag library/theme on a toolkit like dojo is much preferred over basing on a technology. Don Ted Husted wrote: On 12/31/06, Musachy Barroso [EMAIL PROTECTED] wrote: Don Brown wrote: This reminds me - what about moving all the ajax tags to a plugin for 2.0.3? Now I'm confused :), weren't you working on this already? Yes, but we were also talking about branching and doing that in Struts 2.1.0. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] XWork Status Quo
At one point wasn't there talk of bring xwork into the apache fold. Is that still an option or is that off the table? It seems to me that since xwork is such a critical piece of struts2 that it should be part of apache and not opensymphony. Then xwork would be forced to follow the apache processes. Ted Husted wrote: As it stands, XWork is a stealth project using a beta/rc release system. Working with XWork from Struts is problematic because * There are no visible mailing lists that track project status * There are no forums in which to discuss XWork 2 specific issues, including the release roadmap and the quality of the development build * Struts 2 is the only major consumer of XWork 2, and our releases are needed to test XWork in production. * The beta/rc system will always mandate at least one more Struts release than a milestone system, since a GA candidate Struts release must follow a final XWork release. The simplest resolution would be for XWork to * utilize its own set of lists and forums and lists, rather than piggyback on WebWork. * adopt the milestone release system used by Struts, iBATIS, Tomcat, HTTPD, MySQL, and many other successful, productive projects. Using a common milestone system will allow us to test both Struts and XWork builds in production, and *then* judge the quality by how well the software performs in the field. Thoughts? -Ted. - 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: [Struts2] Use a list/array of objects in JSP
That should work just fine. What kind of error do you get? What happens when you do: s:property value=objects/ - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=55942messageID=111476#111476 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status
Ted, Making XWork a more public project is not a problem - we just hadn't done so up until now due to no need. As for the names of the releases (RC, beta, 2.0.1.1.1.1, whatever you want...)... that is really easy to fix: just ask Rainer or whoever is doing the release :) OpenSymphony doesn't really have a lot of rules around this. The important thing is that XW is here to serve Struts, and everyone knows that. So if there are needs it isn't providing, I'm sure the gang will work to address them. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=55391messageID=111479#111479 - 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)
+1 I think in general the concept of themes for the AJAX stuff was a mistake. Instead, let's do stuff like: s:dojo-div.../ 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=56165messageID=111480#111480 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] XWork Status Quo
Ted, Your suggestions all sound very reasonable. Rainer and I would be happy to help set this up (I can do the forums/infrastructure, and I'm sure Rainer can help by giving releases more compatible version numbers in the future). - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=56191messageID=111481#111481 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] XWork Status Quo
As a first follow up, happy new year to everyone. As Pat mentioned, the infrastructure at OpenSymphony does not have the rules and bounds Apache has. I have no problem to release milestones, dot releases or the like, but I want to achieve that certain issues are fixed and targets were reached for a release. The only point currently holding up a final xwork 2.0 release is related to documentation tasks. 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. I had very good discussions with Ian, Phil and Rene at JavaPolis about open issues, tasks and todos, but it takes lots of time to tackle all of them... Also lots of Teds and others suggestions sound reasonable to me, but I need more help on the xwork side. Currently only Don and Toby help me out there. Ted, if you want karma, Pat or I can set you up there. Bringing over xwork to Apache is only one possibility, but I am not sure if the time for this step has come yet. XWork is not stealth, nor dead at all... XWork has coupled infrastructure with webwork and shares its mailing list, forums and so forth. If you really are in the need of a separated infrastructure we (at OpenSymphony) all are open for suggestions and critics. I think, that we first need to get out a GA release of Struts 2, and I like to follow up on Dons suggestions to fix the currently open issues for 2.0.X instead of branching for 2.1.X series. Thoughts? Rainer PS: Sorry my poor english for now, just came back from a new years eve party! Ted, Your suggestions all sound very reasonable. Rainer and I would be happy to help set this up (I can do the forums/infrastructure, and I'm sure Rainer can help by giving releases more compatible version numbers in the future). - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=56191messageID=111481#111481 - 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]
