Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] JavaEE model change notifications

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:  cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)

"Gerry Kessler" <gerry.kessler@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

05/16/2007 01:02 PM

Please respond to
"gerry.kessler@xxxxxxxxxx" <gerry.kessler@xxxxxxxxxx>; Please respond to
"General discussion of project-wide or architectural issues."        <wtp-dev@xxxxxxxxxxx>

Chuck Bridgham/Raleigh/IBM@IBMUS
"wtp-dev@xxxxxxxxxxx" <wtp-dev@xxxxxxxxxxx>
[wtp-dev] JavaEE model change notifications

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.    
Gerry Kessler
WTP JSF Tools Team_______________________________________________
wtp-dev mailing list

Back to the top