Apache Sling is an innovative REST based Web Framework which has been developped from the ground up as an OSGi based server side application. After a short introduction to Sling itself I will also show why OSGi has been chosen as the basis for the application.

1. Server Side OSGi with Apache Sling Felix Meschberger | Sr. Computer Scientist, Adobe Systems

3. fmeschbe@adobe.com

4. http://blog.meschberger.ch

6. Configuration Admin

8. OSGi Alliance Supporter

10. Why OSGi ?

11. What parts of OSGi ?

12. Advantages and Problems

14. Content-driven (JCR, JSR-170/283)

15. Powered by OSGi

16. Scripting inside (Java Scripting, JSR-223)

17. Apache Open Source Projekt (http://sling.apache.org)

18. Sling Architecture OSGi Framework Felix Web Console WebDAV Server browser filesystem debugger HTTP JSR-170/283 API JCR repository resource resolution servlet resolution standard servlets custom servlets JSR223 Scripting JSP javascript etc.

20. Files in the Filesystem

22. GET for reading only

24. Accept request header currently ignored

25. Sling URL Decomposition /content/cars/audi/s4.details.html

27. Resources maintained in Resource Tree

28. Resources accessed by path in the Resource Tree

29. Request Method, Extension and Selectors define „Method“ to call

31. Resource Super Type

32. „Root Type“: sling/servlet/default

34. JSON

36. Extensible

38. Sakai 3 (http://www.sakaiproject.org)

39. Tuberculosis Project

40. Idium Web (http://www.idium.no/no/idium_web)

41. http://cwiki.apache.org/SLING/who-is-using-sling-.html

43. Why OSGi ?

44. What parts of OSGi ?

45. Advantages and Problems

47. Declared Dependencies

48. Intermodule Communication

49. Lightweight Framework

51. Systems not really dynamic

54. Why OSGi ?

55. What parts of OSGi ?

56. Advantages and Problems

58. Configuration Admin Service

59. Meta Type Service

60. Declarative Services

61. Event Admin Service

62. Log Service

63. HTTP Service

65. Small Footprint Launcher (~30K)

66. Framework in its own ClassLoader

67. Restart of Framework

68. Update of Framework

70. Http Service implementation is the key

72. Provides functionality to pass configuration to consumers

73. Hides persistance problems

75. JCR Install updates through repository

78. Configuration Admin GUI in Web Console supports Metatype Service descriptors

80. Configuration support

83. Apache Felix iPOJO (Successor)

84. Blueprint (OSGi Compendium Specification R 4.2)

85. Peaberry

87. Support for synchronous and asynchronous events

89. Extended to allow for event distribution in Cluster

91. Based on SLF4J API

93. SLF4J Logging

94. Commons Logging

96. Log Levels and Log Format per Logger

97. Multiple Log Files with size and time rotation

105. Deploy Configuration Admin configurations via JCR Repository

107. Why OSGi ?

108. What parts of OSGi ?

109. Advantages and Problems

111. Better Isolation through explicit exports and private classes

112. Classloader Isolation

113. Extensibility built-in, not built-ontop

114. Dynamism

118. Karaf features (Sling provides feature.xml)

120. http://sling.apache.org

121. Apache Felix OSGi Framework and Compendium Service implementations

122. http://felix.apache.org

123. Apache Jackrabbit The JCR (JSR-170/283) Reference Implementation

124. http://jackrabbit.apache.org

125. Day Developer's Home

126. http://dev.day.com

127. Questions

128. Thank you very much !