带有Java新行的自定义异常消息

Question

I am throwing a custom exception as below to UI

StringBuilder errorMessage = new StringBuilder("Error One Message"); 
String newlinetest = System.getProperty("line.separator");
                  // String sep = System.line.separator;
String secondErrorMessage = "Error Two message";
throw new ErrorWhileCreatingMessageException(errorMessage+"\r\n"+secondErrorMessage);

I need to add new line between two error messages before throwing. I tried \\n, \\r\\n and line. separator it didn't work. Any help on this is much appreciated

I am using Angular JS in the UI. I am displaying as below

<div ng-show="error != null">
    <div class="alert alert-danger" role="alert" ng-bind="error"></div>
</div>

Answer 1

Why dont you just read the content of the div you are inserting the error message in, and find/replace \\r\\n with a <br>

or just straight up try a <br> in that error message instead of \\r\\n, does that help?

Answer 2

如果您在HTML中显示结果，请尝试使用<br>替换\\ r \\ n

Answer 3

The idiomatic thing to do here is to return a proper error object from your rest service when an error happens, and split out the error type from the error message . This will require a new class and require you to send that over the wire, but you'll find it easier to deal with as you'll be able to properly populate values for error.type and error.message .

By default, Angular isn't going to allow you to render raw HTML in responses unless you regard it as unsafe. In 99% of the cases I've seen with Angular, that's exactly what you don't want to do.

Alternatively...since exceptions are meant for you as a developer and error messages are meant for consumers, you may want to rethink what you're sending. You don't want to send across the stack trace or anything too specific to the end user, since they're not going to understand it. It would be best to select a generic message which explains what the issue is in general, and what they're doing to fix it. For some inspiration, Stack Overflow's error page does a decent job of keeping us as clients shielded from the actual error.