In this series, you've seen how to create WS-Resources out of bundles of information. In Part 1, you created the Person WS-Resource, and in Part 2, you added the ability to send and receive notifications to that resource.
In this final installment, you created a WS-Resource not from an object that you created, but out of the Derby database itself. In doing that, you created a Web service that enabled you to start and stop Derby remotely using a Web services client. This process demonstrated the use of the Apache Muse application, which makes this kind of thing much more straightforward than it would be if you were doing it on your own. More importantly, it demonstrated the fact that you can control applications -- or even devices -- using Web services.
At this point, you've seen WS-Resources from two sides: from the standpoint of creating them though information from the Derby database and from the standpoint of creating one out of the Apache Derby server itself. To do that, you used the Apache Muse application, which is designed as an implementation of the WSRF. You can also use this same technique to control other applications through the use of Web services, or you can build your own application from scratch.