RE: Integrating WADL and Spring

2009-03-09 Thread Jerome Louvel
Hi all,

This is a good idea indeed. I've made a first step by updating
WadlApplication to make it easy to customize the way resources are created
based on the WADL resource descriptor, as suggested by Rhett.

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


-Message d'origine-
De : Rhett Sutphin [mailto:rh...@detailedbalance.net] 
Envoyé : dimanche 8 mars 2009 03:07
À : discuss@restlet.tigris.org
Objet : Re: Integrating WADL and Spring

Hi David,

On Mar 6, 2009, at 4:10 PM, David Bordoley wrote:

 On Fri, Mar 6, 2009 at 11:32 AM, Rhett Sutphin 
 rh...@detailedbalance.net wrote:

 This would be an RFE (at least, I'm not aware of any way to get it to 
 work currently).  I'm curious about how you would tie the resources 
 in your application context to the WADL.  Would you add a custom 
 attribute for the spring bean id?  Is there a WADL feature which 
 would help with this?  I'm not that familiar with it.

 Rhett

 Hi,

 The current way WADL works in Restlet is to require implementors to 
 specify the class of the resource you want to map a WADL resource to 
 using the resource's id attribute. You then pass the the WADL xml as a 
 constructor argument to a WadlComponent or WadlApplication. You can 
 see an example of this in org.restlet.test.YahooSearch.wadl (omitting 
 the details in the example below):

 application
  resources base=http://api.search.yahoo.com/NewsSearchService/V1/;
resource id=org.restlet.test.NewsSearchResource  
 path=newsSearch
/resource
  /resources
 /application

 It would be cool if you could do something similar but instead of 
 passing a Resource class (and be stuck using the default constructor 
 etc.), instead use a Spring Bean id as the resource id in WADL, and 
 have restlet use spring to wire all the resources together, thus 
 getting all the benefits of IOC, while also being able to more 
 explicitly state your resource interface in a standard method.

 Anyway i can open an RFE if necessary, but I wanted to ask on the list 
 first.

This is a good idea.  I think the implementation might be more generic than
just spring support, so I went ahead and entered the RFE against the WADL
component:  http://restlet.tigris.org/issues/show_bug.cgi?id=756

Thanks,
Rhett

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=12864
20

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1297634


Re: Integrating WADL and Spring

2009-03-09 Thread David Bordoley
It would be nice if you could allow more fine grain configuration
support via WADL, including adding Guards to resources, configuring
what methods and variants a resource supports via WADL etc. I added
some technical suggestions in the bug itself.

dave

On Mon, Mar 9, 2009 at 10:02 AM, Jerome Louvel
jerome.lou...@noelios.com wrote:
 Hi all,

 This is a good idea indeed. I've made a first step by updating
 WadlApplication to make it easy to customize the way resources are created
 based on the WADL resource descriptor, as suggested by Rhett.

 Best regards,
 Jerome Louvel
 --
 Restlet ~ Founder and Lead developer ~ http://www.restlet.org
 Noelios Technologies ~ Co-founder ~ http://www.noelios.com


 -Message d'origine-
 De : Rhett Sutphin [mailto:rh...@detailedbalance.net]
 Envoyé : dimanche 8 mars 2009 03:07
 À : discuss@restlet.tigris.org
 Objet : Re: Integrating WADL and Spring

 Hi David,

 On Mar 6, 2009, at 4:10 PM, David Bordoley wrote:

 On Fri, Mar 6, 2009 at 11:32 AM, Rhett Sutphin
 rh...@detailedbalance.net wrote:

 This would be an RFE (at least, I'm not aware of any way to get it to
 work currently).  I'm curious about how you would tie the resources
 in your application context to the WADL.  Would you add a custom
 attribute for the spring bean id?  Is there a WADL feature which
 would help with this?  I'm not that familiar with it.

 Rhett

 Hi,

 The current way WADL works in Restlet is to require implementors to
 specify the class of the resource you want to map a WADL resource to
 using the resource's id attribute. You then pass the the WADL xml as a
 constructor argument to a WadlComponent or WadlApplication. You can
 see an example of this in org.restlet.test.YahooSearch.wadl (omitting
 the details in the example below):

 application
  resources base=http://api.search.yahoo.com/NewsSearchService/V1/;
    resource id=org.restlet.test.NewsSearchResource
 path=newsSearch
    /resource
  /resources
 /application

 It would be cool if you could do something similar but instead of
 passing a Resource class (and be stuck using the default constructor
 etc.), instead use a Spring Bean id as the resource id in WADL, and
 have restlet use spring to wire all the resources together, thus
 getting all the benefits of IOC, while also being able to more
 explicitly state your resource interface in a standard method.

 Anyway i can open an RFE if necessary, but I wanted to ask on the list
 first.

 This is a good idea.  I think the implementation might be more generic than
 just spring support, so I went ahead and entered the RFE against the WADL
 component:  http://restlet.tigris.org/issues/show_bug.cgi?id=756

 Thanks,
 Rhett

 --
 http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=12864
 20

 --
 http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1297634


