On Mon, Mar 2, 2009 at 9:03 PM, Solomon Duskis <sduskis(a)gmail.com&gt; wrote: > Are you actively working on that integration? The integration work resulted in a preview release last summer, then we waited for RE to stabilize and GA. I checked two weeks or so ago, and Jozef had already upgraded the Seam integration code to compile and run against RE GA 1.0.

There is a chapter in the Seam reference documentation that describes the integration and features: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/webservices.html... The remaining issues range from trivial to major, however, there is not much critical functionality missing. Jozef, are you aware of anything that has not already been reported in JIRA?

We bundle these activities under the "WS" component in Seam JIRA: https://jira.jboss.org/jira/browse/JBSEAM/component/12310823 > version of RESTEasy. Do you have some time to help out with that, and to > point me in the right direction for the current Seam/RESTEasy code? The code is in Seam trunk which is the 2.1.x release line. So now that RE GA is here we would certainly welcome any help on ironing out the remaining issues. Have a look at the reported stuff in JIRA and see if you like to pick something - even if it's assigned to me ;) I will go through the list again as well and see if there is anything missing and maybe set some priorities. Jozef, let us know what your status/plans are.

For the future and more elaborate Seam/REST integration work: There are some great ideas floating around, mostly things people have been discussing directly or posting on some mailing list or another. My opinion has been so far that we get the basic stuff working in Seam 2.1.x and then wait for the Web Beans RI to stabilize and start with the more advanced REST stuff (like XHTML representation mapping with Facelets) in Seam 3.

