[ http://issues.apache.org/jira/browse/MUSE-168?page=comments#action_12459643 ] Dan Jemiolo commented on MUSE-168: ----------------------------------
This is a result of fixing MUSE-141 - in both the Axis2 and Mini projects read from WEB-INF/classes in order to allow initialization within a packaged jar/war. WEB-INF/classes is in the classpath of the web application, so we can read files from it without referencing the underlying file system directly (with java.io.File). It's not an architecture change, it's just relying on the J2EE classloader instead of the Axis2 classloader; the directories and files are all in the same layout, but under /classes instead of /services. The only file that needs to be under WEB-INF/services/muse for Axis2 apps is services.xml. Make sure when you download/install 2.1.0 that you run the update-install script as specified in the tutorial - don't just copy over the old libraries you had for 2.0. Axis2 1.1 has been released since 2.0 was released and some backwards compatiblity was lost in it (and we had to work around it). As with the previous item, I think if you run wsdl2java on your WSDLs or the sample builds on the 2.1 code/samples, you'll find they work - if you try and overlay or mix them with old 2.0 projects/content, they will not. The reasons go back to MUSE-141 and compatibility changes in Axis2 1.1 Final. > Muse 2.2.0 deploy structure changed, can't find muse.xml and other files > ------------------------------------------------------------------------ > > Key: MUSE-168 > URL: http://issues.apache.org/jira/browse/MUSE-168 > Project: Muse > Issue Type: Bug > Affects Versions: 2.1.0 > Environment: Muse 2.1.0, Tomcat 5.5, Apache 2.2, Eclipse 3.2.1, JDK > 1.5.0 > Reporter: Vinh Nguyen > Assigned To: Dan Jemiolo > > Ramesh brought this issue up earlier, and Dan submitted a fix, but I don't > think it's the correct fix. > In 2.0.0, the muse.xml, wsdl folder, and router-entries folder were in the > WEB-INF/services/muse folder. But now, 2.1.0 only works if these items are > moved to the /classes folder. I don't think this is right as I don't see why > any non-class files are supposed to be in the /classes folder. > During the 2.1.0 pre-release voting period, this issue arose and Dan fixed > the build.xml in the samples to automatically copy these files to the > /classes folder, so the samples work when deployed. But, my current 2.0.0 > project breaks in 2.1.0 because of the changed dir structure. > If these dir changes are permanent going forward, then nothing needs to be > done, but the architecture change should be described to the community in > some release details. If this is not the intended change for 2.1.0, then > there is a bug in the Muse code, and all the build.xml files in the samples > need to be fixed back to 2.0.0 dir style. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
