Hi All
On Tue, Dec 20, 2016 at 9:48 PM, Frank Leymann wrote:
> If an API Resource or endpoint is nothing stand-alone, i.e. if it needs an
> API Definition and can't live without it, it should be nested under API
> Definition. Thus, "+1!
>
> Furthermore, I took a look at [1]. In line 167, a HEA
If an API Resource or endpoint is nothing stand-alone, i.e. if it needs an
API Definition and can't live without it, it should be nested under API
Definition. Thus, "+1!
Furthermore, I took a look at [1]. In line 167, a HEAD method is defined.
A HEAD on a certain URI returns the very same than a
This is how you access propertise in the 'templateFillingObject' (e.g.
{name: "Saman", age: 10})
In the Handlebars template,
{{@params.name}}
Inside the 'onRequest(env)' function (serverside)
env.params.name
With that in mind, I think your requirement can be done. Refer following
example.
Le
Hi Sajith,
This will be very useful since currently a fragment can be invoked only
from a page or another fragment. Need to know what will happen if we
implemented to get the JSON object (which will be used to fill the
fragment's template) by calling an OSGI service, in the onRequest() method
of t
