Hi Alexander,
The main reason for me to port it to 2.1.2 was creating a Struts
blank-style application for my company branch having AppFuse as startup
example. Our existing web applications were already developed on top of
Struts 2.x
What I posted was a straight port but there are other nice to have
targets I have like controlling the mix of ways to do the same things
e.g. the AppFuse Struts Basic relies a lot on JSP tag libraries for
accomplishing things that are implemented using the Struts tags. I am
aiming to getting rid of:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core"; prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/fmt"; prefix="fmt" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/functions"; prefix="fn" %>
except when strictly necessary e.g. displaytag.
I have still pending to send a patch, I will then maybe include also
some of the nice to have in my opinion.
Best regards,
Giovanni
Alexander Coles wrote:
On Jun 21, 2008, at 12:32 PM, Giovanni Azua wrote:
Hi,
Attached is the full diff:
The s20111 folder is the project folder containing AppFuse Struts
basic
after creating the archetype and doing "mvn appfuse:full-source"
The s212 is a copy of s20111 ported to Struts 2.1.2
regards,
Giovanni
Hi Giovanni,
Thanks for posting this! I wish I had seen this a few days ago, as I
just completed the porting work myself without this diff.. but I
pretty got to the same place as you (except for missing one of the JSP
changes you made).
Just out of interest why did you upgrade to Struts 2.1.2? To use the
REST plugin, perhaps? I'd love to know if other Appfusers are using
the REST-plugin.
Cheers,
Alex
---------------------------------------------------------------------
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]
