|
»
»
Mule Startup Issue
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Mule Startup Issue
by Mike Carr-6
::
Rate this Message:
Just downloaded mule standalone 2.2.1 on windows xp and trying to run the hello world example. I setup the MULE_HOME env variable via control panel and also setup the MULE_LIB. I took the hello-config file under the examples\hello\conf directory and put it under MULE_HOME\conf and renamed to mule-config.xml. Checked that it references <component class="org.mule.example.hello.Greeter"/> - File is attached
Please see the error that I am getting when I try to launch mule C:\mule-standalone-2.2.1\bin>mule start -config file:.\conf\mule-config.xml 'xá-' is not recognized as an internal or external command,operable program or batch file. C:\mule-standalone-2.2.1\bin>echo %MULE_LIB% .\conf C:\mule-standalone-2.2.1\bin>echo %MULE_HOME% C:\mule-standalone-2.2.1 C:\mule-standalone-2.2.1\bin>echo %JAVA_HOME% C:\Program Files\Java\jdk1.5.0_20\bin Please help. Thanks. <?xml version="1.0" encoding="UTF-8"?> <mule xmlns="http://www.mulesource.org/schema/mule/core/2.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:spring="http://www.springframework.org/schema/beans" xmlns:stdio="http://www.mulesource.org/schema/mule/stdio/2.2" xmlns:vm="http://www.mulesource.org/schema/mule/vm/2.2" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://www.mulesource.org/schema/mule/core/2.2 http://www.mulesource.org/schema/mule/core/2.2/mule.xsd http://www.mulesource.org/schema/mule/stdio/2.2 http://www.mulesource.org/schema/mule/stdio/2.2/mule-stdio.xsd http://www.mulesource.org/schema/mule/vm/2.2 http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd"> <description> The hello sample application has two components - 1. The Greeter component that adds a greeting to the event it receives 2. The ChitChater component that adds some additional conversation to the event it receives An event is triggered by input through the system console and the outbound event is also written out through the system console. This configuration also demonstrates user and system error handling. User error handling returns an error message to the end user. System error handling logs errors. </description> <!-- The system stream connector is used to send and receive information via the System.in and System.out. Note this connector is only really useful for testing purposes. promptMessage - is what is written to the console messageDelayTime - is the time in milliseconds before the user is prompted again. These properties are set as bean properties on the connector. --> <stdio:connector name="SystemStreamConnector" promptMessageCode="3" resourceBundle="messages.hello-example-messages" messageDelayTime="1000"/> <!-- All transformers must be defined here. For this example we have two transformers used to transform the inbound events for the Greeter and Chatter components into objects they understand. The entryPointResolver configured on the Model below will determine which method to call on our components based on the return types of these transformers. --> <custom-transformer name="StdinToNameString" class="org.mule.example.hello.StdinToNameString"/> <custom-transformer name="NameStringToChatString" class="org.mule.example.hello.NameStringToChatString"/> <custom-transformer name="ChatStringToString" class="org.mule.example.hello.ChatStringToString"/> <custom-transformer name="ExceptionToString" class="org.mule.example.hello.ExceptionToString"/> <!-- An interceptor is a piece of code that can be configured to execute before and/or after an event is received for a component. You can define a stack of interceptors that will be executed in sequence. You can then configure the stack on your components. --> <!-- The Mule model initialises and manages your UMO components --> <model name="helloSample"> <!-- A Mule service defines all the necessary information about how your components will interact with the framework, other components in the system and external sources. Please refer to the Configuration Guide for a full description of all the parameters. --> <service name="GreeterUMO"> <inbound> <stdio:inbound-endpoint system="IN" transformer-refs="StdinToNameString"/> </inbound> <component class="org.mule.example.hello.Greeter"/> <outbound> <filtering-router> <vm:outbound-endpoint path="chitchatter"/> <payload-type-filter expectedType="org.mule.example.hello.NameString"/> </filtering-router> <filtering-router> <vm:outbound-endpoint path="userErrorHandler"/> <payload-type-filter expectedType="java.lang.Exception"/> </filtering-router> </outbound> <!-- Route unexpected errors to separate error handler --> <default-service-exception-strategy> <vm:outbound-endpoint path="systemErrorHandler"/> </default-service-exception-strategy> </service> <service name="ChitChatUMO"> <inbound> <vm:inbound-endpoint path="chitchatter" transformer-refs="NameStringToChatString"/> </inbound> <component class="org.mule.example.hello.ChitChatter"/> <outbound> <pass-through-router> <stdio:outbound-endpoint system="OUT" transformer-refs="ChatStringToString" /> </pass-through-router> </outbound> </service> <!-- This error handler returns user error messages to caller. Errors could also be routed elsewhere, e.g. into an error file, send via email to a list, stored in a database, etc. --> <service name="UserErrorHandler"> <inbound> <vm:inbound-endpoint path="userErrorHandler" transformer-refs="ExceptionToString"/> </inbound> <outbound> <pass-through-router> <stdio:outbound-endpoint system="OUT"/> </pass-through-router> </outbound> </service> <!-- Handle any unexpected errors. Errors could also be routed elsewhere, e.g. into an error file, send via email to a list, stored in a database, etc. --> <service name="SystemErrorHandler"> <inbound> <vm:inbound-endpoint path="systemErrorHandler"/> </inbound> <outbound> <pass-through-router> <stdio:outbound-endpoint system="ERR"/> </pass-through-router> </outbound> </service> </model> </mule> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
|
|
|
Re: Mule Startup Issue
by Mike Carr-6
::
Rate this Message:
Tried below, same problem..
C:\mule-standalone-2.2.1\bin>mule -config file:.\conf\mule-config.xml 'xá-' is not recognized as an internal or external command, operable program or batch file. C:\mule-standalone-2.2.1\bin> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
|
|
|
|
|
|
Re: Mule Startup Issue
by Mike Carr-6
::
Rate this Message:
Thanks a bunch! Works now. The PATH env variable was corrupted in the control panel on XP.
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
