Community
Participate
Working Groups
As navigation is an important part in Riena, using it could be easier. Many controllers need to access navigation arguments or their parameters or need to navigate to another controller. During a customer project we have come up with 5 convenience methods, that make life easier and prevent the developer from writing the same code over and over again. The attached patch adds these methods to SubModuleController. I'm not sure whether they'd better be moved to NavigationNode.
Created attachment 188680 [details] convenience methods for navigation
how about a declarative approach ? @RequiresNavigationParameter(type=Customer.class) public void configureRidgets(Customer customer) { }
The declarative approach would be preferable, but IMHO not at the cost of an impaired flexibility. So multiple annotations would be required to differentiate between required and optional navigation parameters.
(In reply to comment #3) > The declarative approach would be preferable, but IMHO not at the cost of an > impaired flexibility. So multiple annotations would be required to > differentiate between required and optional navigation parameters. I totally agree. I was also thinking of multiple annotations. (just too lazy to actually write them down :-) )
