<div>Maybe allow our users to programatically specify it, but is not high priority now, I just asked to know.
</div><div><br></div><div>Let's think about it later and move forward/stabilise the integration with Resteasy before.</div>
<div><div><br></div><div>Great work Daniel!</div><div><br></div><div><div>-- </div><div>"The measure of a man is what he does with power" - Plato</div><div>-</div><div>@abstractj</div><div>-</div><div>Volenti Nihil Difficile</div></div></div>
<p style="color: #A0A0A8;">On Monday, October 22, 2012 at 11:25 AM, Daniel Bevenius wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><blockquote type="cite"><div>Do you have something in mind for HTTP responses?</div></blockquote><div>At the moment, the only support for responses is taking what is</div><div>returned from the target method, and depending on what the value of</div><div>'produces' is and what the client requested, that type will be</div><div>returned.</div><div>This is what one of the RESTful routes looks like in aerogear-controller-demo:</div><div>route()</div><div> .from("/hello2")</div><div> .consumes("*/*")</div><div> .on(RequestMethod.GET)</div><div> .produces("application/json")</div><div> .to(HelloRest.class).hello(queryParam(String.class,</div><div>"firstname"), queryParam(String.class, "lastname"));</div><div><br></div><div>So, this produces a JSON response and RestEasy will to this mapping:</div><div>curl -i "<a href="http://localhost:8080/aerogear-controller-demo/hello2?firstname=Daniel&lastname=Bevenius">http://localhost:8080/aerogear-controller-demo/hello2?firstname=Daniel&lastname=Bevenius</a>"</div><div>HTTP/1.1 200 OK</div><div>Server: Apache-Coyote/1.1</div><div>Content-Type: application/json</div><div>Transfer-Encoding: chunked</div><div>Date: Mon, 22 Oct 2012 13:19:15 GMT</div><div><br></div><div>{"msg":"Hello Daniel Bevenius"}</div><div><br></div><div>We can certainly add other things and if you let me know what you'd</div><div>like to see I'll take a stab at it.</div><div>Perhaps we could have something like this:</div><div>route()</div><div> .from("/hello2")</div><div> .consumes("*/*")</div><div> .on(RequestMethod.GET)</div><div> .produces("application/json")</div><div> .response(statusCodeMethodName(msg))</div><div> .to(HelloRest.class).hello(queryParam(String.class,</div><div>"firstname"), queryParam(String.class, "lastname"));</div><div><br></div><div>What do you think?</div><div><br></div><div><br></div><div><br></div><div>On 22 October 2012 15:06, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>> wrote:</div><blockquote type="cite"><div><div>Awesome Daniel,</div><div><br></div><div>Do you have something in mind for HTTP responses?</div><div><br></div><div><br></div><div>--</div><div>"The measure of a man is what he does with power" - Plato</div><div>-</div><div>@abstractj</div><div>-</div><div>Volenti Nihil Difficile</div><div><br></div><div>On Friday, October 19, 2012 at 9:24 AM, Daniel Bevenius wrote:</div><div><br></div><div>Hi everyone,</div><div><br></div><div>I've updated the section "Programmatic endpoint configuration in</div><div>RestEasy" in the gist (<a href="https://gist.github.com/3871798">https://gist.github.com/3871798</a>) with progress</div><div>made the last few days. Hopefully this will explain how the current</div><div>configuration works and what options it supports.</div><div><br></div><div>If this looks alright, I'll shift focus back to aerogear-controller,</div><div>and look into adding support for things like query/form/header</div><div>parameters etc. This will enable us to update aerogear-controller demo</div><div>with more examples and that way get a better feel for how using the</div><div>programmatic configuration works in real life as opposed to tests.</div><div><br></div><div>cheers,</div><div><br></div><div>/Dan</div><div>_______________________________________________</div><div>aerogear-dev mailing list</div><div><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div><div><br></div><div><br></div><div><br></div><div>_______________________________________________</div><div>aerogear-dev mailing list</div><div><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote><div>_______________________________________________</div><div>aerogear-dev mailing list</div><div><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>