Databases
StackOverflow2013
Postsdbo
POJSF 2 inject Spring bean/service with @ManagedProperty and no xml
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJSF 2 inject Spring bean/service with @ManagedProperty and no xml
    primarykey
    data
    text
    <p>I would like to use jsf annotations and some spring annotations to inject a spring bean/service into a jsf managed bean. (on the jsf bean i only want to use jsf annotations) I dont want to use annotations like <code>@named</code> / <code>@inject</code>.</p> <p>I have tried to find a solution on the net but without any luck.</p> <p>Example</p> <pre><code>@ManagedBean @ViewScoped public class MyBean { @ManagedProperty(value = "#{mySpringBean}") private MySpringBean mySpringBean; public void setMySpringBean(MySpringBean mySpringBean) { this.mySpringBean = mySpringBean; } public void doSomething() { //do something with mySpringBean } } </code></pre> <p>Is something like this possible without the use of xml. For example, I would NOT like to use something like</p> <pre><code>FacesContextUtils.getWebApplicationContext(context).getBean("MySpringBean"); </code></pre> <p>or in <code>faces-config.xml</code></p> <pre class="lang-xml prettyprint-override"><code>&lt;managed-bean&gt; &lt;managed-bean-name&gt;myBean&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;com.mytest.MyBean&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;view&lt;/managed-bean-scope&gt; &lt;managed-property&gt; &lt;property-name&gt;mySpringBean&lt;/property-name&gt; &lt;value&gt;#{mySpringBean}&lt;/value&gt; &lt;/managed-property&gt; &lt;/managed-bean&gt; </code></pre> <p>Is something like the above possible with annotations and without defining all the jsf beans/properties and the spring beans/properties for every bean in the config xml files?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDani
    1. USDimman
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. 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. POJSF 2 inject Spring bean/service with @ManagedProperty and no xml
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJSF 2 inject Spring bean/service with @ManagedProperty and no xml
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJSF 2 inject Spring bean/service with @ManagedProperty and no xml
      1. This table or related slice is empty.
      1. VTUpMod
    1. COFunny, I use this method of injection and it works for me, but then I also include the property injection in my `applicationContext.xml` as well. The Spring EL resolver does not seem to work with ViewScoped beans that I have noticed. Try changing this to SessionScoped and see if the property becomes injected.
      singulars
      1. POJSF 2 inject Spring bean/service with @ManagedProperty and no xml
      1. USmaple_shaft
    2. COI want to avoid the applicationContext.xml (I'm a bit stubborn! thanks) But thanks :)
      singulars
      1. POJSF 2 inject Spring bean/service with @ManagedProperty and no xml
      1. USDimman
 

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