[jboss-jira] [JBoss JIRA] Commented: (JBSPRING-4) Classpath scanning in Spring-based web applications and VFS using Spring 2.5.x and JBoss 5.0/5.1

[David Ward (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSPRING-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12486128#action_12486128 ] 

David Ward commented on JBSPRING-4:
-----------------------------------

At Alfresco we found that the VFSResource implementation still didn't work with some of our webapps that would work in Tomcat. For example this context file that uses ".." in a relative URL

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>

<beans>
   <!--
      The bean definitions for this subsystem are shared by the ldap and ldap-ad subsystems with different property
      defaults
   -->
   <import resource="../common-ldap-context.xml" />
</beans>

We fixed our own VFSResource implementation as follows

public Resource createRelative(String relativePath) throws IOException

{ return new VFSResource(VFS.getRoot(new URL(getURL(), relativePath))); } 

Please consider reopening this issue and fixing as above.


> Classpath scanning in Spring-based web applications and VFS using Spring 2.5.x and JBoss 5.0/5.1
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBSPRING-4
>                 URL: https://jira.jboss.org/jira/browse/JBSPRING-4
>             Project: JBoss Spring Integration
>          Issue Type: Bug
>            Reporter: Marius Bogoevici
>            Assignee: Marius Bogoevici
>         Attachments: jboss-spring-int-deployers.jar, jboss-spring-int-vfs.jar
>
>
> As reported in the forum issue, classpath scanning in Spring does not work properly in conjunction with VFS. A fix has been created, in the form of the VFSResourceResolver, but there are still issues reported against it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira