THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The Apache Tuscany Project implements the SCA specifications and easier SOA developments by it's comprehensive infrastructure of components that can be assembled into applications called composites. Tuscany also provide extensions revealed to be useful when binding components with one another using specific protocol (CORBA, JSON, SOA/HTTP).
bTo To make a bright and effective use of Tuscany SCA's opportunities, applications are to be developed on fully featured and OPENED platform so that innovative and reusable solutions and components can be created and reassembled. The new Google Android Mobile platform provides such features(opensource, extendable, operating system, api, sdk, middleware, adequate tools) and has consequently been targeted to host tuscany and to demonstrate it capabilities under the "tuscany-host-android" subproject. Started last year at GSOC08, the project has been going peacefully along, and great efforts have already been accomplished including porting tuscany SCA(core/runtime + extensions) in a light version onto Android and partially implementing an android store app, which consumes services from a SCA friendly store app.
...
Android client: Makes a call to the catalog service in order to retrieve the full catalog or part of it by specifying a search criteria. This will result into a JSONRPC invocation having the webservice URI and the request querystring as parameters.
Store web App: Will Answer to the call, and load the catalog items from a datasource, probably XML file. Either all items or a part equivalent to the user's request, will be loaded and sent back to the Client as JSON String. In case it's a request for a part of the catalog, the catalog service will not do the search itself, but will just reference another a catalogBrowser service to perform the search. Another process should there be undertaken too, to decide how items are going to be displayed, according to the catalog currency. Handling automatically the switch from a currency to another and providing the choice of currency from a user predefine's predefined list will be interesting there. This emphasis then the need to create a currencies datasource, from which they can all be loaded, and their value easily be converted to one another. A simple xml file once again will make it.
...
According to that scenario, the project can be divided in three parts as quoted below:
Ressources:
- Currencies.xml;
- Store.xml;
- Product images folder;
- Customer ratings file (leave as last).
Web App Store
+ Configuration file;
Android Client Store
...
Resources description
- Currencies.xml
This file will contain all possible currencies the store can use. This means an extension of the number of currencies that can be used.
It should reference one of the currencies as the reference currency, and all conversions will be made passing by it. A DTD or a schema
validation may be implemented to validate it's structure.
...
Will mainly contains path to the ressourcesresources.
eg:
CATALOG_FILE="<path_to_the_file>"
CURRENCIES_FILE="<path_to_the_file>"
IMAGES_DIR="<path_to_the_files>"
...
| Wiki Markup |
|---|
* Store Home page with buttons driving to: \[X\] * Catalog categories page; * Products list page - (This page should will show up after a category has been selected, or after a product search submission); Items will be displayed in a listView using a simpleAdaptor to re-arrangeearrange the item's attribute that are to be displayed. Items quantity can be typed in from the list. * Product details page: displays all possible details about the product; * Shopping cart page: Displays selected items, and the total. \[/X\] and \* Preferences page; I intend to assemble \[X/\] pages under a same TabActivity, for a praticalpractical switch between them. Any other proposal surely will be welcomed and discussed. |
...