Databases
StackOverflow2013
Postsdbo
PODependency injection with Spring (JSR 330 annotations) in WebSphere 7 is not working
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODependency injection with Spring (JSR 330 annotations) in WebSphere 7 is not working
    primarykey
    data
    text
    <p>I have an enterprise application built with Java 6, Spring Framework 3.1.2 and Mule-ESB 3.3.0, among other libraries not related to this question.</p> <p>Our beans and services are all declared with @Named and @Inject JSR-330 annotations, respectively for automatic component scanning and for dependency injection (no EJBs, only service beans). When deployed into JBoss 4.2.3 (our test environment) everything works fine. However, when deployed into WebSphere 7, the JSR-330 annotations seem not to be working. The beans marked with @Named are just not detected, at all.</p> <p>I can assure everything is configured right (since it is working in JBoss). Specifically, the has the base-package attribute correctly defined and the scope-resolver attribute correctly configured to use Jsr330ScopeMetadataResolver (we tried without it too).</p> <p>I am aware WebSphere 7 (7.0.0.23) may not support such kind of annotations. I am yet to test it with @Component and @Autowired Spring equivalents. Unfortunately, we would very much like to use JSR 330 annotations so our classes wouldn't directly depend on Spring, even though we're using Spring Framework under the hood.</p> <p>Nevertheless, although I'd spent one full work's day looking for a definite statement that WebSphere 7 does not support JSR 330 annotations, I haven't found anything so far.</p> <p>Further, I can't see why it would not work, since I'm assuming Spring Framework is the one doing all the work, through the directive in the application-context.xml file.</p> <p>Can anyone bring some light into this issue?</p> <p>Is there a way to activate dependency injection via annotations in WebSphere 7?</p> <p>If I switch back from the JSR 330 @Named / @Inject annotations to Spring's own @Component and @Autowired is it likely to work?</p> <p>In a desperate attempt, can I extend Spring's ComponentScanBeanDefinitionParser so it will detect JSR 330 annotations even in WebSphere 7?</p> <p>If nothing works, I will eventually fall back to plain XML configuration. That is highly undesirable, however, because there will be hundreds of beans to be manually configured in the XML.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USFilipe Fedalto
    plurals
    1. This table or related slice is empty.
    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. PODependency injection with Spring (JSR 330 annotations) in WebSphere 7 is not working
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm certain that the Spring annotations will work. I've never tried it with Named and Inject. It's no surprise that WebSphere doesn't support it - IBM's software is awful.
      singulars
      1. PODependency injection with Spring (JSR 330 annotations) in WebSphere 7 is not working
      1. USduffymo
    2. COAll the CDI stuff I've seen for WebSphere starts at version 8, but I agree I can't find a definitive statement to that effect. It's definitely in the v8 documentation. https://ibm.biz/BdxmBv
      singulars
      1. PODependency injection with Spring (JSR 330 annotations) in WebSphere 7 is not working
      1. USdbreaux
 

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