[ 
https://issues.apache.org/jira/browse/WINK-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851123#action_12851123
 ] 

Bryant Luk commented on WINK-269:
---------------------------------

Yes, that's a conflicting statement but the maven-bundle-plugin actually makes 
export win.  I'll remove it in the patch.  When I originally developed the 
patch, I thought I could make the internal code private (hence there's actually 
comments to not export the internal packages).  However, with the way that Wink 
is currently written and if each wink-common, wink-server, etc. JAR was an OSGi 
bundle, then the wink-server bundle for instance couldn't access internal 
wink-common code.  I guess I could re-write these internal private calls but I 
think that's complicating something even further.  Even though technically they 
are suppose to be private, we didn't really change anything internally so I 
don't want to break people for no reason.

We can also discuss making a public RestServlet if that is more appealing for 
people to call.

> org.apache.wink.server.internal.servlet.RestServlet should be made as a SPI 
> and exported to OSGi
> ------------------------------------------------------------------------------------------------
>
>                 Key: WINK-269
>                 URL: https://issues.apache.org/jira/browse/WINK-269
>             Project: Wink
>          Issue Type: Wish
>            Reporter: Raymond Feng
>
> In Apache Tuscany, we try to integrate wink to support JAX-RS with a plugable 
> http container (such as embedded Tomcat/Jetty or OSGi http service). We need 
> to create the RestServlet and register it to our HTTP servlet host. This is 
> different from the web.xml configuration for a fully-blown web app.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to