There are a few reasons:

1. It&#39;s easier to target pointcuts with more specific annotations. Do _not_ underestimate the usefulness of this!
2. The `@Repository` annotation carries with it some additional functionality: it causes exceptions to be [wrapped up as `DataAccessException`s](http://docs.spring.io/spring-framework/docs/3.2.0.M2/api/org/springframework/stereotype/Repository.html).
3. The `@Service` annotation [may gain additional semantics in the future](http://forum.springsource.org/showthread.php?45397-What-is-the-Service-annotation&amp;p=147796#post147796) but it&#39;s not happened yet…

The `@Repository` annotation (introduced in Spring 2.0) and `@Service` annotation (introduced in Spring 2.5) are specialization of the `@Component` annotation. 

The main advantage of using `@Repository` or `@Service` over `@Component` is that it&#39;s easy to write an AOP pointcut that targets, for instance, all classes annotated with `@Repository`.
 
Also, the specialized annotations help to clearly demarcate application layers (in a standard 3 tiers application).

I believe that there are two things Spring had in mind when they added these Component annotations.

1. They can be used to specify point cuts across all objects annotated with that sub-component.  (All @Repository or all @Service pointcuts)
2. I think Spring also mentioned that they would be adding some future functionality to them.  (I have no citation for this, I just think I read this somewhere)

If you [TDD][1] it would be useful to carefully design (an test of course) @Services because they will benefit of full injection of all the @Autowired components you have defined.

You could implement your functionalities directly into a @Controller for example, but in this case testing will be harder and you need to define all the mock elements (quite easier in springframework 3.1 but still &quot;bad design&quot;).


  [1]: http://en.wikipedia.org/wiki/Test-driven_development

I have the following piece of code in a file that I opened in `Vim`:

    &lt;p&gt;Hello stackoverflow!&lt;/p&gt;

How can I delete `&lt;p&gt;` and `&lt;/p&gt;` tags but keep the contents between them? That is, what should I press to end with:

    Hello stackoverflow!

I know pressing &lt;kbd&gt;d&lt;/kbd&gt; &lt;kbd&gt;i&lt;/kbd&gt; &lt;kbd&gt;t&lt;/kbd&gt; will do opposite.

I&#39;m using [Janus][1].


  [1]: https://github.com/carlhuda/janus

How to delete HTML tags, not the contents in Vim

I have a file with a list of user-agents which are encoded.
E.g.:

    Mozilla%2F5.0%20%28Macintosh%3B%20U%3B%20Intel%20Mac%20OS%20X%2010.6%3B%20en

I want a shell script which can read this file and write to a new file with decoded strings.

    Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en

I have been trying to use this example to get it going but it is not working so far.

    $ echo -e &quot;$(echo &quot;%31+%32%0A%33+%34&quot; | sed &#39;y/+/ /; s/%/\\x/g&#39;)&quot;

My script looks like:

    #!/bin/bash
    for f in *.log; do
      echo -e &quot;$(cat $f | sed &#39;y/+/ /; s/%/\x/g&#39;)&quot; &gt; y.log
    done

  [1]: http://geni.ath.cx/unix.html

How to decode URL-encoded string in shell?

What are the advantages of using [@Repository](http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/stereotype/Repository.html) and [@Service](http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/stereotype/Service.html)?

Don&#39;t tell me about component scanning etc., I am looking forward to something extra benefits or features that are there if at all.

what happens if I don&#39;t use it? what is that I would be missing?

Spring annotations @Repository and @Service

What are the advantages of using <a href="http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/stereotype/Repository.html" target="_blank" rel="noopener noreferrer">@Repository</a> and <a href="http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/stereotype/Service.html" target="_blank" rel="noopener noreferrer">@Service</a>?
Don't tell me about component scanning etc., I am looking forward to something extra benefits or features that are there if at all.
what happens if I don't use it? what is that I would be missing?

Shown below is a snippet of code where I try and reference my ApplicationProperties bean. When I reference it from the constructor it is null, but when referenced from another method  it is fine. Up until now I have not had no problem using this autowired bean in other classes. But this is the first time I have tried to use it in the constructor of another class.

In the code snippet below applicationProperties is null when called from the constructor but when referenced in the convert method it is not. What am I missing

    @Component
    public class DocumentManager implements IDocumentManager {

      private Log logger = LogFactory.getLog(this.getClass());
      private OfficeManager officeManager = null;
      private ConverterService converterService = null;

      @Autowired
      private IApplicationProperties applicationProperties;


      // If I try and use the Autowired applicationProperties bean in the constructor
      // it is null ?
	
      public DocumentManager() {
	  startOOServer();
      }
	
      private void startOOServer() {
        if (applicationProperties != null) {
          if (applicationProperties.getStartOOServer()) {
            try {
              if (this.officeManager == null) {
                this.officeManager = new DefaultOfficeManagerConfiguration()
                  .buildOfficeManager();
                this.officeManager.start();
                this.converterService = new ConverterService(this.officeManager);
              }
            } catch (Throwable e){
              logger.error(e);	
            }
          }
        }
      }

      public byte[] convert(byte[] inputData, String sourceExtension, String targetExtension) {
        byte[] result = null;
		
        startOOServer();
        ...

Below is s snippet from ApplicationProperties ...

    @Component
    public class ApplicationProperties implements IApplicationProperties {

      /* Use the appProperties bean defined in WEB-INF/applicationContext.xml
       * which in turn uses resources/server.properties
       */
      @Resource(name=&quot;appProperties&quot;)
      private Properties appProperties;

      public Boolean getStartOOServer() {
        String val = appProperties.getProperty(&quot;startOOServer&quot;, &quot;false&quot;);
        if( val == null ) return false;
        val = val.trim();
        return val.equalsIgnoreCase(&quot;true&quot;) || val.equalsIgnoreCase(&quot;on&quot;) || val.equalsIgnoreCase(&quot;yes&quot;);
      }


@Autowired bean is null when referenced in the constructor of another bean

I was wondering how I could implement the simple factory pattern with Spring 3 annotations.  I saw in the documentation that you can create beans that call the factory class and run a factory method.  I was wondering if this was possible using annotations only.

I have a controller that currently calls 

    MyService myService = myServiceFactory.getMyService(test);
    result = myService.checkStatus();

MyService is an interface with one method called checkStatus().

My factory class looks like this:

    @Component
    public class MyServiceFactory {
    
    	public static MyService getMyService(String service) {
    		MyService myService;
    		
    		service = service.toLowerCase();
    		
    		if (service.equals(&quot;one&quot;)) {
    			myService = new MyServiceOne();
    		} else if (service.equals(&quot;two&quot;)) {
    			myService = new MyServiceTwo();
    		} else if (service.equals(&quot;three&quot;)) {
    			myService = new MyServiceThree();
    		} else {
    			myService = new MyServiceDefault();
    		}
    		
    		return myService;
    	}
    }

MyServiceOne class looks like this :

	@Autowired
	private LocationService locationService;
	
	public boolean checkStatus() {
          //do stuff
	}

When I run this code the locationService variable is alwasy null.  I beleive this is because I am creating the objects myself inside the factory and autowiring is not taking place.  Is there a way to add annotations to make this work correctly?

Thanks


Implement a simple factory pattern with Spring 3 annotations

Is the Userprincipal I retrieve from `SecurityContextHolder` bound to requests or to sessions?

`UserPrincipal principal = (UserPrincipal) SecurityContextHolder.getContext().getAuthentication().getPrincipal();`

This is the way I access the currently logged in user. Will this invalidate if the current session is destroyed?

Spring security&#39;s SecurityContextHolder: session or request bound?

In a Spring web application I have several DAO and service layer beans. One service layer bean has annotated @Async / @Scheduled methods. These methods depend on other (autowired) beans.
I have configured two thread pools in XML:

    &lt;bean id=&quot;taskExecutor&quot; class=&quot;org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor&quot;&gt;
         &lt;property name=&quot;corePoolSize&quot; value=&quot;2&quot; /&gt;
         &lt;property name=&quot;maxPoolSize&quot; value=&quot;5&quot; /&gt;
         &lt;property name=&quot;queueCapacity&quot; value=&quot;5&quot; /&gt;
         &lt;property name=&quot;waitForTasksToCompleteOnShutdown&quot; value=&quot;true&quot; /&gt;
         &lt;property name=&quot;rejectedExecutionHandler&quot;&gt;
    			&lt;bean class=&quot;java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy&quot;/&gt;
    		&lt;/property&gt;
    	&lt;/bean&gt;
    	
    &lt;bean id=&quot;taskScheduler&quot; class=&quot;org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler&quot;&gt;
         &lt;property name=&quot;poolSize&quot; value=&quot;10&quot; /&gt;
         &lt;property name=&quot;waitForTasksToCompleteOnShutdown&quot; value=&quot;true&quot; /&gt;
         &lt;property name=&quot;rejectedExecutionHandler&quot;&gt;
    			&lt;bean class=&quot;java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy&quot;/&gt;
    		&lt;/property&gt;
    	&lt;/bean&gt;
    
    	&lt;task:annotation-driven executor=&quot;taskExecutor&quot; scheduler=&quot;taskScheduler&quot;/&gt;

Everything works as expected. My problem is that I cannot get a clean shutdown of the task pools to work. The tasks operate on the database and on the file system. When I stop the web application it takes some time until it is stopped. This indicates that the `waitForTasksToCompleteOnShutdown` property works. However, I get IllegalStateExceptions in the log indicating that some beans are already destroyed but some worker task threads are still executing and they fail because their dependencies are destroyed.

There is a JIRA issue which might be relevant: [SPR-5387 ][1]

**My question is: Is there a way to tell Spring to initialize the task executor/scheduler beans last or is there a way to tell Spring to destroy them first?**

My understanding is that destruction takes place in reversed init order. Therefore the bean init&#39;ed last will be destroyed first. If the thread pool beans are destroyed first, all currently executing tasks would finish and could still access dependent beans.

I have also tried using the depends-on attribute on the thread pools referring to my service bean which has the @Async and @Scheduled annotations. Seems like they are never executed then and I do not get context initialization errors. I assume the annotated service bean somehow needs these thread pools initialized first and if I use depends-on I reverse the order and make them non-functional.

  [1]: https://jira.springsource.org/browse/SPR-5387 &quot;SPR-5387&quot;

How can I shutdown Spring task executor/scheduler pools before all other beans in the web app are destroyed?

An `@Async` method in a `@Service`-annotated class is not being called asynchronously - it&#39;s blocking the thread.

I&#39;ve got `&lt;task: annotation-driven /&gt;` in my config, and the call to the method is coming from outside of the class so the proxy should be being hit. When I step through the code, the proxy is indeed hit, but it doesn&#39;t seem to go anywhere near any classes related to running in a task executor. 

I&#39;ve put breakpoints in `AsyncExecutionInterceptor` and they never get hit. I&#39;ve debugged into `AsyncAnnotationBeanPostProcessor` and can see advice getting applied.

The service is defined as an interface (with the method annotated `@Async` there for good measure) with the implementation&#39;s method annotated `@Async` too. Neither are marked `@Transactional`.

Any ideas what may have gone wrong?

-=UPDATE=-

Curiously, it works *only* when I have my `task` XML elements in my app-servlet.xml file, and not in my app-services.xml file, and if I do my component scanning over services from there too. Normally I have one XML file with only controllers in it (and restrict the component-scan accordingly), and another with services in it (again with a component-scan restricted such that it doesn&#39;t re-scan the controllers loaded in the other file).

**app-servlet.xml**

&lt;!-- language: xml --&gt;

    &lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot; 
	xmlns:context=&quot;http://www.springframework.org/schema/context&quot;
	xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; 
	xmlns:jee=&quot;http://www.springframework.org/schema/jee&quot; 
	xmlns:mvc=&quot;http://www.springframework.org/schema/mvc&quot;
	xmlns:webflow=&quot;http://www.springframework.org/schema/webflow-config&quot; 
	xmlns:task=&quot;http://www.springframework.org/schema/task&quot;
	xmlns:tx=&quot;http://www.springframework.org/schema/tx&quot;
	xsi:schemaLocation=&quot;http://www.springframework.org/schema/beans 
		http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
		http://www.springframework.org/schema/context
		http://www.springframework.org/schema/context/spring-context-3.0.xsd
		http://www.springframework.org/schema/tx
		http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
		http://www.springframework.org/schema/task
		http://www.springframework.org/schema/task/spring-task-3.0.xsd
		http://www.springframework.org/schema/mvc
        http://www.springframework.org/schema/mvc/spring-mvc-3.0.xsd
		http://www.springframework.org/schema/jee 
		http://www.springframework.org/schema/jee/spring-jee-3.0.xsd&quot;
	&gt;
	&lt;task:annotation-driven executor=&quot;executor&quot; /&gt;
	&lt;task:executor id=&quot;executor&quot; pool-size=&quot;7&quot;/&gt;
	
	&lt;!-- Enable controller annotations --&gt;
	&lt;context:component-scan base-package=&quot;com.package.store&quot;&gt;
		&lt;!-- &lt;context:include-filter type=&quot;annotation&quot; expression=&quot;org.springframework.stereotype.Controller&quot; /&gt; --&gt;
	&lt;/context:component-scan&gt;
	
	&lt;tx:annotation-driven/&gt;
	&lt;bean id=&quot;transactionManager&quot; class=&quot;org.springframework.orm.hibernate3.HibernateTransactionManager&quot;&gt;
        &lt;property name=&quot;sessionFactory&quot; ref=&quot;sessionFactory&quot;/&gt;
    &lt;/bean&gt;

	&lt;mvc:annotation-driven conversion-service=&quot;conversionService&quot; /&gt;
	
	&lt;bean id=&quot;viewResolver&quot; class=&quot;org.springframework.web.servlet.view.InternalResourceViewResolver&quot;&gt;
		&lt;property name=&quot;prefix&quot; value=&quot;/WEB-INF/jsp/&quot; /&gt;
		&lt;property name=&quot;suffix&quot; value=&quot;.jsp&quot; /&gt;
	&lt;/bean&gt;
&lt;/beans&gt;

**app-services.xml** (doesn&#39;t work when specified here)

&lt;!-- language: xml --&gt;

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot; 
    xmlns:context=&quot;http://www.springframework.org/schema/context&quot; xmlns:task=&quot;http://www.springframework.org/schema/task&quot;
    	xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
    	xsi:schemaLocation=&quot;http://www.springframework.org/schema/beans 
    		http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
    		http://www.springframework.org/schema/context
    		http://www.springframework.org/schema/context/spring-context-3.0.xsd
    		http://www.springframework.org/schema/task
    		http://www.springframework.org/schema/task/spring-task-3.0.xsd&quot;&gt;
    
    	&lt;!-- Set up Spring to scan through various packages to find annotated classes --&gt;
    	&lt;context:component-scan base-package=&quot;com.package.store&quot;&gt;
    		&lt;context:exclude-filter type=&quot;annotation&quot; expression=&quot;org.springframework.stereotype.Controller&quot; /&gt;
    	&lt;/context:component-scan&gt;
    
    	&lt;task:annotation-driven executor=&quot;han&quot; /&gt;
    	&lt;task:executor id=&quot;han&quot; pool-size=&quot;6&quot;/&gt;
    	...

Am I missing something glaringly obvious in my configuration, or is there some subtle interplay between config elements going on?

Content Type	Original Author	Original Content on Stackoverflow
Question	BlueSky	View Question on Stackoverflow
Solution 1 - Spring	Donal Fellows	View Answer on Stackoverflow
Solution 2 - Spring	Luciano Fiandesio	View Answer on Stackoverflow
Solution 3 - Spring	nicholas.hauschild	View Answer on Stackoverflow
Solution 4 - Spring	lrkwz	View Answer on Stackoverflow

Spring annotations @Repository and @Service

Spring Problem Overview

Spring Solutions

Solution 1 - Spring

Solution 2 - Spring

Solution 3 - Spring

Solution 4 - Spring

How to decode URL-encoded string in shell?

How to delete HTML tags, not the contents in Vim

Attributions