Maybe.
I think the reason is not so simple.Indeed,the manual on adop is too few.Do you think more and more people will use AOSD to develop software in future?
I have some e-book about AspectJ,e.g. Aspectj cook,Eclipse AspectJ,Master AspectJthat's all.
Sorry,I does not have got any link to these source.
I am very sorry ,I make a mistake on the technique's name.The technique is AOSD ,not ADOP.I think you will find a suitable link byGOOGLE.
Message was edited by:
Microwave
Message was edited by:
Microwave
ADOP? Or AOP?
A lot of people are already (somewhat unwittingly) using AOP, or a subset of such. EJB containers provide services such as remoting and transaction management through very AOP-like techniques. The Spring framework, as well as providing an AOP framework, delivers it's services via AOP.
But, no, it's not a very mature technology yet
> ADOP? Or AOP?
>
> A lot of people are already (somewhat unwittingly)
> using AOP, or a subset of such. EJB containers
> provide services such as remoting and transaction
> management through very AOP-like techniques. The
> Spring framework, as well as providing an AOP
> framework, delivers it's services via AOP.
>
> But, no, it's not a very mature technology yet
Do you think it would substitute for OOAD
> > ADOP? Or AOP?
> >
> > A lot of people are already (somewhat unwittingly)
> > using AOP, or a subset of such. EJB containers
> > provide services such as remoting and transaction
> > management through very AOP-like techniques. The
> > Spring framework, as well as providing an
> AOP
> > framework, delivers it's services via AOP.
> >
> > But, no, it's not a very mature technology yet
>
> Do you think it would substitute for OOAD
It's not intended as an alternative to OO, but as a complementary technique