com.sun.xml.ws.rx.rm.localization.Localization.properties Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of webservices-rt Show documentation
This module contains the Metro runtime code.
There is a newer version: 4.0.4
#
# Copyright (c) 2010, 2018 Oracle and/or its affiliates. All rights reserved.
#
# This program and the accompanying materials are made available under the
# terms of the Eclipse Distribution License v. 1.0, which is available at
# http://www.eclipse.org/org/documents/edl-v10.php.
#
# SPDX-License-Identifier: BSD-3-Clause
#

# policy / config
WSRM1001_ASSERTION_NOT_COMPATIBLE_WITH_RM_VERSION = WSRM1001: Assertion [ {0} ] is not compatible with [ {1} ] WS-RM version
WSRM1002_MULTIPLE_WSRM_VERSIONS_IN_POLICY=WSRM1002: Multiple WS-ReliableMessaging Policy versions specified in a single policy alternative.
WSRM1003_MUTLIPLE_DA_TYPES_IN_POLICY=WSRM1003: Inconsistent RM policy - multiple delivery assurance types specified.
WSRM1004_EXPECTED_DA_NOT_SPECIFIED_IN_POLICY=WSRM1004: Inconsistent RM policy - expected delivery assurance not specified in RM1.1 assertion.
WSRM1005_MULTIPLE_SECURITY_BINDINGS_IN_POLICY=WSRM1005: Inconsistent RM policy - multiple security binding types specified.
WSRM1006_MULTIPLE_BUFFER_SIZES_IN_POLICY=WSRM1006: Inconsistent RM policy - multiple flow control buffer sizes specified.
WSRM1007_MULTIPLE_OCCURENCES_OF_ASSERTION_PARAMETER=WSRM1007: Multiple occurences of assertion parameter [ {0} ] detected in the policy assertion [ {1} ]
# {0} - number, {1} - qname
WSRM1008_DUPLICATE_ASSERTION_IN_POLICY=WSRM1008: {0} duplicate [ {1} ] policy assertions in a single policy alternative detected
WSRM1009_INCONSISTENCIES_IN_POLICY=WSRM1009: Inconsistency detected in a WS-Policy expression:\n \
[ {0} ] assertion is not compatible with WS-ReliableMessaging version [ {1} ].\n \
Please, update your WS-Policy expression by replacing current assertion with the assertions compatible \
with the used WS-ReliableMessaging version. Note that future Metro release may decide reject such inconsistent \
policies and fail to deploy your web service.

