I solved this. The root of the problem was that I was:
a.) using the @RequestParameter annotation b.) trying to use different methods in the same class, LinkEditor, to handle the different functions (events) related to editting links in my application. This suggests that I would need to create a separate class for each of my use cases unless they shared exactly the same (@)Injection state. In other words, for my 'read' and 'delete' use cases, I need the id of the desired link entity, so I used the @RequestParameter. When I update the link, this same request parameter was not in my form and thus I ran into the exception. I wonder if it makes sense to add an 'optional' or 'required' parameter to the @RequestParameter...? Also, Gavin, I wonder if you have some suggestions for how to organize and group related code since it seems like using a single class to encapsulate related methods might not be best..? (the 'best practices' stuff) Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944039#3944039 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944039 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
