core-messages.properties

提供ESB 应用mule源代码 提供ESB 应用mule源代码

144=Failed to create UMOManager instance "{0}"
145=Failed to clone {0}
146=Exception occurred on connector "{0}". Exception evaluator is not set. This could result in message loss
147=Adapter "{0}" does not support unique identifiers
148=Failed to persist queued event {0}
150=Server Notification Manager is not enabled. Cannot register event listeners.  This usually occurs if the Mule is running in client mode.
151=Failed to schedule work with the Work manager
152=No credentials set
154=The value "{0}" is invalid for property "{1}", check the relevant documentation
155=A container is already registered with the name "{0}"
156=A connector with protocol "{0}" is not registered with this Mule instance
157=Object "{0}" is not of supported type "{1}" it is of type "{2}"
161=Resource manager has not been started
162=Resource manager is set to dirty, this *may* mean it is corrupt. No modifications are allowed until a recovery run has been performed!
163=Resource manager is not ready
164=ReconnectStrategy "{0}" failed to reconnect receiver on endpoint "{1}"
165=Cannot not set property "{0}" once it has already been set
166=Event type "{0}" not recognised by this event manager
167=Cannot route event as component "{0}" is stopped
168=The required property "{0}" is not set on the event
171=Descriptor "{0}" already exists in the model
172=Failed to invoke REST service "{0}"
174=There is no Encryption Strategy registered called "{0}"
175=Header field "{0}" is malformed. Value is "{1}"
176=A transaction manager is required but no set on this Mule instance
177=Transform on event for component "{0}" not of type requested by component, type needed is "{1}"
178=An endpoint cannot use remote Sync when it is transacted. Check your endpoint configuration
180=Failed to build message. See next excpetion trace for more details
181=There were no matching methods for args "{0}" on object "{1}"
#No longer Used
#182=There were too many matching methods for args "{0}" on object "{1}"
183=Property "{0}" not set.  One or more of them must be set
184=Script engine is invalid, it must be a compilable engine.
185=Object "{0}" not of correct type. It must be of type "{1}"
188=Failed to convert a string using the {0} encoding
189=Property "{0}" has an incorrect or unsupported value "{1}"

# post 1.2 messages
190=Space Action "{0}" was interrupted
191=Failed to create Space. See preceeding exception for details
192=Scheme of the endpoint cannot be changed at runtime for this type router. Old sche was "{0}" new scheme is "{1}"
193=days
194=hours
195=mins
196=sec

#Post mule_1_3 branch merge
197=Template Endpoint "{0}" resolved into a Malformed endpoint "{1}"
198=Could not determine Destination component from endpoint "{0}"
200=There is no Transaction currently bound
201=Session variable "{0}" is malfomed and cannot be read

#Post 1.3-rc1
202=This type of router can only have a single endpoint registered on it
203=The endpoint is not a streaming endpoint: "{0}"
204=The endpoint does not support streaming: "{0}"
205=Streaming failed. Could not get output stream
206=Endpoint scheme must be compatible with the connector scheme. Connector is: "{0}", endpoint is "{1}"
207=Failed to read attachment "{0}"

#Post 1.3-rc2
208=Failed to initialize security provider "{0}"

#Post Mule 1.3.3
209=Streaming is not supported by the "{0}" transport
210=Streaming Component "{0}" must have exactly one endpoint on the outbound router
211=Streaming Endpoint "{0}" does not provide a response output stream, you need to either add an outbound endpoint or mark the endpoint as asynchronous
212=Streaming failed for endpoint "{0}"
213=Streaming endpoints don't currently support transformers
214=Only Streaming endpoints can be used with the streaming model
215=setter method for binding interface "{0}" not found on service component "{1}"
216=There are too many matching methods on object "{1}" with a return type of "{0}"
217=Failed to set nested binding proxy "{0}" on service component "{1}"
218=This interface already has one router associated with it. If you want to bind to an interface with more than one method you need to configure the method names explicitly on the bindings in the Nested Router.
219=Cannot find binding for method name "{0}"
220=There are no matching methods on object "{1}" with a return type of "{0}"
221=There are at least 2 connectors matching protocol "{0}", so the connector to use must be specified on the endpoint using the ''connector'' property/attribute

