You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/01/29 12:07:35 UTC

[jira] Resolved: (SLING-206) servlet not picked up by resolver unless i restart my bundle

     [ https://issues.apache.org/jira/browse/SLING-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-206.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Fixed in Rev. 616254 by delaying the actual binding of ResourceProviders until after the JcrResourceResolverFactoryImpl component is activated and the ComponentContext is available.

Please close this issue if this fixes your problem. Thanks.

> servlet not picked up by resolver unless i restart my bundle
> ------------------------------------------------------------
>
>                 Key: SLING-206
>                 URL: https://issues.apache.org/jira/browse/SLING-206
>             Project: Sling
>          Issue Type: Bug
>          Components: ServletResolver
>            Reporter: Tobias Bocanegra
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>         Attachments: config_status.txt
>
>
> i have a servlet that is registered with a primary type of a node.
> just after startup, a request to a node with that primary type shows
> the dump of the default servlet. after i restart my bundle that
> contains the servlet (stop/start) the next request is then handled by
> my servlet.

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