public class WarningMessage extends AbstractMessage
| Modifier and Type | Field and Description |
|---|---|
private static long |
serialVersionUID
UID for serialization.
|
TYPE_INFORMATION, TYPE_TECHNICAL_ERROR, TYPE_USER_ERROR, TYPE_VALIDATION_FAILURE, TYPE_WARNING| Modifier | Constructor and Description |
|---|---|
protected |
WarningMessage()
The constructor for de-serialization in GWT.
|
|
WarningMessage(String code,
Object source,
NlsMessage message)
The constructor.
|
|
WarningMessage(String code,
Object source,
NlsMessage message,
UUID uuid,
String details)
The constructor.
|
|
WarningMessage(String code,
Object source,
String message)
The constructor.
|
|
WarningMessage(String code,
Object source,
String message,
UUID uuid,
String details)
The constructor.
|
| Modifier and Type | Method and Description |
|---|---|
String |
getDetails()
This method gets optional details for this message.
|
String |
getType()
This method gets the type of this
Message. |
UUID |
getUuid()
This method gets the
UUID of this object. |
getCode, getMessage, getMessage, getSource, toStringprivate static final long serialVersionUID
protected WarningMessage()
public WarningMessage(String code, Object source, String message, UUID uuid, String details)
public WarningMessage(String code, Object source, NlsMessage message, UUID uuid, String details)
public String getDetails()
getDetails in interface MessagegetDetails in class AbstractMessagenull if no additional details are available.public String getType()
Message. This should be one of the following options:
ValidationFailure.error caused by the
end-user (e.g. by providing invalid data). Unlike Message.TYPE_VALIDATION_FAILURE this is an actual
error that has been detected after a successful validation.error related to
a technical problem (e.g. programming failure such as NullPointerException or operational error
like ConnectException).public UUID getUuid()
UUID of this object. When the object is created, a UUID is
generated. In case the object is created from another object that already has a UUID,
the existing UUID will be used (e.g. for chained
exceptions). UUID will appear in a
stacktrace but NOT in the message. It
will therefore be written to log-files if the NlsThrowable is
logged. If you supply the UUID to the end-user in an error panel or popup (see
Message), he can provide it with the problem report so an administrator
or software developer can easily find the stacktrace in the log-files.getUuid in interface AttributeReadUuidgetUuid in interface MessagegetUuid in class AbstractMessageUUID if this Message. Will typically only be available if type is Message.TYPE_TECHNICAL_ERROR or Message.TYPE_USER_ERROR. Will be null if
not available.Copyright © 2001–2015 mmm-Team. All rights reserved.