Jan 24th, 2012, 07:12 AM
design question on connectcontroller and ConnectionRepository
I was just wondering about the design you provided in the connect contoller..
I saw you inject the repository @ request scope - why is that? isn't it a limitation on the developer having to define controllers in such a way? why not simply provide an api with some user id signature ? (so you can match it against the userconnection table?)
When injecting to the controller the beans in such a way - does it make the entire controller created on each request/thread?
last question - is there a way I can use/get the bean of the connection repository outside the controller? (say - my service layer?)