--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1298256


Re: Integrating WADL and Spring

2009-03-07 Thread Rhett Sutphin
Hi David,

On Mar 6, 2009, at 4:10 PM, David Bordoley wrote:

 On Fri, Mar 6, 2009 at 11:32 AM, Rhett Sutphin
 rh...@detailedbalance.net wrote:

 This would be an RFE (at least, I'm not aware of any way to get it to
 work currently).  I'm curious about how you would tie the resources  
 in
 your application context to the WADL.  Would you add a custom
 attribute for the spring bean id?  Is there a WADL feature which  
 would
 help with this?  I'm not that familiar with it.

 Rhett

 Hi,

 The current way WADL works in Restlet is to require implementors to
 specify the class of the resource you want to map a WADL resource to
 using the resource's id attribute. You then pass the the WADL xml as a
 constructor argument to a WadlComponent or WadlApplication. You can
 see an example of this in org.restlet.test.YahooSearch.wadl (omitting
 the details in the example below):

 application
  resources base=http://api.search.yahoo.com/NewsSearchService/V1/;
resource id=org.restlet.test.NewsSearchResource  
 path=newsSearch
/resource
  /resources
 /application

 It would be cool if you could do something similar but instead of
 passing a Resource class (and be stuck using the default constructor
 etc.), instead use a Spring Bean id as the resource id in WADL, and
 have restlet use spring to wire all the resources together, thus
 getting all the benefits of IOC, while also being able to more
 explicitly state your resource interface in a standard method.

 Anyway i can open an RFE if necessary, but I wanted to ask on the  
 list first.

This is a good idea.  I think the implementation might be more generic  
than just spring support, so I went ahead and entered the RFE against  
the WADL component:  http://restlet.tigris.org/issues/show_bug.cgi?id=756

Thanks,
Rhett

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1286420


Integrating WADL and Spring

2009-03-06 Thread David Bordoley
Hi All,

I've been playing around with Restlet for some projects I'm working on
and have really enjoyed the platform. I'm wondering if there is a way
to define your service in a WADL document but still use Spring to
configure all your applications Resources, etc. In the abstract what I
would like to do is is define a WADL but instead of using ID's which
map to Java classes, map them to Spring bean ids, essentially use WADL
as a replacement for SpringRouter. Any suggestions? Is this an RFE?

Thanks,

Dave

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1278554


Re: Integrating WADL and Spring

2009-03-06 Thread Rhett Sutphin
Hi Dave,

On Mar 6, 2009, at 1:08 PM, David Bordoley wrote:

 I've been playing around with Restlet for some projects I'm working on
 and have really enjoyed the platform. I'm wondering if there is a way
 to define your service in a WADL document but still use Spring to
 configure all your applications Resources, etc. In the abstract what I
 would like to do is is define a WADL but instead of using ID's which
 map to Java classes, map them to Spring bean ids, essentially use WADL
 as a replacement for SpringRouter. Any suggestions? Is this an RFE?

This would be an RFE (at least, I'm not aware of any way to get it to  
work currently).  I'm curious about how you would tie the resources in  
your application context to the WADL.  Would you add a custom  
attribute for the spring bean id?  Is there a WADL feature which would  
help with this?  I'm not that familiar with it.

Rhett

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1278642


Re: Integrating WADL and Spring

2009-03-06 Thread David Bordoley
On Fri, Mar 6, 2009 at 11:32 AM, Rhett Sutphin
rh...@detailedbalance.net wrote:

 This would be an RFE (at least, I'm not aware of any way to get it to
 work currently).  I'm curious about how you would tie the resources in
 your application context to the WADL.  Would you add a custom
 attribute for the spring bean id?  Is there a WADL feature which would
 help with this?  I'm not that familiar with it.

 Rhett

Hi,

The current way WADL works in Restlet is to require implementors to
specify the class of the resource you want to map a WADL resource to
using the resource's id attribute. You then pass the the WADL xml as a
constructor argument to a WadlComponent or WadlApplication. You can
see an example of this in org.restlet.test.YahooSearch.wadl (omitting
the details in the example below):

application
  resources base=http://api.search.yahoo.com/NewsSearchService/V1/;
resource id=org.restlet.test.NewsSearchResource path=newsSearch
/resource
  /resources
/application

It would be cool if you could do something similar but instead of
passing a Resource class (and be stuck using the default constructor
etc.), instead use a Spring Bean id as the resource id in WADL, and
have restlet use spring to wire all the resources together, thus
getting all the benefits of IOC, while also being able to more
explicitly state your resource interface in a standard method.

Anyway i can open an RFE if necessary, but I wanted to ask on the list first.

thanks,

Dave

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1279214