I haven't been seeing this, it's new to me.  What JDK and OS are you using?

Earlier versions had some issues with inner classes that were resolved.

If you could turn on debugging of generated classes it would be
useful.  Enable logging for your component class name and it will be
produced at level debug.  The output is a description of all the
changes that occured to the class file as part of the transformation
and can be quite useful.

On Feb 8, 2008 8:33 AM, Adriaan Joubert <[EMAIL PROTECTED]> wrote:
> Hi,
>
> tapestry 5 is great and it is fantastic how easy it is to write new
> components for tapestry.
>
> One problem we have though is that using injected variables at times breaks
> the application in unpredictable ways. A typical example is as follows:
>
> Getting some information from a wrapping component (we are transforming our
> internal report structure to HTML using Tapestry components here)
>
>     @Parameter(value = "componentResources.container")
>     private ReportDisplayInterface reportInterface_;
>
> Having a private variable
>
>    private ReportData data_;
>
> which is initialised in
>
>    @SetupRender
>    void setupRender() {
>        data_ = reportInterface_.getData();
>       ....
>
>
> So far so good and this works fine. But we have need to make modifications
> to data_ as we progress with the generation of the page. Frequently calls
> like
>
>     data_.someMethod();
>
> will lead to a ClassNotFound exceptions - as the class could not be
> transformed. (Previously I used to get an ArrayIndexOutOfBounds exception
> out of javaassist, but with the latest snapshots that has gone away).
>
> Frequently this can be solved by moving the call into a method, so turning
> this into
>
>     // data_.someMethod();
>     myUnnecessaryMethod(data_);
>
>
>     void myUnnecessaryMethod(ReportData data) {
>         data.someMethod();
>     }
>
> This can be quite frustrating, as it leads to long sessions of commenting
> out one line after the other to find the offending line of code.
>
> So are there any guidelines as to what can be done with fields that are
> linked through to properties in other classes? Are these bugs or am I just
> trying to do something I shouldn't? Are there any standard templates for
> usages that work?
>
> I'm using 5.0.10-SNAPSHOT and have updated today, but this has been a
> problem since 5.0.5.
>
> Cheers,
>
> Adriaan
>



-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

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

Reply via email to