5 Replies Latest reply on Aug 4, 2009 10:30 PM by Marius Bogoevici

    Reconsidering VFS URLS - JBoss5 and Spring

    sammy Jenkis Newbie

      I know there are several posts and jiras related to this issue, but I wanted to ask the question in possibly a different way.
      This post is related https://jira.jboss.org/jira/browse/JBSPRING-4, which basically describes a problem where Spring has trouble locating resources because the jar URL's have changed with JBoss 5's VFS. It’s also known on the Spring forums as http://jira.springframework.org/browse/SPR-5120.

      The thing is, a lot of people are burning a lot of time over this issue. I realize the VFS has the potential to be very clean, and I'm sure there are a lot of great benefits to it. But for my situation, I'm not getting any benefits from it, and I'm dealing with several applications that I can't deploy to JBoss 5 because they use Spring.

      Here’s what I’m wondering: Is there any way to configure JBoss 5 so we get the older style URLs from the classloader?

      If not, I think JBoss should consider adding backward compatibility support here. While one could argue this is Spring’s problem, there's now a lot of broken code that either uses Spring or made similar assumptions about JAR urls. I’m personally working with 5 projects that are broken because of this issue (most are Spring related, but not all). What do you think?