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

ASF subversion and git services commented on ARIES-1861:
--------------------------------------------------------

Commit 1846591 from gno...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1846591 ]

[ARIES-1861] Blueprint Spring does not work without internet connection

> Blueprint Spring does not work without internet connection
> ----------------------------------------------------------
>
>                 Key: ARIES-1861
>                 URL: https://issues.apache.org/jira/browse/ARIES-1861
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: blueprint-spring-extender-0.4.0
>            Reporter: Zsolt Beothy-Elo
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: blueprint-spring-extender-0.6.0
>
>         Attachments: blueprint-spring.zip, karaf.log
>
>
> We are migrating for a customer a lot of old Spring-DM based bundles he used 
> to run on a Karaf 2.x to Karaf 4.x. We were hoping to leverage the Blueprint 
> Spring functionality available in Karaf to not have to not have to change to 
> Blueprint (at least for now).
> Unfortunately, it doesn't seem to work when no internet connection is 
> available, because it is trying to download the spring bean schema 
> 'http://www.springframework.org/schema/osgi/spring-osgi.xsd'.
> I created a simple Spring-DM based bundle  based on the Aries blueprint Hello 
> World sample and I am able successfully run it on a Karaf 4.2.1 - start 
> karaf, install aries-blueprint-spring and copy the jar to the deploy folder 
> => bundle starts and service is available. Same scenario with internet 
> connection disabled => the bundle is in failed status .
> I have attached the simple project and the Karaf log file with the exception.
> Requiring a internet connection is a no go for the customer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to