On Fri, 17 Apr 2015 04:54:33 -0300, Lance Java
wrote:
In theory, that's possible. Tapestry doesn't reference ASM classes, it's
only dependency is plastic. So in theory you could have a layer in
plastic to choose ASM or javassist as the "provider" (or another byte
code
library).
Yeah, I
On second thought... Why would you want to swap out the the bytecode
provider?
With clientside javascript it makes sense to choose the provider since you
will be directly using jquery or prototype in your own code. Having a
single provider reduces the scripts downloaded by the client.
But with pl
In theory, that's possible. Tapestry doesn't reference ASM classes, it's
only dependency is plastic. So in theory you could have a layer in plastic
to choose ASM or javassist as the "provider" (or another byte code
library).
I'd doubt that this is high priority for the tapestry team. I seem to
rec
