Dropwizard hibernate session aware lazy loading
up vote
0
down vote
favorite
I have following issue that when I fetch my principal class (Account
) in my authenticator and then inject it with the @Auth
annotation I'm not able to fetch any lazy loaded attributes with hibernate as I'm getting an exception indicating that there is no session avaliable.
@UnitOfWork
@PermitAll
@GET
public Response fetchCharacters(@Auth Account account) {
List<Character> chars = account.getCharacters();
return Response.status(Status.OK).entity(chars).build();
}
If I use an extra DAO class it's working fine
@UnitOfWork
@PermitAll
@GET
public Response fetchCharacters(@Auth Account account) {
List<Character> chars = dao.getCharacters(account);
return Response.status(Status.OK).entity(chars).build();
}
and while I could do that of cause as it's only a very small drawback I was wondering why this is not working as I'd expect it.
I get that the session is obviously closed after fetching the principal in the authenticator, but why is a new session opened for a DAO but not for a hibernate lazy fetch? And is there a way to fix it or is that just as intended?
java hibernate dropwizard
add a comment |
up vote
0
down vote
favorite
I have following issue that when I fetch my principal class (Account
) in my authenticator and then inject it with the @Auth
annotation I'm not able to fetch any lazy loaded attributes with hibernate as I'm getting an exception indicating that there is no session avaliable.
@UnitOfWork
@PermitAll
@GET
public Response fetchCharacters(@Auth Account account) {
List<Character> chars = account.getCharacters();
return Response.status(Status.OK).entity(chars).build();
}
If I use an extra DAO class it's working fine
@UnitOfWork
@PermitAll
@GET
public Response fetchCharacters(@Auth Account account) {
List<Character> chars = dao.getCharacters(account);
return Response.status(Status.OK).entity(chars).build();
}
and while I could do that of cause as it's only a very small drawback I was wondering why this is not working as I'd expect it.
I get that the session is obviously closed after fetching the principal in the authenticator, but why is a new session opened for a DAO but not for a hibernate lazy fetch? And is there a way to fix it or is that just as intended?
java hibernate dropwizard
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have following issue that when I fetch my principal class (Account
) in my authenticator and then inject it with the @Auth
annotation I'm not able to fetch any lazy loaded attributes with hibernate as I'm getting an exception indicating that there is no session avaliable.
@UnitOfWork
@PermitAll
@GET
public Response fetchCharacters(@Auth Account account) {
List<Character> chars = account.getCharacters();
return Response.status(Status.OK).entity(chars).build();
}
If I use an extra DAO class it's working fine
@UnitOfWork
@PermitAll
@GET
public Response fetchCharacters(@Auth Account account) {
List<Character> chars = dao.getCharacters(account);
return Response.status(Status.OK).entity(chars).build();
}
and while I could do that of cause as it's only a very small drawback I was wondering why this is not working as I'd expect it.
I get that the session is obviously closed after fetching the principal in the authenticator, but why is a new session opened for a DAO but not for a hibernate lazy fetch? And is there a way to fix it or is that just as intended?
java hibernate dropwizard
I have following issue that when I fetch my principal class (Account
) in my authenticator and then inject it with the @Auth
annotation I'm not able to fetch any lazy loaded attributes with hibernate as I'm getting an exception indicating that there is no session avaliable.
@UnitOfWork
@PermitAll
@GET
public Response fetchCharacters(@Auth Account account) {
List<Character> chars = account.getCharacters();
return Response.status(Status.OK).entity(chars).build();
}
If I use an extra DAO class it's working fine
@UnitOfWork
@PermitAll
@GET
public Response fetchCharacters(@Auth Account account) {
List<Character> chars = dao.getCharacters(account);
return Response.status(Status.OK).entity(chars).build();
}
and while I could do that of cause as it's only a very small drawback I was wondering why this is not working as I'd expect it.
I get that the session is obviously closed after fetching the principal in the authenticator, but why is a new session opened for a DAO but not for a hibernate lazy fetch? And is there a way to fix it or is that just as intended?
java hibernate dropwizard
java hibernate dropwizard
asked Nov 8 at 8:26
Fussel
57112
57112
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53203879%2fdropwizard-hibernate-session-aware-lazy-loading%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password