On 20/02/14 08:30, Lance Java wrote: > I think the whole philosophy of Plastic is that you shouldn't ever need to > use ASM directly. I'm no expert but my understanding is that you can write > normal java code by implementing interfaces and use Plastic to weave the > implementations into the byte code.
Well, the InstructionBuilder API requires you to understand the byte code that's generated. Also, I agree that it is sane to transform existing classes, and I originally tried to do so but found Plastic didn't let me implement abstract methods from my superclass. This is possibly a Plastic bug. With respect, no Plastic experts have responded. Should I take my request to the dev list? - Phil --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
