[
https://jira.jboss.org/jira/browse/JBSPRING-4?page=com.atlassian.jira.plu...
]
Canny Duck commented on JBSPRING-4:
-----------------------------------
Hi Marius,
thanks for your workaround implemention. It works but I still have a problem with resource
loading. I definded the folowing patterns to search up my message property files:
<util:list id="messages">
<value>classpath:/properties/**/*</value>
<value>classpath:/messages/**/*</value>
</util:list>
This works fine in Tomcat and Jetty Environment but in JBoss 5.0.1 the property entries
are not found and so the messages are not resolved. You have a solution for that problem?
Best regards
Canny Duck
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