Javassist vs. Plastic vs. ComponentClassTransformWorker
Imagine if you could contribute a "classic"
ComponentClassTransformWorker or some new interface for working with a
Plastic class, both to the same service:
ComponentClassTransformWorker. The "classic" style would be
transformed, via TypeCoercer, to the new form. And, of course, we'd
make that work for all service configurations. That's my plan,
anyway. Configurations should, instead of complaining that provided
types are bad, attempt to coerce first.
I think the new interface will look more like:
public interface ComponentClassTransformer
{
void transformClass(PlasticClass componentClass, MutableComponentModel model);
}
On Tue, Feb 8, 2011 at 1:25 PM, Igor Drobiazko <igor.drobia...@gmail.com> wrote:
> Having an official road map would be a great improvement for Tapestry. Also
> having two releases in 2011 is great.
>
> My plans for 5.3/5.4 are:
>
> - Support for JSR-330 (almost done)
> - Support for some HTML5 features
> - Support for "multidimensional" caching of pages, components, etc.
> - Helping you out by migrating from javassist to plastic (I already started
> learning ASM + Plastic)
> - Maybe some support for other frameworks: Event though we having JPA
> support in Tynomo, I'm thinking to move it into Tapestry? Such a widely used
> framework should be supported.
>
> Along the way I'm working on the book which hopefully will be released
> before summer.
>
> What do you think about moving some stuff from tapx to Tapestry core?
>
> On Tue, Feb 8, 2011 at 7:13 PM, Howard Lewis Ship <hls...@gmail.com> wrote:
>
>> Been chatting with clients (who may help fund this) and just thinking
>> about plans. Here's a rough outline of what I think I can commit to
>> in 5.3 and 5.4.
>>
>> 5.3
>> - Deprecate Javassist inside ComponentClassInstantiator, replace with
>> Plastic
>> - Deprecate ClassFactory, provide necessary hooks to use Plastic
>> - Move Plastic into Tapestry?
>> - Gradle build for Tapestry
>> - Improve debugging experience (shadow per-thread values into shared
>> object fields in development mode)
>> - Improve asset pipelines for
>> - Dynamic generation of content (example, .less files converted to
>> static CSS automatically)
>> - JS/CSS minimization
>> - Do something about Component Report ... turn it into an Ant task,
>> perhaps, or integrate Component Report into JavaDoc directly
>> - Minor JS improvements, set expectations for 5.4 rewrite
>>
>> 5.4
>> - Remove Javassist entirely
>> - Remove ClassFactory
>> - Rewrite JS entirely, introduce abstraction layer and backwards
>> compatibility layer
>> - Maybe cometd/server-push support
>>
>> I'd love to see both these releases in 2011.
>>
>> In case you missed in: http://github.com/hlship/plastic
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: dev-h...@tapestry.apache.org
>>
>>
>
>
> --
> Best regards,
>
> Igor Drobiazko
> http://tapestry5.de
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
