> Yes, it's only recompiling - nothing more (well, at least in > theory :) ) > > Carsten >
For non-trivial Cocoon sites the 2.0.x to 2.1 migration will require more than just recompiling component classes. There are incompatibilities on different levels. The ones I am aware of are: 1.) sitemap.xmap must add <map:pipes> in components definition. 2.) File upload class name changed from o.a.c.components.request.multipart.FilePart to o.a.c.servlet.multipart.Part. 3.) File upload method names changed from FilePart.getFilePath() to Part.getUploadName(). (Need to confirm on this one. I don't have file upload working yet with M2.) 4.) RequestGenerator changed namespace from http://xml.apache.org/cocoon/requestgenerator/2.0 to http://apache.org/cocoon/request/2.0. I don't think it is worthwhile to attempt complete backwards compatibilitity in 2.0 to 2.1. Instead there should be a Migration Guide listing the known incompatibilities in a more comprehendable form than the Changes file. Otherwise Cocoon users will be in for a rough ride in the migration, possible producing a lot of bad press at this crucial moment. Cheers, Alfred. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company.
