When the BeanEditForm instantiates a new Model instance, it now uses the same code that instantiates service implementations (and injects dependencies). By default, Tapestry will find the constructor with the most parameters for this purpose, and will attempt to match each parameter to a service. That's why you get the Exception "No service matches..."
In this case, you don't want that behavior. You surely want BeanEditForm to instantiate via the public no-arguments constructor. By placing an @Inject annotation on the public no-arguments constructor, you can direct BeanEditForm to use that constructor instead. Regards, nillehammer -- http://www.winfonet.eu manuel aldana schrieb: > I am using BeanEditForm. I get an exception if I have model-class with a > constructor with an enumeration parameter. > > //WORKS > public class Model{ > public Model(){..} > } > > //WORKS > public class Model{ > public Model(String s){..} > } > > //CRASHES with error message: No service implements the interface > <foo.bar.MyEnum> > public class Model{ > public Model(MyEnum){..} > } > > public enum MyEnum{...} > > > apart from the constructor problem the bean-edit-form handles the > enumeration good (gets displayed as combo-box) > > am using 5.0.18. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
