When you open configuration/config.ini, you'll see a large number of framework
properties used to determine the bundles that get started in your basic runtime.
You're looking for the Derby entry that's something like the following:
You need to change the JAR name in this entry to derbyclient.jar so that the Derby
network client code is available, as follows:
After you've done this in both of your frameworks (the service provider and consumer
frameworks), it's time to start up your application again. Initially there should be no
difference at all; after all, your previous database had perfectly good read-only behav-
ior (see figure 10.19).
Running with a remote database
If you attempt to buy some of your foreign food, then, as before, you're allowed to put
some values into the form (see figure 10.20).
A second attempt to buy from your foreign foods department
This time, however, the result is a lot more pleasant! See figure 10.21.
Now that you have a single backing database, you're able to interact with the same
data that your remote system is. As a result, your superstore can be distributed across
A successful purchase