This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hello, I've just updated an application from struts 2.0.6 to 2.2.1. The previous version used the dojo plugin extensively for date time pickers, but this time I have gone with the jQuery struts plugin and it's datepicker tag. There isn't much else I had to change, which was pleasing (and suspicious!)
I've come across a few niggles with warnings appearing in the server log, but they seem to be spurious and the system works. However, I have public methods in my action class called confirm(), complete(), a struts.xml that contains
This used to work fine, and would post the form to the same action that generated the page (in this case, DaytimeBooking.action), and calling the method called confirm().
Since I've updated struts, this same form now simply calls execute() instead of confirm(). I've tried a few different forms of submit:
is my standard unchanged version. This now calls execute() rather than confirm().
gives me an action not found error: There is no Action mapped for namespace /supervisor and action name DaytimeBooking!confirm. I do have <constant name="struts.enable.DynamicMethodInvocation" value="false" /> set in my xml too.
Actually works. But I don't want to hard-code the name of the action into the jsp because then I can't reuse it in other actions. This is also the reason for not having the action="DaytimeBooking" property in the <s:form ..> tag.
Has something anything changed in the way struts (or the taglib) handles these forms? Is there a better way of decoupling the jsp from the action rather than just omitting the action property?
2010-11-04 14:52:44,395 WARN - Could not create JarEntryRevision for [besjar:C%3A/Borland/BAS660/var/domains/base/configurations/... path to deployed *.war]!
java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
Is the "spurious" error that I'm getting in the logs, in case this is relevant.