[
https://jira.jboss.org/browse/JBAS-8543?page=com.atlassian.jira.plugin.sy...
]
David Bosschaert commented on JBAS-8543:
----------------------------------------
I dug a little deeper and managed to get the tests passing. The issue turned out to be the
following.
In JBoss Modules paths (e.g. exported paths) are always expressed using unix separators
'/'. Also when loading files from VFS the forward slash is always needed (this
might be indirectly caused by the modules constraint). The OSGi code uses File.separator
when registering exported paths so that becomes '\' on Windows. Also when loading
class files from VFS the OSGi code converts the class name to a file name using
File.separator which is then not found.
I managed to get the tests passing with the changes on the following two repos (branch
name: jbas8543):
http://github.com/jbosgi/jbosgi-vfs/tree/jbas8543
http://github.com/jbosgi/jbosgi-framework/commits/jbas8543
I came across one other issue:
ModuleAccessesOSGiServiceTestCase.testModuleInvokesTargetBundleService() passes for me
with the above fixes when run on its own. However it fails when run as part of the larger
set.
Whether the fix that I put on this branch is the desired solution depends on the outcome
of this discussion:
http://community.jboss.org/thread/158022
Verify AS functionality on Windows
----------------------------------
Key: JBAS-8543
URL:
https://jira.jboss.org/browse/JBAS-8543
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assignee: David Bosschaert
SachaL reports build problems on AS7 master.
Please post a link to the Hudson QA that shows the matrix of supported OS
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira