[jira] Commented: (FELIX-1962) Add support for (select) Servlet API listeners
[ https://issues.apache.org/jira/browse/FELIX-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795900#action_12795900 ] Sten Roger Sandvik commented on FELIX-1962: --- Cool. Was thinking of supporting this in both ExtHttpService and whiteboard. Will check out your patch. Also support for HttpSession*Listeners should be possible. ServletContextListeners could be nice to have if you want to use unmodified code that depend on such startup mechanism. Add support for (select) Servlet API listeners -- Key: FELIX-1962 URL: https://issues.apache.org/jira/browse/FELIX-1962 Project: Felix Issue Type: New Feature Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Felix Meschberger Attachments: FELIX-1962.patch The new Http Service implementation currently does not support any Servlet API listeners at all. Support for some listeners can easily be implemented in a transparent way: ServletContextAttributeListener, ServletRequestListener, ServletRequestAttributeListener. The HttpSession listeners can probably not easily be implemented in such a transparent way. The ServletContextListener is probably not worth it supporting. Most (if not all) use cases for ServletContextListeners in traditional web applications can be solved in better ways in an OSGi framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1962) Add support for (select) Servlet API listeners
[ https://issues.apache.org/jira/browse/FELIX-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sten Roger Sandvik updated FELIX-1962: -- Fix Version/s: http-2.0.6 Moving this to version 2.0.6. Add support for (select) Servlet API listeners -- Key: FELIX-1962 URL: https://issues.apache.org/jira/browse/FELIX-1962 Project: Felix Issue Type: New Feature Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Felix Meschberger Fix For: http-2.0.6 Attachments: FELIX-1962.patch The new Http Service implementation currently does not support any Servlet API listeners at all. Support for some listeners can easily be implemented in a transparent way: ServletContextAttributeListener, ServletRequestListener, ServletRequestAttributeListener. The HttpSession listeners can probably not easily be implemented in such a transparent way. The ServletContextListener is probably not worth it supporting. Most (if not all) use cases for ServletContextListeners in traditional web applications can be solved in better ways in an OSGi framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1963) Add possibility to share ServletContext between bundles
Add possibility to share ServletContext between bundles --- Key: FELIX-1963 URL: https://issues.apache.org/jira/browse/FELIX-1963 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Sten Roger Sandvik Assignee: Sten Roger Sandvik Fix For: http-2.0.6 Check out the possibility to share ServletContext between bundles. If ServletContextManager is global instead of local to each bundle then it chould be done. If you want to share ServletContext each HttpContext must implement equals method that ensures equality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1963) Add possibility to share ServletContext between bundles
[ https://issues.apache.org/jira/browse/FELIX-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sten Roger Sandvik updated FELIX-1963: -- Issue Type: New Feature (was: Bug) Add possibility to share ServletContext between bundles --- Key: FELIX-1963 URL: https://issues.apache.org/jira/browse/FELIX-1963 Project: Felix Issue Type: New Feature Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Sten Roger Sandvik Assignee: Sten Roger Sandvik Fix For: http-2.0.6 Check out the possibility to share ServletContext between bundles. If ServletContextManager is global instead of local to each bundle then it chould be done. If you want to share ServletContext each HttpContext must implement equals method that ensures equality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1946) jetty http service issues 'started' message when disabled
[ https://issues.apache.org/jira/browse/FELIX-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sten Roger Sandvik updated FELIX-1946: -- Fix Version/s: http-2.0.6 Assignee: Sten Roger Sandvik jetty http service issues 'started' message when disabled - Key: FELIX-1946 URL: https://issues.apache.org/jira/browse/FELIX-1946 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Derek Baum Assignee: Sten Roger Sandvik Priority: Minor Fix For: http-2.0.6 I want to configure the felix jetty http service using config admin, so I set the following properties to stop it from starting automatically: org.osgi.service.http.port = -1 org.apache.felix.http.enable = false However, when the bundle is activated, it still reports that it has started: % [INFO] Started jetty 6.1.x at port -1 A 'Jetty HTTP Service' thread is actually started, but as http is not enabled, no http server connector is created. The above 'Started' message should not appear when http (and https) are disabled, and it would be good if the 'Jetty HTTP Service' was not created until the service is enabled using config admin, for example: % setpid org.apache.felix.http org.osgi.service.http.port==1234 org.apache.felix.http.enable==true % [INFO] Started jetty 6.1.x at port 1234 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1946) jetty http service issues 'started' message when disabled
[ https://issues.apache.org/jira/browse/FELIX-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795903#action_12795903 ] Sten Roger Sandvik commented on FELIX-1946: --- You are right. The message appears always. Will schedule this fix for version 2.0.6. jetty http service issues 'started' message when disabled - Key: FELIX-1946 URL: https://issues.apache.org/jira/browse/FELIX-1946 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Derek Baum Priority: Minor Fix For: http-2.0.6 I want to configure the felix jetty http service using config admin, so I set the following properties to stop it from starting automatically: org.osgi.service.http.port = -1 org.apache.felix.http.enable = false However, when the bundle is activated, it still reports that it has started: % [INFO] Started jetty 6.1.x at port -1 A 'Jetty HTTP Service' thread is actually started, but as http is not enabled, no http server connector is created. The above 'Started' message should not appear when http (and https) are disabled, and it would be good if the 'Jetty HTTP Service' was not created until the service is enabled using config admin, for example: % setpid org.apache.felix.http org.osgi.service.http.port==1234 org.apache.felix.http.enable==true % [INFO] Started jetty 6.1.x at port 1234 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1955) Possibility to configure keystore type (Currently only JKS is available)
[ https://issues.apache.org/jira/browse/FELIX-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795905#action_12795905 ] Sten Roger Sandvik commented on FELIX-1955: --- Will investigate this and find a way to support other keystore's. Possibility to configure keystore type (Currently only JKS is available) Key: FELIX-1955 URL: https://issues.apache.org/jira/browse/FELIX-1955 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Boris Toninski There should be a way to configure the keystore type to be used for SSL comunication. Currently as I can see JKS is used as default in org.mortbay.jetty.security.SslSocketConnector. The problem with this is that there are classpath implementations that do not support JKS keystore algorithm. We develop a project which runs on such classpath and this is a real stopper for us. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (FELIX-1963) Add possibility to share ServletContext between bundles
I traced ServletContext in diffrent bundles , seems it has been shared. In org.apache.felix.http.base.internal.DispatcherServlet this.controller.register(getServletContext()); will get only ServletContext which provided by jetty. put it in HttpServiceFactory When servlet register, retrived this servletContext from HttpServiceFactory. I think the servlet context has been shard , at least in my application. Tommy Wang On Sun, Jan 3, 2010 at 3:25 AM, Sten Roger Sandvik (JIRA) j...@apache.orgwrote: [ https://issues.apache.org/jira/browse/FELIX-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] Sten Roger Sandvik updated FELIX-1963: -- Issue Type: New Feature (was: Bug) Add possibility to share ServletContext between bundles --- Key: FELIX-1963 URL: https://issues.apache.org/jira/browse/FELIX-1963 Project: Felix Issue Type: New Feature Components: HTTP Service Affects Versions: http-2.0.4 Reporter: Sten Roger Sandvik Assignee: Sten Roger Sandvik Fix For: http-2.0.6 Check out the possibility to share ServletContext between bundles. If ServletContextManager is global instead of local to each bundle then it chould be done. If you want to share ServletContext each HttpContext must implement equals method that ensures equality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
