[ https://issues.apache.org/jira/browse/ARIES-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295346#comment-13295346 ]
Christian Schneider commented on ARIES-861: ------------------------------------------- I think we could test if there is a no args constructor and use it if it is there. So for older JDK versions it would work like before and for the current version there would have to be a no args constructor. We could add it to BlueprintCommand and it would work again. Of course this is not the long term solution but I think it would help us till we find a better way. > 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 > Fix For: proxy.impl-0.4 > > > 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