![]() Being able to link to the charting page with just a regular hyperlink would probably be pretty handy. Those three would accomplish what you need though, again, my recommendation would be number one. This works the same way as number one but isn't quite as clean as you will need a similar form everywhere you want to do this and it cannot be a normal hyperlink. Three, you can use a regular HTTP form and POST to the charting page, using the same kind of RequestParameterMap dredging that you did for number one. This is probably the simplest but you will need to ensure that the bean is cleaned up when you no longer need it and thus, somewhat dangerous. Two, you can simply make your bean session scoped (or, conversation scoped if you're using Seam or similar) so that the two pages simply share the one bean. This is the way I would personally do this. This achieves a good separation of concerns, letting your charting page just do charting without having to worry about what beans it will be getting the charts from. You can use that to get the StuffID and build your chart. ( FacesContext.getCurrentInstance().getExternalContext().getRequestParameterMap().get("stuffID) Then in your chart page's backing bean you can either use JAX-RS to pass in the page parameter or you can dredge the request object, ie: One, you can make the chart page RESTful and pass in the ID of the stuff you're going to chart. There are a couple of different things you can do here. Add a file named table. This sample project will demonstrate how to run a dataTable component in a IceFaces environment. Add the libraries both in the Build Path and in the Java EE Module dependancies. Flow being: Navigate to Page A -> Look through the table -> Click something on Page A to look at charts -> Navigate to Page B -> Read Charts. Create a new Web Project and add all IceFaces libraries (except the one just mentioned). So you have Page A with the table of stuff and Page B with charts of individual stuffs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |