📄 core-messages.properties
字号:
0=No Message was set1=Mule Version Info not set2=Server started: {0}3=Server shutdown: {0}4=Agents Running:5=Not Set6=Version: {0}7=Mule shut down normally on: {0}8=Server was up for: {0}9=\n\n\*******************************************************************************\n\ No config file specified and no config by the name of mule-config.xml\n\ found on the classpath.\n\ \nUsage: mule -config <mule-configuration> [ -main <main class> ] \ \n [-builder <config-builder>] [-debug] [-version]\n\ \n mule-configuration - a URL for the Mule Config XML to use,\ \n if not specified the config will be loaded from\ \n the classpath\n\ \n main-class - the main class to start instead of \ \n org.mule.module.boot.MuleServerWrapper \n config-builder - a fully qualified class name of the builder to use\ \n to configure Mule.\n\ \n debug - configure Mule for JPDA remote debugging.\ \n Customize settings by editing a JPDA_OPTS variable\ \n in the 'mule' startup script\n\ \n version - print full product information\n\*******************************************************************************\n\n10=A Fatal error has occurred while the server was running:11=Root Exception stack trace:12=Exception stack is:13=For more information about this exception see -14=For more information see -15=JavaDoc Reference:16=Documentation Reference:17=See exception below for details18=Message payload is of type: {0}19=Message Details:20=The error is fatal, the system must shutdown21=The server is shutting down due to normal shutdown request22=None23=Not clustered30=Failed to route event via endpoint: {0}31=No component implementation found as local reference using: {0}32=Cannot perform an action on a connector when it is or while it is being disposed33=Connector that caused exception is: {0}34=Endpoint cannot be null when registering a listener35=There is already a listener registered on this connector on endpointUri: {0}36=Connector "{0}" has not been started. Cannot create dispatcher37=Object "{0}" has already been initialised38=Component that caused exception is: {0}39=Object that caused exception is: {0}40={0} Failed to initialise41=Failed to stop {0}42=Failed to start {0}43=Proxy pool timed out44=Failed to borrow object from pool45=The required object/property "{0}" is null46=Component not registered: {0}47=Failed to register listener {0} on endpoint {1}48=Failed to unregister listener {0} on endpoint {1}49=Failed to pause {0}50=Failed to resume {0}51=The endpoint "{0}" is malformed and cannot be parsed. If this is the name of a global endpoint, check the name is correct, that the endpoint exists, and that you are using the correct configuration (eg the "ref" attribute). Note that names on inbound and outbound endpoints cannot be used to send or receive messages; use a named global endpoint instead.52=Failed to transform message before applying the filter53=The object transformed is of type: "{0}", but the expected return type is "{1}"54=The transformer "{0}" does not support source type "{1}". Endpoint is "{2}"55=Failed to transform data from {0}57=Failed to load {0} transformer "{1}"58=Failed to load {0}59=Message type "{0}" is not supported by adapter "{1}"60=Found too many possible methods on object "{0}" that accept parameters "{1}"61=Failed to set property "{0}" on object "{1}" with parameter type "{2}"62=Failed to obtain session for component "{0}" while reloading persistent queue63=Failed to find endpoint "{0}" for component "{1}" while reloading persistent queue64=Cannot dispatch event, Endpoint is a receiver endpoint and there is no current component65=Failed to create {0}66=There is no Correlation Id set on the message67=Failed while disposing {0}68=Failed to invoke {0}69=Could not read message payload as bytes (byte[]). Payload type is "{0}"70=Could not read message payload as String. Payload type is "{0}"71=Class "{0}" not found on classpath72=Failed to route event to component "{0}". The endpoint received on is "{0}"73=Failed to instanciate finder class "{0}"74=Failed to create "{0}" with "{1}"75="{0}" not set in service descriptor "{1}"76=Object "{0}" not found in container77=Cannot commit transaction transaction is marked for rollback78=Can not bind resource to a null key79=Can not bind a null resource80=Only a single resource can be bound to this type of transaction81=This transformer can only be invoked when an event is being processed. It needs a current event to perform a transform82=OBject of type "{0}" with name "{1}" is not available in the registry83=Failed to set properties on {0}84=Failed to create connector from Uri: {0}85=Initialisation Failure: {0}86=Failed to initialise interceptors on component "{0}"87=Failed to create endpoint from service location: {0}88=Manager is already started89=No endpoints are set on this router, cannot route message90=Response timed out ({0}ms) waiting for message response id "{1}" or this action was interrupted.91=Component implementation type is "local" but no property called "{0}" is set on the descriptor "{1}"92=Failed to instanciate non-container managed object reference "{0}"93=Failed to receive event over: {0} (timeout={1})94=Failed to write message id "{0}" to store: {1}95=Failed to read from store: {0}96=Can not start {0} transaction97=Transaction commit failed98=Transaction rollback failed99=Unable to read transaction state100=A resource has already been enlisted for key "{0}"101=There is no outbound router configured on component "{0}"102=Failed to set property "{0}" on object "{1}"103=A transaction is available for this session, but transaction action is "{0}"104=A transaction is not available for this session, but transaction action is "{0}"105=Cannot route event in Catch all as no endpoint has been set106=Interrupted while queue event for "{0}"107=Failed unbind transaction, current transaction and referenced transaction are not the same108=Cannot bind transaction as a transaction is already bound109=Invocation error. Method "{0}", with parameters "{1}" not found on "{2}"110=Failed to transform from "{0}" to "{1}"112=Crypto Failure115=The Endpoint Uri scheme "{0}" is not compatible with Connector "{1}"116=Could not find entry point on: "{0}" with arguments: "{1}"117=There is no Security Provider reqistered called "{0}"120=Can only bind "{0}" type resources122=Failed to load "{0}" from classpath or file system124=Failed to read payload data126=Endpoint "{0}" not found127=Failed to process event for component "{0}"128=Failed to dispatch event on replyTo destination "{0}"130=Crypto strategy is: {0}131=The authentication type {0} is not recognised by the Security Manager132=A Security Manager has not been configured on this Mule instance133=Registered authentication is set to {0} but there was no security context on the session135=Authentication failed for principal {0}136=The Endpoint that this security filter is associated with must be able to send or receive (it cannot be global).137=No Authentication Provider registered for "{0}"140=The transaction manager on the MuleManager cannot be set one has already been set141=Could not recover container configuration from fragment142=For this builder the config resources should be null (and "mule-config.xml" will be used by default)\ or a single name of the resuorces to look up should be specified143=Only CustomEvent events can be fired through the MuleManager
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -