Hi Matt, On 20 Sep 2007 at 21:13, Matt Raible wrote:
> On 9/20/07, Rob Hills <[EMAIL PROTECTED]> wrote: > > Hi Matt, > > > > On 20 Sep 2007 at 19:56, Matt Raible wrote: > > > > > On 9/20/07, Rob Hills <[EMAIL PROTECTED]> wrote: <..> > > and regenerating my pojos (using appfuse:gen) over again. However, I've > > run appfuse:gen on my modified User class and > > I'm now wondering if I shouldn't have. It fails with the error message > > "Expression field.value.typeName is undefined on line > > 51, column 22 in appfuse/web/struts/web-tests.ftl". Is that a bug, or > > should I not have run appfuse:gen over my modified > > org.appfuse.model.User class? > > You probably shouldn't run it on your modified class because the > User-related classes are customized to do the specialized User > Management that AppFuse provides. > > With that being said, appfuse:gen shouldn't error out with an > exception. I'd rather have it warn the user that it doesn't handle > something, or simply ignore it - rather than throwing an error that > makes no sense. It's likely that a @OneToMany, @Component or some > other annotation is causing the problem. I'd eventually like to > support all of these, but we need a pattern on the UI that makes sense > before we do it. Yes, in this case, I have an @ManyToOne annotation which I guess probably caused the problem. It doesn't seem to have caused any problems though fortunately, but I agree about the thought that it should alert the user that it doesn't handle that class. Could the pattern be as simple as something like having an exclude filter somewhere that filters out the org.appfuse.model classes? Perhaps the same filter could be used to trigger the alert. Cheers, Rob Hills Waikiki, Western Australia Mobile +61 (412) 904-357 Fax: +61 (8) 9529-2137 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
