Re: Problem with component containing form

[Spencer W. Thomas]

I'll try that (when I get back to work tomorrow), but I thought I had 
already tried using "form" for the direction and still had the problem.  
However, now that I think about it, I was nesting my form component 
inside another component.  Presumably the parameter needs to be "form" 
in BOTH components?

I need the explicit getItem() because I create the value of the Item in 
the Java.  And once I've made an explicit getItem(), I must also supply 
setItem() or Tapestry gets upset.

=S
Robert Zeigler wrote:
Change the direction of item from "in" to either of "form" or "auto".
Also, in your home page, you don't need the property accessors, unless
you need to access the property from code. If you do, then the simplest
way to make sure things work right is to make your class and those
accessors abstract.
Robert
 

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