Yeah that was it. I had t5c-commons still hanging around. Thanks.
Carl Crowder wrote: > > Could it be that you have the older version of Tapestry still on the > classpath? Or some other Tapestry module that automatically adds itself? > > Britske wrote: >> Also: I should have added that I'm not contributing anything remotely >> related >> to AppModule.java >> >> >> Britske wrote: >>> Hi all, >>> >>> I'm in the process of updating from 5.0.17 to the latest stable release: >>> 5.1.0.5 >>> Most of the process is pretty smooth except the following: >>> >>> on page X I have an actionlink defined which updates a zone. (see >>> snippets >>> below) . >>> The problem is thaty I'm getting a 'conflicting contribution error' >>> when >>> clicking the actionlink thus trying to populate the zone. Everything >>> worked fine in 5.0.17. >>> Anyone knows what's wrong? >>> >>> relevant info below. >>> thanks, >>> Geert-Jan >>> >>> .tml >>> ---------------------------------- >>> zoek bestemming >>> >>> <div t:type="zone" t:id="locationhelpZone" t:visible="false" >>> id="locationhelpZone" class="mff" style="display:none;"> >>> # close >>> <div class="popcont t-zone-update"/> >>> </div> >>> >>> relevant snippet of class X: >>> ------------------------------------ >>> Object onActionFromLocationhelp(){ >>> return >>> getResources().getComponent().getComponentResources().getEmbeddedComponent >>> ("locationHelper"); >>> } >>> >>> >>> error: (enormous stacktrace, only showing the root-cause. BTW: I >>> couldn't >>> find any classes of my own that were referenced in the stacktrace) >>> >>> Caused by: java.lang.IllegalArgumentException: Service contribution (to >>> service 'AjaxComponentEventResultProcessor') conflicts with existing >>> contribution (by >>> org.apache.tapestry.commons.TapestryCommonsModule.contributeAjaxComponentEventResultProcessor(MappedConfiguration, >>> ObjectLocator, Response) (at TapestryCommonsModule.java:127)). >>> at >>> org.apache.tapestry5.ioc.internal.ValidatingMappedConfigurationWrapper.add(ValidatingMappedConfigurationWrapper.java:83) >>> at >>> org.apache.tapestry5.ioc.internal.ValidatingMappedConfigurationWrapper.addInstance(ValidatingMappedConfigurationWrapper.java:115) >>> at >>> org.apache.tapestry5.services.TapestryModule.contributeAjaxComponentEventResultProcessor(TapestryModule.java:1535) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) >>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) >>> at java.lang.reflect.Method.invoke(Unknown Source) >>> at >>> org.apache.tapestry5.ioc.internal.ContributionDefImpl.invokeMethod(ContributionDefImpl.java:110) >>> ... 114 more >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > -- View this message in context: http://www.nabble.com/T5%3A-service-contribution-conflict-after-updating-from-5.0.17--to-5.1.0.5-tp25033459p25038498.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org