What's cool in the new and updated. OSGi Specs. Carsten Ziegeler. David Bosschaert. 1 of 53

Transcription

1 What's cool in the new and updated OSGi Specs Carsten Ziegeler David Bosschaert 1 of 53

2 Speakers Carsten Ziegeler RnD Adobe Research Switzerland OSGi Board, CPEG and EEG Member ASF member David Bosschaert RnD Adobe Research Dublin Co-chair OSGi EEG Open-source and cloud enthusiast 2 of 53

3 Agenda Framework updates Repository update Asynchronous Services & Promises Declarative Services Http Service Cloud Semantic Versioning Annotations Other spec updates 3 of 53

4 OSGi Core R6 Release Service Scopes Package and Type Annotations Data Transfer Objects Native Namespace WeavingHook Enhancements System Bundle Framework Hooks Extension Bundle Activators Framework Wiring 4 of 53

5 Framework Updates Service Scopes (RFC 195) OSGi R5 supports two service scopes: Singleton Bundle (ServiceFactory) Transparent to the client S getservice(servicereference <S> r e f ) v o i d ungetservice(servicereference <S> r e f ) 5 of 53

6 Framework Updates Service Scopes (RFC 195) Third Scope: prototype Driver: Support for EEG specs (EJB, CDI) Usage in other spec updates Clients need to use new API / mechanisms 6 of 53

7 Framework Updates Service Scopes (RFC 195) New BundleContext Methods API S getserviceobjects(servicereference <S> r e f ).getservice() v o i d getserviceobjects(servicereference <S> r e f ).ungetservice(s) Transparent to the client 7 of 53

8 Framework Updates Service Scopes (RFC 195) New PrototypeServiceFactory interface Managed service registration properties for inspection Support in component frameworks (DS, Blueprint) 8 of 53

9 Data Transfer Objects 9 of 53

10 RFC 185 Data Transfer Objects Defines a DTO model for OSGi Serializable/Deserializable objects Use cases: REST, JMX, Web Console... To be adopted by other specs 10 of 53

11 RFC 185 Data Transfer Objects Getting DTOs: adapter pattern p u b l i c c l a s s B u n d l e D T O e x t e n d s org.osgi.dto.dto { p u b l i c l o n g id; p u b l i c l o n g lastmodified; p u b l i c i n t state; p u b l i c S t r i n g symbolicname; } p u b l i c S t r i n g version; 11 of 53

12 RFC 185 Data Transfer Objects DTOs for the OSGi framework FrameworkDTO BundleDTO ServiceReferenceDTO BundleStartLevelDTO, FrameworkStartLevelDT CapabilityDTO, RequirementDTO, ResourceDT BundleWiringsDTO, etc 12 of 53

13 Repository of 53

14 14 of 53 OSGi Repository today

15 15 of 53 Example Repository namespaces

16 RFC Repository 1.1 Existing repository powerful but: limited to queries in a single namespace New in RFC 187: Combine requirements spanning multiple namespaces: R e p o s i t o r y repo =... // Obtain from Service Registry C o l l e c t i o n <R e s o u r c e > res = repo.findproviders( repo.getexpressioncombiner().and ( repo.newrequirementbuilder("osgi.wiring.package"). adddirective("filter","(osgi.wiring.package=foo.pkg1)"). buildexpression(), repo.newrequirementbuilder("osgi.identity"). adddirective("filter", "(license= buildexpression())); 16 of 53

17 Asynchronous Services & Promises 17 of 53

18 Async Services Asynchronously invoke services existing service new ones, written for async access Client invokes the service via a mediator Invocation returns quickly result can be obtained later 18 of 53

19 Async Services - example A typical service: p u b l i c i n t e r f a c e C a l c S e r v i c e { B i g I n t e g e r factorial(int num); } Invoke it asynchronously: C a l c S e r v i c e mysvc =... // from service registry A s y n c asyncservice =... // from service registry C a l c S e r v i c e mymediator = asyncservice.mediate(mysvc); f i n a l P r o m i s e <B i g I n t e g e r > p = asyncservice.call( mymediator.factorial( )); //... factorial invoked asynchronously... // callback to handle the result when it arrives p.onresolve(new R u n n a b l e () { p u b l i c v o i d run() { S y s t e m.o u t.println("found the answer: " + p.getvalue()); } }); 19 of 53

