Without looking at the code, it sounds like we might be able to add a backwardly-compatible signature, and deprecate the former. If that can be done, we could re-tag .10 and try again. Anyone up for the patch?
-Ted. On 9/16/07, Piero Sartini <[EMAIL PROTECTED]> wrote: > After looking at the code the problem is within Component.java. > > The determineActionURL method has 2 new parameters which were not present in > 2.0.9 and are passed to UrlHelper.java: > boolean forceAddSchemeHostAndPort, boolean escapeAmp > > It should be safe to call with > forceAddSchemeHostAndPort=false, escapeAmp=true > (That is what UrlHelper.java does when these params are missing ..) > > This can be fixed in tabletags quite easy. > > Anyway, since 2.0.10 fixes a security issue: Would it be good to have a method > in Component.java that is compatible with 2.0.9? Maybe tagged as @Deprecated? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
