That's true. I didn't think of that.
I'm running tapestry 5.1 for this particular app (I'm wanting to port an
app over to android), I think it uses something else for byte code
manipulation, but it is still byte code and hence not dalvik compatible :(
And byte code manipulation is pretty core to Tapestry, so I guess there
isn't really much hope of getting it going, not unless there is an
Android version of ASM (or whatever it is using, javassist?, I can't
remember) ?
Or would it be possible to get Tapestry to pre-generate the byte code
rather than at runtime?
Thanks, Ryan
On 28/05/2013 3:52 PM, Lance Java wrote:
Tapestry uses ASM under the hood for it's runtime byte code manipulation
magic. I'm pretty sure that this would fail on dalvik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org