[TAP5-853] Move away from Javassist

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 23/Sep/09 21:39
• Updated: 04/Jul/11 20:21
• Resolved: 02/May/11 22:57

Description

A long-term, multi-release strategy to replace ClassFactory/ClassGen and ClassTransformation methods with equivalents that are not tied to Javassist.

Over a couple of releases, the methods could be introduced (still implemented on top of Javassist), and the Javassist-centric methods deprecated, then eventually disabled (NotImplementedException) or even removed.

Rationale: Javassist is unprofessionally and fitfully maintained; many users have problems under Java6 due to Javassist.

Issue Links

• incorporates: TAP5-1138 ClassTransformation deprecated a bunch of methods, then refers to replacements that don't exist
• incorporates: TAP5-993 Reorganize ComponentClassTransformWorkers to start moving away from Javassist
• is related to: TAP5-519 Javassist error - javassist.bytecode.BadBytecode: bad array type for AALOAD: null
• is related to: TAP5-1509 PlasticField should support adding read and write advice to fields that can be used even in conjunction with a field conduit