The new model is also an EMF model with the same listener/adapter frameworks - the only change is many of these interfaces are not exposed, so casting is required for these facilities. This is the tradeoff of working with a "clean" model interface.
Do you have a particular problem? Maybe we should move this to newsgroups? (I'll promise to check later) - Chuck Rational Java Enterprise Tooling Team Lead IBM Software Lab - Research Triangle Park, NC Email: [EMAIL PROTECTED] Phone: 919-254-1848 (T/L: 444) "Gerry Kessler" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 05/16/2007 01:02 PM Please respond to "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>; Please respond to "General discussion of project-wide or architectural issues." <[email protected]> To Chuck Bridgham/Raleigh/[EMAIL PROTECTED] cc "[email protected]" <[email protected]> Subject [wtp-dev] JavaEE model change notifications Chuck, To monitor changes to the deployment descriptors using the J2EE models, we add adapters to the EObjects that we are interested in. How do we now listen for changes using the new JavaEE models? Specifically, we need to be able to detect additions, deletions and changes to the context params of a web app. Thanks, Gerry Kessler WTP JSF Tools Team_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
