[jira] [Resolved] (ARIES-863) Blueprint container needs to use bundle's permissions, not its own permissions, for looking up services
[ https://issues.apache.org/jira/browse/ARIES-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Holly Cummins resolved ARIES-863. - Resolution: Fixed Now fixed. (The subversion commits are probably listed under ARIES-363 by accident.) Blueprint container needs to use bundle's permissions, not its own permissions, for looking up services --- Key: ARIES-863 URL: https://issues.apache.org/jira/browse/ARIES-863 Project: Aries Issue Type: Bug Components: Blueprint Affects Versions: blueprint-core-0.4.1, 1.0 Reporter: Holly Cummins Assignee: Holly Cummins Priority: Minor We've regressed the testNoImportPermission test in the blueprint.secure suite of the OSGi compliance tests (from a clean run in 0.3). What it's testing is that when the blueprint container gets services on behalf of a bundle, it uses that bundle's permission. ARIES-727 switched from the ReferenceRecipe calling the getService() method on BluePrintContainerImpl to calling getService() itself. I believe the reason was to allow different bundle contexts to be used for some references and reference lists, to support namespace handlers adding service references. ARIES-816 re-introduced a doPrivileged block, but using the privileges of the blueprint code, not the managed bundle. I think in the case where a reference uses a different bundle context, the lookup should probably be done with the privileges of the bundle which can 'see' the service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ARIES-861) Error on retrieving constructor for proxy of karaf BlueprintCommand class on jdk 6 update 33
[ https://issues.apache.org/jira/browse/ARIES-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved ARIES-861. --- Resolution: Fixed Vote started. Error on retrieving constructor for proxy of karaf BlueprintCommand class on jdk 6 update 33 Key: ARIES-861 URL: https://issues.apache.org/jira/browse/ARIES-861 Project: Aries Issue Type: Bug Components: Proxy Reporter: Christian Schneider Assignee: Daniel Kulp Fix For: proxy.impl-0.4.1 When I switch my karaf trunk snapshot from jdk 6 update 31 to update 33 all karaf commands stop working. I was able to track this down to blueprint and the proxy facility or aries. The exception I get is: org.osgi.framework.ServiceException: Service factory exception: (class: org/apache/karaf/shell/console/commands/$BlueprintCommand16496117, method: init signature: (Ljava/lang/reflect/InvocationHandler;)V) Call to wrong initialization method In the log this does not show. There I only get a Nullpointer exception as the service object for the command is returned as null. I have documented more details in the linked karaf issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Proxy 0.3.1 and 0.4.1
+infinity on this. On Jun 22, 2012, at 10:09 AM, Daniel Kulp wrote: This is a vote to release versions 0.3.1 and 0.4.1 of the proxy impl and bundle. The only real change is a fix for ARIES-861 to allow the class based proxies to have any chance of working with JDK6 update 33 and JDK7 update 5. Staging repos: https://repository.apache.org/content/repositories/orgapachearies-264 https://repository.apache.org/content/repositories/orgapachearies-265 Tags: http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.proxy-0.3.1/ http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.proxy-0.4.1/ http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.proxy.impl-0.3.1/ http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.proxy.impl-0.4.1/ Here is my +1. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Jenkins build is still unstable: Aries » Apache Aries JNDI iTests for jndi-url #1522
See https://builds.apache.org/job/Aries/org.apache.aries.jndi$org.apache.aries.jndi.url.itest/1522/
Jenkins build is still unstable: Aries #1522
See https://builds.apache.org/job/Aries/changes
Jenkins build is still unstable: Aries » Apache Aries JNDI iTests for jndi-url #1523
See https://builds.apache.org/job/Aries/org.apache.aries.jndi$org.apache.aries.jndi.url.itest/1523/
Jenkins build is still unstable: Aries » Apache Aries Blog sample iTests #1523
See https://builds.apache.org/job/Aries/org.apache.aries.samples.blog$org.apache.aries.samples.blog.itests/1523/
Jenkins build is still unstable: Aries #1523
See https://builds.apache.org/job/Aries/1523/
[jira] [Commented] (ARIES-861) Error on retrieving constructor for proxy of karaf BlueprintCommand class on jdk 6 update 33
[ https://issues.apache.org/jira/browse/ARIES-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399522#comment-13399522 ] Holly Cummins commented on ARIES-861: - I'm seeing local test failures in the proxy tests running with r33, presumably for the cases that we just can't handle, even after this fix. Should we disable the tests, or hope that we can find a more clever long-term workaround, or ...? (I don't think we should leave the tests failing long term, since it makes it easy to inadvertently commit other test regressions.) Error on retrieving constructor for proxy of karaf BlueprintCommand class on jdk 6 update 33 Key: ARIES-861 URL: https://issues.apache.org/jira/browse/ARIES-861 Project: Aries Issue Type: Bug Components: Proxy Reporter: Christian Schneider Assignee: Daniel Kulp Fix For: proxy.impl-0.4.1 When I switch my karaf trunk snapshot from jdk 6 update 31 to update 33 all karaf commands stop working. I was able to track this down to blueprint and the proxy facility or aries. The exception I get is: org.osgi.framework.ServiceException: Service factory exception: (class: org/apache/karaf/shell/console/commands/$BlueprintCommand16496117, method: init signature: (Ljava/lang/reflect/InvocationHandler;)V) Call to wrong initialization method In the log this does not show. There I only get a Nullpointer exception as the service object for the command is returned as null. I have documented more details in the linked karaf issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ARIES-861) Error on retrieving constructor for proxy of karaf BlueprintCommand class on jdk 6 update 33
[ https://issues.apache.org/jira/browse/ARIES-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399527#comment-13399527 ] Daniel Kulp commented on ARIES-861: --- Is it the testFinalConstructor test? I did stick an @Ignore on that on the fixes branches for that exact reason. So yea, disable it. Error on retrieving constructor for proxy of karaf BlueprintCommand class on jdk 6 update 33 Key: ARIES-861 URL: https://issues.apache.org/jira/browse/ARIES-861 Project: Aries Issue Type: Bug Components: Proxy Reporter: Christian Schneider Assignee: Daniel Kulp Fix For: proxy.impl-0.4.1 When I switch my karaf trunk snapshot from jdk 6 update 31 to update 33 all karaf commands stop working. I was able to track this down to blueprint and the proxy facility or aries. The exception I get is: org.osgi.framework.ServiceException: Service factory exception: (class: org/apache/karaf/shell/console/commands/$BlueprintCommand16496117, method: init signature: (Ljava/lang/reflect/InvocationHandler;)V) Call to wrong initialization method In the log this does not show. There I only get a Nullpointer exception as the service object for the command is returned as null. I have documented more details in the linked karaf issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
