[
https://issues.apache.org/jira/browse/TUSCANY-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam reassigned TUSCANY-3128:
--------------------------------------------
Assignee: Ramkumar Ramalingam
> Spring app context classloader doesn't find contribution artifacts if the
> contribution isn't also on the application classpath
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3128
> URL: https://issues.apache.org/jira/browse/TUSCANY-3128
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Spring Implementation Extension
> Affects Versions: Java-SCA-1.5
> Environment: Win XP SP2 Sun JDK1.6
> Reporter: Simon Laws
> Assignee: Ramkumar Ramalingam
> Fix For: Java-SCA-Next
>
>
> The SpringContextTie.createApplicationContext() operation tries to set up the
> beanFactory classpath to be the contribution classpath. However tracing in
> the debugger it seems that the GenericApplicationContext.refresh() method
> always sets it back to the application classpath.
> To get round this I've extended the GenericApplicationContext class to do
> some post processing and push the contribution classpath back into the
> beanFactory after it has been rest. I'll commit if I get a clean built.
> recently
> However there have been a number of classpath processing changes in
> implementation spring so it would be good if Ram could take a look at this
> and see if this problem has always been there or if it's just come up due to
> other changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
