> [mailto:[EMAIL PROTECTED] On Behalf Of Pierre van Rooden > > The onyl solution I currently see (to keep it working in SCAN) is to > make xmlimporter dependent on SCAN. > That way I can move the interface, and don't have to make > changes that > may break stuff. > It's not nice, but I don't think I can fix this without breaking > xmlimporter so SCAN can't use it anymore.
Make it so. I agree it's not nice, but if that bothers us we can deal with it later. For now it shouldn't get in the way for cleaning. For the historically interested: The xmlimporter extends the socalled TCP (Temporary Cloud Project) semantics. TCP was mostly tied to scan, but the xmlimporter added interfaces for it to be used standalone. Hence it still has dependencies on SCAN although it can be used independently. Rob van Maris Technical Consultant Quantiq xmedia & communication solutions
