[
https://issues.apache.org/jira/browse/TUSCANY-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Housley updated TUSCANY-2882:
----------------------------------
Attachment: tuscany-spring-url.zip
Test case of various different spring configurations. This file is a zipped
maven project (and eclipse project files) for a web application, using tuscany
filter.
The aim is to load a composite called "One", which loads a Spring context from
a beans file in the war, which imports a further beans file from inside a jar
in the lib folder. End result should be the output "TestBean()" as a spring
bean is created.
The example will work if you change the compositeContext-One.xml file to import
a relative path, as per the comment in the file.
For comparison, the commented out section in One.composite will trigger
programatic starting of the spring context using
ClassPathXmlApplicationContext, rather than using implementation.spring.
Please let me know if this could be clearer.
> Relative path imports don't work in Spring implementations.
> -----------------------------------------------------------
>
> Key: TUSCANY-2882
> URL: https://issues.apache.org/jira/browse/TUSCANY-2882
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Spring Implementation Extension
> Affects Versions: Java-SCA-1.5
> Reporter: Phil Housley
> Attachments: tuscany-spring-url.zip
>
>
> Using implementation.spring, the Tuscany bean file parser and Spring's parser
> interpret import links in different ways. Spring sees them as relative,
> tuscany as absolute, so one parser will generally fail unless everything goes
> into a root folder.
> I have a patch for this, using Spring's relative resource system, but I
> cannot guarantee that the two parsers now use the same mechanisms. I'll
> attach when I've cleaned it up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