# runtime
WSRM1101_UNSUPPORTED_OPERATION=WSRM1101: This operation is not supported in [ {0} ] implementation
WSRM1102_RESENDING_DROPPED_MESSAGE=WSRM1102: Resending dropped message
WSRM1103_RM_SEQUENCE_NOT_TERMINATED_NORMALLY=WSRM1103: Unable to terminate RM sequence normally due to an unexpected exception
WSRM1104_RM_VERSION_NOT_SUPPORTED=WSRM1104: Unsupported WS-ReliableMessaging version [ {0} ]
WSRM1105_SEQUENCE_ID_NOT_RECOGNIZED=WSRM1105: Sequence id in the message header [ {0} ] does not match the expected sequence id bound to this session [ {1} ]
WSRM1106_SENDING_RM_SESSION_CONTROL_MESSAGE_FAILED=WSRM1106: Attempt to send a [ {0} ] RM session control message failed with an exception
WSRM1107_MAX_RM_SESSION_INIT_ATTEMPTS_REACHED=WSRM1107: Unable to initiate RM Session - maximum attempts to initiate RM session reached
WSRM1108_NULL_RESPONSE_FOR_ACK_REQUEST=WSRM1108: Response for the acknowledgement request is 'null'
WSRM1109_SOAP_FAULT_RESPONSE_FOR_ACK_REQUEST=WSRM1109: Acknowledgement request ended in a SOAP fault
WSRM1110_ACK_REQUEST_FAILED=WSRM1110: Acknowledgement request failed
WSRM1111_WAITING_FOR_SEQ_ACKS_UNEXPECTED_EXCEPTION=WSRM1111: Unexpected exception occured while waiting for message acknowledgements on a sequence [ {0} ]
WSRM1112_WAITING_FOR_SEQ_ACKS_TIMED_OUT=WSRM1112: Waiting for message acknowledgements on a sequence [ {0} ] timed out after {1} milliseconds.
WSRM1113_WAITING_FOR_SEQ_ACKS_INTERRUPTED=WSRM1113: Waiting for message acknowledgements on a sequence [ {0} ] has been interrupted
WSRM1114_NULL_RESPONSE_ON_PROTOCOL_MESSAGE_REQUEST=WSRM1114: Response to {0} request message was 'null'
WSRM1115_PROTOCOL_MESSAGE_REQUEST_REFUSED=WSRM1115: {0} was refused by the RMDestination
WSRM1116_ACKS_TO_NOT_EQUAL_TO_ENDPOINT_DESTINATION=WSRM1116: Unsupported "AcksTo" destination. Inbound sequence "AcksTo" destination [ {0} ] must be the same as the service endpoint destination [ {1} ]
WSRM1117_UNEXPECTED_SEQUENCE_ID_IN_TERMINATE_SR=WSRM1117: The sequence identifier in the terminate sequence response message [ {0} ] does not correspond to the terminating outbound sequence identifier [ {1} ]
WSRM1118_MANDATORY_HEADER_NOT_PRESENT=WSRM1118: Mandatory {0} header not present on the response message
WSRM1119_UNEXPECTED_SEQUENCE_ID_IN_CLOSE_SR=WSRM1119: The sequence identifier in the close sequence response message [ {0} ] does not correspond to the closing outbound sequence identifier [ {1} ]
WSRM1120_RESPONSE_NOT_IDENTIFIED_AS_PROTOCOL_MESSAGE=WSRM1120: Unable to process response packet - the packet was not identified as an RM protocol message
WSRM1121_SECURE_CONVERSATION_INIT_FAILED=WSRM1121: Unable to start secure conversation
WSRM1122_ERROR_MARSHALLING_RM_HEADER=WSRM1122: Unable to unmarshall RM header [ {0} ]
WSRM1123_ERROR_UNMARSHALLING_MESSAGE=WSRM1123: Unable to unmarshall a message
WSRM1124_NO_SUCH_SEQUENCE_ID_REGISTERED=WSRM1124: No sequence registered with id [ {0} ]
WSRM1125_ILLEGAL_MESSAGE_ID=WSRM1125: "Message number [ {1} ] not found among the unacknowledged message numbers on a sequence [ {0} ]."
WSRM1126_DUPLICATE_SEQUENCE_ID=WSRM1126: Sequence with id [ {0} ] already registered.
WSRM1127_UNEXPECTED_EXCEPTION_WHEN_SENDING_ACK_REQUEST=WSRM1127: An unexpected exception occured while sending acknowledgement request
# {0} - "CreateSequence"/"CloseSequence"/"TerminateSequence" (types of messages)
WSRM1128_MAX_RM_SESSION_CONTROL_MESSAGE_RESEND_ATTEMPTS_REACHED="WSRM1128: Failed to send a [ {0} ] RM session control message: Maximum number of resend attempts has been reached."
WSRM1129_INVALID_VALUE_OF_MESSAGE_HEADER=WSRM1129: Invalid value of \"{0}\" header on "{1}" message: [ {2} ]
WSRM1130_MISSING_MESSAGE_HEADER=WSRM1130: Missing \"{0}\" header on "{1}" message: [ {2} ]
WSRM1131_SECURITY_TOKEN_AUTHORIZATION_ERROR=WSRM1131: SecurityToken Authorization error Got {0} Expected {1}
WSRM1132_SECURITY_REFERENCE_ERROR=WSRM1132: Cannot handle the Reference from the SecurityToken reference; class name {0}
WSRM1133_NO_SECURITY_TOKEN_IN_REQUEST_PACKET=WSRM1133: No security token found in the request packet
WSRM1134_UNSUPPORTED_PROTOCOL_MESSAGE=WSRM1134: Internal error - The RM protocol message processing for WS-Addressing action [ {0} ] is not implemented
WSRM1135_WRONG_SEQUENCE_STATE_ACKNOWLEDGEMENT_REJECTED=WSRM1135: The sequence [ {0} ] is in state [ {1} ] and does not accept further acknowledgements
WSRM1136_WRONG_SEQUENCE_STATE_MESSAGE_REGISTRATION=WSRM1136: The sequence [ {0} ] is in state [ {1} ] and is not ready to register messages
WSRM1137_OFFERED_ID_ALREADY_IN_USE=WSRM1137: The offered sequence identifier [ {0} ] is already in use
WSRM1138_MESSAGE_NUMBER_ROLLOVER=WSRM1138: The maximum value for a message number on a sequence  [ {0} ] has been exceeded: {1}
WSRM1139_NO_OUTBOUND_SEQUENCE_FOR_RESPONSE=WSRM1139: Unable to send response reliably - no outbound sequence bound to an inbound sequence [ {0} ]
WSRM1140_NO_ADDRESSING_VERSION_ON_ENDPOINT=WSRM1140: WS-Addressing not enabled on the service endpoint. In order to use WS-ReliableMessaging, you must enable WS-Addressing feature as well.
WSRM1141_UNEXPECTED_MESSAGE_CLASS=WSRM1141: Unexpected message class [ {0} ], expected class [ {1} ]
WSRM1142_ERROR_CREATING_HA_BACKING_STORE=WSRM1142: Unable to create [ {0} ] HA backing store.
#WSRM1143_=WSRM1143:
#WSRM1144_=WSRM1144: 
WSRM1145_DUPLICATE_MSG_NUMBER_RECEIVED=WSRM1145: Duplicate message number [ {0} ] received on sequence [ {1} ]
WSRM1146_UNEXPECTED_ERROR_WHILE_REGISTERING_MESSAGE=WSRM1146: Unexpected exception while registering message
WSRM1147_ADDING_MSG_TO_QUEUE_INTERRUPTED=WSRM1147: Operation of adding a message to an internal message queue was interrupted
WSRM1148_DUPLICATE_MSG_NUMBER_REGISTRATION_ATTEMPTED=WSRM1148: Attempt to register a duplicate message number [ {0} ] detected on the sequence [ {1} ]
WSRM1149_DIFFERENT_MSG_SEQUENCE_ID=WSRM1149: Cannot register message: Sequence identifier on the application message [ {0} ] is different from the identifier of this sequence [ {1} ]
WSRM1150_UNABLE_TO_RESCHEDULE_SEQUENCE_MAINTENANCE_TASK=WSRM1150: Unable to re-schedule the sequence maintenance task for an endpoint UID [ {0} ]
WSRM1151_TERMINATING_SEQUENCE_MAINTENANCE_TASK=WSRM1151: Terminating sequence maintenance task for an endpoint UID [ {0} ]: Sequence manager instance has been garbage-collected
WSRM1152_REMOVING_SEQUENCE=WSRM1152: Removing sequence [ {0} ]
WSRM1153_TERMINATING_SEQUENCE=WSRM1153: Terminating sequence [ {0} ]
WSRM1154_UNEXPECTED_CLASS_OF_JNDI_BOUND_OBJECT=WSRM1154: Object of class [ {0} ] bound in the JNDI under [ {1} ] is not an instance of [ {2} ]
WSRM1155_RM_JDBC_CONNECTION_POOL_NOT_FOUND=WSRM1155: Unable to lookup Metro reliable messaging JDBC connection pool
WSRM1156_MAX_CONCURRENT_SESSIONS_REACHED=WSRM1156: Unable to create new Reliable Messaging sequence - maximum number ( {0} ) of concurrently opened Reliable Messaging sessions has been reached.
WSRM1157_WAITING_FOR_SEQ_STATE_CHANGE_TIMED_OUT=WSRM1157: Waiting for sequence [ {0} ] state change to [ {1} ] has timed out after {2} milliseconds
WSRM1158_WAITING_FOR_SEQ_STATE_CHANGE_INTERRUPTED=WSRM1158: Waiting for sequence [ {0} ] state change to [ {1} ] has been interrupted
WSRM1159_MAX_MESSAGE_RESEND_ATTEMPTS_REACHED=WSRM1159: Maximum number of message resend attempts has been reached.
WSRM1160_DELIVERY_QUEUE_CLOSED=WSRM1160: Sequence delivery queue has been closed

