Databases
StackOverflow2013
Postsdbo
POWhy is Spring @Value incompatible with @Controller?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is Spring @Value incompatible with @Controller?
    primarykey
    data
    text
    <p>I'm looking for a better understanding of this problem. A workaround is pretty simple, namely move the configuration data to another class that does not have proxies/advice wrapped around it, but I think understanding this better will help me avoid other related problems in the future, so I'd like whatever explanation anyone can provide. </p> <p>I'm using Spring 3.1.0.RELEASE with Spring STS and the vFabric tc server. Implemented a basic little REST server using a @Controller class. That's all great (really, it is), but the @Controller is also @Transactional, and between that and the load time weaving and the vFabric tc server, it breaks @Value.</p> <pre><code>@Controller @RequestMapping("/hello") public class MyAPI { @Value("${my.property}") private String prop; ... @Transactional handleRequest(...) ... } </code></pre> <p>And a properties file app.properties:</p> <pre><code>my.property = SUCCESS </code></pre> <p>This works fine under JUnit, with the test getting a MyAPI object that has prop set to "SUCCESS". But when the app gets loaded into vFabric, I'm guessing it gets load time weaving and proxying. Whatever happens, there are two MyAPI instances created, one which has prop == "SUCCESS" and another (which is unfortunately the one that handles the http request) which has prop == "${my.prop}".</p> <p>So all-in-all I call this a failure of magic, which is my biggest concern with using stuff like AOP. Even with STS I don't know how to track down what is the cause behind the problem or figure out if this is a serious bug. If it is a bug, I don't know whether it's a bug in Spring, AspectJ, the load-time weaver, or vFabric, so I don't even know where to file a bug report.</p> <p>So any help in understanding this would be appreciated. Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USOld Pro
    1. USOld Pro
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy is Spring @Value incompatible with @Controller?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy is Spring @Value incompatible with @Controller?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy is Spring @Value incompatible with @Controller?
      1. USOld Pro
      1. VTFavorite
    1. COAre you sure that it's caused by AOP? What if you remove `@Transactional`?
      singulars
      1. POWhy is Spring @Value incompatible with @Controller?
      1. USaxtavt
    2. CO@axtavt you pointed me to the solution [here](http://stackoverflow.com/a/4335438/712765). See my answer in full below, but the short answer is that `Controller`s alone are being created twice in my (mis-)configuration. Not a problem with `@Transactional` as that is using AspectJ, not proxies.
      singulars
      1. POWhy is Spring @Value incompatible with @Controller?
      1. USOld Pro
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload