example-web is not reachable via browser

[jangalinski]

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

[ghost]

Hi Jan,

If I remember correctly from the hackdays, the engine-rest is deployed
as root app, so /default or just /process-definition should work
(without /engine).

Cheers,
Christian

On 08.09.15 17:58, Jan Galinski wrote:

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

—
Reply to this email directly or view it on GitHub
#20.

[jangalinski]

OK, will give it a try. Few questions though:

• why is the path with "engine" correctly resolved in the ITest? What is different when the SpringRunner starts the application?
• If my spring-boot-process-app serves forms or exposes other api via REST, shouldn't we have a clear separation of paths?
• Where and how can I configure this? I just found the RestConfiguration and it seems to be "magic".
• Wouldn't it be great to have this in the docs (both starter-docs and example readme? (don't get me wrong: I can take over documenting this (when I understood how it works).

[ghost]

I need to dig into it too. There seems to be also an issue when building
the example-web that you need both, RestEasy and Jersey bundled. This
causes all kind of strange errors. Daniel had the problem on the
hackdays, but I did not reproduce it yet.

On 09.09.15 10:58, Jan Galinski wrote:

OK, will give it a try. Few questions though:

• why is the path with "engine" correctly resolved in the ITest?
  What is different when the SpringRunner starts the application?
• If my spring-boot-process-app serves forms or exposes other api
  via REST, shouldn't we have a clear separation of paths?
• Where and how can I configure this? I just found the
  RestConfiguration and it seems to be "magic".
• Wouldn't it be great to have this in the docs (both starter-docs
  and example readme? (don't get me wrong: I can take over
  documenting this (when I understood how it works).

—
Reply to this email directly or view it on GitHub
#20 (comment).

[jangalinski]

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?

[ghost]

+1

On 09.09.15 11:23, 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?

—
Reply to this email directly or view it on GitHub
#20 (comment).

[jangalinski]

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).

[osteinhauer]

I am in vacation, so I am just happy to get some mails...test it latest when I am back

Am 10.09.2015 um 20:30 schrieb Jan Galinski notifications@github.com:

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).

—
Reply to this email directly or view it on GitHub.

[osteinhauer]

By the way...are you starting deploying in a tomcat or just a java run?

Am 10.09.2015 um 20:30 schrieb Jan Galinski notifications@github.com:

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).

—
Reply to this email directly or view it on GitHub.

[jangalinski]

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!

[ghost]

I'm gonna work on the Extension in the next few days to make it ready for
the community day.

Gesendet mit AquaMail für Android
http://www.aqua-mail.com

Am 10. September 2015 20:46:21 schrieb Jan Galinski notifications@github.com:

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!

---

Reply to this email directly or view it on GitHub:
#20 (comment)

[osteinhauer]

tested with:

• "run as" inside IDE (eclipse)
• java -jar target/camunda-bpm-spring-boot-starter-example-web-1.1.0-SNAPSHOT.jar

http://localhost:8080/rest/engine/default/process-definition is reachable (user: user, password: password).

[jangalinski]

yes, thanks for confirming, this was fixed during #22 when we removed resteasy and made a view changes to the Jersey config.