[
https://issues.apache.org/jira/browse/SLING-11728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696041#comment-17696041
]
Carsten Ziegeler commented on SLING-11728:
------------------------------------------
[~olli] I think
[https://github.com/apache/sling-org-apache-sling-engine/commit/1cef49c5e1a5dd1c5240416864e5d3971e810da8]
fixes the problem. The tests in servlets resolver pass with using the new and
the old interface now. Its not the nicest solution, but should do the trick. It
also shows that code registering with the old interface still works and we
don't break code.
> Remove bi-directional dependencies between Engine and Servlets Resolver
> -----------------------------------------------------------------------
>
> Key: SLING-11728
> URL: https://issues.apache.org/jira/browse/SLING-11728
> Project: Sling
> Issue Type: Improvement
> Components: API, Engine, Servlets
> Affects Versions: Engine 2.12.0
> Reporter: Oliver Lietz
> Assignee: Oliver Lietz
> Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> *Situation*
> * bundle {{org.apache.sling.engine}} requires a {{ServletResolver}} which is
> provided by bundle {{org.apache.sling.servlets.resolver}}
> * bundle {{org.apache.sling.servlets.resolver}} depends on
> {{org.apache.sling.engine.servlets}} API
> The bi-directional dependencies between Engine and Servlets Resolver prevent
> the creation of meaningful and light deployment units (testing, features).
> *Options*
> # Merge {{org.apache.sling.engine}} and
> {{org.apache.sling.servlets.resolver}} into a single entity (bundle)
> # Move {{org.apache.sling.engine.servlets.ErrorHandler}} into Sling API
> (package {{org.apache.sling.api.servlets}}) and adjust usage in Servlets
> Resolver
> # Keep as is – leading to bigger, less manageable deployment units
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
