[jira] [Commented] (FELIX-4866) Improve service registry
[ https://issues.apache.org/jira/browse/FELIX-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545978#comment-14545978 ] Pierre De Rop commented on FELIX-4866: -- Since the bndtools project is a bit too large to be attached, I have committed it in my sandbox ([1]). Thank you. [1] http://svn.apache.org/viewvc/felix/sandbox/pderop/bndtools-FELIX-4866/ > Improve service registry > > > Key: FELIX-4866 > URL: https://issues.apache.org/jira/browse/FELIX-4866 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-5.0.0 >Reporter: Carsten Ziegeler >Assignee: David Bosschaert > Fix For: framework-5.2.0 > > > The current service registry is currently not using any of the Java 5 > concurrent data structures. Using those could improve the implementation, the > readibility of the code and potentially the performance of the service > registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4866) Improve service registry
[ https://issues.apache.org/jira/browse/FELIX-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545962#comment-14545962 ] Pierre De Rop commented on FELIX-4866: -- David, Can you please take a look at the bndtools project that I have joined to this issue, which seems to reproduce the problem I was talking about in the mailing list. I have checked it 100 times, but I'm not able to find a bug and now, with the last patches applied in the framework, I have some failing DM integrations tests. The tool is not based on dependency manager, but only on a little fluent APi that replaces DM, and it is only based on standard service trackers. It requires Java8, BndTools, and Eclipse Mars. Using Felix 5.0.0, or using Equinox 3.10.1, the tool runs and completes seamlessly. but using the latest Felix fwk from trunk that includes the FELIX-4866 patch, then the tool fails. and I have now four failing DM integration tests. What is doing this load test ? This loader creates a graph of service components that have dependencies between each other. For sake of simplicity, a simple scenario domain is used (actually, this example domain has been inspired from the "Java8 Lambdas" book, O'reilly) and we have the following kind of services: - Artist service: An Artist is an individual or group of musicians, who creates some "Albums". One Artist service depends on several Album services. - Album service: is a single release of musics, comprising several music Tracks. One Album depends on several Track services. - Track service: A piece of music. The scenario consists in starting/stopping 1 times a bundle that will synchronously create the graph of components (7 by default). A scenario constroller monitors the number of created components (Artists, Albums, Tracks) and when the number of expected components are created, then the controller stops the bundle. Finally, when the controller detects that all components are unregistered, the elapsed time is recorded in a list of time duration (in nano seconds). The same is done for another bundle that does exactly the same, but using concurrent component registration. But when registering components concurrently, this does not work with the latest framework. At the end of the test (that is, when the bundle that creates the components has been started/stopped 10 times), then the list of time duration is sorted: the first element of the list corresponds to the shortest elapsed time used by the bundle to create and destroy the components; and the last element in the list corresponds to the slowest elapsed time. The middle in the duration time list is the average. We display the first entry (fastest), the entry at 1/4 of the list, the middle of the list, the entry at 3/4 of the list, and the last entry (slowest time). We don't do an average, because usually, when running benchmark, some measurements don't reflect reality, especially, when there is a full GC or when the JVM is warming up. (we actually do the same as in Java Chronicle: https://github.com/peter-lawrey/Java-Chronicle). Bundle descriptions: === - org.apache.felix.framework.loadtest.tracker: a test bundle that creates 7 components synchronously when the bundle is started, and when it is stopped, then the components are unregistered. This test works fine with the latest Felix framework / trunk. - org.apache.felix.framework.loadtest.tracker.parallel: same as before, but the components are created concurrently. this test fails with the FELIX-4866 patch applied in the trunk. - org.apache.felix.framework.loadtest.scenario: this bundle contains the component classes that are part of the scenario: we have an Artist service that depends on some Albums services, each Album also depends on some music Track services. The components are bounded using a special "id" service property. - org.apache.felix.framework.loadtest.scenario.impl: the simple Artist/Albums/Track implementations. - org.apache.felix.framework.loadtest.controller: provides a ScenarioController service that is injected in all Artist/Album/Track components. When an Artist, an Album, or a Track component is started, it notifies the ScenerioController. Then when the controller detects that all components are properly created, it then stops the bundle, which in turns unregisters all components. - org.apache.felix.framework.loadtest.controller.impl: this is the ScenarioController implementation. API used to define service components: = Internally, basic Service Trackers are used to define dependencies between components. But we are using a light fluent api in order to describe component definitions, which is used to replace the DependencyManage API. Notice that DM is still used, but only to activate the controller bundle. And the Artis
[jira] [Created] (FELIX-4888) ServletHandler's are not sorted by longest matching path
Carsten Ziegeler created FELIX-4888: --- Summary: ServletHandler's are not sorted by longest matching path Key: FELIX-4888 URL: https://issues.apache.org/jira/browse/FELIX-4888 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.base-3.0.0 If more than one servlet handler matches the request, the result is sorted by service ranking and not by longest matching path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4796) Log deprecation warning if Felix whiteboard is used
[ https://issues.apache.org/jira/browse/FELIX-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4796. - Resolution: Fixed Fix Version/s: http.whiteboard-2.3.4 Assignee: Carsten Ziegeler Added log messages with level warn > Log deprecation warning if Felix whiteboard is used > --- > > Key: FELIX-4796 > URL: https://issues.apache.org/jira/browse/FELIX-4796 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0, http.whiteboard-2.3.4 > > > If a whiteboard service is using the propriatary Felix registration (servlet, > filter, http context or listener), we should log a warning and potentially > containing a hint on how to migrate -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4060) Implement HTTP Whiteboard Service (RFC-189)
[ https://issues.apache.org/jira/browse/FELIX-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545343#comment-14545343 ] Carsten Ziegeler commented on FELIX-4060: - The code has in the meantime moved to trunk. Currently affected/changed projects - api - servlet-api - base - jetty - itest > Implement HTTP Whiteboard Service (RFC-189) > --- > > Key: FELIX-4060 > URL: https://issues.apache.org/jira/browse/FELIX-4060 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0 > > > The OSGi early draft 2013-03 contains a version of RFC 189, the HTTP service > update. > This issue is for keeping track of the changes and their implementations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4779) Improve request dispatching
[ https://issues.apache.org/jira/browse/FELIX-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4779. - Resolution: Duplicate > Improve request dispatching > --- > > Key: FELIX-4779 > URL: https://issues.apache.org/jira/browse/FELIX-4779 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler > > Right now all services (especially filters) are matched against the request, > we could improve this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4779) Improve request dispatching
[ https://issues.apache.org/jira/browse/FELIX-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4779: Fix Version/s: (was: http.base-3.0.0) > Improve request dispatching > --- > > Key: FELIX-4779 > URL: https://issues.apache.org/jira/browse/FELIX-4779 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler > > Right now all services (especially filters) are matched against the request, > we could improve this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4864) Implement whiteboard security checks
[ https://issues.apache.org/jira/browse/FELIX-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4864. - Resolution: Not A Problem It seems there are no specific checks to be performed > Implement whiteboard security checks > > > Key: FELIX-4864 > URL: https://issues.apache.org/jira/browse/FELIX-4864 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler > Fix For: http.base-3.0.0 > > > The whiteboard specification defines some security checks that need to be > performed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4887) Provide capabilities
[ https://issues.apache.org/jira/browse/FELIX-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4887. - Resolution: Fixed Added capabilities for osgi.implementation, osgi.contract and osgi.service > Provide capabilities > > > Key: FELIX-4887 > URL: https://issues.apache.org/jira/browse/FELIX-4887 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.jetty-3.1.0, http.servlet-api-1.1.2 > > > We need to provide the capabilities mentioned in 140.11 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4887) Provide capabilities
[ https://issues.apache.org/jira/browse/FELIX-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4887: Fix Version/s: (was: http.base-3.0.0) http.servlet-api-1.1.2 > Provide capabilities > > > Key: FELIX-4887 > URL: https://issues.apache.org/jira/browse/FELIX-4887 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.jetty-3.1.0, http.servlet-api-1.1.2 > > > We need to provide the capabilities mentioned in 140.11 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4841) Support HttpSessionIdListener
[ https://issues.apache.org/jira/browse/FELIX-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4841. - Resolution: Fixed Added the missing pieces in rev 1679520 > Support HttpSessionIdListener > - > > Key: FELIX-4841 > URL: https://issues.apache.org/jira/browse/FELIX-4841 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0, http.jetty-3.1.0 > > > The new http whiteboard specification supports servlet 3.1 including the new > HttpSessionIdListener -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4887) Provide capabilities
Carsten Ziegeler created FELIX-4887: --- Summary: Provide capabilities Key: FELIX-4887 URL: https://issues.apache.org/jira/browse/FELIX-4887 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.base-3.0.0, http.jetty-3.1.0 We need to provide the capabilities mentioned in 140.11 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4874) IllegalArgumentException: Invalid syntax for version: 0.1-SNAPSHOT
[ https://issues.apache.org/jira/browse/FELIX-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545179#comment-14545179 ] Carsten Ziegeler commented on FELIX-4874: - [~amichai] Thanks for reporting; Could you please attach a simple test project? > IllegalArgumentException: Invalid syntax for version: 0.1-SNAPSHOT > -- > > Key: FELIX-4874 > URL: https://issues.apache.org/jira/browse/FELIX-4874 > Project: Felix > Issue Type: Bug > Components: Maven Bundle Plugin >Affects Versions: maven-bundle-plugin-2.5.4 >Reporter: Amichai Rothman > Fix For: maven-bundle-plugin-2.5.5 > > > Started getting this exception in 2.5.4 (doesn't happen in 2.5.3 and earlier, > where everything builds and runs just fine): > java.lang.IllegalArgumentException: Invalid syntax for version: 0.1-SNAPSHOT > at aQute.bnd.version.Version.(Version.java:46) > at aQute.bnd.osgi.Analyzer.augmentExports(Analyzer.java:1711) > at aQute.bnd.osgi.Analyzer.analyze(Analyzer.java:229) > at aQute.bnd.osgi.Builder.analyze(Builder.java:352) > at aQute.bnd.osgi.Analyzer.calcManifest(Analyzer.java:618) > at aQute.bnd.osgi.Builder.build(Builder.java:81) > at > org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:632) > at > org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:351) > at > org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:268) > at > org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:259) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4865) Take service hooks into account
[ https://issues.apache.org/jira/browse/FELIX-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4865. - Resolution: Fixed Implemented by trying to get the service reference to the SCH on behalf of the whiteboard bundle first > Take service hooks into account > --- > > Key: FELIX-4865 > URL: https://issues.apache.org/jira/browse/FELIX-4865 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0 > > > The whiteboard spec has been updated with a section about respecting service > hooks. Basically whiteboard services should only be bound to a > ServletContextHelper if the servlet context helper service is visible to the > bundle registering the whiteboard service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Strange behaviour with maven bundle plugin 2.5.4
The reason for this seems to be https://issues.apache.org/jira/browse/FELIX-4882 which I hopefully fixed. Carsten Am 27.04.15 um 19:45 schrieb Carsten Ziegeler: > Hi, > > in the Sling project I noticed a strange behaviour while trying to > update the plugin from 2.5.3 to 2.5.4. With the latest version several > phases in maven are executed several times, e.g. I see the resources or > the SCR plugin running three to four times at the same phase (according > to the output). > > Does anyone experience similar behaviour? > > Regards > Carsten > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Updated] (FELIX-4874) IllegalArgumentException: Invalid syntax for version: 0.1-SNAPSHOT
[ https://issues.apache.org/jira/browse/FELIX-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4874: Fix Version/s: maven-bundle-plugin-2.5.5 > IllegalArgumentException: Invalid syntax for version: 0.1-SNAPSHOT > -- > > Key: FELIX-4874 > URL: https://issues.apache.org/jira/browse/FELIX-4874 > Project: Felix > Issue Type: Bug > Components: Maven Bundle Plugin >Affects Versions: maven-bundle-plugin-2.5.4 >Reporter: Amichai Rothman > Fix For: maven-bundle-plugin-2.5.5 > > > Started getting this exception in 2.5.4 (doesn't happen in 2.5.3 and earlier, > where everything builds and runs just fine): > java.lang.IllegalArgumentException: Invalid syntax for version: 0.1-SNAPSHOT > at aQute.bnd.version.Version.(Version.java:46) > at aQute.bnd.osgi.Analyzer.augmentExports(Analyzer.java:1711) > at aQute.bnd.osgi.Analyzer.analyze(Analyzer.java:229) > at aQute.bnd.osgi.Builder.analyze(Builder.java:352) > at aQute.bnd.osgi.Analyzer.calcManifest(Analyzer.java:618) > at aQute.bnd.osgi.Builder.build(Builder.java:81) > at > org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:632) > at > org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:351) > at > org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:268) > at > org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:259) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FELIX-4060) Implement HTTP Whiteboard Service (RFC-189)
[ https://issues.apache.org/jira/browse/FELIX-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-4060: --- Assignee: Carsten Ziegeler > Implement HTTP Whiteboard Service (RFC-189) > --- > > Key: FELIX-4060 > URL: https://issues.apache.org/jira/browse/FELIX-4060 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0 > > > The OSGi early draft 2013-03 contains a version of RFC 189, the HTTP service > update. > This issue is for keeping track of the changes and their implementations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4060) Implement HTTP Whiteboard Service (RFC-189)
[ https://issues.apache.org/jira/browse/FELIX-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4060: Summary: Implement HTTP Whiteboard Service (RFC-189) (was: Implement HTTP Service Update (RFC-189)) > Implement HTTP Whiteboard Service (RFC-189) > --- > > Key: FELIX-4060 > URL: https://issues.apache.org/jira/browse/FELIX-4060 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Reporter: Carsten Ziegeler > Fix For: http.base-3.0.0 > > > The OSGi early draft 2013-03 contains a version of RFC 189, the HTTP service > update. > This issue is for keeping track of the changes and their implementations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4546) Implement HttpServiceRuntime service
[ https://issues.apache.org/jira/browse/FELIX-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4546. - Resolution: Fixed > Implement HttpServiceRuntime service > > > Key: FELIX-4546 > URL: https://issues.apache.org/jira/browse/FELIX-4546 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: David Bosschaert >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0 > > Attachments: felix-4546.e2a36d1.81e5a8f.patch, > felix-4546.failure_dtos.patch, felix-4546.requestinfo.patch, > felix-4546.resource_dto.patch, patch.txt > > > Implement the Http Service Runtime service as described in RFC 189 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4541) Add support for multiple patterns in servlet/filter registration
[ https://issues.apache.org/jira/browse/FELIX-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4541. - Resolution: Fixed > Add support for multiple patterns in servlet/filter registration > > > Key: FELIX-4541 > URL: https://issues.apache.org/jira/browse/FELIX-4541 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: J.W. Janssen >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0 > > Attachments: FELIX-4541.patch, FELIX-4541.trunk-1671836.patch, > FELIX-4541.trunk-1672365.patch > > > RFC-189 allows servlets and filters to be registered with multiple paths (and > even regex's for filters). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4548) Implement the missing errors registration
[ https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4548. - Resolution: Fixed > Implement the missing errors registration > - > > Key: FELIX-4548 > URL: https://issues.apache.org/jira/browse/FELIX-4548 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0 > > Attachments: FELIX-4548.patch, felix-4548-errorcodes_xx.patch, > felix-4548-exception-hierarchy.patch > > > Current implementation of RFC189 does not support yet errors registration. > Questions are: > * do we want to have a servlet (or maybe a filter fits better) > implementation which serves a static file whenever an HTTP error is detected? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4798) Support async servlets (filters)
[ https://issues.apache.org/jira/browse/FELIX-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4798. - Resolution: Fixed > Support async servlets (filters) > > > Key: FELIX-4798 > URL: https://issues.apache.org/jira/browse/FELIX-4798 > Project: Felix > Issue Type: Task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FELIX-4865) Take service hooks into account
[ https://issues.apache.org/jira/browse/FELIX-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-4865: --- Assignee: Carsten Ziegeler > Take service hooks into account > --- > > Key: FELIX-4865 > URL: https://issues.apache.org/jira/browse/FELIX-4865 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.0 > > > The whiteboard spec has been updated with a section about respecting service > hooks. Basically whiteboard services should only be bound to a > ServletContextHelper if the servlet context helper service is visible to the > bundle registering the whiteboard service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
