<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 9, 2014 at 6:04 PM, Sébastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Another option could be :<br>
- no change or addition of any endpoint<br>
-no change on the angular side<br>
<br>
Since the result is the same : we want a list of applications (for admin there is just no restriction on developer that owns it)<br>
But in the service layer when retrieving the applications we check the role (do we have a method hasRole(string) ? ) to see if we add the criteria of developer.<br></blockquote><div><br></div><div>yeah, that;s what I had in my email from last night as well. the service returns a list of applications.</div><div>Inside we handle the different cases:</div><div>- admin</div><div> Select all (e.g. "select pa from PushApplication pa")</div><div>-developer</div><div> select 'my apps' (e.g. "select pa from PushApplication pa where pa.developer = :loginName")</div><div><br></div><div><br></div><div>-Matthias</div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Envoyé de mon iPhone<br>
<br>
> Le 9 oct. 2014 à 17:45, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>> a écrit :<br>
<div class=""><div class="h5">><br>
> Good morning, moving forward with<br>
> <a href="https://issues.jboss.org/browse/AGPUSH-1036" target="_blank">https://issues.jboss.org/browse/AGPUSH-1036</a>. What is the most<br>
> recommended approach for admin-ui.<br>
><br>
> Have separated endpoints for the admin like:<br>
><br>
> 1.<br>
><br>
> @RolesAllowed("admin")<br>
> @Path("/admin/applications")<br>
> public class AdminApplicationEndpoint extends AbstractBaseEndpoint {<br>
><br>
> @GET<br>
> @Produces(MediaType.APPLICATION_JSON)<br>
> public Response listAllPushApplications(){<br>
> //queries<br>
> }<br>
> }<br>
><br>
> Or introduce a new method inside the current PushApplicationEndpoint:<br>
><br>
> 2.<br>
><br>
> @GET<br>
> @Produces(MediaType.APPLICATION_JSON)<br>
> @RolesAllowed("admin")<br>
> public Response listAllPushApplications(){<br>
> //queries<br>
> }<br>
> // READ<br>
> @GET<br>
> @Produces(MediaType.APPLICATION_JSON)<br>
> public Response listAllPushApplicationsByUsername(@Context HttpServletRequest request) {<br>
> return Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();<br>
> }<br>
><br>
><br>
> If the option 2 is the correct. How the Angular.js service would look<br>
> like? Once the username is not informed as argument on<br>
> pushApplicationService.js, because for obvious reasons it can be<br>
> retrieved with HttpServletRequest.<br>
><br>
> One of my poor ideas due to my "amazing" Angular skills would be to do<br>
> something like:<br>
><br>
> @GET<br>
> @Produces(MediaType.APPLICATION_JSON)<br>
> @RolesAllowed("admin")<br>
> @Path("/all")<br>
> public Response listAllPushApplications(){<br>
> //queries<br>
> }<br>
><br>
> And:<br>
><br>
> backendMod.factory('pushApplication', function ($resource) {<br>
> return $resource('rest/applications/all/:verb', {<br>
> .....<br>
><br>
><br>
> Help?<br>
><br>
><br>
><br>
><br>
><br>
><br>
> --<br>
><br>
> abstractj<br>
> PGP: 0x84DC9914<br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>