I am working on Seam+RESTEasy integration as a part of my university thesis. I am focusing more on new features rather than bug fixing as this is more interesting for university however I was fixing some bugs as well. The plan is to implement following things: * REST API for application framework - I am working on a component that exposes CRUD API to manipulate database entities (using Seam's home and query components)- I have some working prototypes already, working on details now. * Exception mapping in pages.xml * Facelets XHTML mapping Furthermore, I am planning on creating a sample application demonstrating Seam+RESTEasy integration. It will be a simple todo app exposing REST API.

Not sure, here's some guesses on what making JSF "RESTFul" means: * Unique URIs to each "page" * don't overload the meaning of HTTP methods. i.e. don't change state of server with a GET * No sessions, stateless Or maybe people just want nice URI templating and JAX-RS injection annotations. I don't know. Which isn't persay, "REST", but still nice to have.

Dan Allen wrote: > I am working on Seam+RESTEasy integration as a part of my > university > thesis. I am focusing more on new features rather than bug > fixing as > this is more interesting for university however I was fixing some > bugs as well. The plan is to implement following things: > * REST API for application framework - I am working on a > component that exposes CRUD API to manipulate database entities > (using Seam's home and query components)- I have some working > prototypes already, working on details now. > * Exception mapping in pages.xml > * Facelets XHTML mapping > Furthermore, I am planning on creating a sample application > demonstrating Seam+RESTEasy integration. It will be a simple todo > app exposing REST API. > Jozef, while you are thinking about how to expand this integration, > could you record some thoughts about how JSF might leverage REST. > One of the features that has been long requested of JSF is that it > support REST. The problem is, we have to first figure out what that > even means. Maybe it isn't even relevant. Either way, if there is a > sensible integration, we (Red Hat) want to be the ones that figure > it out and propose it to the JSF EG for JSF 2.1. > It may well be that the JSF REST merely consists of defining > mappings in the PDL (i.e., Facelets). > If anyone else has any thoughts, feel free to share them. > -Dan > -- > Dan Allen > Senior Software Engineer, Red Hat | Author of Seam in Action > http://mojavelinux.com > http://mojavelinux.com/seaminaction > NOTE: While I make a strong effort to keep up with my email on a > daily > basis, personal or other work matters can sometimes keep me away > from my email. If you contact me, but don't hear back for more than > a week, > it is very likely that I am excessively backlogged or the message was > caught in the spam filters. Please don't hesitate to resend a > message if > you feel that it did not reach my attention. -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Bill, agreed on all these things - JSF2 no longer overloads POST for GET (which it did previously), adds good support for statelessness and unique URIs for a resource through page actions. However I don't think full REST is possible in JSF (not overloading POST for PUT/ DELETE). On 4 Mar 2009, at 17:53, Bill Burke wrote: > Not sure, here's some guesses on what making JSF "RESTFul" means: > > * Unique URIs to each "page" > * don't overload the meaning of HTTP methods. i.e. don't change > state of server with a GET > * No sessions, stateless > > Or maybe people just want nice URI templating and JAX-RS injection > annotations. I don't know. Which isn't persay, "REST", but still > nice to have. These would also be nice and are on the cards for JSF 2.1... > > > Dan Allen wrote: >> I am working on Seam+RESTEasy integration as a part of my >> university >> thesis. I am focusing more on new features rather than bug >> fixing as >> this is more interesting for university however I was fixing some >> bugs as well. The plan is to implement following things: >> * REST API for application framework - I am working on a >> component that exposes CRUD API to manipulate database entities >> (using Seam's home and query components)- I have some working >> prototypes already, working on details now. >> * Exception mapping in pages.xml >> * Facelets XHTML mapping >> Furthermore, I am planning on creating a sample application >> demonstrating Seam+RESTEasy integration. It will be a simple todo >> app exposing REST API. >> Jozef, while you are thinking about how to expand this >> integration, could you record some thoughts about how JSF might >> leverage REST. One of the features that has been long requested of >> JSF is that it support REST. The problem is, we have to first >> figure out what that even means. Maybe it isn't even relevant. >> Either way, if there is a sensible integration, we (Red Hat) want >> to be the ones that figure it out and propose it to the JSF EG for >> JSF 2.1. >> It may well be that the JSF REST merely consists of defining >> mappings in the PDL (i.e., Facelets). >> If anyone else has any thoughts, feel free to share them. >> -Dan >> -- >> Dan Allen >> Senior Software Engineer, Red Hat | Author of Seam in Action >> http://mojavelinux.com >> http://mojavelinux.com/seaminaction >> NOTE: While I make a strong effort to keep up with my email on a >> daily >> basis, personal or other work matters can sometimes keep me away >> from my email. If you contact me, but don't hear back for more >> than a week, >> it is very likely that I am excessively backlogged or the message >> was >> caught in the spam filters. Please don't hesitate to resend a >> message if >> you feel that it did not reach my attention. > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev -- Pete Muir http://www.seamframework.org http://in.relation.to/Bloggers/Pete _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

On Wed, Mar 4, 2009 at 2:23 PM, Emmanuel Bernard <emmanuel(a)hibernate.org > wrote: REST kinda mandates to have a stateless application design. Ie the necessary state is always passed through each request. No sure JSF can cope with that. Why not? JSF's state management is only for the UI ( the component tree). JSF always marshalls the data back and forth through POST. So really if you put the UI aside, it is stateless. There is some gray area, but I think it's feasible to use JSF this way. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

* Unique URIs to each "page"

* don't overload the meaning of HTTP methods. i.e. don't change state of server with a GET

* No sessions, stateless

Or maybe people just want nice URI templating and JAX-RS injection annotations. I don't know. Which isn't persay, "REST", but still nice to have.

> > * Unique URIs to each "page" > > We are going to call these "pretty" or "friendly" URLs and it is slated > for JSF 2.1. We intentionally want to avoid the word REST here. > Actually, I think this comes with page parameters, as those define a unique URI (but not path) for a resource. URL rewrite just makes em look nice.

Query parameters really shouldn't contain information about identity. You can't create URI hierarchies then. For example: For example: /customers /customers/123 /customers/123/address But I guess this is the "prettiness" factor and nothing really to do about whether it is RESTFul or not.

> JSF 2.0 will have bookmarkable URLs, which are used, for example, to > retrieve a record by ID. In JSF 2.1 we intend to add page actions, which may > change the state of the server with a GET, but those are discretionary cases > to adapt to an action-oriented world (sometimes, it just has to be done). > > Why can't POST be used? Sys admins and caches don't understand an action-oriented world, but they do know the difference between GET and POST.

I am working on Seam+RESTEasy integration as a part of my university > thesis. I am focusing more on new features rather than bug fixing as this is > more interesting for university however I was fixing some bugs as well. The > plan is to implement following things: > * REST API for application framework - I am working on a component > that exposes CRUD API to manipulate database entities (using Seam's home and > query components)- I have some working prototypes already, working on > details now. > * Exception mapping in pages.xml > * Facelets XHTML mapping > Furthermore, I am planning on creating a sample application demonstrating > Seam+RESTEasy integration. It will be a simple todo app exposing REST API. Jozef, while you are thinking about how to expand this integration, could you record some thoughts about how JSF might leverage REST. One of the features that has been long requested of JSF is that it support REST. The problem is, we have to first figure out what that even means. Maybe it isn't even relevant. Either way, if there is a sensible integration, we (Red Hat) want to be the ones that figure it out and propose it to the JSF EG for JSF 2.1. It may well be that the JSF REST merely consists of defining mappings in the PDL (i.e., Facelets). If anyone else has any thoughts, feel free to share them. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

On Mar 04, 2009, at 12:19 , Jozef Hartinger wrote: >> status/plans are. > I am working on Seam+RESTEasy integration as a part of my university > thesis. I am focusing more on new features rather than bug fixing as > this is more interesting for university however I was fixing some bugs > as well. The plan is to implement following things: > * REST API for application framework - I am working on a component > that exposes CRUD API to manipulate database entities (using Seam's > home and query components)- I have some working prototypes already, > working on details now. > * Exception mapping in pages.xml > * Facelets XHTML mapping > Furthermore, I am planning on creating a sample application > demonstrating Seam+RESTEasy integration. It will be a simple todo app > exposing REST API. I've created JIRA issues for these and added some of my older ideas as well as some prototype code for the Facelets mapping feature. Following is a list of the open issues. Jozef, it looks like you want to work on most of the feature requests.

Can we close 3449, some guys start to think it's a catch-all thread?

Also, I think the "anemic HTTP session" feature request is currently the most important one because heavy REST usage will bring down your service at some point (max session limit). Solomon, the @Context problem in 3383 would be a good start as it requires some knowledge of RESTEasy internals. Bugs: https://jira.jboss.org/jira/browse/JBSEAM-3383 REST @Context injection for Seam component resources https://jira.jboss.org/jira/browse/JBSEAM-3965 @Providers not working - ResteasyDispatcher registers components and providers in wrong order https://jira.jboss.org/jira/browse/JBSEAM-3915 RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method https://jira.jboss.org/jira/browse/JBSEAM-3449 Upgrade to latest RestEasy beta

Features: https://jira.jboss.org/jira/browse/JBSEAM-3264 REST requests create anemic HttpSessions https://jira.jboss.org/jira/browse/JBSEAM-3265 RESTEasy exception handling https://jira.jboss.org/jira/browse/JBSEAM-3987 Integrate RESTEasy with Seam Application fwk for easy CRUD https://jira.jboss.org/jira/browse/JBSEAM-3988 Support for mapping RESTful XHTML resource representations with Facelets templates https://jira.jboss.org/jira/browse/JBSEAM-3989 Map conversations to URI spaces for REST integration