[jira] [Commented] (GERONIMO-6132) Not search wired bundles in bundle classloader by default

["Jarek Gawor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GERONIMO-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467501#comment-13467501 ] 

Jarek Gawor commented on GERONIMO-6132:
---------------------------------------

Moving the searchWiredBundles property to etc/system.properties created the following problem for app client container:

Caused by: java.lang.IllegalArgumentException: Could not find client identity strategy 'geronimo'
	at org.apache.openejb.client.ClientSecurity.getIdentityResolver(ClientSecurity.java:163)
	at org.apache.openejb.client.ClientSecurity.getIdentity(ClientSecurity.java:148)
	at org.apache.openejb.client.EJBInvocationHandler.getClientIdentity(EJBInvocationHandler.java:164)

I was able to work-around that by setting the identity resolver to GeronimoIdentityResolver using OpenEJB's ClientSecurity API. Changes committed in revision 1392749.

                
> Not search wired bundles in bundle classloader by default
> ---------------------------------------------------------
>
>                 Key: GERONIMO-6132
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6132
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: Ivan
>            Assignee: Ivan
>             Fix For: 3.0
>
>
> From the testing result, it seems that all the functions works well without searching wired bundles. Also, considering that all kinds of Java EE applications are installed as one bundle, including EAR package, it should not an issue for user application to finding the resources in the same application.
> I am thinking to change the codes in xbean and geronimo-hook, by default, wired bundles will not be searched.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira