Databases
StackOverflow2013
Postsdbo
POWhy my @ApplicationScope CDI bean not updated?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy my @ApplicationScope CDI bean not updated?
    primarykey
    data
    text
    <p>In my application, I have an <code>@ApplicationScoped</code> CDI bean to store some information from the database:</p> <pre><code>@Named @ApplicationScoped public class MrBean { @EJB private SoyaBean soyaBean; private List&lt;Toys&gt; myToys; @PostConstruct public void prepareMrBean() { this.myToys = soyaBean.getToys(); } public void updateToys() { this.myToys = soyaBean.getToys(); } } </code></pre> <p>I also have a AddToy.xhtml page which would simply add a toy to the database. The backing bean is as following:</p> <pre><code>@Named @RequestScoped public class MrsBean { @EJB private SoyaBean soyaBean; @Inject private MrBean mrBean; public void addToy() { this.soyaBean.addToy(); this.mrBean.updateToys(); } } </code></pre> <p>Since there is a new toy added to the database, I wanted to update the list of toys in mrBean. However, even though mrsBean called <code>mrBean.updateToys()</code>, the list of toys in mrBean is not updated at all. I have another ViewToys.xhtml with a <code>@RequestScoped</code> backing bean to view the list of toys and I didn't see the list get updated.</p> <p>I'd be very grateful if someone could give me an advice on how to tackle this problem.</p> <p><strong>UPDATE</strong>: This is my SoyaBean implementation:</p> <pre><code>@Stateless public class SoyaBeanImpl implements SoyaBean { @PersistenceContext() private EntityManager em; @Override public List&lt;Toys&gt; getToys() { Query q = em.createQuery("SELECT T from Toys T"); return (List&lt;Toys&gt;) q.getResultList(); } @Override public void addToy() { Toys newToy = new Toys(); em.persist(newToy); } } </code></pre> <p><strong>UPDATE 2</strong> I'd also really appreciate if someone could show me how I can achieve the same goal in any ways other than my troubling way. </p> <p>Best regards,</p> <p>James Tran </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBalusC
    1. USMr.J4mes
    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
    1. VO
      singulars
      1. POWhy my @ApplicationScope CDI bean not updated?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy my @ApplicationScope CDI bean not updated?
      1. USMr.J4mes
      1. VTBountyStart
    3. VO
      singulars
      1. POWhy my @ApplicationScope CDI bean not updated?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYour question is sound, but your example has a red herring: the both beans have the same name, which is illegal in this construct.
      singulars
      1. POWhy my @ApplicationScope CDI bean not updated?
      1. USBalusC
    2. COI have just realized it after I clicked submit =). I have already updated my question with the proper name. :P
      singulars
      1. POWhy my @ApplicationScope CDI bean not updated?
      1. USMr.J4mes
    3. COHaha, `MrsBean` :) Well, I believe the problem is related to EJB transactions. What happens if you call `updateToys()` in a new subsequent HTTP request?
      singulars
      1. POWhy my @ApplicationScope CDI bean not updated?
      1. USBalusC
 

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