Hi Daniel,
I think a better idea would be to provide a service that could be consumed by UICommands
that could consume REST services.
One idea is to place this in the addon-manager addon for now (keeping it simple) and we
can refactor it out later.
Another idea (that I like it better) is to add dependencies to the JAX-RS 2.0 Client API
through the javaee addon. That would allow addons to consume REST services using the
standard JAX-RS classes.
Thoughts?
Em 18/05/2014, às 09:21, Daniel Cunha <danielsoro(a)gmail.com>
escreveu:
Morning,
I thought create a new addon: rest-consumer. I'll use this addon to consume any
endpoints. With this addon I can resolve this issue and when we need to consume other
endpoints we can use this addon. WDYT?
Att;
Daniel Cunha (soro)
Sent from my cell phone.
> On May 17, 2014 11:34 PM, "Daniel Cunha" <danielsoro(a)gmail.com>
wrote:
> George,
>
> thanks. :)
>
>
>> On Sat, May 17, 2014 at 11:08 PM, George Gastaldi <ggastald(a)redhat.com>
wrote:
>> There isn't a model class in forge/core, only in forge/website (Addon class).
>> You can use the parser-json addon to read the contents.
>>
>>> Em 17/05/2014, às 22:59, Daniel Cunha <danielsoro(a)gmail.com>
escreveu:
>>>
>>
>>> Hi folks,
>>>
>>> I can't identify this object in forge, I searched but I don't found.
[
http://website-forge.rhcloud.com/rest/addons/org.jboss.forge.addon:jira]
>>>
>>> What model it's that?
>>> I need create it?
>>>
>>> --
>>> Att;
>>> Daniel Cunha (soro)
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
> --
> Att;
> Daniel Cunha (soro)
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev