In this step the application will be launched from within the Eclipse IDE and tested using the OSGi console.
org.eclipse.soda.sat.tutorial.customer
org.eclipse.soda.sat.tutorial.vendor.hotdog
org.eclipse.soda.sat.tutorial.vendor.popcorn
org.eclipse.soda.sat.tutorial.vendor.service
false for both
the org.eclipse.soda.sat.tutorial.vendor.hotdog bundle and
the org.eclipse.soda.sat.tutorial.vendor.popcorn bundle.
This will prevent these bundles from starting automatically when we
launch the application.
-Dorg.eclipse.soda.sat.core.util.trace=true to the
VM arguments field. This enables SAT's tracing capability that
will provide additional information with regards to why an imported
service was not acquired.
[DEBUG] - SAT Core: The bundle org.eclipse.soda.sat.core failed to acquire the service
org.osgi.service.log.LogService.
[INFO] - The Customer bundle has been started
[DEBUG] - SAT Core: The bundle org.eclipse.soda.sat.tutorial.customer failed to acquire the
service org.eclipse.soda.sat.tutorial.vendor.service.VendorService matching the
filter "(spiciness<=8)".
[DEBUG] messages designed to help understand why a
bundle failed to acquire an imported service. You can safely ignore the
first [DEBUG] message, since SAT optionally imports the
LogService, which in this case is not available.
[DEBUG] message is more interesting in that it
is saying that the org.eclipse.soda.sat.tutorial.customer
bundle failed to acquire a VendorService with a spiciness
property of less than or equal to 8. Since we have not yet started
either of the bundles that export a VendorService this is
hardly surprising.
Copyright © 2001, 2007 IBM Corporation and others. All Rights Reserved.