I was thinking that it might be possible to have a check in the component if the value is a collection then I keep the existing behaviour and otherwise use it as a single value instead.
I need to change the javascript a bit as well but it should be possible I think. I'll try to find some time for this tonight I think. :-) /Joakim On Wed, Aug 10, 2011 at 4:23 PM, George Christman <gchrist...@cardaddy.com> wrote: > So I'm seeing where my issue is based on your code. > > As indicated, I'd like to use this component as a replacement to a select > menu, but here lies the problem. > > I have two tables, UserAccount and PurchaseRequest. There can only be one > UserAccount per PurchaseRequest. > > I have a OneToMany from UserAccount to PurchaseRequest > > ManyToOne from PurchaseRequest to UserAccount. > > Within the template, I'm using PurchaseRequest as my object, so I'm unable > to user a collection, only a single UserAccount object can be set. Looks as > if I'm asking the component to do something it wasn't designed to do. > Perhaps it would be a nice addition to the component if we could figure out > how to resolve this issue. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/ANN-Tapestry-tagselect-version-1-0-released-tp4639340p4685978.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