#Post Mule 1.4
223=Failed to get output stream
224=No-args method "{1}" not found for object "{0}"
225=Both "class" and "method" attributes must be configured on this component if no "delegateInstance" provided
226=No "class" must be specified if "ref" is specified for this component

#Post Mule 2.0
227=No service descriptor found for transport: "{0}".  This transport does not appear to be installed.
228=Failed to invoke lifecycle phase "{0}" on object: {1}
229=Unrecognised servce type: "{0}"
230=ServiceFinder unable to locate the real service "{0}"

231="Model name on descriptor: "{0}" is "{1}" but doesn't match the model being registered on: "{2}"
232=The endpoint "{0}" is not an inbound endpoint. Inbound endpoints must be used with the inbound router collection "{1}
233=The endpoint "{0}" is not an outbound endpoint. Outbound endpoints must be used with the outbound router "{1}
234=The endpoint "{0}" is not a response endpoint. Response endpoints must be used with the response router collection "{1}
235=The endpoint "{0}" is not a outbound endpoint. Outbound endpoints must be used with the exception strategy "{1}

# 227 in Mule 1.4
236=\n\n\
*******************************************************************************\
\n{0}\
\nVersion: {1}\
\n{2}\n\
*******************************************************************************\n\n
237=Could not find a transformer to transform "{0}" to "{1}".
238=Could not read InputStream.

239=No-args method "{0}" not found for object "{1}" using resolver "{2}"
240=Could not find entry point on: "{0}" with arguments: "{1}" using resolver "{2}"
241=There are no matching methods on object "{0}" with a return type of "{1}" using resolver "{2}"
242=Found too many possible methods on object "{0}" that accept parameters "{1}" using resolver "{2}"
243=There are too many matching methods on object "{0}" with a return type of "{1}" using resolver "{2}"
244=Object "{0}" does not implement required interface "{1}"
245=Invocation was successful, cannot set error message
246=Could not find entry point on: "{0}" with method name: "{1}" using resolver "{2}"
247=No JTA transaction associated with thread {0}
248={0} is not an instance of Mule XaTransaction
249=No queue timeout value set on component "{0}"
250=Failed to process Expression Evaluation "{0}"
251=An Expression Evaluator for "{0}" is not registered with Mule. Make sure you have the the module for this expression type on your classpath. for example, if you are using an xpath expression you need to have the Mule XML module on your classpath.
252=Object already exists or is already registered: "{0}"
253=Mule transaction is null, but enlist method is called
254=Object "{0}" has already been registered in the Registry. Registered object is "{1}", Object being registered is "{2}"
255=Transformer does not implement Discoverable interface, it must do so to be registered via the Registry Bootstrap. Transformer is "{0}"
256=There are two transformers that are an exact match for input: "{0}", output: "{1}". Transformers are: "{2}" and "{3}"
257=Configured Mule using "{0}" with "{1}" resource(s)
258=Configured Mule using "{0}" with configuration resource(s): "{1}"
259=No suitable configuration builder for resource "{0}" found.  Check you have configuration module on your classpath and are using correct file extension.
260=Configuration with "{0}" failed.
261=Unsupported request for retry in nested lifetime transition.
263=Expression Evaluator "{0}" with expression "{1}" returned null but a value was required.
264=You must supply a valid expression for property "{0}" the invalid expression is "{1}"
265=Expression "{0}" is malformed for evaluator "{1}". Please check the documentation for this evaluator.
266=Correlation timed out while waiting on event group with Id: "{0}"
267=An invalid return type "{0}" was specified for transformer "{1}"
268=There is no resource binding to current transaction
269=TransactionFactory is mandatory when action is {0}
270=Failed to create proxy for {0}
271=Authentication Attempt Failed
# Reconnection strategies
272=Retry policy is exhausted. Policy is: "{1}"
273="{0}" has not managed to connect yet, cannot process any messages for this object until it has connected
274={0} event(s) were lost when the service "{1}" was stopped while paused.  To avoid message loss use a persistent SEDA queue by configuring the service queue profile to use persistence.
275=No Routing path for split message. Check splitter router settings. Service name is "{0}", message part is "{1}" If you want to ignore some message parts add failIfNoMatch=false to your splitter router config
276=The expression "{0}" did not result in a value but a value is required.