xml file for each
bean you want to create. This parameter points to your beans.xml file. This is less desirable
though because it means more to change should you ever move the file, but it does serve
the same purpose. Lastly, there is a programmatic way to get the same effect, by using the
SpringCreator??™s setOverrideBeanFactory() method. Any code in this book that uses Spring
will be using the listener though, so if the other two approaches appeal to you, I suggest
perusing the DWR documentation to get the specifics.
CHAPTER 3 n ADVANCED DWR 118
JSF
JSF (java.sun.com/javaee/javaserverfaces) is the one endorsed (because it??™s part of the JEE
spec) framework for web application development in the Java world (don??™t take that to mean
it??™s necessarily the best choice, just that it??™s the only ???official??? framework in the Java world),
and DWR would be remiss to not support it. Fortunately, it does!
DWR??™s support of JSF is very similar to that of Spring in that it allows you to remote your
managed JSF beans, and not much more. This can certainly be enough though! In classic DWR
form, using this capability is very easy:
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243