[STANBOL-120] Refactor HTTP Endpoint

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0-incubating
• Component/s: Enhancer, Web
• Labels: Endpoint HTTP Refactoring
• Assignee: Alessandro Adamou
• Reporter: Fabian Christ
• Created: 24/Mar/11 11:57
• Updated: 02/May/13 02:29
• Resolved: 05/Apr/11 07:34

Description

The Stanbol HTTP endpoint entry point is currently packaged in the enhancer/jersey bundle.

The HTTP endpoint should be refactored into its own top level OSGi bundle called org.apache.stanbol.web. Other components, like the enhancer, can then contribute their JAXRS resources to this top level bundle.

The top level web bundle should not have any knowledge about concrete bundles that contribute their JAXRS resources to this web bundle.

• New bundles register their JAXRS resources at the commons web bundle.
• The commons web bundle is responsible for making the resources available.

Issue Links

• is depended upon by: STANBOL-136 Stanbol Web GUI should consider configured alias when creating links
• is depended upon by: STANBOL-144 Refactor Entity hub's HTTP Jersey Endpoint
• is depended upon by: STANBOL-151 Refactor Store's Jersey HTTP Endpoint
• relates to: STANBOL-128 Refactoring the KReS Jersey module