<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 8, 2013 at 5:57 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.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"><div class="im"><br>
<br>
----- Original Message -----<br>
| From: "Matthias Wessendorf" <<a href="mailto:matzew@apache.org">matzew@apache.org</a>><br>
| To: "AeroGear Developer Mailing List" <<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
</div><div class="im">| Sent: Monday, April 8, 2013 10:28:46 AM<br>
| Subject: Re: [aerogear-dev] [Aerogear Pipeline] Support for nested endpoints<br>
|<br>
</div><div class="im">| or, like before said - reading "lists" (e.g. all the comments for specific<br>
| blog post):<br>
| <a href="https://gist.github.com/matzew/04f069dfbed2cc77a8b4" target="_blank">https://gist.github.com/matzew/04f069dfbed2cc77a8b4</a><br>
|<br>
|<br>
| For Java.... I guess...... resolving this URL:<br>
| <a href="http://some.server.com/posts/1/comments" target="_blank">http://some.server.com/posts/1/comments</a><br>
|<br>
| could be done with this - right ?<br>
|<br>
| =======<br>
| Class Post:<br>
| - string: title;<br>
| - string: postContent;<br>
| - List<Comment> comments;<br>
| Class Comment:<br>
| - string username;<br>
| - string comment;<br>
|<br>
|<br>
| // get all the comments for 1:<br>
| Post myPostOne = postPipe.read("1");<br>
| myPostOne.getComments();<br>
|<br>
| // get all the comments for 2:<br>
| Post myPostTwo = postPipe.read("2");<br>
| myPostTwo.getComments();<br>
| =======<br>
<br>
</div>It can be done with that yes. My concern was more when we had a Pipe of type <Post> and a readForResource(String property) method. </blockquote><div><br></div><div style>Ok - one more question</div><div style>
<br></div><div style><br></div><div style>So... when doing: myPipe.read(1); does that "only" issue a GET against the '<span style="color:rgb(80,0,80)"> </span><a href="http://some.server.com/posts/1">http://some.server.com/posts/1</a>' resource?</div>
<div style><br></div><div style>A second get, for the comments collection is than issued when calling <span style="color:rgb(80,0,80)">myPostOne.getComments();? </span></div><div style><span style="color:rgb(80,0,80)">(GET against </span>'<span style="color:rgb(80,0,80)"> </span><a href="http://some.server.com/posts/1/comments'">http://some.server.com/posts/1/comments'</a>)? </div>
<div style><span style="color:rgb(80,0,80)"><br></span></div><div style><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">
The type information of the property isn't available unless we can infer it from the Post object.<br></blockquote><div><br></div><div><br></div><div style><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">
<div class=""><div class="h5"><br>
<br>
|<br>
|<br>
| Greetings,<br>
| Matthias<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| On Fri, Apr 5, 2013 at 2:37 PM, Matthias Wessendorf < <a href="mailto:matzew@apache.org">matzew@apache.org</a> ><br>
| wrote:<br>
|<br>
|<br>
|<br>
| Thought a bit more about it and chatted with friends,<br>
|<br>
| the issue with the sub pipes is: it adds state and is perhaps an API<br>
| construct that is a bit hard to understand (see all the discussions here)<br>
|<br>
| Not sure - but currently we can access "kid resources", with our API - right<br>
| ?<br>
|<br>
| <a href="https://gist.github.com/matzew/6ab432e437b9a017a21d" target="_blank">https://gist.github.com/matzew/6ab432e437b9a017a21d</a><br>
|<br>
|<br>
| Perhaps it's better to just keep it that way? This has the benefit of using<br>
| an established and know API, the different pipes are accessible via the<br>
| pipeline object;<br>
|<br>
| And the code is not too much code; it's simply an explicit pipe ...<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| On Fri, Apr 5, 2013 at 10:56 AM, Matthias Wessendorf < <a href="mailto:matzew@apache.org">matzew@apache.org</a> ><br>
| wrote:<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| On Fri, Apr 5, 2013 at 10:52 AM, Sebastien Blanc < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> ><br>
| wrote:<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| On Fri, Apr 5, 2013 at 10:36 AM, Matthias Wessendorf < <a href="mailto:matzew@apache.org">matzew@apache.org</a> ><br>
| wrote:<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| On Fri, Apr 5, 2013 at 10:14 AM, Christos Vasilakis < <a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a> ><br>
| wrote:<br>
|<br>
|<br>
|<br>
| Hi<br>
|<br>
| some comments<br>
|<br>
| I believe the method can't be used since you don't know the team for the<br>
| players so you can't retrieve the pipe directly..right?<br>
|<br>
| Isn't that really up to the impl of the rest service?<br>
| They could return a list of teamsHePlayed for;<br>
|<br>
| So, let's not tie this API to a specific, not existing RESTful service;<br>
|<br>
| +1, we don't need to care about that, we must just focus on how we can<br>
| declare and call nested pipes.<br>
|<br>
|<br>
|<br>
|<br>
| yep<br>
|<br>
| I guess this is perhaps the closest we can come to :<br>
|<br>
| id<AGPipe> allOwnersInNewYorkPipe = [leaguesPipe subPipe:@"owners"<br>
| for:@"newyork"];<br>
|<br>
| and than.... on the 'leaguesPipe' you can access its kids with something like<br>
| :<br>
|<br>
| NSArray* kids = [leaguesPipe subPipes];<br>
|<br>
|<br>
| However, that adds some state to a specific pipe object<br>
|<br>
|<br>
| -M<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
</div></div><div class="im">| getPlayers ( Callback < List < Player >> callback ) {<br>
| pipe . get ( "player" ). read ( callback );<br>
| }<br>
|<br>
</div><div class=""><div class="h5">| Further my questions is, how is a third (or arbitrary) nested resources are<br>
| supported? I mean for a url schema like this<br>
|<br>
| <a href="http://soccer.org/leagues/" target="_blank">soccer.org/leagues/</a> {id}/teams/{id}/players/{id}<br>
|<br>
| first we access the leagues:<br>
| ---<br>
| getLeagues(Callback<List<Leagues>> callback) {<br>
| pipe.get("leagues").read(callback);<br>
| }<br>
| ---<br>
| then the teams for this league:<br>
| ---<br>
| getTeamsOnLeaque(Leaque league, Callback<List<Team>> callback) {<br>
| pipe.junction("league","team").read(leaque, callback);<br>
| }<br>
| ---<br>
| ..and then we access the "Players" for a "Team":<br>
| ---<br>
| getPlayersOnTeam(Team team, Callback<List<Player>> callback) {<br>
| pipe.junction("team","player").read(team, callback);<br>
| }<br>
| ---<br>
| But where is the "League" information to fill the "/leagues/{id}..." path?<br>
|<br>
|<br>
| I'd assume the information is 'inherited' out of a given pipe, when doing the<br>
| 'join'<br>
|<br>
| e.g. like<br>
| myTeamsForLeaguePipe = leaguePipe.junction("team");<br>
|<br>
| not sure...<br>
|<br>
|<br>
|<br>
|<br>
| Unless you mean something like:<br>
| ---<br>
| getPlayersOnTeam(Leaque league, Team team, Callback<List<Player>> callback) {<br>
| pipe.junction("league", "team","player").read(league, team, callback);<br>
| }<br>
|<br>
| I am not sure if that is really easy to understand/use<br>
|<br>
| Yes and the term "junction" is a bit confusing as it don't express explicitly<br>
| a parent/child relation.<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
|<br>
| ---<br>
|<br>
| probably I am missing sth..<br>
|<br>
| Thanks,<br>
| Christos<br>
|<br>
| On Apr 4, 2013, at 5:52 PM, Summers Pittman < <a href="mailto:supittma@redhat.com">supittma@redhat.com</a> > wrote:<br>
|<br>
|<br>
|<br>
| What if we create a new metaphor, a Junction.<br>
|<br>
| <a href="https://gist.github.com/secondsun/dcf5682b6ff17c729d9a" target="_blank">https://gist.github.com/secondsun/dcf5682b6ff17c729d9a</a><br>
|<br>
| It joins two pipes together and can be used over and over again with<br>
| different data?<br>
| It isn't a Pipe though, but perhaps that could be changed to look more like<br>
| Christos's previous example.<br>
|<br>
| At the very least I like the words "junction" or "join" more than "of"<br>
|<br>
| ----- Original Message -----<br>
| | From: "Christos Vasilakis" < <a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a> ><br>
| | To: "AeroGear Developer Mailing List" < <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> ><br>
| | Sent: Wednesday, April 3, 2013 3:03:02 AM<br>
| | Subject: Re: [aerogear-dev] [Aerogear Pipeline] Support for nested<br>
| | endpoints<br>
| |<br>
| |<br>
| | On Apr 2, 2013, at 4:03 PM, Matthias Wessendorf < <a href="mailto:matzew@apache.org">matzew@apache.org</a> ><br>
| | wrote:<br>
| |<br>
| |<br>
| |<br>
| |<br>
| | Two thoughts....<br>
| |<br>
| | 1) the 'original' leaguesPipe has no clue about the subpipes, right ?<br>
| | 2) should a pipe offer a 'getter' for all it's sub pipes ?<br>
| |<br>
| |<br>
| | Just a thought is instead of using Pipe, to continue using Pipeline adding<br>
| | an<br>
| | extra parameter " of" for specifying the parent : E.g.:<br>
| |<br>
| | …..<br>
| | id<AGPipe> leaguesPipe = [pipeline pipe@"leagues"];<br>
| |<br>
| | id<AGPipe> allTeamsInSeattlePipe = [pipeline subPipe@"teams" of<br>
| | :leaguesPipe<br>
| | for:@"seattle"]<br>
| |<br>
| | id<AGPipe> allPlayersInTrebuchetPipe = [pipeline subPipe:@"players" of:<br>
| | allTeamsInSeattlePipe for:@"trebuchet"];<br>
| | …..<br>
| |<br>
| |<br>
| | Wdyt?<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| | -M<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| | Thanks,<br>
| | Christos<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| | <a href="http://soccer.org/leagues/seattle/teams/trebuchet/players/foo" target="_blank">soccer.org/leagues/seattle/teams/trebuchet/players/foo</a> - ><br>
| | [[pipeline pipe:@"players" pathParams:@[@"seattle", @"trebuchet"]] read<br>
| | :@"foo"] ..<br>
| | -----<br>
| |<br>
| |<br>
| | Wdyt?<br>
| |<br>
| | Thanks<br>
| | Christos<br>
| |<br>
| | On Mar 18, 2013, at 1:12 PM, Sebastien Blanc < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> > wrote:<br>
| |<br>
| |<br>
| |<br>
| | Well, that would not be possible, for that you will have to create a<br>
| | "child"<br>
| | pipe. But I agree, that is maybe no optimal ...<br>
| |<br>
| |<br>
| | On Fri, Mar 15, 2013 at 6:44 PM, Summers Pittman < <a href="mailto:supittma@redhat.com">supittma@redhat.com</a> ><br>
| | wrote:<br>
| |<br>
| |<br>
| |<br>
| | On 03/15/2013 01:34 PM, Sebastien Blanc wrote:<br>
| |<br>
| |<br>
| | I like the idea but I will more see that has a method/function for the<br>
| | pipelineManager (and will be easier to implement in JS, I think) :<br>
| |<br>
| | var myParentPipe = Aerogear.Pipeline({name:"parentPipe"}).pipes.parentPipe<br>
| |<br>
| | var myChildPipe = Aerogear.Pipeline.fromParent(myParentPipe, {options} )<br>
| | What would it look like to get a child record from a parent?<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| |<br>
| | On Fri, Mar 15, 2013 at 5:37 PM, Douglas Campos < <a href="mailto:qmx@qmx.me">qmx@qmx.me</a> > wrote:<br>
| |<br>
| |<br>
| | What about this?<br>
| |<br>
| | Pipeline<Post> postPipeline = …<br>
| | Post post = // get from the pipeline<br>
| | Pipeline<Comment><br>
| | postPipeline.childPipelineForOrOtherWeirdName(Comment.class, post)<br>
| |<br>
| |<br>
| | On 15/03/2013, at 12:26, Summers Pittman < <a href="mailto:supittma@redhat.com">supittma@redhat.com</a> > wrote:<br>
| |<br>
| | > On 03/14/2013 04:48 AM, Matthias Wessendorf wrote:<br>
| | >><br>
| | >><br>
| | >> On Thu, Mar 14, 2013 at 9:32 AM, Sebastien Blanc < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> ><br>
| | >> wrote:<br>
| | >> Hi,<br>
| | >> While I was playing with scaffolding and tried to build a simple Blog<br>
| | >> Application with Aerogear I faced the current situation :<br>
| | >> I have a Post object which contains many Comment objects. Now I want to<br>
| | >> call my Post pipe to retrieve the related comments, I have currently 2<br>
| | >> options :<br>
| | >><br>
| | >> /posts/1 -> assuming comments will be implicitly retrieved (eager<br>
| | >> loading)<br>
| | >> /comments/?postid=1<br>
| | >><br>
| | >> But regarding our model the correct form should be :<br>
| | >><br>
| | >> /posts/1/comments<br>
| | >><br>
| | >><br>
| | >> +1<br>
| | >> that is the ideal way to model URIs for "nested" resources.<br>
| | >><br>
| | >> See [1], extracted from [2]<br>
| | >><br>
| | >><br>
| | >><br>
| | >> But, AFAIK, with the current API, it is not possible to define this last<br>
| | >> pattern (at least for JS and iOs, confirmed by Matzew). When doing a<br>
| | >> read<br>
| | >> we can pass an id option but as mentioned in the doc, this id will<br>
| | >> always<br>
| | >> be append to the endpoint.<br>
| | >><br>
| | >><br>
| | >> Well, it is possible - but in a very (IMO) ugly way:<br>
| | >><br>
| | >> <a href="https://gist.github.com/matzew/6ab432e437b9a017a21d" target="_blank">https://gist.github.com/matzew/6ab432e437b9a017a21d</a><br>
| | >><br>
| | >><br>
| | >><br>
| | >><br>
| | >> IMO, we should be able to support this pattern but for now I'm not<br>
| | >> really<br>
| | >> sure how to specify this in our API, so if you have any ideas feedback<br>
| | >> this thread has been made for you !<br>
| | >><br>
| | >><br>
| | >><br>
| | >> Suggestion: Enhance the read function - example:<br>
| | >><br>
| | >> <a href="https://gist.github.com/matzew/04f069dfbed2cc77a8b4" target="_blank">https://gist.github.com/matzew/04f069dfbed2cc77a8b4</a><br>
| | > I'm thinking of the inverse myself. Add a "ParentPath" property which can<br>
| | > be used to extract information from parent objects.<br>
| | ><br>
| | > <a href="https://gist.github.com/secondsun/17ce96082eda37dbd10e" target="_blank">https://gist.github.com/secondsun/17ce96082eda37dbd10e</a><br>
| | ><br>
| | >><br>
| | >><br>
| | >> -Matthias<br>
| | >><br>
| | >><br>
| | >> [1]<br>
| | >> <a href="http://www.infoq.com/resource/articles/rest-introduction/en/resources/figure2.jpg" target="_blank">http://www.infoq.com/resource/articles/rest-introduction/en/resources/figure2.jpg</a><br>
| | >> [2] <a href="http://www.infoq.com/articles/rest-introduction" target="_blank">http://www.infoq.com/articles/rest-introduction</a><br>
| | >><br>
| | >><br>
| | >><br>
| | >><br>
| | >> Seb<br>
| | >><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><br>
| | >><br>
| | >><br>
| | >><br>
| | >> --<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><br>
| | >><br>
| | >> _______________________________________________<br>
| | >> aerogear-dev mailing list<br>
| | >><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><br>
| |<br>
| | -- qmx<br>
| |<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><br>
| |<br>
| |<br>
| |<br>
| | _______________________________________________<br>
| | aerogear-dev mailing list <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>
| | _______________________________________________<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><br>
| |<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><br>
| |<br>
| |<br>
| |<br>
| | --<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><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>
| | _______________________________________________<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>
| |<br>
| | --<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><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>
| | _______________________________________________<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><br>
|<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><br>
|<br>
|<br>
|<br>
| --<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><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><br>
|<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><br>
|<br>
|<br>
|<br>
| --<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><br>
|<br>
|<br>
|<br>
| --<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><br>
|<br>
|<br>
|<br>
| --<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><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><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>