[ http://issues.apache.org/jira/browse/MUSE-168?page=comments#action_12459810 ] Vinh Nguyen commented on MUSE-168: ----------------------------------
Thanks again Dan. I see the new changes described in the 2.1.0 tutorials. I will try to test further and adapt to the new setup. > 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]
