aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Siano (JIRA)" <>
Subject [jira] [Updated] (ARIES-1065) Blueprint - ServiceFactory can't be specified as the bean class
Date Thu, 08 Aug 2013 12:10:47 GMT


Stephan Siano updated ARIES-1065:

    Attachment: ARIES1063-ARIES1065-ServiceFactory-cant-be-specified.patch

Merges this patch with the one from ARIES-1063
> Blueprint - ServiceFactory can't be specified as the bean class
> ---------------------------------------------------------------
>                 Key: ARIES-1065
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>            Reporter: Simon Gormley
>         Attachments: ARIES1063-ARIES1065-ServiceFactory-cant-be-specified.patch, blueprint_servicefactory.patch,
> Specifying a class that implements org.osgi.framework.ServiceFactory as the bean class
causes an error indicating that the class does not implement the specified interfaces.
> e.g. a blueprint.xml containing:
> <?xml version="1.0" encoding="UTF-8"?>
> <blueprint xmlns="">
> 	<bean id="MyServiceImplBean" class="com.code.impl.MyServiceFactory"/>
> 	<service ref="MyServiceImplBean" id="MyServiceImplBeanService" interface="com.code.api.MyServiceInterface"></service>
> </blueprint>
> Where MyServiceFactory implements ServiceFactory and can be used to obtain the actual
service class that implements the MyServiceInterface would cause an error indicating that
MyServiceFactory does not implement MyServiceInterface (which is true)
> Suggested fix (patch attached) is to ensure for this case that the proxy class indicates
it implements the ServiceFactory interface, and then delay validation until after the service
is obtained.

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:

View raw message