20 OSGi Promises Inspired by JavaScript Promises Make latency and errors explicit Provide async chaining mechanism Based on callbacks Promises are Monads Works with many (older) Java versions Designed to work with Java 8 CompletableFuture and Lambdas Used with Async Services Also useful elsewhere 20 of 53

21 OSGi Promises - example S u c c e s s <S t r i n g,s t r i n g > transformresult = n e w S u c c e s s <>() { p u b l i c P r o m i s e <S t r i n g > call(promise <S t r i n g > p) { r e t u r n P r o m i s e s.resolved(tohtml(p.getvalue())); } }; P r o m i s e <S t r i n g > p = asyncremotemethod(); p.then (validateresult).t h e n (transformresult).t h e n (showresult, showerror); 21 of 53

22 Declarative Services 22 of 53

23 RFC Declarative Services Enhancements Support of prototype scope Introspection API DTOs But most importantly of 53

24 Simplify Component ={ M y C o m p o n e n t.prop_enabled + ":Boolean=" + M y C o m p o n e n t.default_ena M y C o m p o n e n t.prop_topic + "=" + M y C o m p o n e n t.default_topic_1, M y C o m p o n e n t.prop_topic + "=" + M y C o m p o n e n t.default_topic_2, "service.ranking:integer=15" }) p u b l i c c l a s s M y C o m p o n e n t { s t a t i c f i n a l S t r i n g PROP_ENABLED = "enabled"; s t a t i c f i n a l S t r i n g PROP_TOPIC = "topic"; s t a t i c f i n a l S t r i n g PROP_USERNAME = "username"; s t a t i c f i n a l b o o l e a n DEFAULT_ENABLED = t r u e ; s t a t i c f i n a l S t r i n g DEFAULT_TOPIC_1 = "topica"; s t a t i c f i n a l S t r i n g DEFAULT_TOPIC_2 = "topicb"; 24 of 53

25 Simplify Component p r o t e c t e d v o i d activate(final M a p config) { f i n a l b o o l e a n enabled = P r o p e r t i e s U t i l.toboolean(config.get(prop_enabled), DEFAULT_ENABLED); i f ( enabled ) { t h i s.username = P r o p e r t i e s U t i l.tostring(config.get(prop_username), n u l l t h i s.topics = P r o p e r t i e s U t i l.tostringarray(config.get(prop_topic), n e w S t r i n g [] {DEFAULT_TOPIC_1, DEFAULT_TOPIC_2}); } } 25 of 53

26 Use annotations for M y C o n f i g { b o o l e a n enabled() d e f a u l t t r u e ; S t r i n g [] topic() d e f a u l t {"topica", "topicb"}; S t r i n g username(); i n t service_ranking() d e f a u l t 15; } 26 of 53

27 ...and reference them in lifecycle p u b l i c c l a s s M y C o m p o n e n t { S t r i n g username; S t r i n g [] topics; p r o t e c t e d v o i d activate(final M y C o n f i g config) { // note: annotation MyConfig used as interface i f ( config.enabled() ) { t h i s.username = config.username(); t h i s.topics = config.topic(); } } 27 of 53

28 ...or even p u b l i c c l a s s M y C o m p o n e n t { p r i v a t e M y C o n f i g configuration; p r o t e c t e d v o i d activate(final M y C o n f i g config) { // note: annotation MyConfig used as interface i f ( config.enabled() ) { t h i s.configuration = config; } } 28 of 53

29 Annotation Mapping Fields registered as component properties Name mapping (_ ->.) Type conversion for configurations 29 of 53

30 Additional Metatype Support (RFC Component", description="coolest component in the M y C o n f i g description="topic and user name are used if enabled") b o o l e a n enabled() d e f a u l t t r u e S t r i n g [] topic() d e f a u l t {"topica", S t r i n g username(); } i n t service_ranking() d e f a u l t 15; // maps to service.ranking 30 of 53

31 RFC Declarative Services Enhancements Annotation configuration support Support of prototype scope Introspection API DTOs 31 of 53

32 HTTP Service 32 of 53

33 Http Whiteboard Service RFC 189 Whiteboard support Servlet API 3+ Support and Introspection API 33 of 53

34 Whiteboard Servlet = javax.servlet.servlet.c l a s s, scope="prototype", p r o p e r t y ={ "osgi.http.whiteboard.servlet.pattern=/products/*", }) p u b l i c c l a s s M y S e r v l e t e x t e n d s H t t p S e r v l e t {... } 34 of 53

35 Whiteboard Servlet Filter = javax.servlet.filter.c l a s s, scope="prototype", p r o p e r t y ={ "osgi.http.whiteboard.filter.pattern=/products/*", }) p u b l i c c l a s s M y F i l t e r i m p l e m e n t s F i l t e r {... } 35 of 53

36 Additional Support Most listener types are supported Register with their interface Error Pages and Resources Shared and segregated HttpContexts Target Http Service 36 of 53

37 37 of 53 Cloud

38 38 of 53 Current PaaS offerings...

39 39 of 53 OSGi Cloud Ecosystems PaaS

40 An OSGi cloud ecosystem... Many frameworks hosting a variety of deployments Together providing The Application Not a bunch of replicas rather a collection of different nodes with different roles working together some may be replicas Load varies over time... and so does your cloud system topology configuration number of nodes depending on the demand 40 of 53

41 To realize this you need... Information! need to know what nodes are available ability to react to changes Provisioning capability Remote invocation inside your cloud system to get nodes to communicate either directly or as a means to set up communication channels 41 of 53

42 RFC Cloud Ecosystems FrameworkNodeStatus service: information about each Cloud node accessible as a Remote Service throughout the ecosystem Information such as: Hostname/IP address Location (country etc) OSGi and Java version running A REST management URL Runtime metadata Available memory / disk space Load measurement... you can add custom metadata too of 53

43 43 of 53 FrameworkNodeStatus service properties

44 RFC REST API A cloud-friendly remote management API works great with FrameworkNodeStatus Example: addingservice(servicereference <F r a m e w o r k N o d e S t a t u s > r e f ) { // A new Node became available S t r i n g url = r e f.getproperty("org.osgi.node.rest.url"); R e s t C l i e n t rc = n e w R e s t C l i e n t (n e w URI(url)); } // Provision the new node rc.installbundle(...); rc.startbundle(...); 44 of 53

45 Additional ideas in RFC 183 Special Remote Services config type osgi.configtype.ecosystem defines supported Remote Service data types not visible outside of cloud system Ability to intercept remote service calls can provide different service for each client can do invocation counting (quotas, billing) Providing remote services meta-data quota exceeded payment needed maintenance scheduled 45 of 53

46 Current OSGi cloud work Provides a base line to build fluid cloud systems portability across clouds Where everything is dynamic nodes can be repurposed... and you deal with your cloud nodes through OSGi services 46 of 53

47 Type and Package Annotations 47 of 53

48 Semantic Versioning is a versioning policy for exported packages. OSGi versions: <major>.<minor>.<micro>.<qualifier> Updating package versions: fix/patch (no change to API): update micro extend API (affects implementers, not clients): update minor API breakage: update major Note: not always used for bundle versions 48 of 53

49 RFC 197 OSGi Type and Package Annotations Annotations for documenting semantic versioning information Class @ConsumerType 49 of 53

50 Other Enterprise Spec updates 50 of 53

51 Remote Service Admin 1.1 Remote Service registration modification Subsystems 1.1 Provide Deployment Manifest separately Many small enhancements Portable Java SE/EE Contracts 51 of 53

52 Where can I get it? Core R6 spec released this week: ( Enterprise R6 draft released this week: ( RFCs 189, 190, 208 included in zip All current RFCs at ( 52 of 53

53 53 of 53 Questions?