cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: The OSGi fundament
Date Tue, 23 May 2006 09:51:20 GMT
A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1151.html

Document ID: 1151
Branch: main
Language: default
Name: The OSGi fundament (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 5/23/06 9:51:02 AM
Updated by: Reinhard Pötz

A new version has been created, state: publish

Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 14720 bytes (previous version: 14023 bytes)
Content diff:
(23 equal lines skipped)
    
    <p><img daisy-caption="UML 2 component diagram" src="daisy:1160"/></p>
    
--- <p class="warn">Not everything implemented yet!</p>
+++ <p>The implementation can be found in following packages (the links below refer
+++ to the package in SVN)</p>
    
--- <p>First a little bit about Declarative Services (DS), that is used everywhere
--- in the design and replaces<tt> block.xml</tt> among other things in the current
--- design.</p>
+++ <ul>
+++ <li>
+++ <a href="http://svn.apache.org/repos/asf/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/core/osgi/">org.apache.cocoon.core.osgi</a>
+++ - cocoon-core module</li>
+++ <li>
+++ <a href="http://svn.apache.org/repos/asf/cocoon/trunk/core/cocoon-blocks-fw/cocoon-blocks-fw-impl/src/main/java/org/apache/cocoon/blocks/">org.apache.cocoon.blocks</a>
+++ - cocoon-blocks-fw-impl</li>
+++ </ul>
    
+++ <p class="note">Not everything implemented yet, but most of the parts described
+++ in the document here, already work! If you want to give it a try, see the
+++ <a href="daisy:1153">Using Cocoon 3.0 with Eclipse</a> tutorial.</p>
+++ 
+++ <p>First a little bit about <strong>Declarative Services</strong> (DS),
that is
+++ used everywhere in the design and replaces<tt> block.xml</tt> among other
things
+++ in the current design.</p>
+++ 
    <h1>Declarative Services</h1>
    
    <p>Declarative services simplify service (component) handling in OSGi by making
(13 equal lines skipped)
    
    <h1>The dispatcher</h1>
    
--- <p>The role of the dispatcher (ServletRegistrationActivator) is that the blocks
--- (servlets) are mounted in it based together with their URI prefixes. The
--- dispatcher then calls the blocks based on the incoming URIs. This is already
+++ <p>The role of the dispatcher (<tt>ServletRegistrationActivator</tt>)
is that
+++ the blocks (servlets) are mounted in it based together with their URI prefixes.
+++ The dispatcher then calls the blocks based on the incoming URIs. This is already
    handled by the OSGi HTTP service which provides a service that a servlet can
    lookup and register itself in. <br/>
    A HTTP service implementation normally contains a HTTP server. But an
(223 equal lines skipped)


Fields
======
no changes

Links
=====
no changes

Custom Fields
=============
no changes

Collections
===========
no changes

Mime
View raw message