# protocol JAXB elements
# WSRM4001_
# Nack = Negative Acknowledge. This term is used in the specification of WS-ReliableMessaging. Should not be translated.
WSRM4002_BOTH_ACKS_AND_NACKS_MESSAGE=WSRM4002: A SequenceAcknowledgement cannot contain both AcknowledgementRanges and NACKS.
WSRM4003_UPPERBOUND_LESSTHAN_LOWERBOUND_MESSAGE=WSRM4003: The Upper Bound of a SequenceAcknowledgement range is less than the Lower Bound.      
WSRM4004_SEQUENCE_ACKNOWLEDGEMENT_TOSTRING_STRING=WSRM4004: SequenceAcknowledgement:\n\tid = {0}\n\tRanges:\n\tbufferRemaining = {1}\n
WSRM4005_SEQUENCE_TOSTRING_STRING=WSRM4005: SequenceElement:\n\tid = {0}\n\tnumber = {1}\n\tlast = {2}

# intermediary use case related messages
# WSRM5001_
WSRM5001_COULD_NOT_BEGIN_TRANSACTION=WSRM5001: Distributed transaction could not be started. Existing transaction found.
WSRM5002_CLIENTTUBE_PROCESSING_CANNNOT_HAVE_TRANSACTION=WSRM5002: ClientTube message processing cannot be part of a distributed transaction.
WSRM5003_RECEIVED_WSRM_FAULT_RESPONSE=WSRM5003: Received WS-RM fault response. Fault action is: [ {0} ]