It's just an expression of frustration. I already experienced quite a lot issues in this migration (not trying to say it's Tapestry's fault ).
Anyway, thanks for respond to my post. I was able to by pass the original issue and encounter another one. Exception assembling embedded component 'abcadvancedsearchform' (of type com.xxx.components.search.ABCAdvancedSearchForm, within search/Advanced:advancedsearchcomponent.advancedsearchform): Could not convert 'itemsFound' into a component parameter binding: Exception generating conduit for expression 'itemsFound': java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType This is how it looks like. In containing template <t:container xmlns:t="http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";> ....something else here... <t:block id="forABC" > <t:search.abcAdvancedSearchForm criterionsNumber="6" module="module" state="state" itemsFound="itemsFound">ABC ADVANCED SEARCH FORM</t:search.dynamicAdvancedSearchForm> </t:block> ....something else here... </t:container> In component template, this line gives error <t:search.collapsable itemsFound="itemsFound" > ... </t:search.collapsabl> search.collapsable is my a component that has parameter itemsFound It works fine in T5.0. I understand in literal what the error is saying. But not sure what changes should be made to work in T5.2. Thanks, Simon -- View this message in context: http://tapestry.1045711.n5.nabble.com/Another-case-of-Block-parameters-are-only-allowed-directly-within-component-elements-tp4585262p4587190.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
