The SMS project WP 4.2: Component authoring ICCS

The general view Server Side Components –Server side –SMS low level component services –SMS self-standing component services –SMS composite services –Clients interact with them –Have dependencies –Described using various assets and artifacts

Developing components for SMS SMILE API –Can build components using SMILE API –Work resulted in decoupling core API from bindings –Supports both request/response and notification –Current version uses RMI binding –Lacks a runtime environment –Process description is limited to the name of the port type (Yellow Pages) – Ongoing work for registry LightDL –Description of service interfaces –Initial version generates HTML description –New version supports code generation for parts of a code –Uses Velocity Templates –Near future: Support for Data Types

Implementation (1) Simple Content Provider –Already implemented using the previous tools Authentication & Authorization –Interaction with WP4.5 Payment Service –Wrap an existing bank payment system (i.e. ProxyPay) –Investigate solutions of TGS – ORGA GetTime –Simple get current time –SMILE has a simple example –Nice starting example for adapting context to services MEM Repository

Implementation (2) Notification Service –Retrieval of MEMs when client’s offline –Raises the question about user management Rating Service –How to avoid client side code? Asking A Location –WWRF demo component needs to be adjusted Profile data* –Select appropriate solution –LID, FOAF, Liberty Alliance, Facebook, OpenSocial –Allow importing/exporting from other types of profile data Persistence Service –Generic service allowing different components to share stored data –Reference implementation can offer various common persistence types

Next steps Finalize and release new version of tools Integrate APIs and tools to a solid development process –Use Apache Ant or Maven –Document on how to develop and test a component using Eclipse or other tool Implement a concrete set of services –Adapt WWRF services to new SMILE core –Continue development of core services Knowledge base for future component authoring –Use long list of services Further investigate MDA for component authoring –State Diagrams can be used for modeling (part of) internal logic – especially when used for service composition