To add my 3 cents (inflation!) worth:
I love the power of AspectJ, and in particular areas it's fantastic. e.g.
Spring Insight uses weaving of aspects to give very focused and lightweight
probing to an application running under Tomcat/tcServer.
For tooling, the Eclipse support is excellent, part
5-16 15:10:49.492] region-dm-3
>> org.springframework.osgi.util.DebugUtils
>> Could not find class [java.lang.ObjectBeanInfo] required by
>> [neo4j.domain(com.example.neo4j.domain)] scanning available bundles
>> [2011-05-16 15:10:49.493] region-dm-3
>> org.springframework.beans.CachedIntrospectionResult
In OSGi, missing classes can be down to which bundles are visible to
the bundle doing the scanning. In this case, whatever is doing the
classpath scanning cannot see the bundle exporting your domain package.
From a number of years back, I remember having to use
eclipse-registerbuddy to solv
3 matches
Mail list logo
