Changes

com.ebookfrenzy.database.provider

</pre>

The new package should now be listed within the Project tool window as illustrated in Figure 50-1:

Finally, these two string elements are combined, prefixed with content:// and converted to a Uri object using the parse() method of the Uri class. The result is assigned to a variable named CONTENT_URI.

== Implementing URI Matching in the Content Provider ==

The UriMatcher instance (named sURIMatcher) is now primed to return the value of PRODUCTS when just the products table is referenced in a URI, and PRODUCTS_ID when the URI includes the ID of a specific row in the table.

== Implementing the Content Provider onCreate() Method ==

}

</pre>

== Implementing the Content Provider update() Method ==

All that remains before testing the application is to modify the database handler class to use the content provider instead of directly accessing the database.

== Modifying the Database Handler ==

}

</pre>

Next, the addProduct(), findProduct() and removeProduct() methods need to be re-written to use the content resolver and content provider for data management purposes:

<hr>

<table border="0" cellspacing="0" width="100%">