[ http://issues.apache.org/jira/browse/AXIS2-598?page=comments#action_12376691 ]
Michel.Drescher commented on AXIS2-598: --------------------------------------- Hi Dims, the bug occurred on the client side. At the moment, I deploy axis2.war in Tomcat, and add my service(s) as needed. Here, the axis2.xml refers to a conf and modules directory, so the bug environment does not apply. On the client side, I intentionally do *not* use a file system based configuration as the client applications I write must be completely location and OS independent. Hence the only way to load the modules is via $CLASSPATH, and manually engage the modules as needed. The module(s) are found when $CLASSPATH does not contain LWS, and are *not* when LWS are present. I did not test other special charactrers like TAB, NUL, etc. I will check wheher the bug still exists with Axis 1.0RC3 Cheers, Michel > $CLASSPATH based module discovery does not work with LWS (linear white spaces) > ------------------------------------------------------------------------------ > > Key: AXIS2-598 > URL: http://issues.apache.org/jira/browse/AXIS2-598 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: core > Versions: 0.94 > Environment: Mac OS X 10.4.6, Java 5.0 > Reporter: Michel.Drescher > > When having linear white spaces (ASCII code 32) in the class path, the > discovery of Axis2 modules fails with "AxisFault: Module not found". > Keeping the exact same environment except replacing the LWS with something > different solves the problem. > Cheers, > Michel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
