For what it's worth... I face the exact same problem after upgrading to cocoon2.1.10. The way I solved some nasy ambiguity problems was by doing more coding in java. There at least I'm not facing errors like "ambiguous constructor for ...". And I'm actually wondering if it's not safer to make the choice of instantiating a dedicated java_flowcontroller with only one constructor which initializes everything (so no worries there). Cheers, Robby
_____ Van: Andrew Madu [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 20 februari 2007 19:02 Aan: [email protected] Onderwerp: Re: Ambiguous Java class Import! Hi, Anyway I resolved the issue by placing the importPakage statement as the very first of the import statements. Trust me to speak to quickly! Well it worked the once, I swear it did!!!! I take it the latest snapshot build is where I need to be heading to resolve this issue, correct? -- Regards Andrew
