Hi Andy,

If you open the properties page for your project in eclipse and select project facets, you can change the Java version to 5, and the errors you are having will go away. We have a JDK 6 requirement as well, so have been working with Tapestry and JDK 6 for quite some time now, and it is possible to get it working correctly. The first thing you will need to do is ensure that you have a recent version of javassist... the latest snapshots do. The second thing is to use eclipse for compilation, instead of command line tools that use the Java C compiler. This problem had frustrated us a great deal until we discovered that Java C compiler has problems with class transformation, but thankfully eclipse doesn't. Very occasionally, if ever you might have to re-factor your code a little, but we have always got Tapestry to work under JDK 6.

Whilst class transformation is a real marvel, unfortunately in Java it appears far from stable, and with JDK 7 already on its way perhaps class transformation brings less than it offers.

Peter

Andy Blower wrote:
I just ran into this issue myself, and switching to a 1.5 jre fixed it.
(although now I get a "Java compiler level does not match the version of the
installed Java project facet." error reported by Eclipse... which means
nothing to me)

I thought that reporting what was causing the problem may help Howard and
the T5 developers.

        @BeforeRenderBody
        boolean currentPage(MarkupWriter writer)
        {
           if (pager.getCurrentPageNum() == value)
           {
                writer.element("span", "class", "thispage");
                writer.write(Integer.toString(value));
                writer.end();
                return false;
           }
           return true;
        }

No problems occurred if I removed the writer.method() calls. Also if I put
these called in an @AfterRenderBody method it worked fine. Very odd
behavior, and it would be nice to know what the plans are are to resolve
this so that T5 can work well with jdk1.6, although I'm not clear whether
the fix would be in the JRE, javassist lib or T5. Sorry for my ignorance -
just trying to provide useful info.



joshcanfield wrote:
I don't have personal experience with your problem, but when I
searched the list on nabble I found that there is an issue with Java 6
and running on Java 5 will solve the problem.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to