PaxWeb: Whiteboard and compliance to the R6 specification

2017-08-07 Thread Jérémie Brébec
Hello,

I don't know if PaxWeb intends to be compliant to the whiteboard R6 
specification. However, the following items are not compliant :

- Every Whiteboard component which doesn't target a ServletContextHelper 
should use a default shared ServletContext (linked to a 
ServletContextHelper named "default"). Today, these elements doesn't share 
the same ServletContext
- It should be possible for a Whiteboard component to target multiple 
ServletContextHelper (the spec advises to use the "prototype" scope when 
implementing a whiteboard component) : the whiteboard implementation should 
instantiate (with ServiceObjects) a new instance for every target
- It should be possible to target a ServletContextHelper with an osgi 
filter : Today, PaxWeb assume the filter is only matching the name of the 
ServletContextHelper
- It should be possible to override any ServletContextHelper (including the 
"default" one)
- Every ServletContextHelper should be resolved in the context of the 
bundle of the whiteboard component using it (the spec advises to use the 
"prototype" scope when implementing a ServletContextHelper)
- Every Whiteboard component have a delegating "ServletContext", which 
delegate to the shared ServletContext, and the ServletContextHelper

Is there a planned roadmap on these items/jira issues ?

Regards,
Jérémie

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: PaxWeb: Whiteboard and compliance to the R6 specification

2017-08-07 Thread Marc Schlegel
Hi Jérémie

We definately want to be spec-compliant and I didnt realize that there are 
so many points missing. I know we have some parts missing regarding the 
whiteboard-dtos (mostly error cases).

Do you already have access to our Jira? If not, we can add you there so you 
can submit a bug-report. Since we need to check the spec, it would be 
helpfull if you could provide a section where we can find the missing 
requirements.

We usually keep track of the features by integration-tests [1] and samples 
provided by Pax-Web. For example, we have a sample project which uses R6 
whiteboard services [2].
It would be highly appreciated if you could send us a pull-request with an 
updated integration-test or sample which uses the missing pieces.

regards
Marc

[1] 
https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WhiteboardR6IntegrationTest.java
[2] 
https://github.com/ops4j/org.ops4j.pax.web/tree/master/samples/whiteboard-ds/src/main/java/org/ops4j/pax/web/samples/whiteboard/ds

Am Montag, 7. August 2017 20:42:34 UTC+2 schrieb Jérémie Brébec:
>
> Hello,
>
> I don't know if PaxWeb intends to be compliant to the whiteboard R6 
> specification. However, the following items are not compliant :
>
> - Every Whiteboard component which doesn't target a ServletContextHelper 
> should use a default shared ServletContext (linked to a 
> ServletContextHelper named "default"). Today, these elements doesn't share 
> the same ServletContext
> - It should be possible for a Whiteboard component to target multiple 
> ServletContextHelper (the spec advises to use the "prototype" scope when 
> implementing a whiteboard component) : the whiteboard implementation should 
> instantiate (with ServiceObjects) a new instance for every target
> - It should be possible to target a ServletContextHelper with an osgi 
> filter : Today, PaxWeb assume the filter is only matching the name of the 
> ServletContextHelper
> - It should be possible to override any ServletContextHelper (including 
> the "default" one)
> - Every ServletContextHelper should be resolved in the context of the 
> bundle of the whiteboard component using it (the spec advises to use the 
> "prototype" scope when implementing a ServletContextHelper)
> - Every Whiteboard component have a delegating "ServletContext", which 
> delegate to the shared ServletContext, and the ServletContextHelper
>
> Is there a planned roadmap on these items/jira issues ?
>
> Regards,
> Jérémie
>

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.