RE: strange tapestry problem

From: Gentry, Michael (
Date: Mon Nov 01 2004 - 09:51:35 EST

  • Next message: Tore Halset: "Re: strange tapestry problem"

    Just out of curiosity, does it happen on the very first item it is
    iterating over or does it happen further down?


    -----Original Message-----
    From: Tore Halset []
    Sent: Monday, November 01, 2004 9:47 AM
    To: Cayenne mailing list post
    Subject: Re: strange tapestry problem

    On Nov 1, 2004, at 15:29, Andrus Adamchik wrote:

    > Is it possible that the problem is still with the declaration of
    > "getCurrentVessel()" in the component class? How is it declared in the
    > file?

    getCurrentVessel() are not declared in the .page-file. Almost all of my
    .page-files are empty. It looks like this in the component class:
         public void setCurrentVessel(GdsVessel v) {
             _currentVessel = v;

         public GdsVessel getCurrentVessel() {
             return _currentVessel;

    setCurrentVessel are called from a tapestry..oreach component.

    If remove ".name" this is left:
    <span jwcid=..nsert" value="ognl:currentVessel"/>
    That works as expected and prints out CayenneDataObjects toString. So
    it looks like getCurrentVessel works.

    > Also what happens if you create a cover method like
    > "getCurrentVesselName()" in the component and caling it instead
    > (ognl:currentVesselName)?

    That does work. That is my current work-around.

      - Tore.

    This archive was generated by hypermail 2.0.0 : Mon Nov 01 2004 - 09:51:42 EST