[#MULE-2907] confusing message when starting the examples

Details

Type: Improvement
Status: Closed
Priority: Trivial
Resolution: Fixed
Affects Version/s: 2.0.0-RC1
Fix Version/s: 2.0.0-RC3
Component/s: Examples / Tutorials
Labels:
None

User impact:
Low
Similar Issues:
MULE-5629 JDBC connector and endpoint confusion when the queryKey property starts with the string "select"
~~MULE-2635~~ Loanbroker example fails to start
~~MULE-5331~~ Starting a stopped Async service results in the service NOT consuming any messages
MULE-2773 MuleServer has confusing internals (hard to debug/fix)
~~MULE-3061~~ Slighlty confusing message in sendDirect()
~~MULE-6023~~ Flow should be ready to process messages as soon as the message processors are started
~~MULE-4589~~ java.lang.IllegalStateException: Phase 'start' has already been executed
~~MULE-526~~ Connecters route messages to components before components have started
~~MULE-4150~~ Mule stops sending JMS messages when large number of messages are queued up
~~MULE-5233~~ CLONE - java.lang.IllegalStateException: Phase 'start' has already been executed

Description

When I ran examples\echo\echo.bat, I got the following message and I was confused.

> Usage: "e:\mule-2.0.0-RC1\bin\mule.bat" { console : start : pause : resume : stop : restart : install : remove }
> No command specified, running in console/foreground mode by default, use Ctrl-C to exit...

If it's not intentional, could you fix this?
I don't make sure, but I guess other examples have same problem.

More Options
- Sort By Name
- Sort By Date
- Ascending
- Descending

Attachments

patch

17/Jan/08 03:02 AM

1 kB

Yuji Yamano

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Yuji Yamano added a comment - 17/Jan/08 03:02 AM

This is the patch for examples/echo.

Show

Yuji Yamano added a comment - 17/Jan/08 03:02 AM This is the patch for examples/echo.

Hide

Permalink

Dirk Olmes added a comment - 17/Jan/08 03:56 AM

Unfortunately the message is a "feature" of the wrapper and the way we use it.

While your patch would make the message go away for regular usage in the console I'm not sure how the wrapper behaves if mule.sh is started as a Unix service (i.e. doesn't even have a virtual console attached).

I'm tending to close this as "Won't fix" but leave this issue open for now for others to correct me if I'm wrong.

Show

Dirk Olmes added a comment - 17/Jan/08 03:56 AM Unfortunately the message is a "feature" of the wrapper and the way we use it. While your patch would make the message go away for regular usage in the console I'm not sure how the wrapper behaves if mule.sh is started as a Unix service (i.e. doesn't even have a virtual console attached). I'm tending to close this as "Won't fix" but leave this issue open for now for others to correct me if I'm wrong.

Hide

Permalink

Holger Hoffstaette added a comment - 17/Jan/08 04:03 AM

I always found the nmessage very confusing too. NO other command prints its usage when it will happily continue to work anyway! I agree that using the wrapper this way is a separate case, but I don't understand why the usage can be shown only when -h or --help is given as argument?

Show

Holger Hoffstaette added a comment - 17/Jan/08 04:03 AM I always found the nmessage very confusing too. NO other command prints its usage when it will happily continue to work anyway! I agree that using the wrapper this way is a separate case, but I don't understand why the usage can be shown only when -h or --help is given as argument?

Hide

Permalink

Travis Carlson added a comment - 21/Jan/08 11:45 AM

I had it display the usage message when I implemented the service wrapper as a way of "advising" users that they now had more options available to them (previously Mule just ran in the foreground). But I see your point, and we do document usage in the README.txt, so I will remove this message now.

Show

Travis Carlson added a comment - 21/Jan/08 11:45 AM I had it display the usage message when I implemented the service wrapper as a way of "advising" users that they now had more options available to them (previously Mule just ran in the foreground). But I see your point, and we do document usage in the README.txt, so I will remove this message now.

Hide

Permalink

Andrew Perepelytsya added a comment - 21/Jan/08 11:46 AM

Travis, I wouldn't be so sure. E.g. I and many people never referred to readme file for available options only because they were readily available in the startup message.

Show

Andrew Perepelytsya added a comment - 21/Jan/08 11:46 AM Travis, I wouldn't be so sure. E.g. I and many people never referred to readme file for available options only because they were readily available in the startup message.

Hide

Permalink

Holger Hoffstaette added a comment - 21/Jan/08 11:53 AM

Solution: -h / --help flag.

Show

Holger Hoffstaette added a comment - 21/Jan/08 11:53 AM Solution: -h / --help flag.

Hide

Permalink

Dirk Olmes added a comment - 29/Feb/08 04:51 AM

I have removed the confusing message now. The mule start script now only prints out that it runs in the foreground.

http://fisheye.codehaus.org/changelog/mule/?cs=11123

Show

Dirk Olmes added a comment - 29/Feb/08 04:51 AM I have removed the confusing message now. The mule start script now only prints out that it runs in the foreground. http://fisheye.codehaus.org/changelog/mule/?cs=11123

Hide

Permalink

Dirk Olmes added a comment - 29/Feb/08 05:55 AM

Oops, the previous fix was for Unix only. Windows: http://fisheye.codehaus.org/changelog/mule/?cs=11124

Show

Dirk Olmes added a comment - 29/Feb/08 05:55 AM Oops, the previous fix was for Unix only. Windows: http://fisheye.codehaus.org/changelog/mule/?cs=11124

People

Assignee:

Dirk Olmes

Reporter:

Yuji Yamano

Vote (0)

Watch (0)

Dates

Created:

17/Jan/08 03:01 AM

Updated:

29/Feb/08 05:55 AM

Resolved:

29/Feb/08 04:51 AM