-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
example-web is not reachable via browser #20
Comments
Hi Jan, If I remember correctly from the hackdays, the engine-rest is deployed Cheers, On 08.09.15 17:58, Jan Galinski wrote:
|
OK, will give it a try. Few questions though:
|
I need to dig into it too. There seems to be also an issue when building On 09.09.15 10:58, Jan Galinski wrote:
|
OK, thanks. Do we agree that solving this (= having an easy, clean and well documented way of activating camundas REST API) is a crucial milestone for the first release? |
+1 On 09.09.15 11:23, Jan Galinski wrote:
|
Could you please start the example-web application and try to reach it via Browser? I tried all possible combinations I could think of, but all I get is 404. I guess the example is broken (in a way that there is something in the test scope that lets it work). |
I am in vacation, so I am just happy to get some mails...test it latest when I am back
|
By the way...are you starting deploying in a tomcat or just a java run?
|
I just click „run as java application“ on the Application class inside the IDE. Enjoy your vacation, this can wait! |
I'm gonna work on the Extension in the next few days to make it ready for Gesendet mit AquaMail für Android Am 10. September 2015 20:46:21 schrieb Jan Galinski notifications@github.com:
|
tested with:
http://localhost:8080/rest/engine/default/process-definition is reachable (user: user, password: password). |
yes, thanks for confirming, this was fixed during #22 when we removed resteasy and made a view changes to the Jersey config. |
The ITest works, but when I start the application itself and open http://localhost:8080/engine/default/process-definition I get a 404. Is there something wrong with the starter or am I missing something? I did do any configuration, just started the Application
The text was updated successfully, but these errors were encountered: