OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [AAA-231] Resources not found with web-osgi-impl https://jira.opendaylight.org/browse/AAA-231 aaa <p>After berman-02 removal it's no more possible to access swagger UI at:</p> <p><a href="http://localhost:8181/apidoc/explorer/index.html," class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/apidoc/explorer/index.html</a></p> <p>nor</p> <p><a href="http://localhost:8181/apidoc/18/explorer/index.html." class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/apidoc/18/explorer/index.html</a></p> <p>On both sites we get HTTP ERROR 404 Not Found.</p> AAA-231 Resources not found with web-osgi-impl Bug Medium Resolved Done Ivan Martiniak Ivan Hrasko Wed, 24 Aug 2022 14:59:03 +0000 Fri, 16 Sep 2022 18:12:09 +0000 Tue, 13 Sep 2022 10:56:44 +0000 0.16.0 0.16.1 0.16.2 General 0 3 <p><a href="http://localhost:8181/apidoc/18/explorer/index.html" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/apidoc/18/explorer/index.html</a> is not available on Sulfur SR1, too.</p> <p>IMO: probably different WebInitializers dont play together well.</p> <p>Possible problems: auth redirect, support sessions, missing resources "explorer/index.html".</p> <p>In Lighty.io using NETCONF 4.0.1 swagger UI works - with no credentials.</p> <p>Eventually, bierman removal was not an issue. The original reason was change of web server implementation, from pax-web to whiteboard, and its inconsistencies. The description with further details is in patch <a href="https://git.opendaylight.org/gerrit/c/aaa/+/102350" class="external-link" target="_blank" rel="nofollow noopener">#102350</a>.</p> <p>So there are two issues</p> <ul> <li>path mapping for HTTP Whiteboard, tracked by <a href="https://jira.opendaylight.org/browse/AAA-230" title="web-impl-osgi mis-represents servlet paths" class="issue-link" data-issue-key="AAA-230"><del>AAA-230</del></a></li> <li>/explorer path specification, tracked by this issue</li> </ul> <p>So the semantics for resource alias/name is coming from  <a href="https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.http.html#org.osgi.service.http.HttpService" class="external-link" target="_blank" rel="nofollow noopener">OSGi HTTP Service</a> specification. The OSGi implementation needs to take this into account and use alias for patterns (updated appropriately).</p> Issue split AAA-230 Development Rank 0|i042xb: