Re: Encoder may not be instantiated directly.

2008-09-27 Thread Keith Bottner
Ted, That worked but I am getting null for the value. In my page class I have: @Property private Country test; And in my template I have: (It is vf,countrySelect because I have this bundled in a library of share components and such.) No matter what I set it to when the page displays aft

Re: Encoder may not be instantiated directly.

2008-09-27 Thread Keith Bottner
Ted, Thanks for the pointer, that made it stop giving me the error all right and now it displays. Now all I have to do is figure out why it always comes back as null when I include it in my template. Keith On Sep 27, 2008, at 1:36 AM, Ted Steen wrote: You should not put non-component c

Re: Encoder may not be instantiated directly.

2008-09-26 Thread Ted Steen
You should not put non-component code under component packages. see http://tapestry.apache.org/tapestry5/guide/component-classes.html move the CountryEncoder to something like com.shared.util instead. 2008/9/27 Keith Bottner <[EMAIL PROTECTED]>: > I am trying to use a bundle a select component for

Encoder may not be instantiated directly.

2008-09-26 Thread Keith Bottner
I am trying to use a bundle a select component for the specific case of displaying a list of countries and from the all the documentation that I have run across and I always get an exception when the page is rendered. It says: Component class com.shared.base.CountryEncoder may not be instan