[jira] Commented: (FELIX-2741) NPE in ResolverImpl.calculatePackageSpaces
[ https://issues.apache.org/jira/browse/FELIX-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978747#action_12978747 ] Ancoron Luciferis commented on FELIX-2741: -- We just saw this one again during a bundle update and maybe could be reproduced by refreshing a package with changed dynamic package imports (at least this is what we've done here). > NPE in ResolverImpl.calculatePackageSpaces > -- > > Key: FELIX-2741 > URL: https://issues.apache.org/jira/browse/FELIX-2741 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-3.0.6 >Reporter: Sahoo > Fix For: framework-3.2.0 > > > A GlassFish user has reported a NPE while doing stress testing and the stack > is given below: > [#|2010-12-22T11:28:28.910+0100|INFO|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-1;|java.lang.NullPointerException > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:557) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:94) > at > org.apache.felix.framework.Felix$FelixResolver.resolve(Felix.java:3982) > at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3397) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1714) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1136) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1122) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1115) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:433) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:241) > |#] > m_wires must be null for this NPE to be caused by the following code: > for (Wire wire : module.getWires()) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Fwd: Re: org.apache.felix.http.bundle-2.0.5-SNAPSHOT release ?
On 1/7/11 0:21, Rob Walker wrote: Views on whether current code is in position to do this? We're certainly using it successfully with no major issues on our project Anyone know if Sten no longer able to be actively involved here? -> richard - R Original Message Subject: Re: org.apache.felix.http.bundle-2.0.5-SNAPSHOT release ? Date: Fri, 07 Jan 2011 07:20:51 +0200 From: Rob Walker To: us...@felix.apache.org I think most of us working on the dev side have tended just to use the SVN source and create our own bundles with mods as needed. We can certainly call a vote for a new release though if there is interest -- Rob On 07/01/2011 1:04 AM, Christian Parker wrote: Hello. I currently have a project depending on org.apache.felix.http.bundle-2.0.5-SNAPSHOT, and I was wondering if there was a schedule for producing a release version of org.apache.felix.http.bundle. Thanks! Christian, Boulder, CO
[jira] Commented: (FELIX-2741) NPE in ResolverImpl.calculatePackageSpaces
[ https://issues.apache.org/jira/browse/FELIX-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978823#action_12978823 ] Richard S. Hall commented on FELIX-2741: What do you mean exactly? Bundle v1 had something like: DynamicImport-Package: org.foo And you updated it to bundle v2 with something like: DynamicImport-Package: org.bar Then refreshed? If I can get a reproducible example, I can fix it. > NPE in ResolverImpl.calculatePackageSpaces > -- > > Key: FELIX-2741 > URL: https://issues.apache.org/jira/browse/FELIX-2741 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-3.0.6 >Reporter: Sahoo > Fix For: framework-3.2.0 > > > A GlassFish user has reported a NPE while doing stress testing and the stack > is given below: > [#|2010-12-22T11:28:28.910+0100|INFO|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-1;|java.lang.NullPointerException > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:557) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:94) > at > org.apache.felix.framework.Felix$FelixResolver.resolve(Felix.java:3982) > at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3397) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1714) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1136) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1122) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1115) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:433) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:241) > |#] > m_wires must be null for this NPE to be caused by the following code: > for (Wire wire : module.getWires()) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2767) gogo telnet IP address
gogo telnet IP address -- Key: FELIX-2767 URL: https://issues.apache.org/jira/browse/FELIX-2767 Project: Felix Issue Type: New Feature Components: Gogo Shell Affects Versions: gogo-0.6.1 Reporter: Arjun Panday Priority: Minor Attachments: Telnet.java I would need to specify the IP address on which gogo telnet is listening (in addition to the port) Please find attached a proposed patch. /arjun -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2767) gogo telnet IP address
[ https://issues.apache.org/jira/browse/FELIX-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Panday updated FELIX-2767: Attachment: Telnet.java a simple addition to configure the telnet IP address > gogo telnet IP address > -- > > Key: FELIX-2767 > URL: https://issues.apache.org/jira/browse/FELIX-2767 > Project: Felix > Issue Type: New Feature > Components: Gogo Shell >Affects Versions: gogo-0.6.1 >Reporter: Arjun Panday >Priority: Minor > Attachments: Telnet.java > > > I would need to specify the IP address on which gogo telnet is listening (in > addition to the port) > Please find attached a proposed patch. > /arjun -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2768) HttpContext.handleSecurity returns SC_FORBIDDEN unless response is comitted
HttpContext.handleSecurity returns SC_FORBIDDEN unless response is comitted
---
Key: FELIX-2768
URL: https://issues.apache.org/jira/browse/FELIX-2768
Project: Felix
Issue Type: Bug
Components: HTTP Service
Reporter: Derek Baum
The JavaDoc for HttpContext.handleSecurity states:
* If the request requires authentication and the Authorization header
in
* the request is missing or not acceptable, then this method should
set the
* WWW-Authenticate header in the response object, set the status in the
* response object to Unauthorized(401) and return false
So the following implementation of handleSecurity() should cause an
UNAUTHORIZED response:
response.setHeader("WWW-Authenticate", "BASIC realm=\"Secure
Moixa Energy Gateway\"");
response.setStatus(HttpServletResponse.SC_UNAUTHORIZED);
return false;
This worked OK in org.apache.felix.http.jetty-1.0.1, but fails in
org.apache.felix.http.jetty-2.0.4, by always returning SC_FORBIDDEN.
Examining the implementation:
org/apache/felix/http/base/internal/handler/ServletHandler.java:
if (!getContext().handleSecurity(req, res)) {
if (!res.isCommitted()) {
res.sendError(HttpServletResponse.SC_FORBIDDEN);
}
}
which means that SC_FORBIDDEN is always returned, unless the response is
committed.
In order to commit the response, response.flushBuffer() must be called in the
handleSecurity() implementation after setting the response code to
unauthorized. Howver, the JavaDoc for HttpContext does not indicate that it is
necessary to commit the response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2741) NPE in ResolverImpl.calculatePackageSpaces
[ https://issues.apache.org/jira/browse/FELIX-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979021#action_12979021 ] Ancoron Luciferis commented on FELIX-2741: -- Exactly, e.g. I previously used the upstream version of WSS4j v1.5.9 which doesn't declared and DynamicImport-Package manifest header but at runtime it e.g. tries to load the following JCE providers: * org.bouncycastle.jce.provider.BouncyCastleProvider * org.apache.security.juice.provider.JuiCEProviderOpenSSL So I've just tried to update the WSS4J bundle with a modified version that includes this new header: DynamicImport-Package: org.bouncycastle.jce.provider,org.apache.security.juice.provider And just by that I could raise the issue here. > NPE in ResolverImpl.calculatePackageSpaces > -- > > Key: FELIX-2741 > URL: https://issues.apache.org/jira/browse/FELIX-2741 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-3.0.6 >Reporter: Sahoo > Fix For: framework-3.2.0 > > > A GlassFish user has reported a NPE while doing stress testing and the stack > is given below: > [#|2010-12-22T11:28:28.910+0100|INFO|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-1;|java.lang.NullPointerException > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:557) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:94) > at > org.apache.felix.framework.Felix$FelixResolver.resolve(Felix.java:3982) > at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3397) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1714) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1136) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1122) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1115) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:433) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:241) > |#] > m_wires must be null for this NPE to be caused by the following code: > for (Wire wire : module.getWires()) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2768) HttpContext.handleSecurity returns SC_FORBIDDEN unless response is comitted
[
https://issues.apache.org/jira/browse/FELIX-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979026#action_12979026
]
Felix Meschberger commented on FELIX-2768:
--
I also ran into this issue a few times ...
I think the problem that the ServletHandler tries to solve is to send back a
sensible error instead of a successfull 200 response in case the HttpContext
did not send a response.
Maybe doHandle method should be modified like this:
res.setStatus(HttpServletResponse.SC_FORBIDDEN);
if (getContext().handleSecurity(req, res)) {
res.setStatus(HttpServletResponse.SC_OK); // default back to OK
servlet.service(...)
}
This would ensure the request is terminated with 403 unless the handleSecurity
method returning false has set a different status.
WDYT ?
> HttpContext.handleSecurity returns SC_FORBIDDEN unless response is comitted
> ---
>
> Key: FELIX-2768
> URL: https://issues.apache.org/jira/browse/FELIX-2768
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
>Affects Versions: http-2.0.4
>Reporter: Derek Baum
>
> The JavaDoc for HttpContext.handleSecurity states:
>* If the request requires authentication and the Authorization header
> in
>* the request is missing or not acceptable, then this method should
> set the
>* WWW-Authenticate header in the response object, set the status in the
>* response object to Unauthorized(401) and return false
> So the following implementation of handleSecurity() should cause an
> UNAUTHORIZED response:
> response.setHeader("WWW-Authenticate", "BASIC realm=\"Secure
> Moixa Energy Gateway\"");
> response.setStatus(HttpServletResponse.SC_UNAUTHORIZED);
> return false;
> This worked OK in org.apache.felix.http.jetty-1.0.1, but fails in
> org.apache.felix.http.jetty-2.0.4, by always returning SC_FORBIDDEN.
> Examining the implementation:
> org/apache/felix/http/base/internal/handler/ServletHandler.java:
> if (!getContext().handleSecurity(req, res)) {
> if (!res.isCommitted()) {
> res.sendError(HttpServletResponse.SC_FORBIDDEN);
> }
> }
> which means that SC_FORBIDDEN is always returned, unless the response is
> committed.
> In order to commit the response, response.flushBuffer() must be called in the
> handleSecurity() implementation after setting the response code to
> unauthorized. Howver, the JavaDoc for HttpContext does not indicate that it
> is necessary to commit the response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2768) HttpContext.handleSecurity returns SC_FORBIDDEN unless response is comitted
[
https://issues.apache.org/jira/browse/FELIX-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-2768:
-
Affects Version/s: http-2.0.4
> HttpContext.handleSecurity returns SC_FORBIDDEN unless response is comitted
> ---
>
> Key: FELIX-2768
> URL: https://issues.apache.org/jira/browse/FELIX-2768
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
>Affects Versions: http-2.0.4
>Reporter: Derek Baum
>
> The JavaDoc for HttpContext.handleSecurity states:
>* If the request requires authentication and the Authorization header
> in
>* the request is missing or not acceptable, then this method should
> set the
>* WWW-Authenticate header in the response object, set the status in the
>* response object to Unauthorized(401) and return false
> So the following implementation of handleSecurity() should cause an
> UNAUTHORIZED response:
> response.setHeader("WWW-Authenticate", "BASIC realm=\"Secure
> Moixa Energy Gateway\"");
> response.setStatus(HttpServletResponse.SC_UNAUTHORIZED);
> return false;
> This worked OK in org.apache.felix.http.jetty-1.0.1, but fails in
> org.apache.felix.http.jetty-2.0.4, by always returning SC_FORBIDDEN.
> Examining the implementation:
> org/apache/felix/http/base/internal/handler/ServletHandler.java:
> if (!getContext().handleSecurity(req, res)) {
> if (!res.isCommitted()) {
> res.sendError(HttpServletResponse.SC_FORBIDDEN);
> }
> }
> which means that SC_FORBIDDEN is always returned, unless the response is
> committed.
> In order to commit the response, response.flushBuffer() must be called in the
> handleSecurity() implementation after setting the response code to
> unauthorized. Howver, the JavaDoc for HttpContext does not indicate that it
> is necessary to commit the response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-2691) Apache Felix HTTP service HttpServiceImpl.isNameValid does not match OSGi R4.2 spec?
[
https://issues.apache.org/jira/browse/FELIX-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned FELIX-2691:
Assignee: Felix Meschberger
> Apache Felix HTTP service HttpServiceImpl.isNameValid does not match OSGi
> R4.2 spec?
>
>
> Key: FELIX-2691
> URL: https://issues.apache.org/jira/browse/FELIX-2691
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
>Affects Versions: http-2.0.4
> Environment: Not relevant
>Reporter: Misha Koshelev
>Assignee: Felix Meschberger
> Attachments:
> FELIX-2691-HttpServiceImpl-isNameValid-comply-OSGI-R42.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> Filing bug per:
> http://www.mail-archive.com/dev@felix.apache.org/msg19853.html
> The R4.2 enterprise spec from
> http://www.osgi.org/Download/File?url=/download/r4v42/r4.enterprise.pdf
> on page 48 clearly states:
> The name parameter must also not end with slash ('/') with the
> exception that a name of the form "/" is used to denote the root of
> the bundle.
> The relevant code, in trunk, is, from
> http://svn.apache.org/repos/asf/felix/trunk/http/base/src/main/java/org/apache/felix/http/base/internal/service/HttpServiceImpl.java
> public void registerResources(String alias, String name, HttpContext context)
> throws NamespaceException
> {
> if (!isNameValid(name)) {
> throw new IllegalArgumentException( "Malformed resource
> name [" + name + "]");
> }
> ...
> and
> private boolean isNameValid(String name)
> {
> if (name == null) {
> return false;
> }
> if (name.endsWith( "/" )) {
> return false;
> }
> return true;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2691) Apache Felix HTTP service HttpServiceImpl.isNameValid does not match OSGi R4.2 spec?
[
https://issues.apache.org/jira/browse/FELIX-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-2691.
--
Resolution: Fixed
Fix Version/s: http-2.0.6
Thanks for providing the patch.
Fixed in Rev. 1056570
> Apache Felix HTTP service HttpServiceImpl.isNameValid does not match OSGi
> R4.2 spec?
>
>
> Key: FELIX-2691
> URL: https://issues.apache.org/jira/browse/FELIX-2691
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
>Affects Versions: http-2.0.4
> Environment: Not relevant
>Reporter: Misha Koshelev
>Assignee: Felix Meschberger
> Fix For: http-2.0.6
>
> Attachments:
> FELIX-2691-HttpServiceImpl-isNameValid-comply-OSGI-R42.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> Filing bug per:
> http://www.mail-archive.com/dev@felix.apache.org/msg19853.html
> The R4.2 enterprise spec from
> http://www.osgi.org/Download/File?url=/download/r4v42/r4.enterprise.pdf
> on page 48 clearly states:
> The name parameter must also not end with slash ('/') with the
> exception that a name of the form "/" is used to denote the root of
> the bundle.
> The relevant code, in trunk, is, from
> http://svn.apache.org/repos/asf/felix/trunk/http/base/src/main/java/org/apache/felix/http/base/internal/service/HttpServiceImpl.java
> public void registerResources(String alias, String name, HttpContext context)
> throws NamespaceException
> {
> if (!isNameValid(name)) {
> throw new IllegalArgumentException( "Malformed resource
> name [" + name + "]");
> }
> ...
> and
> private boolean isNameValid(String name)
> {
> if (name == null) {
> return false;
> }
> if (name.endsWith( "/" )) {
> return false;
> }
> return true;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-2398) Config property to disable NIO use in http.bundle doesn't work
[ https://issues.apache.org/jira/browse/FELIX-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned FELIX-2398: Assignee: Felix Meschberger > Config property to disable NIO use in http.bundle doesn't work > -- > > Key: FELIX-2398 > URL: https://issues.apache.org/jira/browse/FELIX-2398 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: All >Reporter: Bruce Jackson >Assignee: Felix Meschberger > > In Felix-870 (https://issues.apache.org/jira/browse/FELIX-870) a property was > added to disable the use of NIO by the jetty embedded http server. This > config property no longer works. From Rob Walker: > "Just grepping the source code, and I think this property was in the original > felix/http.jetty bundle but may not have made it across to the new felix/http > bundle." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2398) Config property to disable NIO use in http.bundle doesn't work
[ https://issues.apache.org/jira/browse/FELIX-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-2398. -- Resolution: Fixed Fix Version/s: http-2.0.6 Fixed in Rev. 1056579 Add configuration properties to set whether NIO is to be used for HTTP(S): org.apache.felix.http.nio - (boolean) whether to use NIO for HTTP or not, default is true org.apache.felix.https.nio - (boolean) whether to use NIO for HTTPS or not, default is to use the value of the org.apache.felix.http.nio property Does that suite your need ? > Config property to disable NIO use in http.bundle doesn't work > -- > > Key: FELIX-2398 > URL: https://issues.apache.org/jira/browse/FELIX-2398 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: All >Reporter: Bruce Jackson >Assignee: Felix Meschberger > Fix For: http-2.0.6 > > > In Felix-870 (https://issues.apache.org/jira/browse/FELIX-870) a property was > added to disable the use of NIO by the jetty embedded http server. This > config property no longer works. From Rob Walker: > "Just grepping the source code, and I think this property was in the original > felix/http.jetty bundle but may not have made it across to the new felix/http > bundle." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2769) Provide Metatype Descriptor for Jetty Configuration properties
Provide Metatype Descriptor for Jetty Configuration properties -- Key: FELIX-2769 URL: https://issues.apache.org/jira/browse/FELIX-2769 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: http-2.0.6 To support configuration of the Jetty embedded servlet container e.g. with the Web Console, a metatype descirptor would be useful describing the properties, their types and default values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2769) Provide Metatype Descriptor for Jetty Configuration properties
[ https://issues.apache.org/jira/browse/FELIX-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-2769. -- Resolution: Fixed Added a Metatype descriptor for Jetty Configuration in Rev. 1056629. > Provide Metatype Descriptor for Jetty Configuration properties > -- > > Key: FELIX-2769 > URL: https://issues.apache.org/jira/browse/FELIX-2769 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.0.6 > > > To support configuration of the Jetty embedded servlet container e.g. with > the Web Console, a metatype descirptor would be useful describing the > properties, their types and default values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
