[jira] [Assigned] (FELIX-5883) Add support to enable and configure the jetty GzipHandler to the entire server
[ https://issues.apache.org/jira/browse/FELIX-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-5883: --- Assignee: Carsten Ziegeler > Add support to enable and configure the jetty GzipHandler to the entire server > -- > > Key: FELIX-5883 > URL: https://issues.apache.org/jira/browse/FELIX-5883 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.jetty-4.0.0, http.jetty-4.0.2 >Reporter: Eric Norman >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty-4.0.4 > > > > As per [1], jetty provides a GzipHandler that fixes many of the bugs in > commonly available compression filters. Unlike 3rd party GzipFilters, this > mechanism works with asynchronously generated responses and does not need to > wrap the response or it's output stream. Instead it uses the efficient > HttpOutput.Interceptor mechanism. > It should be possible to enable and configure this GzipHandler with Felix > Http Jetty. > # https://www.eclipse.org/jetty/documentation/9.4.x/gzip-filter.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FELIX-5883) Add support to enable and configure the jetty GzipHandler to the entire server
[ https://issues.apache.org/jira/browse/FELIX-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-5883: Fix Version/s: http.jetty-4.0.4 > Add support to enable and configure the jetty GzipHandler to the entire server > -- > > Key: FELIX-5883 > URL: https://issues.apache.org/jira/browse/FELIX-5883 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.jetty-4.0.0, http.jetty-4.0.2 >Reporter: Eric Norman >Priority: Major > Fix For: http.jetty-4.0.4 > > > > As per [1], jetty provides a GzipHandler that fixes many of the bugs in > commonly available compression filters. Unlike 3rd party GzipFilters, this > mechanism works with asynchronously generated responses and does not need to > wrap the response or it's output stream. Instead it uses the efficient > HttpOutput.Interceptor mechanism. > It should be possible to enable and configure this GzipHandler with Felix > Http Jetty. > # https://www.eclipse.org/jetty/documentation/9.4.x/gzip-filter.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FELIX-5883) Add support to enable and configure the jetty GzipHandler to the entire server
[ https://issues.apache.org/jira/browse/FELIX-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-5883: Affects Version/s: http.jetty-4.0.2 > Add support to enable and configure the jetty GzipHandler to the entire server > -- > > Key: FELIX-5883 > URL: https://issues.apache.org/jira/browse/FELIX-5883 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.jetty-4.0.0, http.jetty-4.0.2 >Reporter: Eric Norman >Priority: Major > Fix For: http.jetty-4.0.4 > > > > As per [1], jetty provides a GzipHandler that fixes many of the bugs in > commonly available compression filters. Unlike 3rd party GzipFilters, this > mechanism works with asynchronously generated responses and does not need to > wrap the response or it's output stream. Instead it uses the efficient > HttpOutput.Interceptor mechanism. > It should be possible to enable and configure this GzipHandler with Felix > Http Jetty. > # https://www.eclipse.org/jetty/documentation/9.4.x/gzip-filter.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FELIX-5883) Add support to enable and configure the jetty GzipHandler to the entire server
[ https://issues.apache.org/jira/browse/FELIX-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-5883. - Resolution: Fixed Thanks for your patch [~edn]. It's applied > Add support to enable and configure the jetty GzipHandler to the entire server > -- > > Key: FELIX-5883 > URL: https://issues.apache.org/jira/browse/FELIX-5883 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.jetty-4.0.0, http.jetty-4.0.2 >Reporter: Eric Norman >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty-4.0.4 > > > > As per [1], jetty provides a GzipHandler that fixes many of the bugs in > commonly available compression filters. Unlike 3rd party GzipFilters, this > mechanism works with asynchronously generated responses and does not need to > wrap the response or it's output stream. Instead it uses the efficient > HttpOutput.Interceptor mechanism. > It should be possible to enable and configure this GzipHandler with Felix > Http Jetty. > # https://www.eclipse.org/jetty/documentation/9.4.x/gzip-filter.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FELIX-5786) DS does not propagate activation exceptions from ComponentFactory.newInstance()
[
https://issues.apache.org/jira/browse/FELIX-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16541361#comment-16541361
]
Todor Boev commented on FELIX-5786:
---
Maybe the exception can be stored in a field instead?
> DS does not propagate activation exceptions from
> ComponentFactory.newInstance()
> ---
>
> Key: FELIX-5786
> URL: https://issues.apache.org/jira/browse/FELIX-5786
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.14
>Reporter: Todor Boev
>Priority: Minor
>
> For Factory Components when {{ComponentFactory.newInstance()}} is called and
> this leads to a failure of the component {{activate()}} method the exception
> that method throws is not propagated to the caller of
> {{ComponentFactory.newInstance()}}.
> Although the DS spec does not seem to require that this error propagation is
> done nevertheless this seems like a natural thing to expect on one hand and
> on another it can be extremely useful for certain use cases.
> The use case that exposed this is:
> - A server offers the uses means to create service components
> - The components are created from data received in the rest request - not
> from configuration.
> - The users expect synchronous reply of success or failure. In case of
> failure the users must get a meaningful error message.
> - The activate() method validates the configuration and fails with an
> exception if invalid.
> - The exception is retrieved from {{ComponentException.getCause()}} and the
> error is sent back in the rest reply.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FELIX-5884) HTTP Jetty Managed Service Factory (Factory Configuration) not working
Jorge Cercas created FELIX-5884:
---
Summary: HTTP Jetty Managed Service Factory (Factory
Configuration) not working
Key: FELIX-5884
URL: https://issues.apache.org/jira/browse/FELIX-5884
Project: Felix
Issue Type: Bug
Components: HTTP Service
Affects Versions: http.jetty-4.0.0
Environment: - Linux
- Apache Felix Framework 6.0.0
- Apache Felix Fileinstall 3.6.4
- Apache Felix ConfigAdmin 1.9.2
- SCR 2.1.0
- org.apache.felix.http.servlet-api 1.1.2
- org.apache.felix.http.jetty 4.0.0
- org.apache.felix.http.whiteboard 4.0.0
Reporter: Jorge Cercas
When providing multiple org.apache.felix.http PID's in order to create multiple
Jetty services on different ports, the HTTP Jetty 4.0.0 implementation never
creates more than one. The same setup works with version 3.4.8.
+*Sample setup*+
- config file *org.apache.felix.http.cfg*:
{code:java}
org.apache.felix.http.enable=false
{code}
- config file *org.apache.felix.http-8081.cfg*:
{code:java}
org.apache.felix.http.enable=true
org.osgi.service.http.port=8081
{code}
- config file *org.apache.felix.http-8082.cfg*:
{code:java}
org.apache.felix.http.enable=true
org.osgi.service.http.port=8082
{code}
With the above setup, the observed behaviour is that only port 8082 is
accessible.
+*Captured logs*+
{code:java}
Started Jetty 9.4.9.v20180320 at port(s) HTTP:8081 on context path /
[minThreads=8,maxThreads=200,acceptors=1,selectors=4]
ServiceEvent REGISTERED - [org.osgi.service.http.HttpService] -
org.apache.felix.http.jetty
ServiceEvent REGISTERED - [org.osgi.service.http.runtime.HttpServiceRuntime] -
org.apache.felix.http.jetty
ServiceEvent REGISTERED - [org.osgi.service.http.context.ServletContextHelper]
- org.apache.felix.http.jetty
[ServiceReference 46 from bundle 17 : org.apache.felix.http.jetty:4.0.0
ref=[org.osgi.service.http.context.ServletContextHelper]
properties={objectClass=[org.osgi.service.http.context.ServletContextHelper],
osgi.http.whiteboard.context.name=default, osgi.http.whiteboard.context.path=/,
service.bundleid=17, service.id=46, service.ranking=-2147483648,
service.scope=bundle}] Ignoring shadowed ServletContextHelper service
[ServiceReference 41 from bundle 18 : jmdsc.osgi.example.http:1.0.0
ref=[jmdsc.osgi.example.http.user.UserResource] properties={component.id=0,
component.name=jmdsc.osgi.example.http.user.UserResource,
objectClass=[jmdsc.osgi.example.http.user.UserResource],
osgi.http.whiteboard.context.select=(osgi.http.whiteboard.context.name=Users),
osgi.http.whiteboard.resource.pattern=[/img/*],
osgi.http.whiteboard.resource.prefix=/META-INF/resources/users/img,
service.bundleid=18, service.id=41, service.scope=bundle}] Ignoring unmatching
Resource service
[ServiceReference 39 from bundle 18 : jmdsc.osgi.example.http:1.0.0
ref=[java.lang.Object] properties={objectClass=[java.lang.Object],
osgi.http.whiteboard.context.select=(osgi.http.whiteboard.context.name=App1),
osgi.http.whiteboard.resource.pattern=/img/*,
osgi.http.whiteboard.resource.prefix=/META-INF/resources/app1/img,
service.bundleid=18, service.id=39, service.scope=singleton}] Ignoring
unmatching Resource service
[ServiceReference 46 from bundle 17 : org.apache.felix.http.jetty:4.0.0
ref=[org.osgi.service.http.context.ServletContextHelper]
properties={objectClass=[org.osgi.service.http.context.ServletContextHelper],
osgi.http.whiteboard.context.name=default, osgi.http.whiteboard.context.path=/,
service.bundleid=17, service.id=46, service.ranking=-2147483648,
service.scope=bundle}] Ignoring shadowed ServletContextHelper service
[ServiceReference 42 from bundle 18 : jmdsc.osgi.example.http:1.0.0
ref=[javax.servlet.Servlet] properties={component.id=1,
component.name=jmdsc.osgi.example.http.user.UserServlet,
objectClass=[javax.servlet.Servlet],
osgi.http.whiteboard.context.select=(osgi.http.whiteboard.context.name=Users),
osgi.http.whiteboard.servlet.pattern=[/*], service.bundleid=18, service.id=42,
service.scope=bundle}] Ignoring unmatching Servlet service
ServiceEvent REGISTERED - [javax.servlet.Servlet] - org.apache.felix.http.jetty
ServiceEvent UNREGISTERING - [org.osgi.service.http.HttpService] -
org.apache.felix.http.jetty
ServiceEvent UNREGISTERING - [javax.servlet.Servlet] -
org.apache.felix.http.jetty
[ServiceReference 38 from bundle 18 : jmdsc.osgi.example.http:1.0.0
ref=[javax.servlet.Servlet] properties={objectClass=[javax.servlet.Servlet],
osgi.http.whiteboard.context.select=(osgi.http.whiteboard.context.name=App1),
osgi.http.whiteboard.servlet.pattern=/, service.bundleid=18, service.id=38,
service.scope=singleton}] Ignoring unmatching Servlet service
ServiceEvent UNREGISTERING -
[org.osgi.service.http.context.ServletContextHelper] -
org.apache.felix.http.jetty
ServiceEvent UNREGISTERING - [org.osgi.service.http.runtime.HttpServiceRuntime]
- org.apache.felix.http.jetty
Stopped Jet
[jira] [Created] (FELIX-5885) Felix SCR uses an overly restrictive import range for promises
Timothy Ward created FELIX-5885: --- Summary: Felix SCR uses an overly restrictive import range for promises Key: FELIX-5885 URL: https://issues.apache.org/jira/browse/FELIX-5885 Project: Felix Issue Type: Bug Components: Declarative Services (SCR) Affects Versions: scr-2.1.2 Reporter: Timothy Ward Fix For: scr-2.1.2 The Felix SCR bundle embeds the OSGi promise library at version 1.0 to make it easy to deploy DS. This is great, but the import range used is [1.0,1.1), which prevents users of the DS API from using promises 1.1. There should be no reason that Felix SCR needs to have a provider import range - it should be able to substitute any backward compatible version and use a range of [1,2). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FELIX-5885) Felix SCR uses an overly restrictive import range for promises
[ https://issues.apache.org/jira/browse/FELIX-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-5885: --- Assignee: Carsten Ziegeler > Felix SCR uses an overly restrictive import range for promises > -- > > Key: FELIX-5885 > URL: https://issues.apache.org/jira/browse/FELIX-5885 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) >Affects Versions: scr-2.1.0 >Reporter: Timothy Ward >Assignee: Carsten Ziegeler >Priority: Major > Fix For: scr-2.1.2 > > > The Felix SCR bundle embeds the OSGi promise library at version 1.0 to make > it easy to deploy DS. This is great, but the import range used is [1.0,1.1), > which prevents users of the DS API from using promises 1.1. > There should be no reason that Felix SCR needs to have a provider import > range - it should be able to substitute any backward compatible version and > use a range of [1,2). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FELIX-5885) Felix SCR uses an overly restrictive import range for promises
[ https://issues.apache.org/jira/browse/FELIX-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-5885: Affects Version/s: (was: scr-2.1.2) scr-2.1.0 > Felix SCR uses an overly restrictive import range for promises > -- > > Key: FELIX-5885 > URL: https://issues.apache.org/jira/browse/FELIX-5885 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) >Affects Versions: scr-2.1.0 >Reporter: Timothy Ward >Priority: Major > Fix For: scr-2.1.2 > > > The Felix SCR bundle embeds the OSGi promise library at version 1.0 to make > it easy to deploy DS. This is great, but the import range used is [1.0,1.1), > which prevents users of the DS API from using promises 1.1. > There should be no reason that Felix SCR needs to have a provider import > range - it should be able to substitute any backward compatible version and > use a range of [1,2). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FELIX-5885) Felix SCR uses an overly restrictive import range for promises
[ https://issues.apache.org/jira/browse/FELIX-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-5885. - Resolution: Fixed Fixed in rev 1835788 > Felix SCR uses an overly restrictive import range for promises > -- > > Key: FELIX-5885 > URL: https://issues.apache.org/jira/browse/FELIX-5885 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) >Affects Versions: scr-2.1.0 >Reporter: Timothy Ward >Assignee: Carsten Ziegeler >Priority: Major > Fix For: scr-2.1.2 > > > The Felix SCR bundle embeds the OSGi promise library at version 1.0 to make > it easy to deploy DS. This is great, but the import range used is [1.0,1.1), > which prevents users of the DS API from using promises 1.1. > There should be no reason that Felix SCR needs to have a provider import > range - it should be able to substitute any backward compatible version and > use a range of [1,2). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
