WebApplicationException not logged depending on constructor
up vote
0
down vote
favorite
Whenever I throw a WebApplicationException with a Response in the constructor (normally a 400 response), I don't get a stack trace logged. If I neglect the Response, I see the stack trace logged but then I can't send an entity to the client. I could just remember to log the exception explicitly every time before I throw it, but I don't understand why this is necessary.
I want to be able to send a message to the client via a Response entity, AND I want the exception to be logged. Why do the constructor arguments affect whether my WebApplicationException is logged?
java logging web-applications server response
add a comment |
up vote
0
down vote
favorite
Whenever I throw a WebApplicationException with a Response in the constructor (normally a 400 response), I don't get a stack trace logged. If I neglect the Response, I see the stack trace logged but then I can't send an entity to the client. I could just remember to log the exception explicitly every time before I throw it, but I don't understand why this is necessary.
I want to be able to send a message to the client via a Response entity, AND I want the exception to be logged. Why do the constructor arguments affect whether my WebApplicationException is logged?
java logging web-applications server response
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Whenever I throw a WebApplicationException with a Response in the constructor (normally a 400 response), I don't get a stack trace logged. If I neglect the Response, I see the stack trace logged but then I can't send an entity to the client. I could just remember to log the exception explicitly every time before I throw it, but I don't understand why this is necessary.
I want to be able to send a message to the client via a Response entity, AND I want the exception to be logged. Why do the constructor arguments affect whether my WebApplicationException is logged?
java logging web-applications server response
Whenever I throw a WebApplicationException with a Response in the constructor (normally a 400 response), I don't get a stack trace logged. If I neglect the Response, I see the stack trace logged but then I can't send an entity to the client. I could just remember to log the exception explicitly every time before I throw it, but I don't understand why this is necessary.
I want to be able to send a message to the client via a Response entity, AND I want the exception to be logged. Why do the constructor arguments affect whether my WebApplicationException is logged?
java logging web-applications server response
java logging web-applications server response
edited Nov 19 at 22:48
asked Nov 19 at 18:49
efthimio
167
167
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380910%2fwebapplicationexception-not-logged-depending-on-constructor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown