[jira] [Resolved] (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:all-tabpanel ] Carsten Ziegeler resolved FELIX-4550. - Resolution: Fixed > 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 >Assignee: J.W. Janssen > Fix For: http-2.4.0 > > Attachments: 141204_FELIX-4550_jetty9.patch, 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.3.4#6332)
[jira] [Created] (FELIX-4776) Add true for configuration of maven-bundle-plugin
Stefan Itu created FELIX-4776: - Summary: Add true for configuration of maven-bundle-plugin Key: FELIX-4776 URL: https://issues.apache.org/jira/browse/FELIX-4776 Project: Felix Issue Type: Improvement Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-2.5.3 Reporter: Stefan Itu Priority: Minor It would be nice to have a way to skip the execution of the plugin in some cases (e.g. when packaging is pom) to avoid having a warning log message in Maven build. A configuration like true would be great. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4526) Initial RFC189 (HttpService) implementation attempt
[ https://issues.apache.org/jira/browse/FELIX-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4526: Fix Version/s: (was: http-2.4.0) http-next > Initial RFC189 (HttpService) implementation attempt > --- > > Key: FELIX-4526 > URL: https://issues.apache.org/jira/browse/FELIX-4526 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.3.0 >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler > Fix For: http-next > > Attachments: FELIX-4526.patch > > > [~cziegeler] already kindly created a dedicated > [sandbox|https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/] for > that, this will be the place where contributing such implementation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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 updated FELIX-4548: Fix Version/s: (was: http-2.4.0) http-next > 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-next > > 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.3.4#6332)
[jira] [Updated] (FELIX-4547) Implement the missing resources registration
[ https://issues.apache.org/jira/browse/FELIX-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4547: Fix Version/s: (was: http-2.4.0) http-next > Implement the missing resources registration > > > Key: FELIX-4547 > URL: https://issues.apache.org/jira/browse/FELIX-4547 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler > Fix For: http-next > > Attachments: FELIX-4547.patch > > > Current implementation of RFC189 does not support yet resources registration. > Questions are: > * do we want to have a servlet implementation which serves a static file? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] Release Apache Felix Http 2.4.0
Hi, We solved 3 issues in this release, the most important one is the update to Jetty 9 https://issues.apache.org/jira/browse/FELIX/fixforversion/12327075 This release includes only the changed modules compared to the 2.3.2 release. Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-1051/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1051 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Felix Http 2.4.0
+1 David On 29 January 2015 at 12:51, Carsten Ziegeler wrote: > Hi, > > We solved 3 issues in this release, the most important one is the update > to Jetty 9 > > https://issues.apache.org/jira/browse/FELIX/fixforversion/12327075 > > This release includes only the changed modules compared to the 2.3.2 > release. > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1051/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1051 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org
Re: [VOTE] Release Apache Felix Http 2.4.0
+1 Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Felix Http 2.4.0
+1, Regards, Clement 2015-01-29 14:52 GMT+01:00 Carsten Ziegeler : > +1 > > Carsten > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org >
[iPOJO] Non-primitive typed properties and constructors
Dear iPOJO developers, I've stumbled upon a situation with fields in components that are annotated with @Property but are of non-primitive and non-String type. iPOJO has the nice feature that you still can provide default values and configurations as Strings and it will try to find an appropriate String constructor for that object. This is done in the Property class [1], starting from line 436 (v1.12.0). However, it will only look for the one constructor with a single String argument and ignore constructors with the Object argument. For example, I often have joda-time Duration and DateTime objects as configurations. Those only have Object constructors which still parse Strings properly. Wouldn't it be a nice feature if the Property class could fall back and try the Object constructor when no String constructor could be found? At the moment I have to make them String properties and parse those into shadow members upon activation, which is a little cumbersome. For my own types, I'd be able to add a String constructor, but since this is an external library, a cannot do that as easily. Please let me know what you think of it and if there are any connected issues I'd have to think of, and I'd happily provide a patch / pull request. Should I open an issue on github or Jira? Kind regards, Benjamin [1] http://grepcode.com/file/repo1.maven.org/maven2/org.apache.felix/org.apache.felix.ipojo/1.12.0/org/apache/felix/ipojo/util/Property.java#436
Re: [iPOJO] Non-primitive typed properties and constructors
Hi, On 29 janvier 2015 at 18:34:08, Benjamin Debeerst (benjamin.debee...@younicos.com) wrote: Dear iPOJO developers, I've stumbled upon a situation with fields in components that are annotated with @Property but are of non-primitive and non-String type. iPOJO has the nice feature that you still can provide default values and configurations as Strings and it will try to find an appropriate String constructor for that object. This is done in the Property class [1], starting from line 436 (v1.12.0). However, it will only look for the one constructor with a single String argument and ignore constructors with the Object argument. For example, I often have joda-time Duration and DateTime objects as configurations. Those only have Object constructors which still parse Strings properly. Wouldn't it be a nice feature if the Property class could fall back and try the Object constructor when no String constructor could be found? At the moment I have to make them String properties and parse those into shadow members upon activation, which is a little cumbersome. Yes, definitely a good idea! For my own types, I'd be able to add a String constructor, but since this is an external library, a cannot do that as easily. Please let me know what you think of it and if there are any connected issues I'd have to think of, and I'd happily provide a patch / pull request. Should I open an issue on github or Jira? Please open a ticket in Jira (https://issues.apache.org/jira/browse/FELIX). If you can attach a patch that would be awesome (and I will be really happy to integrate it) Cheers, Clement Kind regards, Benjamin [1] http://grepcode.com/file/repo1.maven.org/maven2/org.apache.felix/org.apache.felix.ipojo/1.12.0/org/apache/felix/ipojo/util/Property.java#436
RE: [VOTE] Release Apache Felix Http 2.4.0
+1 (non-binding) >-Original Message- >From: Carsten Ziegeler [mailto:cziege...@apache.org] >Sent: Thursday, January 29, 2015 1:51 PM >To: dev@felix.apache.org >Subject: [VOTE] Release Apache Felix Http 2.4.0 > >Hi, > >We solved 3 issues in this release, the most important one is the >update >to Jetty 9 > >https://issues.apache.org/jira/browse/FELIX/fixforversion/12327075 > >This release includes only the changed modules compared to the 2.3.2 >release. > >Staging repository: >https://repository.apache.org/content/repositories/orgapachefelix- >1051/ > >You can use this UNIX script to download the release and verify the >signatures: >http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > >Usage: >sh check_staged_release.sh 1051 /tmp/felix-staging > >Please vote to approve this release: > >[ ] +1 Approve the release >[ ] -1 Veto the release (please provide specific comments) > >This vote will be open for at least 72 hours. > >Regards >Carsten >-- >Carsten Ziegeler >Adobe Research Switzerland >cziege...@apache.org
Re: [VOTE] Release Apache Felix Http 2.4.0
+1