Hello,
 
I am are interested in the wildcard action mapping functionality in Struts
1.2.  Since 1.2 is not in a release state, I went back to the contributor of
the wildcard action mapping functionality to get his oppinion on whether or
not is was better to use the seperate package he use to maintain.
 
He recommended going with Struts 1.2 because he has been maintaining the
struts source and that code was ready and more solid than the old package.
It was his oppinion that Struts 1.2 was stable enough to use even though it
was not in a release state and the reason Struts 1.2  wasnt released yet was
that the powers that be to move 1.2 along were extremely busy(which I can
understand) and/or they might be waiting on milestones to proceed moving
Struts 1.2 ahead.
 
My question(s) are:
 
1) Were there significant changes in sources or concepts to Struts 1.2 from
Struts 1.1 that make using Struts 1.2 too risky to use prior to it going to
release status.  My understanding(from the web site) is that most of the
changes were removing deprecated code) though I noticed a few features
added.
 
2) If no to question 1, is there a particular nightly build you have
selected as the release candidate for Struts 1.2 or one that has been
regressioned should I decide to give go with Struts 1.2?
 
3) If yes to question 1, do you have an alternative
suggestion/recommendation to make use of this wildcard mapping feature..
 
 
Thanks for any advice in advance.
 

Reply via email to