Mailing-List: contact stanbol-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stanbol-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
Sender: me@farewellutopia.com
Date: Thu, 11 Aug 2011 15:00:34 +0200
Message-ID: 
 <CALvhUEWbGUUfzpy=jHrWcQ-O84KSwt+5SMQG0oreWUHvwbdHeg@mail.gmail.com>
Subject: Registering individual jax-rs resources
From: =?ISO-8859-1?Q?Reto_Bachmann=2DGm=FCr?= <reto@apache.org>
To: stanbol-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hello

As you might know the registration of JAX-RS resources is different in
Stanbol and in Clerezza, this is the main reason one cannot run the
two UIs simultaneously. It would however be handy to have some of the
clerezza tools (like graph-management and backup) available in stanbol
as well.

In clerezza a jax-rs resource is simply a service, in stanbol we have
WebFragment-services that provide jax-rs resources as well as some
non-jax-rs that make up a web-fragment. I've written a component that
picks up clerezza style root-resources and wrapps them for Stanbol.

The wrapper looks like this:

/**
 * A WebFragment holding one Jax-rs resource
 */
class ResourceHolder(component: Object) extends WebFragment {

    def getName() = component.getClass.getName

    def getStaticResourceClassPath(): String = null

    import java.util._
    def getJaxrsResourceClasses(): Set[Class[_]] =
Collections.emptySet[Class[_]]

    def getJaxrsResourceSingletons(): Set[Object] =
Collections.singleton(component);

    def getTemplateLoader(): TemplateLoader = null;

    def getLinkResources(): List[LinkResource] =
Collections.emptyList[LinkResource]

    def getScriptResources(): List[ScriptResource] =
Collections.emptyList[ScriptResource];

    def getNavigationLinks(): List[NavigationLink] =
Collections.emptyList[NavigationLink];

    def getBundleContext(): BundleContext = null;
}

The log output indicates that for every new fragment jersey is reinitialized:

2011-08-11 14:34:40,856 [ForkJoinPool-1-worker-15] INFO
ForkJoinPool-1-worker-15
org.apache.stanbol.webfragmentcreator.WFCreator - regstering:
org.apache.clerezza.rdf.web.core.PlatformRestorer@16e4d6b
2011-08-11 14:34:40,887 [ForkJoinPool-1-worker-15] INFO
ForkJoinPool-1-worker-15
org.apache.stanbol.commons.web.base.JerseyEndpoint - Unregistering
aliases [/static/home, /static/enhancer, /static/entityhub,
/static/owl, /static/ontonet, /static/rules, /]
2011-08-11 14:34:40,888 [ForkJoinPool-1-worker-15] INFO
ForkJoinPool-1-worker-15
org.apache.stanbol.commons.web.base.JerseyEndpoint - Initializing the
Jersey subsystem
2011-08-11 14:34:40,888 [ForkJoinPool-1-worker-15] INFO
ForkJoinPool-1-worker-15
org.apache.stanbol.commons.web.base.JerseyEndpoint - Registering web
fragment 'home' into jaxrs application
2011-08-11 14:34:40,888 [ForkJoinPool-1-worker-15] INFO
ForkJoinPool-1-worker-15
org.apache.stanbol.commons.web.base.JerseyEndpoint - Registering web
fragment 'sparql' into jaxrs application
...
2011-08-11 14:34:40,905 [ForkJoinPool-1-worker-15] INFO
ForkJoinPool-1-worker-15
org.apache.stanbol.commons.web.base.JerseyEndpoint - Registering web
fragment 'org.apache.clerezza.rdf.web.core.PlatformRestorer' into
jaxrs application
2011-08-11 14:34:40,906 [ForkJoinPool-1-worker-15] INFO
ForkJoinPool-1-worker-15
com.sun.jersey.server.impl.application.WebApplicationImpl - Initiating
Jersey application, version 'Jersey: 1.7 05/20/2011 11:04 AM'

However I cannot access the my root resources wrapped by the above
wrapper. Is there any other requirement of the JerseyEndpoint to
actually register the resource with Jersey?

Cheers,
Reto