Like I said, it??™s a perfectly
ordinary javabean, save for the setType() method. The four fields you see should be selfexplanatory,
as they match the columns the user sees on the screen.
Figure 6-15. UML class diagram for the FileVO class
DirectoryVO.java
The DirectoryVO class, just like the FileVO class, is an ordinary javabean that provides some
extra information the File class wouldn??™t, and gets rid of all the superfluous information.
Figure 6-16 shows the UML class diagram for this class.
Figure 6-16. UML class diagram for the DirectoryVO class
It??™s obvious, I think, what the name and path fields are. The hasChildren field is set to true
when the directory has child directories, false when it doesn??™t. As we saw earlier, this is used
to set up the UI properly in terms of branches being expandable or not in the directory tree.
CHAPTER 6 n REMOTELY MANAGING YOUR FILES: DWR FILE MANAGER 316
To save some space, the code for the DirectoryVO class isn??™t shown here, but have a look
anyway. It literally is just the private members, getters and setters, and toString(). There??™s not
even an interesting setter like in FileVO!
FileSystemFunctions.java
We saw as we looked over the client-side code that all the calls to the server via DWR were to
the FileSystemFunctions class, and now it??™s time to check that class out and see how all the
features of Fileman are actually implemented.
Pages:
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565