I may have missed it but what is our error and exception handling strategy in java Tuscany? Working on some of the demos I can say that we really need to strive hard to provide the context that these happen. As an end user I think I'd really like any exceptions that happens in the context of a System / Subsystem/ Module/ Component/(fragment?) has something in the message that identifies these. Personally I'd go as far as the naming the SCDL file these are associated with.
How about at runtime and exceptions generated in user written components ? Will we have a separate log that will identify the component/module/subsystem? From the code I see it looks like there is a a lot there to make Tuscany scale well, and if we foresee complex and very large composite configurations if we can't identify the location of exceptions by the SCA artifacts for the end user I think that will be a major real world useablity issue. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
