Re: DependencyManager + DeploymentAdmin used in Apache ACE
> > > How about deploying them - as they are - at >> http://people.apache.org/repo/m2-snapshot-repository/org/apache/felix/ >> or similar ? >> > > I have no objections against that, and perhaps we could even automatically > deploy snapshots from within our continuous build server Bamboo. In fact, > that has already been discussed but I think there were some issues with that > (things that needed to be configured on the Bamboo server). > I'm +1 on this. Better release something that can be used / tested, then do not release it because it is not feature complete. -- Alin Dreghiciu Software Developer - Looking for new projects! My profile: http://www.linkedin.com/in/alindreghiciu My blog: http://adreghiciu.blogspot.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development.
Re: DependencyManager + DeploymentAdmin used in Apache ACE
Hello Toni, On Jun 29, 2009, at 23:36 , Toni Menzel wrote: Apache Ace, new in incubator and since last weekend also with code in svn, has some dependencies of Felix Subprojects like DependencyManager and (more important to me at least) DeploymentAdmin. Those have never released so far but should be, if you ask me, at least accessable as snapshot builds from some maven repository. Would that make big problems ? The dependency manager has been released and can be downloaded from the Felix website. Deployment admin has not yet been released, that is correct. It probably makes sense to start working towards a release of the latter, even if it's not 100% feature complete yet. How about deploying them - as they are - at http://people.apache.org/repo/m2-snapshot-repository/org/apache/felix/ or similar ? I have no objections against that, and perhaps we could even automatically deploy snapshots from within our continuous build server Bamboo. In fact, that has already been discussed but I think there were some issues with that (things that needed to be configured on the Bamboo server). Once they are there, its much easier to use/test/evaluate them even outside of Ace. True. For ACE itself it does not matter much, since it embeds all required components anyway (so it does not depend on any external repository). Greetings, Marcel
DependencyManager + DeploymentAdmin used in Apache ACE
Hi, Apache Ace, new in incubator and since last weekend also with code in svn, has some dependencies of Felix Subprojects like DependencyManager and (more important to me at least) DeploymentAdmin. Those have never released so far but should be, if you ask me, at least accessable as snapshot builds from some maven repository. Would that make big problems ? How about deploying them - as they are - at http://people.apache.org/repo/m2-snapshot-repository/org/apache/felix/ or similar ? Once they are there, its much easier to use/test/evaluate them even outside of Ace. ? cheers, Toni -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com t...@okidokiteam.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
[jira] Created: (FELIX-1285) SecureAction captures the calling context incorrectly
SecureAction captures the calling context incorrectly - Key: FELIX-1285 URL: https://issues.apache.org/jira/browse/FELIX-1285 Project: Felix Issue Type: Bug Components: Framework Affects Versions: felix-1.8.1 Reporter: Richard S. Hall Assignee: Karl Pauls Fix For: felix-2.0.0 In SecureAction we capture the calling context for optimization purposes, but the context captures the current stack no matter who is on the stack. Since the whole point of SecureAction is to allow the framework to perform sensitive operations without worrying about who is on the call stack, this seems to be a bug since there could be someone with lower privileges on the stack. I think we need to capture the calling context inside a privileged block. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1284) Support for the 'modified' operation (DS in OSGi 4.2 compendium)
[ https://issues.apache.org/jira/browse/FELIX-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-1284: - Fix Version/s: scr-1.2.0 Targetting for next release. > Support for the 'modified' operation (DS in OSGi 4.2 compendium) > > > Key: FELIX-1284 > URL: https://issues.apache.org/jira/browse/FELIX-1284 > Project: Felix > Issue Type: New Feature > Components: Declarative Services (SCR), Specification compliance >Reporter: Erin Schnabel > Fix For: scr-1.2.0 > > > 112.5.11-12, 112.7.1 from 4.2 Compendium spec (numbers may be slightly > different-- these are from the May 6 draft). > Modifying a component configuration can occur if > * the component description specifies the modified attribute and > * the component properties of the component configuration use a Configuration > object from the Configuration Admin service and > * that Configuration object is modified without causing the component > configuration to become unsatisfied. > If this occurs, the component instance will be _notified of the change in the > component properties_. > If the modified attribute is not specified, then the component configuration > will become unsatisfied if its component properties use a Configuration > object and that Configuration object is modified in any way. > -- > Basically: you can specify a 'modified' attribute/method that should be > called when ConfigAdmin pushes a changed configuration for a component, > instead of deactivating and then re-activating the component on a > configuration change. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1280) Package Admin - getExportedPackages must return null instead of an empty array
[ https://issues.apache.org/jira/browse/FELIX-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard S. Hall closed FELIX-1280. -- Resolution: Fixed Fix Version/s: felix-2.0.0 Assignee: Richard S. Hall I committed a fix. I will close this simple issue. Thanks. > Package Admin - getExportedPackages must return null instead of an empty array > -- > > Key: FELIX-1280 > URL: https://issues.apache.org/jira/browse/FELIX-1280 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: felix-1.8.1 >Reporter: Clement Escoffier >Assignee: Richard S. Hall >Priority: Minor > Fix For: felix-2.0.0 > > Attachments: org.apache.felix.framework.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > The PackageAdmin implementation has a minor bug in the getExportedPackages > method. According to the spec, this method must return null if the bundle > does not export any packages (currently). However, the Felix implementation > returns an empty array. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1284) Support for the 'modified' operation (DS in OSGi 4.2 compendium)
Support for the 'modified' operation (DS in OSGi 4.2 compendium) Key: FELIX-1284 URL: https://issues.apache.org/jira/browse/FELIX-1284 Project: Felix Issue Type: New Feature Components: Declarative Services (SCR), Specification compliance Reporter: Erin Schnabel 112.5.11-12, 112.7.1 from 4.2 Compendium spec (numbers may be slightly different-- these are from the May 6 draft). Modifying a component configuration can occur if * the component description specifies the modified attribute and * the component properties of the component configuration use a Configuration object from the Configuration Admin service and * that Configuration object is modified without causing the component configuration to become unsatisfied. If this occurs, the component instance will be _notified of the change in the component properties_. If the modified attribute is not specified, then the component configuration will become unsatisfied if its component properties use a Configuration object and that Configuration object is modified in any way. -- Basically: you can specify a 'modified' attribute/method that should be called when ConfigAdmin pushes a changed configuration for a component, instead of deactivating and then re-activating the component on a configuration change. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT] Re: [VOTE] Apache Felix File Install 1.2.0
The Apache Felix File Install 1.2.0 release has passed. The votes were: * Filippo Diotalevi, Richard S. Hall, Rob Walker, Clement Escoffier, Karl Pauls, and Toni Menzel. I will make the artifacts available shortly. -> richard On 6/22/09 4:45 PM, Richard S. Hall wrote: I'd like to call a vote for the Apache Felix File Install 1.2.0. We solved 8 issues in this release: http://issues.apache.org/jira/browse/FELIX/fixforversion/12313932 Staging repository: https://repository.apache.org/content/repositories/felix-staging-005/ 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 005 /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 72 hours.
[RESULT] Re: [VOTE] Apache Felix HTTP Service Jetty 1.0.1
The Apache Felix HTTP Service Jetty 1.0.1 release passes. The votes were: * +1 from Richard S. Hall, Rob Walker, Clement Escoffier, Karl Pauls, Stuart McCulloch, Marcel Offermans, and Guillaume Nodet. I will make the artifacts available shortly. -> richard On 6/24/09 12:05 PM, Richard S. Hall wrote: This release of Apache Felix HTTP Service Jetty addresses this issue: http://issues.apache.org/jira/browse/FELIX-1236 Staging repository: https://repository.apache.org/content/repositories/felix-staging-008/ 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 008 /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 72 hours.
[jira] Updated: (FELIX-1015) Hardcoded HTML Header/Footer in AbstractWebConsolePlugin
[
https://issues.apache.org/jira/browse/FELIX-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-1015:
-
Attachment: FELIX-1015-fmeschbe.patch
Thanks for providing your modified patch. I have extended it a bit:
* Extended the API to provide more branding information
* Default implementation extended
* Support reading branding information from META-INF/webconsole.properties in
the DefaultBrandingPlugin
the META-INF/webconsole.properties file is not provided by the Web Console
bundle itself. Instead it may be provided by a fragement attached to the web
console bundle.
See a whiteboard example I created for the Apache Sling project for an example
of providing branding in a fragment:
http://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/webconsolebranding/
WDYT ?
> Hardcoded HTML Header/Footer in AbstractWebConsolePlugin
>
>
> Key: FELIX-1015
> URL: https://issues.apache.org/jira/browse/FELIX-1015
> Project: Felix
> Issue Type: Sub-task
> Components: Web Console
>Affects Versions: webconsole-1.2.8
>Reporter: Thomas Diesler
>Assignee: Felix Meschberger
> Attachments: branding.patch, branding2.patch,
> FELIX-1015-fmeschbe.patch
>
>
> Instead of
> private static final String HEADER = " encoding=\"UTF-8\" ?>"
> + " \"xhtml1-transitional.dtd\">"
> + "http://www.w3.org/1999/xhtml\";>"
> + ""
> + ""
> + ""
> + "{0} - {2}"
> + " language=\"JavaScript\">"
> + " language=\"JavaScript\">"
> + " language=\"JavaScript\">"
> + ""
> + ""
> + "appRoot = \"{5}\";"
> + "pluginRoot = appRoot + \"/{6}\";"
> + ""
> + " type=\"text/css\">"
> + ""
> + ""
> + ""
> + ""
> + ""
> + "{0}{2}"
> + ""
> + ""
> + " src=\"{5}/res/imgs/logo.png\" width=\"165\" height=\"63\" border=\"0\">"
> + "" + "";
> we propose
> protected String getHeader()
> {
>String HEADER = ""
> + " \"xhtml1-transitional.dtd\">"
> + "http://www.w3.org/1999/xhtml\";>"
> + ""
> + ""
> + ""
> + "{0} - {2}"
> + " language=\"JavaScript\">"
> + " language=\"JavaScript\">"
> + " language=\"JavaScript\">"
> + ""
> + ""
> + "appRoot = \"{5}\";"
> + "pluginRoot = appRoot + \"/{6}\";"
> + ""
> + " type=\"text/css\">"
> + ""
> + ""
> + ""
> + ""
> + ""
> + "{0}{2}"
> + ""
> + ""
> + " src=\"{5}/res/imgs/logo.png\" width=\"165\" height=\"63\" border=\"0\">"
> + "" + "";
>return HEADER;
> }
> -
> protected PrintWriter startResponse( HttpServletRequest request,
> HttpServletResponse response ) throws IOException
> {
> ...
> String header = MessageFormat.format( getHeader(), new Object[]
> }
> protected void endResponse( HttpServletRequest request, PrintWriter pw )
> {
> pw.println( "" );
> pw.println( "" );
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1043) Support WebConsole plugins without requiring extending the AbstractWebConsolePlugin
[ https://issues.apache.org/jira/browse/FELIX-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1043. Resolution: Fixed Fix Version/s: webconsole-1.2.12 Tested this and it works even with a plugin providing resources. So considering this issue fixed for now. @Carsten: I18N is upto now no issue, so this is also ignored here. > Support WebConsole plugins without requiring extending the > AbstractWebConsolePlugin > --- > > Key: FELIX-1043 > URL: https://issues.apache.org/jira/browse/FELIX-1043 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-1.2.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: webconsole-1.2.12 > > Attachments: FELIX-1043.patch > > > Currently the web console can be extended by registering a > javax.servlet.Servlet service with a special service property naming the > label of the plugin. For ease of use (namely reusing the header and footer > renderings), plugins must extend the AbstractWebConsolePlugin. > The drawback of this requirement is, that any plugins require a class from > the web console plugin. It would be better to just register a plain servlet > which is rendered by the web console with headers and footers on behalf of > the plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1211) How to provide resources like CSS or JavaScript files for plugins
[ https://issues.apache.org/jira/browse/FELIX-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1211. Resolution: Fixed Fix Version/s: webconsole-1.2.12 Fixed a small glitch in Rev. 789288. Previously the getResource method has been looked up when the AbstractWebConsolePlugin class has been initialized. This causes the method to no be found for wrapped plugins because the field value returned by the getResourceProvider method is not set at the time of the initialization of the AbstractWebConsolePlugin instance. Apart from this minor glitch, this mechanis works and this issue can be closed. > How to provide resources like CSS or JavaScript files for plugins > - > > Key: FELIX-1211 > URL: https://issues.apache.org/jira/browse/FELIX-1211 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-1.2.10 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: webconsole-1.2.12 > > Attachments: FELIX-1211-getResource.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1281) Provide official constants of web console request attributes
[ https://issues.apache.org/jira/browse/FELIX-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1281. Resolution: Fixed The new attribtues are now provided while the old ones still exist (will probably be removed sometime in the future) for backwards compatibliy. Considering this issue fixed. > Provide official constants of web console request attributes > > > Key: FELIX-1281 > URL: https://issues.apache.org/jira/browse/FELIX-1281 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-1.2.10 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: webconsole-1.2.12 > > > The Web Console uses two request attibutes to convey the URI root path of the > web console and a map of labels and titles of registered plugins. Both > attributes may be of use to plugins and should be official constants in the > WebConsoleConstants interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1283) Order page titles in top navigation ignoring case
[ https://issues.apache.org/jira/browse/FELIX-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1283. Resolution: Fixed Implemented in Rev. 789282. > Order page titles in top navigation ignoring case > - > > Key: FELIX-1283 > URL: https://issues.apache.org/jira/browse/FELIX-1283 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-1.2.10 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: webconsole-1.2.12 > > > Currently the titles in the top navigation are not ordered ignoring case, > which causes titles with lowercase starting letters to appear at the end of > the list. This makes identifying the pages somewhat difficult. > It would be better to order the titles ignoring case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1283) Order page titles in top navigation ignoring case
Order page titles in top navigation ignoring case - Key: FELIX-1283 URL: https://issues.apache.org/jira/browse/FELIX-1283 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-1.2.10 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-1.2.12 Currently the titles in the top navigation are not ordered ignoring case, which causes titles with lowercase starting letters to appear at the end of the list. This makes identifying the pages somewhat difficult. It would be better to order the titles ignoring case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1282) Cleanup bundle: do not export SCR API, only embedd header parser
[ https://issues.apache.org/jira/browse/FELIX-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1282. Resolution: Fixed Cleaned up the POM in Rev. 789277. > Cleanup bundle: do not export SCR API, only embedd header parser > > > Key: FELIX-1282 > URL: https://issues.apache.org/jira/browse/FELIX-1282 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-1.2.10 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: webconsole-1.2.12 > > > Currently the Web Console bundle includes the complete bundlerepository > bundle and exports the SCR API. I think this is wrong in two ways: > * The OBR API should not be exported by the Web Console, but imported > * Not the complete bundle repository bundle is required just some classes > to parse the Import/Export-Package headers in > in-active bundles. > The project descriptor should be modified to just include those classes and > not export the SCR API any more. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1282) Cleanup bundle: do not export SCR API, only embedd header parser
Cleanup bundle: do not export SCR API, only embedd header parser Key: FELIX-1282 URL: https://issues.apache.org/jira/browse/FELIX-1282 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-1.2.10 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-1.2.12 Currently the Web Console bundle includes the complete bundlerepository bundle and exports the SCR API. I think this is wrong in two ways: * The OBR API should not be exported by the Web Console, but imported * Not the complete bundle repository bundle is required just some classes to parse the Import/Export-Package headers in in-active bundles. The project descriptor should be modified to just include those classes and not export the SCR API any more. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Embedding Felix in host app with a SecurityManager
Hi Karl, thanks, I figured as much... I'll see if i can make it work. I'll keep you posted. cheers, dennis On 29 jun 2009, at 10:56, Karl Pauls wrote: Thats a tricky one. Generally speaking, the framework needs AllPermission (as per spec). If that's not possible then things are getting really tricky. Sorry. You could try to hack stuff to not use the ExtensionManager and disable URLHandlers and see whether that makes it work... regards, Karl On Mon, Jun 29, 2009 at 10:44 AM, Dennis Geurts> wrote: Hi felix dev, I'm in a situation where I'd like to embed Apache Felix in a host application. The host application, however is equipped with a security manager that does not allow for the creation of a new security manager. This leads to the following error on startup: at org.mortbay.thread.BoundedThreadPool $PoolThread.run(BoundedThreadPool.java:442) Caused by: java.lang.ExceptionInInitializerError at org .apache .felix.framework.ExtensionManager.(ExtensionManager.java:142) at org.apache.felix.framework.Felix.(Felix.java:301) at net.luminis.testdgg.server.Framework.(Framework.java:39) at net .luminis.testdgg.server.OSGiServiceImpl.start(OSGiServiceImpl.java: 24) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun .reflect .DelegatingMethodAccessorImpl .invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) ... 25 more Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createSecurityManager) at java .security .AccessControlContext.checkPermission(AccessControlContext.java:264) at java .security.AccessController.checkPermission(AccessController.java:427) This happens because Felix extends the SecurityManager in SecurityManagerEx to allow for public access to getClassContext(). I do not see an easy way to overcome this situation. Am I missing something ? thanks in advance, dennis -- Karl Pauls karlpa...@gmail.com
Re: Embedding Felix in host app with a SecurityManager
Thats a tricky one. Generally speaking, the framework needs AllPermission (as per spec). If that's not possible then things are getting really tricky. Sorry. You could try to hack stuff to not use the ExtensionManager and disable URLHandlers and see whether that makes it work... regards, Karl On Mon, Jun 29, 2009 at 10:44 AM, Dennis Geurts wrote: > Hi felix dev, > > > I'm in a situation where I'd like to embed Apache Felix in a host > application. The host application, however is equipped with a security > manager > that does not allow for the creation of a new security manager. This leads > to the following error on startup: > > at > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) > Caused by: java.lang.ExceptionInInitializerError > at > org.apache.felix.framework.ExtensionManager.(ExtensionManager.java:142) > at org.apache.felix.framework.Felix.(Felix.java:301) > at net.luminis.testdgg.server.Framework.(Framework.java:39) > at > net.luminis.testdgg.server.OSGiServiceImpl.start(OSGiServiceImpl.java:24) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > ... 25 more > Caused by: java.security.AccessControlException: access denied > (java.lang.RuntimePermission createSecurityManager) > at > java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) > at > java.security.AccessController.checkPermission(AccessController.java:427) > > > This happens because Felix extends the SecurityManager in SecurityManagerEx > to allow for public access to getClassContext(). > I do not see an easy way to overcome this situation. Am I missing something > ? > > > thanks in advance, > > > dennis > > > -- Karl Pauls karlpa...@gmail.com
Embedding Felix in host app with a SecurityManager
Hi felix dev, I'm in a situation where I'd like to embed Apache Felix in a host application. The host application, however is equipped with a security manager that does not allow for the creation of a new security manager. This leads to the following error on startup: at org.mortbay.thread.BoundedThreadPool $PoolThread.run(BoundedThreadPool.java:442) Caused by: java.lang.ExceptionInInitializerError at org .apache.felix.framework.ExtensionManager.(ExtensionManager.java: 142) at org.apache.felix.framework.Felix.(Felix.java:301) at net.luminis.testdgg.server.Framework.(Framework.java:39) at net.luminis.testdgg.server.OSGiServiceImpl.start(OSGiServiceImpl.java: 24) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) at sun .reflect .DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25) at java.lang.reflect.Method.invoke(Method.java:585) ... 25 more Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createSecurityManager) at java .security .AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java: 427) This happens because Felix extends the SecurityManager in SecurityManagerEx to allow for public access to getClassContext(). I do not see an easy way to overcome this situation. Am I missing something ? thanks in advance, dennis
[jira] Commented: (FELIX-1043) Support WebConsole plugins without requiring extending the AbstractWebConsolePlugin
[ https://issues.apache.org/jira/browse/FELIX-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725084#action_12725084 ] Felix Meschberger commented on FELIX-1043: -- In Rev. 789260: Only have the abstract web console plugin handle the request for GET requests. Other requests are forwarded to the plugin directly. > Support WebConsole plugins without requiring extending the > AbstractWebConsolePlugin > --- > > Key: FELIX-1043 > URL: https://issues.apache.org/jira/browse/FELIX-1043 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-1.2.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Attachments: FELIX-1043.patch > > > Currently the web console can be extended by registering a > javax.servlet.Servlet service with a special service property naming the > label of the plugin. For ease of use (namely reusing the header and footer > renderings), plugins must extend the AbstractWebConsolePlugin. > The drawback of this requirement is, that any plugins require a class from > the web console plugin. It would be better to just register a plain servlet > which is rendered by the web console with headers and footers on behalf of > the plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Apache Felix HTTP Service Jetty 1.0.1
+1 On Wed, Jun 24, 2009 at 18:05, Richard S. Hall wrote: > This release of Apache Felix HTTP Service Jetty addresses this issue: > > http://issues.apache.org/jira/browse/FELIX-1236 > > Staging repository: > https://repository.apache.org/content/repositories/felix-staging-008/ > > 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 008 /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 72 hours. > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
[jira] Commented: (FELIX-1211) How to provide resources like CSS or JavaScript files for plugins
[ https://issues.apache.org/jira/browse/FELIX-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725072#action_12725072 ] Felix Meschberger commented on FELIX-1211: -- Applied slightly modified patch in Rev. 789246. The modifications are : * Prevent an NPE from being thrown as indicated by Tim Moloney (Thanks) * Add support for the WebConsolePluginAdapter to have the wrapped plugin to provide resources > How to provide resources like CSS or JavaScript files for plugins > - > > Key: FELIX-1211 > URL: https://issues.apache.org/jira/browse/FELIX-1211 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-1.2.10 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Attachments: FELIX-1211-getResource.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1281) Provide official constants of web console request attributes
[ https://issues.apache.org/jira/browse/FELIX-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725066#action_12725066 ] Felix Meschberger commented on FELIX-1281: -- In Rev. 789243 added two constants to the WebConsoleConstants interface: ATTR_APP_ROOT = "felix.webconsole.appRoot"; ATTR_LABEL_MAP = "felix.webconsole.labelMap"; providing the web console root path and the map of labels/titles of registered plugins. These request attributes are provided by the web console servlet before calling into the console plugin. > Provide official constants of web console request attributes > > > Key: FELIX-1281 > URL: https://issues.apache.org/jira/browse/FELIX-1281 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-1.2.10 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: webconsole-1.2.12 > > > The Web Console uses two request attibutes to convey the URI root path of the > web console and a map of labels and titles of registered plugins. Both > attributes may be of use to plugins and should be official constants in the > WebConsoleConstants interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1043) Support WebConsole plugins without requiring extending the AbstractWebConsolePlugin
[ https://issues.apache.org/jira/browse/FELIX-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725064#action_12725064 ] Felix Meschberger commented on FELIX-1043: -- Applied the patch slightly modified in Rev. 789241. The modification refers to the activation and deavation of the AbstractWebConsolePlugin extended by the WebConsolePluginAdapter. The BundleContext used for activation is the BundleContext of the Bundle registering the plugin servlet service. > Support WebConsole plugins without requiring extending the > AbstractWebConsolePlugin > --- > > Key: FELIX-1043 > URL: https://issues.apache.org/jira/browse/FELIX-1043 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-1.2.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Attachments: FELIX-1043.patch > > > Currently the web console can be extended by registering a > javax.servlet.Servlet service with a special service property naming the > label of the plugin. For ease of use (namely reusing the header and footer > renderings), plugins must extend the AbstractWebConsolePlugin. > The drawback of this requirement is, that any plugins require a class from > the web console plugin. It would be better to just register a plain servlet > which is rendered by the web console with headers and footers on behalf of > the plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1043) Support WebConsole plugins without requiring extending the AbstractWebConsolePlugin
[ https://issues.apache.org/jira/browse/FELIX-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned FELIX-1043: Assignee: Felix Meschberger > Support WebConsole plugins without requiring extending the > AbstractWebConsolePlugin > --- > > Key: FELIX-1043 > URL: https://issues.apache.org/jira/browse/FELIX-1043 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-1.2.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Attachments: FELIX-1043.patch > > > Currently the web console can be extended by registering a > javax.servlet.Servlet service with a special service property naming the > label of the plugin. For ease of use (namely reusing the header and footer > renderings), plugins must extend the AbstractWebConsolePlugin. > The drawback of this requirement is, that any plugins require a class from > the web console plugin. It would be better to just register a plain servlet > which is rendered by the web console with headers and footers on behalf of > the plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
