Hugh OTOH, it also sounds quite depressing that lots of what we have learnt in the past now has to be thrown away. I suppose it is All For Our Own Good... but, nonetheless, it all means more work ito upgrading and supporting legacy apps and in learning new ways to create new apps. Cocoon unfortunately does not have a great track record when it comes to documentation (which has possibly hindered its uptake in the past). I am wondering if this will change now or whether what you are going through is a repeat of the symptom. Derek
>>> "Hugh Sparks" <[EMAIL PROTECTED]> 2007/10/19 07:36 AM >>> > Michel Erard writes: > > Hi Hugh, > ... > you need the declaration of the namespace in the applicationContext.xml. > Here the begining of my whole file: > ... It works! You have Changed My Life. I am surprised about something: Where are all the xconf files and other goop that normally has to exist somewhere to get cocoon working? I couldn't find anything like that in the target directory. I must say that Cocoon 2.2 is looking almost lean and elegant! If I do need to configure one of the core components, where would I put an xconf file to get the job done? Or is this now done with Spring somehow? There is much I need to learn about the new framework... Thanks very much, -Hugh Sparks, [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support.
