@Contribute(ComponentClassTransformWorker2.class)

will work ... as will contributeComponentClassTransformWorker().

I have to wonder about how to make @Contribute(CCTW.class) work as
well, since that's the correct backwards compatible approach.  This
may need a fix for 5.3.1, depending on how soon I can get a 5.3.0
built out.

On Fri, Jun 10, 2011 at 2:56 PM, Josh Canfield <[email protected]> wrote:
> I have a monitoring module that I built to work with 5.3
> (https://github.com/joshcanfield/tapestry-monitoring). I upgraded to
> the latest 5.3 and it appears that deprecating the
> ComponentClassTransformWorker has caused errors during startup.
>
>  @Contribute(ComponentClassTransformWorker.class)
>    public static void
> addMonitorWorker(OrderedConfiguration<ComponentClassTransformWorker>
> configuration, final MonitorAdviser monitorAdviser) {
>
> Results in:
>
> java.lang.IllegalArgumentException: Contribution
> org.apache.tapestry5.monitor.MonitorModule.addMonitorWorker(OrderedConfiguration,
> MonitorAdviser) (at MonitorModule.java:47) is for service 'interface
> org.apache.tapestry5.services.ComponentClassTransformWorker' qualified
> with marker annotations [], which does not exist.
>        at 
> org.apache.tapestry5.ioc.internal.RegistryImpl.validateContributeDefs(RegistryImpl.java:275)
>        at 
> org.apache.tapestry5.ioc.internal.RegistryImpl.<init>(RegistryImpl.java:248)
>
>
> Is a code change expected on the part of the developer for this change?
>
> Josh
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to