Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need to change your <code>@Inject</code> annotations to <code>@EJB</code>, then by default with CMT (container managed transactions) each call by the CDI bean will be in its own TX scope. If you do not want one of the method calls to invoke a TX then add @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) to the method. </p> <p>From the looks of your business logic you could really simplify things by changing <code>@Named</code> to <code>@Stateless</code>, change <code>@Inject</code> to <code>@EJB</code> and add <code>@TransactionalAttribute(TransactionAttributeType.NOT_SUPPORTED)</code> on the getFullName(..) if you don't want that method to run in a TX. With those changes you will get the TX behavior you are looking for.</p> <p>If you want UserController to be a JSF managed bean then along with the other mods I suggested I would change <code>@Named</code> to <code>@ManagedBean</code> and simply add <code>@Stateless</code> under <code>@ManagedBean</code> instead of changing <code>@Named</code> to <code>@Stateless</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow does Java EE container control transactions?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNBW
    1. USNBW
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CONBW, thanks for your contribution but I must say I'm not following this post. Everything I read recently suggests dropping the use of both `@EJB` and `@ManagedBean` in favour of `@Inject` and `@Named`, respectively. By telling me I should use them, you're sending me to a place where I am even more confused. I'll do some further reading on differences between `@EJB` and `@Inject` but I believe that recommendations are published for a reason.
      singulars
      1. PO
      1. USjacekn
    2. CO@jacekn As with most solutions in this space there isn't a right or wrong answer but there are several nuanced ones. If you are coding to EE6 then you would definately use `@Managed` and `@EJB` in EE7 you can use `@Inject` and `@Named` or you can do it the EE6 way. EE7 moves away from the use of `@Managed` because it was seen as extraneous, much the same way the EE6 requirement of an empty beans.xml to enable the CDI container was dropped in EE7.
      singulars
      1. PO
      1. USNBW
    3. CO@jacekn Subjectively, I prefer using `@EJB` for my TX management logic, however, because of the short comings of the the EJB API back in the pre EE5 days they got a bad name. The recent push to add TX mgmnt into CDI is to some extent an effort to market EE as a stack which does not require the 'evil' EJB word. As of EE7 CDI TX support is not as feature rich and powerful as the EJB container and IMHO the EJB API is just as easy if not easier to work with. David Levins (TomEE, OpenEJB, etc.) has a good comparison here http://stackoverflow.com/questions/13487987/where-to-use-ejb-3-1-and-cdi
      singulars
      1. PO
      1. USNBW
 

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