[
https://issues.apache.org/jira/browse/CAMEL-21110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875872#comment-17875872
]
Bruno Meseguer commented on CAMEL-21110:
----------------------------------------
I've added sample files to use and try out:
* server.xml (Server side Camel routes)
* index.html (Home page)
* style.css (style for HTML)
The dynamic HTML page simulates a chat conversation and sends data to Camel,
and Camel responds.
The idea would be to come up with some simple approach where you could run
something similar to:
{code:java}
camel run *{code}
and the user can open the browser and display the page with:
{code:java}
http://localhost:8080 {code}
As a workaround the samples include a Camel route that serves the HTML
resources to simulate the desired behaviour.
> camel-jbang - Make it easy to service HTML/JS pages
> ---------------------------------------------------
>
> Key: CAMEL-21110
> URL: https://issues.apache.org/jira/browse/CAMEL-21110
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.8.0
>
> Attachments: index.html, server.xml, style.css
>
>
> Lets make it easy to have some camel routes and html/js/png files so you can
> have a web front page and let Camel automatic service this via its embedded
> http server (platform-http).
> And then when export to Q/SB then these files should be in src/main/resources
> (and whatever folder they may have for html stuff).
> And the files should not be cached so you can update and reload the webpage
> for updates.
> This makes it easier to build prototypes with camel and web apps.
> Its just for serving those files, not for a template library like thymaleaf
> or qute etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
