October 6, 2004 · 12:47 pm
Seems that (once again (?)) the guys at SUN listened to the many voices out there talking about an independent persistence solution that will unify JDO and persistence inside containers (EJB).
I have wondered from the beginning why persistence inside a container should be different from persistence everywhere. Moreover, I have wonderer why at some point it was decided that 2 gangs must dispute about the best solution in persistence (and a 3rd one win :-)).
Now what is left is to assure that the solution will not be another unusable spec. So good luck guys and put the best of you inside this spec.
It is interesting to see that many people consider that any persistent object must go to a RDBMS. Guys, wake up! Persistence is by no means equivalent with ORM. Persisting entities does not mean JDBC. Maybe persistance to RDBMS represents a large percent of the available solutions, but taking into account the legacy systems we must consider the other solutions/options too.
Having a common spec for persistence will improve/ease our solutions.
This interview with Craig Russell and Rick Cattell (pdf link) clarifies a lot of the fog floating around.
October 6, 2004 · 11:11 am
Today I have found two blog entries very interesting for the people playing or working or evaluating AOP. The first one came from Adrian Colyer (I hope you all know his involvement in AspectJ, appreciate you Adrian) and clarifies the configuration of pathes used by AspectJ. Paraphrasing Adrian I can say that after reading I have three friends standing there [AspectJ] for me.
The second one published by Jon Tirsen can be considered one of the best examples of AOP appliance. I heard lots of voices screaming about the lack of real examples. Here you have one that will proove AOP can take the weight out of your shoulders: undo action. I place it on my hall of fame examples for AOP near the Swing constraint verifier published by Ramnivad Laddad in AspectJ in Action (Ramnivas your book rocks!).
Damn …. I almost forgot the third one (you know: there were once two friends: Foo, Bar and Baz). If you are trying to evaluate which AOP-way you go today (SIC), check the JBossAOP vs Aspectwerkz.
The future looks bright!
Filed under Uncategorized
Tagged as AOP
October 6, 2004 · 8:53 am
Rick Ross analysis the possibility of SUN running out of business or being acquired by some other company. While the possibility of closing is fast eliminated, the author chooses 2 giants which are supposed to be capable of acquiring SUN: IBM and Fujitsu. The analysis is quiet interesting, but I must say that there is no sign of such a movement, and as far as know when talking about large companies I always think that the solution is a jointventure. Another name that is not contained in the analysis is Oracle. I think Oracle can be interesting in keeping Java on its side (even if Oracle might not be interested in SUN hardware). But I let the future decide what we’ll have.