I'd second the top-down approach looking for NotYetImplemented exceptions to be thrown at runtime as the best way to associate user level functionality with low-level Model method calls.
The issue with using a bottom-up approach, inserting breakpoints and waiting for them to be triggered, is that you need to know up front where to put the breakpoints, which is largely the information that you are trying to acquire. Studying the Model/eUML implementation to understand how the functionality is partitioned should be the first task though, to help you understand the overall structure of things and how functionality is partitioned. As you become more familiar with things, you'll know where to add most of the functionality needed for a user function and then you can fill in later the things that you missed when NotYetImplemented exceptions are thrown at runtime. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
