[jira] [Closed] (FELIX-4994) Use Java Logging API in spite of System.out
[ https://issues.apache.org/jira/browse/FELIX-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-4994. --- > Use Java Logging API in spite of System.out > --- > > Key: FELIX-4994 > URL: https://issues.apache.org/jira/browse/FELIX-4994 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.3.2, http-2.4.0 > Environment: Linux, JDK 1.7, Felix 4.6.1 >Reporter: Enrique Ruiz (DiSiD Corporation S.L.) >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.2, http.jetty-3.1.2, http.bridge-3.0.2 > > Attachments: java-logging-api.patch.gz > > > If `LogServiceLogger` doesn't have a reference to the `LogService` it > delegates on `ConsoleLogger`. > The problems are: > * The `ConsoleLogger` writes the messages to `System.out` > * We cannot configure the log verbosity > I think it would be better if `ConsoleLogger` would use the > `java.util.logging.Logger`. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-5053) IllegalArgumentException when forwarding request
[
https://issues.apache.org/jira/browse/FELIX-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed FELIX-5053.
---
> IllegalArgumentException when forwarding request
>
>
> Key: FELIX-5053
> URL: https://issues.apache.org/jira/browse/FELIX-5053
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
>Affects Versions: http.base-3.0.0
>Reporter: Sten Roger Sandvik
>Assignee: Sten Roger Sandvik
> Fix For: http.base-3.0.2, http.jetty-3.1.2, http.bridge-3.0.2
>
>
> It seems to be a problem with forwarding requests in certain cases. I have
> the following setup:
> * Servlet A forwards the request to Servlet 2 (using RequestDispatcher).
> * Servlet B writes to the response using an output stream
> (HttpServletResponse.getOutputStream()).
> When this happens I get an IllegalStateException from Jetty that basically
> saying that the Writer cannot be closed since I have already used an
> OutputStream.
> The code that I think is wrong (or possibly not robust enough) is in
> RequestDispatcherImp line 84.
> {code}
> if (!request.isAsyncStarted())
> {
> response.flushBuffer();
> response.getWriter().close();
> }
> {code}
> The line that causes trouble is:
> {code}
> response.getWriter().close();
> {code}
> We should probably check if we can actually close this writer or just ignore
> the potential exception.
> In my setup I have one servlet that writes to OutputStream using
> HttpServletResponse.getOutputStream(). Then I have another servlet that
> forwards the request to the first servlet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FELIX-5057) Race condition between getService and stopping the http service
[ https://issues.apache.org/jira/browse/FELIX-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-5057. --- > Race condition between getService and stopping the http service > --- > > Key: FELIX-5057 > URL: https://issues.apache.org/jira/browse/FELIX-5057 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http.base-3.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.base-3.0.2, http.jetty-3.1.2, http.bridge-3.0.2 > > > It might happen that getService() is called on the HttpServiceFactory while > stop() is called and the context is set to null. This results in an IAE. > We should first unregister the factory and then set the context to null. In > addition if the context is null, getService should just return null and not > throw -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-5052) Annoying System.out in RequestDispatcherImpl
[ https://issues.apache.org/jira/browse/FELIX-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-5052. --- > Annoying System.out in RequestDispatcherImpl > > > Key: FELIX-5052 > URL: https://issues.apache.org/jira/browse/FELIX-5052 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http.base-3.0.0 >Reporter: Sten Roger Sandvik >Assignee: Sten Roger Sandvik > Fix For: http.base-3.0.2, http.jetty-3.1.2, http.bridge-3.0.2 > > > There's an annoying System.out in RequestDispatcherImpl's constructor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-5059) Embedd http api bundle in jetty bundle
[ https://issues.apache.org/jira/browse/FELIX-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-5059. --- > Embedd http api bundle in jetty bundle > -- > > Key: FELIX-5059 > URL: https://issues.apache.org/jira/browse/FELIX-5059 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http.jetty-3.1.2 > > > As discussed in the mailing list, to make the usage of the http jetty bundle > easier and to provide a more consistent bundle, we should embedd the http.api > bundle in the http.jetty one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Felix Http Base 3.0.2, Http Bridge 3.0.2, and Http Jetty 3.1.2
Vote passes with three binding +1 votes and one non binding +1 vote Thanks Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Created] (FELIX-5076) Website shows a lot of issues
Rolf Geuenich created FELIX-5076: Summary: Website shows a lot of issues Key: FELIX-5076 URL: https://issues.apache.org/jira/browse/FELIX-5076 Project: Felix Issue Type: Improvement Components: Documentation Reporter: Rolf Geuenich On the projects website are a lot of glitches like doubled headings (http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-application-demonstration.html), no line breaks (http://felix.apache.org/documentation/development/building-felix.html), a lot of markdown links which are shown in text form instead as a link (http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-application-demonstration.html), dead links (http://felix.apache.org/documentation.html -> site map) etc. I'm unable to find informations about how the webpage is generated or where the files are stored. So I'm unable to help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-5075) Framework hooks not re-sorted on service ranking update
[ https://issues.apache.org/jira/browse/FELIX-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved FELIX-5075. - Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revision&revision=1708156 > Framework hooks not re-sorted on service ranking update > --- > > Key: FELIX-5075 > URL: https://issues.apache.org/jira/browse/FELIX-5075 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-5.4.0 >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-5.4.0 > > > When framework hooks (or URL handlers) have their properties changed to > reflect a new service ranking order, this order is not reflected when these > hooks are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-5075) Framework hooks not re-sorted on service ranking update
David Bosschaert created FELIX-5075: --- Summary: Framework hooks not re-sorted on service ranking update Key: FELIX-5075 URL: https://issues.apache.org/jira/browse/FELIX-5075 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-5.4.0 Reporter: David Bosschaert Assignee: David Bosschaert Fix For: framework-5.4.0 When framework hooks (or URL handlers) have their properties changed to reflect a new service ranking order, this order is not reflected when these hooks are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (FELIX-5075) Framework hooks not re-sorted on service ranking update
[ https://issues.apache.org/jira/browse/FELIX-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-5075 started by David Bosschaert. --- > Framework hooks not re-sorted on service ranking update > --- > > Key: FELIX-5075 > URL: https://issues.apache.org/jira/browse/FELIX-5075 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-5.4.0 >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-5.4.0 > > > When framework hooks (or URL handlers) have their properties changed to > reflect a new service ranking order, this order is not reflected when these > hooks are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Felix Http Base 3.0.2, Http Bridge 3.0.2, and Http Jetty 3.1.2
+1 (non-binding) On Fri, Oct 9, 2015 at 2:45 PM, Sten Roger Sandvik wrote: > +1 > fre. 9. okt. 2015 kl. 17.43 skrev David Bosschaert < > david.bosscha...@gmail.com>: > >> +1 >> >> David >> >> On 9 October 2015 at 16:15, Carsten Ziegeler wrote: >> > I would like to call a vote on the following subproject releases: >> > >> > Http Base 3.0.2 - 4 issues solved >> > https://issues.apache.org/jira/browse/FELIX/fixforversion/12333076 >> > >> > Http Bridge 3.0.2 - 4 issues solved >> > https://issues.apache.org/jira/browse/FELIX/fixforversion/12333282 >> > >> > Http Jetty 3.1.2 - 5 issues solved >> > https://issues.apache.org/jira/browse/FELIX/fixforversion/12333135 >> > >> > Staging repositories: >> > https://repository.apache.org/content/repositories/orgapachefelix-1098/ >> > >> > 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 1098 /tmp/felix-staging >> > >> > Please vote to approve this release: >> > >> > [ ] +1 Approve the release >> > [ ] -1 Veto the release (please provide specific comments) >> > >> > Regards >> > Carsten >> > -- >> > Carsten Ziegeler >> > Adobe Research Switzerland >> > cziege...@apache.org >>
[jira] [Commented] (FELIX-5074) Using org.apache.felix.scr.bnd together with maven-bundle-plugin leads to using the wrong bnd version
[
https://issues.apache.org/jira/browse/FELIX-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953068#comment-14953068
]
Konrad Windszus commented on FELIX-5074:
I updated the PR. [~pderop] Would you mind testing it again? Now the transitive
dependencies are again embedded in the final JAR but those packages which are
part of bndlib are filtered out.
> Using org.apache.felix.scr.bnd together with maven-bundle-plugin leads to
> using the wrong bnd version
> -
>
> Key: FELIX-5074
> URL: https://issues.apache.org/jira/browse/FELIX-5074
> Project: Felix
> Issue Type: Bug
> Components: SCR Tooling
>Affects Versions: scr bnd plugin 1.4.0
>Reporter: Konrad Windszus
> Attachments: pom.xml
>
>
> If I have a POM with a plugin configuration like this
> {code}
>
> org.apache.felix
> maven-bundle-plugin
> 3.0.0
> true
>
>
>
>
> <_plugin>org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin;destdir=target/classes
>
>
>
>
>
> org.apache.felix
> org.apache.felix.scr.bnd
> 1.4.0
>
>
>
> {code}
> Unfortunately {{org.apache.felix.scr.bnd}} depends on
> {{biz.aQute.bnd:bndlib:jar:2.1.0}}. Therefore the classpath of
> maven-bundle-plugin looks like this:
> {code}
> [DEBUG] Populating class realm
> plugin>org.apache.felix:maven-bundle-plugin:3.0.0
> [DEBUG] Included: org.apache.felix:maven-bundle-plugin:jar:3.0.0
> [DEBUG] Included: org.apache.felix:org.apache.felix.scr.bnd:jar:1.4.0
> [DEBUG] Included: biz.aQute.bnd:bndlib:jar:2.1.0
> [DEBUG] Included: org.osgi:org.osgi.core:jar:4.3.1
> [DEBUG] Included: biz.aQute.bnd:biz.aQute.bndlib:jar:3.0.0
> [DEBUG] Included:
> org.apache.felix:org.apache.felix.bundlerepository:jar:1.6.6
> [DEBUG] Included: org.easymock:easymock:jar:2.5.2
> [DEBUG] Included: org.apache.felix:org.apache.felix.utils:jar:1.6.0
> [DEBUG] Included: org.osgi:org.osgi.compendium:jar:4.2.0
> [DEBUG] Included: org.slf4j:slf4j-jdk14:jar:1.5.6
> [DEBUG] Included: org.slf4j:slf4j-api:jar:1.5.6
> [DEBUG] Included: org.slf4j:jcl-over-slf4j:jar:1.5.6
> [DEBUG] Included: org.apache.maven.reporting:maven-reporting-api:jar:2.2.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-logging-api:jar:1.1
> [DEBUG] Included: junit:junit:jar:4.11
> [DEBUG] Included: org.hamcrest:hamcrest-core:jar:1.3
> [DEBUG] Included: commons-cli:commons-cli:jar:1.2
> [DEBUG] Included:
> org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4
> [DEBUG] Included: backport-util-concurrent:backport-util-concurrent:jar:3.1
> [DEBUG] Included: org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3
> [DEBUG] Included: org.sonatype.plexus:plexus-cipher:jar:1.4
> [DEBUG] Included: org.apache.maven:maven-archiver:jar:2.5
> [DEBUG] Included: org.codehaus.plexus:plexus-archiver:jar:2.1
> [DEBUG] Included: org.codehaus.plexus:plexus-io:jar:2.0.2
> [DEBUG] Included: org.codehaus.plexus:plexus-interpolation:jar:1.15
> [DEBUG] Included: org.apache.maven.shared:maven-dependency-tree:jar:2.1
> [DEBUG] Included: org.codehaus.plexus:plexus-component-annotations:jar:1.5.5
> [DEBUG] Included: org.eclipse.aether:aether-util:jar:0.9.0.M2
> [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:3.0.10
> [DEBUG] Included: org.sonatype.plexus:plexus-build-api:jar:0.0.7
> [DEBUG] Included: org.apache.maven.doxia:doxia-sink-api:jar:1.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-site-renderer:jar:1.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-core:jar:1.0
> [DEBUG] Included: org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7
> [DEBUG] Included: org.codehaus.plexus:plexus-velocity:jar:1.1.7
> [DEBUG] Included: org.apache.velocity:velocity:jar:1.5
> [DEBUG] Included: commons-lang:commons-lang:jar:2.1
> [DEBUG] Included: oro:oro:jar:2.0.8
> [DEBUG] Included: org.apache.maven.doxia:doxia-decoration-model:jar:1.0
> [DEBUG] Included: commons-collections:commons-collections:jar:3.2
> [DEBUG] Included: org.apache.maven.doxia:doxia-module-apt:jar:1.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-module-fml:jar:1.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-module-xdoc:jar:1.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-module-xhtml:jar:1.0
> [DEBUG] Excluded: org.apache.maven:maven-core:jar:2.2.0
> [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.2.0
> [DEBUG] Excluded:
> org.apache.maven:maven-plugin-parameter-documenter:jar:2.2.0
> [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.2.0
> [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.2.0
> [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.2.0
> [DEBUG] Excluded:
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
>
[jira] [Commented] (FELIX-5074) Using org.apache.felix.scr.bnd together with maven-bundle-plugin leads to using the wrong bnd version
[
https://issues.apache.org/jira/browse/FELIX-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953027#comment-14953027
]
Konrad Windszus commented on FELIX-5074:
Actually it is not that simple, because for
org.osgi.service.component.ComponentContext there are only the following
dependencies available:
http://search.maven.org/#search|ga|1|fc%3A%22org.osgi.service.component.ComponentContext%22%20g%3A%22org.osgi%22
Only since DS 1.3 there is a dedicated artifact for something related to OSGi
services.
Therefore maybe the right solution is to somehow invert the classloading order,
so that {{bndlib}} is always loaded first before the {{felix.scr.bnd}} artifact
is being loaded. That way {{bndlib}} would loads its own classes and
{{felix.scr.bnd}} would preferably leverage the classes from {{bndlib}} and
only if they are not contained in {{bndlib}} use its own versions of those
classes.
The problem with that is how to modify the class loading order.
Currently the loading order is:
# maven-bundle-plugin-3.0.0.jar
# org.apache.felix.scr.bnd-1.4.0.jar
# org.osgi.core-4.3.1.jar
# biz.aQute.bndlib-3.0.0.jar
To modify that {{felix.scr.bnd}} would need to depend on {{bndlib}} as well.
Unfortunately {{bndlib}} changed its artifactId from {{bndlib}} to
{{biz.aQute.bndlib}} in version 2.4.1. Therefore it seems impossible to have
the same version of {{felix.scr.bnd}} for both bnd < 2.4.1 and bnd >= 2.4.1.
> Using org.apache.felix.scr.bnd together with maven-bundle-plugin leads to
> using the wrong bnd version
> -
>
> Key: FELIX-5074
> URL: https://issues.apache.org/jira/browse/FELIX-5074
> Project: Felix
> Issue Type: Bug
> Components: SCR Tooling
>Affects Versions: scr bnd plugin 1.4.0
>Reporter: Konrad Windszus
> Attachments: pom.xml
>
>
> If I have a POM with a plugin configuration like this
> {code}
>
> org.apache.felix
> maven-bundle-plugin
> 3.0.0
> true
>
>
>
>
> <_plugin>org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin;destdir=target/classes
>
>
>
>
>
> org.apache.felix
> org.apache.felix.scr.bnd
> 1.4.0
>
>
>
> {code}
> Unfortunately {{org.apache.felix.scr.bnd}} depends on
> {{biz.aQute.bnd:bndlib:jar:2.1.0}}. Therefore the classpath of
> maven-bundle-plugin looks like this:
> {code}
> [DEBUG] Populating class realm
> plugin>org.apache.felix:maven-bundle-plugin:3.0.0
> [DEBUG] Included: org.apache.felix:maven-bundle-plugin:jar:3.0.0
> [DEBUG] Included: org.apache.felix:org.apache.felix.scr.bnd:jar:1.4.0
> [DEBUG] Included: biz.aQute.bnd:bndlib:jar:2.1.0
> [DEBUG] Included: org.osgi:org.osgi.core:jar:4.3.1
> [DEBUG] Included: biz.aQute.bnd:biz.aQute.bndlib:jar:3.0.0
> [DEBUG] Included:
> org.apache.felix:org.apache.felix.bundlerepository:jar:1.6.6
> [DEBUG] Included: org.easymock:easymock:jar:2.5.2
> [DEBUG] Included: org.apache.felix:org.apache.felix.utils:jar:1.6.0
> [DEBUG] Included: org.osgi:org.osgi.compendium:jar:4.2.0
> [DEBUG] Included: org.slf4j:slf4j-jdk14:jar:1.5.6
> [DEBUG] Included: org.slf4j:slf4j-api:jar:1.5.6
> [DEBUG] Included: org.slf4j:jcl-over-slf4j:jar:1.5.6
> [DEBUG] Included: org.apache.maven.reporting:maven-reporting-api:jar:2.2.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-logging-api:jar:1.1
> [DEBUG] Included: junit:junit:jar:4.11
> [DEBUG] Included: org.hamcrest:hamcrest-core:jar:1.3
> [DEBUG] Included: commons-cli:commons-cli:jar:1.2
> [DEBUG] Included:
> org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4
> [DEBUG] Included: backport-util-concurrent:backport-util-concurrent:jar:3.1
> [DEBUG] Included: org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3
> [DEBUG] Included: org.sonatype.plexus:plexus-cipher:jar:1.4
> [DEBUG] Included: org.apache.maven:maven-archiver:jar:2.5
> [DEBUG] Included: org.codehaus.plexus:plexus-archiver:jar:2.1
> [DEBUG] Included: org.codehaus.plexus:plexus-io:jar:2.0.2
> [DEBUG] Included: org.codehaus.plexus:plexus-interpolation:jar:1.15
> [DEBUG] Included: org.apache.maven.shared:maven-dependency-tree:jar:2.1
> [DEBUG] Included: org.codehaus.plexus:plexus-component-annotations:jar:1.5.5
> [DEBUG] Included: org.eclipse.aether:aether-util:jar:0.9.0.M2
> [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:3.0.10
> [DEBUG] Included: org.sonatype.plexus:plexus-build-api:jar:0.0.7
> [DEBUG] Included: org.apache.maven.doxia:doxia-sink-api:jar:1.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-site-renderer:jar:1.0
> [DEBUG] Included: org.apache.maven.doxia:doxia-core:jar:1.0
> [DEBUG] Included: org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7
> [DEBUG] Included: org.codehaus.plexus:plexus-velocity:jar:1.1.7
> [DEBUG
