Howard Lewis Ship wrote: > > I'd be just as happy to outright remove the methods as to keep them > around as non-functional. Again, what we'll see is that 5.1 > compatible code will not even load correctly, due to the references to > (now) non-existend methods on ClassTransformation. As currently > implemented, the code will load and a more understandable exception > report will be generated. >
Well, except the exception report points you at TransformMethod#extend which doesn't exist! You should at least point to addAdvice, ideally with a note that the code needs to be restructured. -- View this message in context: http://tapestry-developers.221625.n2.nabble.com/T5-2-ClassTransformation-why-deprecate-throw-an-exception-tp5028206p5033342.html Sent from the Tapestry Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
