Sure. I can come up with a PAX-Exam test. We're a big slammed right now. 
I'll try to get around to it early next week.

As for implications. I am concerned that sometime later there's code using 
the servlet-name as the internal bundle path. In this case we'd need to 
either add a new member to the mapping classes or if there's no visibility 
on that add some code that substrings the servlet-name after the 
composite-key delimiter.

-Nick Baker


On Friday, February 24, 2017 at 3:36:39 AM UTC-5, Marc Schlegel wrote:
>
> Hi Nick
>
> Thanks for spotting this. Your solution sounds reasonable, but we need to 
> check the implications.
> Could you please file a Jira-issue [1] and provide an example how you 
> configure two colliding resources, so we can add this case to our 
> integration-tests
>
> regards
> Marc
>
> [1] https://ops4j1.jira.com/projects/PAXWEB/issues
>
> Am Donnerstag, 23. Februar 2017 22:14:01 UTC+1 schrieb Nick Baker:
>>
>> Hello All,
>>
>> We're experiencing an issue with bundles supplying Resource mappings. It 
>> appears that the internal path within the bundle is used as the servlet 
>> name [1]. Unfortunately, our teams love standards and conventions so 
>> they're using a "web" folder for all bundles supplying Resources. This was 
>> discovered on 3.1.4 but I've verified that the situation still exists in 
>> master.
>>
>> PAX-Web appropriately doesn't allow multiple servlets of the same name so 
>> we're loosing some resources upon startup of Karaf. The short-term solution 
>> for us was to ensure that each internal bundle path is unique. A better 
>> solution would be to modify PAX to create a composite key of bundle-id + 
>> path when creating the resource Servlet names. 
>>
>> [1] 
>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-extender-whiteboard/src/main/java/org/ops4j/pax/web/extender/whiteboard/internal/element/ResourceWebElement.java#L57-L57
>>
>> -Nick Baker
>>
>

-- 
-- 
------------------
OPS4J - http://www.ops4j.org - [email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to