Re: T5: Unpredictable deploy behaviour in tomcat 6 error - TapestryException FormSupport at ... corelib/pages/ExceptionReport.tml
Yes, thnks, that is why I was testing. As I say, in the end, all OK. Adam On 10/08/2008, Howard Lewis Ship [EMAIL PROTECTED] wrote: This is a good cautionary tail; I develop using Jetty day to day, but it is important to integration test using an environment as close to your deployment setup as possible; in this case, using Tomcat. There shouldn't be glaring differences, but there still are. On Sat, Aug 9, 2008 at 5:44 PM, adasal [EMAIL PROTECTED] wrote: All good. I notice I sent this seven hours ago, so 4 hours of work later ... 1. I deployed into Jetty which has far better error messages. There may be a setting in tomcat for this? It told me there were bad class versions. Of course! 2. In Eclipse land it is necessary to compile and run the container using the same version. If using ant to compile - I do as everything is packed into a war as needed by tomcat - then ant must use the same java version. OK I new that just didn't think! 3. Troubles not completely over, also necessary to take out of the container launch config any conflicting jars, probably put in then when running something else indiscriminately, or just trying to make it work and forgotten they were there. Bottom line - jetty has more useful error messages and that can really matter to someone like me! Adam 2008/8/9 adasal [EMAIL PROTECTED] org.apache.tapestry.ioc.internal.util.TapestryException: org.apache.tapestry.services.FormSupport [at classpath:org/apache/tapestry/corelib/pages/ExceptionReport.tml, line 11, column 45] Does anyone know the way round this? This is the basic test application - Tapestry5Test1. I have been able to deploy this once into tomcat 6 with tapestry 06 libs. I changed to 13 and then to 14 usually getting a class not found exception forg.apache.tapestry.ioc.annotations.InjectService. This exception has disappeared with the following issues. I have reverted to 06 and also deployed the 06 tutorial into tomcat 5. - Both OK I have redeployed Tapestry5Test1 under tomcat 6. - KO. When testing with newer libs I made necessary edits as I understand for the new tapestry5 package name and also in web.xml. I cannot understand why it would work once but not again, I assume I have made a mistake in the libs I have included, but I placed the originals elsewhere and just copied them back, so this doesn't make sense to me. What are the issues with tomcat 6? Jetty seems fine. BTW I have tried with 3 versions of javassist - javassist-3.4.jar, javassist-3.7.ga.jar, javassist-3.8.ga.jar. I can't trace the difficulties to this jar. Any ideas? Adam -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Unpredictable deploy behaviour in tomcat 6 error - TapestryException FormSupport at ... corelib/pages/ExceptionReport.tml
This is a good cautionary tail; I develop using Jetty day to day, but it is important to integration test using an environment as close to your deployment setup as possible; in this case, using Tomcat. There shouldn't be glaring differences, but there still are. On Sat, Aug 9, 2008 at 5:44 PM, adasal [EMAIL PROTECTED] wrote: All good. I notice I sent this seven hours ago, so 4 hours of work later ... 1. I deployed into Jetty which has far better error messages. There may be a setting in tomcat for this? It told me there were bad class versions. Of course! 2. In Eclipse land it is necessary to compile and run the container using the same version. If using ant to compile - I do as everything is packed into a war as needed by tomcat - then ant must use the same java version. OK I new that just didn't think! 3. Troubles not completely over, also necessary to take out of the container launch config any conflicting jars, probably put in then when running something else indiscriminately, or just trying to make it work and forgotten they were there. Bottom line - jetty has more useful error messages and that can really matter to someone like me! Adam 2008/8/9 adasal [EMAIL PROTECTED] org.apache.tapestry.ioc.internal.util.TapestryException: org.apache.tapestry.services.FormSupport [at classpath:org/apache/tapestry/corelib/pages/ExceptionReport.tml, line 11, column 45] Does anyone know the way round this? This is the basic test application - Tapestry5Test1. I have been able to deploy this once into tomcat 6 with tapestry 06 libs. I changed to 13 and then to 14 usually getting a class not found exception forg.apache.tapestry.ioc.annotations.InjectService. This exception has disappeared with the following issues. I have reverted to 06 and also deployed the 06 tutorial into tomcat 5. - Both OK I have redeployed Tapestry5Test1 under tomcat 6. - KO. When testing with newer libs I made necessary edits as I understand for the new tapestry5 package name and also in web.xml. I cannot understand why it would work once but not again, I assume I have made a mistake in the libs I have included, but I placed the originals elsewhere and just copied them back, so this doesn't make sense to me. What are the issues with tomcat 6? Jetty seems fine. BTW I have tried with 3 versions of javassist - javassist-3.4.jar, javassist-3.7.ga.jar, javassist-3.8.ga.jar. I can't trace the difficulties to this jar. Any ideas? Adam -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Unpredictable deploy behaviour in tomcat 6 error - TapestryException FormSupport at ... corelib/pages/ExceptionReport.tml
All good. I notice I sent this seven hours ago, so 4 hours of work later ... 1. I deployed into Jetty which has far better error messages. There may be a setting in tomcat for this? It told me there were bad class versions. Of course! 2. In Eclipse land it is necessary to compile and run the container using the same version. If using ant to compile - I do as everything is packed into a war as needed by tomcat - then ant must use the same java version. OK I new that just didn't think! 3. Troubles not completely over, also necessary to take out of the container launch config any conflicting jars, probably put in then when running something else indiscriminately, or just trying to make it work and forgotten they were there. Bottom line - jetty has more useful error messages and that can really matter to someone like me! Adam 2008/8/9 adasal [EMAIL PROTECTED] org.apache.tapestry.ioc.internal.util.TapestryException: org.apache.tapestry.services.FormSupport [at classpath:org/apache/tapestry/corelib/pages/ExceptionReport.tml, line 11, column 45] Does anyone know the way round this? This is the basic test application - Tapestry5Test1. I have been able to deploy this once into tomcat 6 with tapestry 06 libs. I changed to 13 and then to 14 usually getting a class not found exception forg.apache.tapestry.ioc.annotations.InjectService. This exception has disappeared with the following issues. I have reverted to 06 and also deployed the 06 tutorial into tomcat 5. - Both OK I have redeployed Tapestry5Test1 under tomcat 6. - KO. When testing with newer libs I made necessary edits as I understand for the new tapestry5 package name and also in web.xml. I cannot understand why it would work once but not again, I assume I have made a mistake in the libs I have included, but I placed the originals elsewhere and just copied them back, so this doesn't make sense to me. What are the issues with tomcat 6? Jetty seems fine. BTW I have tried with 3 versions of javassist - javassist-3.4.jar, javassist-3.7.ga.jar, javassist-3.8.ga.jar. I can't trace the difficulties to this jar. Any ideas? Adam
