On 24 March 2011 10:51, Olivier Grisel <[email protected]> wrote: > 2011/3/24 Fabian Christ <[email protected]>: >> Thinking about this, >> >> what about an new bundle >> >> org.apache.stanbol.welcome >> or >> org.apache.stanbol.doc >> >> this bundle would include >> >> * A welcome and intro page to Stanbol >> * Links to API docs that are generated and automatically included in this >> bundle >> * same for REST API docs >> * Further documentation >> * (Interactive) demos/tutorials that show how to use Stanbol >> >> To start this bundle would use the existing pages from the >> enhancer/jersey bundle. >> >> And as I'm working on something similar for the IKS project I would >> like to work on this in Stanbol. People who create new features for >> Stanbol can easily provide demos this way. >> >> WDYT? >> >> Best, >> - Fabian >> >> 2011/3/24 Fabian Christ <[email protected]>: >>> Hi, >>> >>> currently you have to use the Stanbol Enhancer Jersey bundle to get >>> the enhancement functionality. This bundle registers the root resource >>> on "/" and presents a nice intro page when going to localhost:8080. >>> >>> When you are in a scenario where you want to include Stanbol in >>> another technology stack, e.g. the IKS, you don't want this behaviour >>> as you would like to control what happens on root "/". >>> >>> I think it's nice that Stanbol provides this starting screen but what >>> about to map it localhost:8080/stanbol or something similar? Or should >>> we split this and create an own welcome screen bundle. Then an >>> integrator can decide whether to load this bundle or not. Perhaps this >>> could be refactored into an online documentation/demo bundle? >>> >>> WDYT? > > I would rather extract the generic part (the OSGi component, the > RootResource, ...) of stanbol/enhancer/jersey into a toplevel > stanbol/web or stanbol/jersey and have the stanbol/enhancer/jersey > keep the JAX-RS resources related to enhancement of content items that > would incrementally contribute to the OSGi HTTP endpoint, contributing > both the implementation of the JAX-resource and the API documentation > of the resource. Why don't separate the stanbol rest commons and the welcome/demo staff? > > -- > Olivier > http://twitter.com/ogrisel - http://github.com/ogrisel >
-- Enrico Daga -- http://www.enridaga.net skype: enri-pan
