soap command line argument not working

I downloaded the latest jar release the other day and attempted to run graphwalker as a service using the following command line:

java -jar graphwalker-2.6.3-SNAPSHOT.jar soap -f Test.xml

It appears to start and even displays the WSDL path followed by "Press Ctrl+C to quit", but this is followed by the command prompt. The service either never started or starts and immediately quits. The older version of the graphwalker jar that we're using (sorry I don't remember the version) still works.

[KristianKarl-zz]

Very interesting. I'll start checking this. What version of java are you
using?
On 29 Oct 2013 16:19, "SKAhster" notifications@github.com wrote:

I downloaded the latest jar release the other day and attempted to run
graphwalker as a service using the following command line:

java -jar graphwalker-2.6.3-SNAPSHOT.jar soap -f Test.xml

It appears to start and even displays the WSDL path followed by "Press
Ctrl+C to quit", but this is followed by the command prompt. The service
either never started or starts and immediately quits. The older version of
the graphwalker jar that we're using (sorry I don't remember the version)
still works.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11
.

Java version is 7.0.250. By the way, the version of graphwalker I'm using that works is 2.5.17.

[maikeru]

Looks like this broke at 2dca75f
Rolling back to the previous commit fixes the problem. I guess the desired behaviour is to have the CLI thread wait for CTRL-C before shutting down the SOAP endpoint but I'm not sure how best to achieve that.

I've been doing some reading and I would expect that either the original implementation would be fine or we would need to add some kind of signal handler and call endpoint.stop() in that.

[KristianKarl-zz]

Okay, so let's roll back until a better solution is at hand.
Thanx for the investigation Michael

On Tue, Nov 26, 2013 at 2:26 PM, P. Michael Holland <
notifications@github.com> wrote:

Looks like this broke at 2dca75fhttps://github.com/KristianKarl/GraphWalker/commit/2dca75f5a16810954d4fe0e0c2af8fd2216753c6
Rolling back to the previous commit fixes the problem. I guess the desired
behaviour is to have the CLI thread wait for CTRL-C before shutting down
the SOAP endpoint but I'm not sure how best to achieve that.

I've been doing some reading and I would expect that either the original
implementation would be fine or we would need to add some kind of signal
handler and call endpoint.stop() in that.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-29291638
.

[maikeru]

Glad I could help!

[KristianKarl-zz]

Kristian Karl sent you an invitation

Twitter helps you stay connected with what's happening right now and with the people and organizations you care about.

Accept invitation

https://twitter.com/i/d0fcc3e2-fd37-44f3-96dc-2b904678c66e

You can unsubscribe from receiving email notifications from Twitter at anytime. For general inquiries, please visit us at Twitter Support.
Unsubscribe: https://twitter.com/i/o?t=1&iid=ffd058b3b0e04369a0e6a486749310fd&uid=0&c=IuVwbCB3dgEHbZkRTeKppC8yDpEtP1KWH8ujitC09pOcBCKHQB2NuQl9OPMaHLIDOhS2ETlWaEN8Zf4iGlOkZHNI8Q4ECuA7h8gV%2Fn3bAQEn3Yq9n%2BF0JA%3D%3D&nid=9+26

Need help?
https://support.twitter.com