I checked my application. It doesn't have any direct reference to
ResourceCache and it compiled without error.

Regarding the mixed Tapestry JAR, I did run into such issue at the beginning
of migration from T5.0. Below are related maven dependence. Do you see any
potential issue?

            <dependency>
                <groupId>org.apache.tapestry</groupId>
                <artifactId>tapestry-core</artifactId>
                <version>${tapestry.version}</version>
            </dependency>
            
            <dependency>
                <groupId>org.apache.tapestry</groupId>
                <artifactId>tapestry-spring</artifactId>
                <version>5.0.18</version>
            </dependency>
            
            <dependency>
                <groupId>org.apache.tapestry</groupId>
                <artifactId>tapestry-upload</artifactId>
                <version>${tapestry.version}</version>
            </dependency>
            
           <dependency>
                 <groupId>org.chenillekit</groupId>
                 <artifactId>chenillekit-tapestry</artifactId>
                 <version>1.3.0</version>
                 <exclusions>
                      <exclusion>
                          <groupId>org.apache.tapestry</groupId>
                          <artifactId>tapestry-core</artifactId>
                      </exclusion>
                      <exclusion>
                           <groupId>org.apache.tapestry</groupId>
                           <artifactId>tapestry-spring</artifactId>
                      </exclusion>
                      <exclusion>
                            <groupId>org.apache.tapestry</groupId>
                            <artifactId>tapestry-ioc</artifactId>
                      </exclusion>
                      <exclusion>
                            <groupId>org.apache.tapestry</groupId>
                            <artifactId>tapestry-func</artifactId>
                      </exclusion> 
                      <exclusion>
                            <groupId>jboss</groupId>
                            <artifactId>javassist</artifactId>
                      </exclusion>
                      <exclusion>
                            <groupId>commons-beanutils</groupId>
                            <artifactId>commons-beanutils-core</artifactId>
                      </exclusion>
                      <exclusion>
                            <groupId>commons-beanutils</groupId>
                             <artifactId>commons-beanutils</artifactId>
                      </exclusion>
                  </exclusions>
            </dependency>
                        <dependency>
                                <groupId>tapestry5-treegrid</groupId>
                                <artifactId>tapestry5-treegrid</artifactId>
                                <version>5.0.15</version>
                
                        </dependency>
                        
                        
                        <dependency>
                                <groupId>us.antera.t5restfulws</groupId>
                                <artifactId>t5-restful-webservices</artifactId>
                                <version>0.2.1</version>
                        </dependency>


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-tp4585262p4600121.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

Reply via email to