Comments on: Annotation-Driven Dependency Injection in Spring 2.1

By: test

test — Fri, 24 Jun 2011 14:44:56 +0000

nice

By: Annotation-Driven Dependency Injection in Spring 2.1 | Ringo's Blog

Annotation-Driven Dependency Injection in Spring 2.1 | Ringo's Blog — Sat, 17 Jul 2010 15:05:59 +0000

[...] Spring 2.0 introduced annotation support and annotation-aware configuration options that can be leveraged by Spring users who are developing with Java 5 (or later versions)… [Read More] [...]

By: Dav

Dav — Fri, 15 Jan 2010 09:51:31 +0000

Nice article.

Using spring-framework-2.5.6.SEC01-with-dependencies.

I found that @Component was also needed in the declaration of ServiceInvocationLogger to get the aspect stuff to work.

I.e.

@Component
@Aspect
public class ServiceInvocationLogger {
…

By: Ravi

Ravi — Mon, 18 May 2009 22:25:00 +0000

Hi Mark,

Thanks for a great article!

>> I am including all of the code and configuration in a single "blog" package.

Can you please provide access to the sample code? I am trying to build the sample but having some issues.

Thanks!

By: Overview of Dependency Injection in Symfony

Overview of Dependency Injection in Symfony — Wed, 29 Oct 2008 11:34:15 +0000

[...] Injection is something that is quite prominent in Java frameworks, such as Spring. Martin Fowler covers the Dependency Injection pattern in quite some detail if you are [...]

By: SpringSource Team Blog » What's New in Spring Web Services 1.5?

SpringSource Team Blog » What's New in Spring Web Services 1.5? — Sat, 29 Mar 2008 00:38:01 +0000

[...] Another neat new feature is that @Endpoints are now annotated with @Component, so if you are using Spring 2.5 component scanning, your endpoints are picked up automatically, and require no XML configuration! For configuration of Spring-WS components, we now offer two new namespaces, to configure OXM marshallers and other common constructs. For example, here is the configuration of a JAXB2 marshaller: [...]

By: df fdsfsdf

df fdsfsdf — Mon, 17 Mar 2008 10:13:23 +0000

dsfds fds

By: Ferry

Ferry — Mon, 10 Mar 2008 09:58:08 +0000

Hi Mark,
The cost of @Transactional seems very high. If I have a client that call a service that is annotated with @Transactional, it will at least required 300ms (this is relative) just to called the very simple method.
While I don't really need a transactional method, but the problem is that I will get the "Session is closed" exception whenever I called something like this :
em.read(); followed by em.merge(). It seems that without the @Transactional, I'm not able to use the em(EntityManager) more than once in one conversation.

What is the best practice for this issue ? Can I avoid the @Transactional ? It has much better performance if I put the @Transactional at the caller side, but this is not I want.

Thanks, and sorry if this is not the right place to ask :p

By: It’s Only Software » Quick Tip: Spring 2.5 makes use of PropertyPlaceholderConfigurer simpler

Wed, 14 Nov 2007 01:09:55 +0000

[...] The nit-picky will note that you will need to add in the spring-context-2.5.xsd schema reference, however you may be using that already anyway in Spring 2.5 to take advantage of some of the Java-based annotation functionality. [...]

By: Olia

Olia — Wed, 26 Sep 2007 19:41:54 +0000

Hi,
should annotation-based AspectJ work with Java6? I keep getting an error about it, and I am running with Java6:

org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.aop.aspectj.AspectJPointcutAdvisor]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: error the @annotation pointcut expression is only supported at Java 5 compliance level or above
Caused by:
java.lang.IllegalArgumentException: error the @annotation pointcut expression is only supported at Java 5 compliance level or above
at org.aspectj.weaver.tools.PointcutParser.parsePointcutExpression(PointcutParser.java:315)
at org.springframework.aop.aspectj.AspectJExpressionPointcut.buildPointcutExpression(AspectJExpressionPointcut.java:189)
at org.springframework.aop.aspectj.AspectJExpressionPointcut.checkReadyToMatch(AspectJExpressionPointcut.java:176)
at org.springframework.aop.aspectj.AspectJExpressionPointcut.getMethodMatcher(AspectJExpressionPointcut.java:162)
at org.springframework.aop.aspectj.AbstractAspectJAdvice.buildSafePointcut(AbstractAspectJAdvice.java:181)
at org.springframework.aop.aspectj.AspectJPointcutAdvisor.(AspectJPointcutAdvisor.java:51)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:85)
etc..