[jira] [Commented] (FELIX-4548) Implement the missing errors registration
[ https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053508#comment-14053508 ] Simone Tripodi commented on FELIX-4548: --- [~jajans] I just terminated to read the whole commit and I think it can work even better that my original implementation :) I think the issue can be considered resolved since code has been checked-in, WDYT? > 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: J.W. Janssen > Fix For: http-2.4.0 > > Attachments: FELIX-4548.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.2#6252)
About to release the Dependency Manager
Hello everybody; Just to say that this week I will (try to) release the DependencyManager from the trunk; The new release will come with the following fixed issues, and other remaining issues will be addressed later (possibly in the upcoming DM 4.0). So, I will try to proceeed this week, unless someone reports an important unknown issue which shall be resolved before we do the release ? Here are the artifacts and resolved issues about to be included in the new release: dependency manager core: FELIX-3910: Race conditions in DependencyManager FELIX-4334: ServiceDependency properties change callback issue FELIX-4285: Remove abstract modifier from DependencyActivatorBase.destroy() FELIX-4294: Dependency Manager Shell improvements FELIX-4305: DependencyMananer Adapters - service properties propagation FELIX-4002: ComponentStateListener.started is invoked twice when the listener is added in the start method. FELIX-4395: DependencyManager Configuration Dependency does not clone some class fields. FELIX-4014: handleAspectAwareRemoved in ServiceDependencyImpl can cause a possible deadlock FELIX-4097: Allow debug logging for specific instances of service dependencies to debug wiring issues. FELIX-4098: Aspect swap sometimes invokes the callbacks in the wrong order in a multithreaded application. FELIX-4099: Add support for negations in the multi property filter index. FELIX-4186: NPE in DependencyManager Logger FELIX-4226: Add option to have the dependency manager log against a single BundleContext's LogService. FELIX-4361: Possible ConcurrentModificationException in DependencyManager.getComponents() dependency manager shell: FELIX-4294 - Dependency Manager Shell improvements FELIX-4352 - Extend shell command to give better insight in where the problem is dependency manager annotation runtime: * [FELIX-4050] Named dependencies are not injected if new dependencies are added at init phase. * [FELIX-4233] Race condition in dependency manager runtime SerialExecutor. * [FELIX-3869] - Fragment support for DependencyManager-Component * [FELIX-4357] - Support types beside String/String[] in @Property annotation. dependency manager annotation: * [FELIX-3873] - Make the reference to json.org consistent in DM artifactst * [FELIX-3996] - Upgrade to latest bnd version * [FELIX-4357] - Support types beside String/String[] in @Property annotation. kind regards; /Pierre
[jira] [Commented] (FELIX-4550) Upgrade embedded Jetty to version 9.2.x in Felix Http Jetty
[ https://issues.apache.org/jira/browse/FELIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053771#comment-14053771 ] Carsten Ziegeler commented on FELIX-4550: - Many of our (Apache Felix HTTP Service Implementation) clients are still on Java 6. I don't want to get into a long discussion, but what about making this a little bit pluggable, so we end up with two versions, one with Jetty8 and one with Jetty9? > Upgrade embedded Jetty to version 9.2.x in Felix Http Jetty > --- > > Key: FELIX-4550 > URL: https://issues.apache.org/jira/browse/FELIX-4550 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Reporter: Chetan Mehrotra > Attachments: FELIX-4550.patch > > > Currently HTTP Service embeds Jetty 8.1.14.v20131031 which supports Servlet > 3.0. Current Jetty version 9.2.1.v20140609 supports Servlet 3.1 which > provided access to some new NIO based features. Further it also provides lots > of new features like Spdy support , Websocket support etc [1] > [1] https://webtide.com/jetty-9-features/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4550) Upgrade embedded Jetty to version 9.2.x in Felix Http Jetty
[ https://issues.apache.org/jira/browse/FELIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053785#comment-14053785 ] Chetan Mehrotra commented on FELIX-4550: bq. I don't want to get into a long discussion, but what about making this a little bit pluggable, so we end up with two versions, one with Jetty8 and one with Jetty9? Ack. Can rework the patch for that. So what should be the way? One way I can think of * Create a new sibling module with artifactId org.apache.felix.http.jetty9 * Do not update the version in parent pom. Instead use separate profile where Jetty9 has to be used and tested * ConnectorFactory - Instead of changing existing interface introduce a new one ConnectorFactory2 which takes Server instance such that same itest can be run against both * For Servlet API bundle I think it would be fine to export it new 3.1 packages as I do not expect much change in previously released API bundle Would that be ok? > Upgrade embedded Jetty to version 9.2.x in Felix Http Jetty > --- > > Key: FELIX-4550 > URL: https://issues.apache.org/jira/browse/FELIX-4550 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Reporter: Chetan Mehrotra > Attachments: FELIX-4550.patch > > > Currently HTTP Service embeds Jetty 8.1.14.v20131031 which supports Servlet > 3.0. Current Jetty version 9.2.1.v20140609 supports Servlet 3.1 which > provided access to some new NIO based features. Further it also provides lots > of new features like Spdy support , Websocket support etc [1] > [1] https://webtide.com/jetty-9-features/ -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: About to release the Dependency Manager
Hello Pierre, On 07 Jul 2014, at 15:46 pm, Pierre De Rop wrote: > Just to say that this week I will (try to) release the DependencyManager > from the trunk; Sounds like a good idea to do another release! +1 on that... Greetings, Marcel
