We will now build on top of our simple stock quoting service from Phase 3 and add the ability for our resource to persist themselves. This will enable the resources to survive a container shutdown or restart as well as be more stable for resources that might be around for awhile.
4.1 Add the Persistence resource framework option to the StockPortfolioManager service
4.2 Edit the client to demonstrate persistence
4.3 Deploy the modified service
4.4 Start the container
4.5 Invoke the client
|Each phase of this tutorial builds upon the exercise from the previous phase. If you'd prefer to skip the previous exercise and use a pre-built service, you can download load it from here. You'll just need to unzip it to an empty directory. If you are using Eclipse as your IDE to complete these exercises, you'll need to correct the path information in the StockManager/.classpath file.|