That makes sense. It also helps me to better understand the other
components I was looking at to see how they handled it. There is a
definite learning curve here, but things seem to generally be fairly
straightforward to implement after a few pointers. So, kudos to you and
the other committers a
You extract these parts of the remainder part in the component where
you then set those parameters on the endpoint via their setters
The @uripath are for documentation / tooling etc.
On Sun, Jan 16, 2022 at 4:04 PM Steve973 wrote:
>
> Thank you! Is there a way to distinguish a literal string f
Thank you! Is there a way to distinguish a literal string from the name of
a parameter? Or does it only "link" to a parameter if that parameter
exists?
On Sun, Jan 16, 2022 at 9:47 AM Claus Ibsen wrote:
> Hi
>
> You can use @UriPath for context-path parameters.
>
> The name should match the na
Hi
You can use @UriPath for context-path parameters.
The name should match the name you specify in the syntax attribute on
UriEndpoint
On Sun, Jan 16, 2022 at 2:19 PM Steve973 wrote:
>
> Hello. If I want my component's endpoint URI to look something like this:
>
> my-component://{name}/{action
Hello. If I want my component's endpoint URI to look something like this:
my-component://{name}/{action}
How do I specify this? I can create multiple properties annotated
with @UriParam, but they will need to be used together, and in the right
order. I understand how to do this with libraries
