Yes, exactly! Though I suppose if they are using RestEasy they will have this functionality by default, as you suggest. I wasn't thinking clearly when I wrote this, however. You are very correct. If RestEasy is already on the classpath, it should probably provide injection for web-service endpoints (via @Qualifer) annotations. <br>
<br>@Inject @RestEndpoint<br>private Endpoint<DataService> endpoint;<br><br>The endpoint could then provide access to things like the HttpClient, the Request object, methods to invoke:<br><br>endpoint.sendRequest();<br>
endpoint.getResponse();<br><br>And would take care of the bootstrap / typing / (un)marshalling, etc...<br><br>Pretty much a super-quick way of specifying a web-service endpoint and invoking it via RestEasy Client Framework (under the covers of course)<br>
If there's an easier way, then this wouldn't be needed, but that's my thought!<br><br>--Lincoln<br><br><div class="gmail_quote">On Fri, Oct 29, 2010 at 4:09 AM, Jozef Hartinger <span dir="ltr"><<a href="mailto:jharting@redhat.com">jharting@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Do you mean making a fork of the client framework in seam-rest or providing an integration with it (available when RESTEasy is on classpath)? I'll add it to the project ideas page.<div class="im">
<br>
<br>
On 10/27/2010 04:06 PM, Lincoln Baxter, III wrote:<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
Excellent! I think that's a good call, and will help people adopt!<br>
<br>
Have we considered moving the RestEast Client Framework into Seam<br>
RestEasy, or at least pulling it in if we are not already? That might be<br>
another sweet feature to help wet people's appetite.<br>
<br>
Since we're no longer directly targeting RESTEasy, having a client<br>
consumer framework available to them would no longer be a "standard,"<br>
but it certainly would be nice.<br>
<br>
I think we should consider this if not already done.<br>
--Lincoln<br>
<br>
On Wed, Oct 27, 2010 at 6:29 AM, Pete Muir <<a href="mailto:pmuir@bleepbleep.org.uk" target="_blank">pmuir@bleepbleep.org.uk</a><br></div><div class="im">
<mailto:<a href="mailto:pmuir@bleepbleep.org.uk" target="_blank">pmuir@bleepbleep.org.uk</a>>> wrote:<br>
<br>
Jozef has decided to target this module at the JAX-RS standard only,<br>
therefore the module name has changed slightly. We renamed the repo<br>
on github accordingly.<br>
_______________________________________________<br>
seam-dev mailing list<br></div>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a> <mailto:<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a>><div class="im"><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
<br>
<br>
<br>
--<br>
Lincoln Baxter, III<br>
<a href="http://ocpsoft.com" target="_blank">http://ocpsoft.com</a><br>
<a href="http://scrumshark.com" target="_blank">http://scrumshark.com</a><br>
"Keep it Simple"<br>
<br>
<br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></blockquote>
</blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>