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 <steve...@gmail.com> wrote:
>
> 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 <claus.ib...@gmail.com> wrote:
>
> > 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 <steve...@gmail.com> wrote:
> > >
> > > Hello. If I want my component's endpoint URI to look something like
> > this:
> > >
> > > my-component://{name}/{action}<?optional params>
> > >
> > > 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 like Spring Web, but
> > it
> > > is not clear to me how to "compose" the URI this way for the Endpoint.
> > >
> > > Is this merely a matter of parsing, so that the business logic only looks
> > > for "action" in the context of processing things for "name"? Or is there
> > > something more formal? Please pardon my ignorance.
> > >
> > > Thanks,
> > > Steve
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
