[aerogear-dev] Scaffolding questions

[Sebastien Blanc]

Righ, Paging bits will also be scaffolded in the near future !

On Tue, Apr 2, 2013 at 3:50 PM, Kris Borchers <kris at redhat.com> wrote:

>
> On Apr 2, 2013, at 8:45 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>
>
>
>
> On Tue, Apr 2, 2013 at 3:41 PM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>
>>
>>
>> On Tue, Apr 2, 2013 at 3:30 PM, Matthias Wessendorf <matzew at apache.org>wrote:
>>
>>> Howdy,
>>>
>>> I really like the work on AG Scaffolding!
>>>
>>>
>>> A few questions:
>>>
>>> 1) Is this available on an 'official' page ?
>>> https://gist.github.com/sebastienblanc/5222680
>>>
>>
>> Not yet, I think we must find a place for it on aerogear.org,
>> suggestions alre welcome !
>>
>>
>>>
>>> 2) The generated JS controllers are Angular 'controllers' that use
>>> AeroGear for HTTP communication ?
>>>
>>
>> Amgular's controllers uses the Aerogear generated DataService JS file
>> (which contains/defines  the pipes/datastore)
>>
>
> so, basically yes :)
>
>
>
>>
>>>
>>> 3) The generated Java/REST Endpoints are vanilla JAX-RS endpoints, but
>>> the AG Controller (Routes) does the actual
>>> HTTP routing, not the JAX-RS impl. right ?
>>>
>>
>> Right, the "ag controller" scaffolding branch scaffolds a Controller
>> Route and "by pass" the JAX-RS endpoints generated by the REST forge
>> plugin.
>>
>
> ... by leveraging the JAX-RS Response class, for instance ?
>
>
>
>>
>>> So... if 3) the above is right....
>>>
>>> 3a)  is it basically a dispatch ?
>>>
>>
>> It's AG Controller magic, just drop the jar and defines a route, any
>> matches will use the Route defined in the controller.
>>
>
> ok - you anwsered above. Under the hood, it does a by-pass
>
>
>>
>>
>>> 3b) what is the benefit of using the Controler/Routes in this example.
>>>
>>
>> * Show the basic use of the Controller / Promote our own stuff
>> * IMO Controller has a fluent API which make it really a breeze to define
>> REST endpoints,
>> * When Security scaffold will be released (soon ! soon!) ,it will be easy
>> to integrate into the Routes and again show the power of the controller.
>> * In the future, show how we can easily connect to other services (Dan's
>> Camel samples)
>>
>
> +1 all valid point
>
>
> Also, it makes it easy to paginate the endpoints, right? Eventually this
> will be part of scaffolding but it was a couple of simple changes for me to
> add pagination to the scaffolded code.
>
>
>
> Yes, looks good !
>
>
>>
>>
>>>
>>>
>>> Thanks
>>>
>>
>> Thanks for the feedback
>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130402/c13afaa3/attachment.html