Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of, the notation using the $ is correct, not the #</p> <p>Now regarding the original poster, I think you have a conflicting behavior between the 2 annotations (@Controller and @Transactional).</p> <p>Using the @Transactional annotation will proxify your implementation (I guess to detect an error and launch a rollback).</p> <p>Now you are saying that you see 2 instances of your controller. That should not happen. Normally you should have only a single instance of a controller loaded in memory.</p> <p>Could be related to your configuration files or due to the presence of @Transactional and its proxy nature?</p> <p>As a side note, I never use @Transactional in the controllers themselves but either on a method of a service or dao. Since the actual process which can fail and need to be rollbacked is there, and can be access from different controllers/source.</p> <p>Regards.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy is Spring @Value incompatible with @Controller?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USFarid
    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. COI understand the desire to move @Transactional out of the `Controller` and onto a service layer. However, I believe in lean programming where you don't do extra work that you'll never need. In this case, implementing a REST service API, there's basically nothing for the Controller to do but implement the service and no one will ever call the service any other way. If some day they do, it will be easy to refactor then, but up front I've saved creating a whole layer. And by using AspectJ for @Transactional I don't have to worry about proxies.
      singulars
      1. PO
      1. USOld Pro
    2. COlean programming is fine but can take different representation based on the context. In the case of Rest Services, you have to take into consideration that 1. they evolve often (new requirements/demands) 2. you want to have the controllers easily readable for developers and not have them "cluttered" with business rules. it does require slightly more work at the start (creation of the service) but it gives you a real freedom in the long run.
      singulars
      1. PO
      1. USFarid
    3. COFarid, my vision of "lean" is to avoid "more work at the start" where it does not make future growth more difficult. The Controller logic is basically: read the request, perform the requested action, write the response, with the "requested action" inside a try/catch block. Later, if a separate Service object is desired, you can just cut the inside of the try/catch block from the controller and paste it into a service method. Really no limitation on long-run freedom, but definitely faster to get to a working product.
      singulars
      1. PO
      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