The mailreader is a good one, but when I get the chance, I want to
port the bookmarks application from the Restful Web Applications book.
The plugin needs a bit more work (namely wildcards in namespaces)
before that will be fully possible.
Don
On 10/22/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 10/21/07, Matt Raible <[EMAIL PROTECTED]> wrote:
> It'd be very
> interesting to develop a sample application that uses SOFEA principles -
> possibly using the rest-plugin and YUI.
I'm game :)
-Ted.
-
To unsubscribe, e-mail:
On 10/22/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> On 10/21/07, Don Brown <[EMAIL PROTECTED]> wrote:
> > Therefore, I'd like to propose we add the Rest Plugin, now residing
> > in the Struts sandbox, to the list of bundled Struts 2 plugins.
>
> I'd like to put together a RESTful Mailreader first.
On 10/22/07, Martin Cooper <[EMAIL PROTECTED]> wrote:
> On 10/21/07, Don Brown <[EMAIL PROTECTED]> wrote:
> >
> > [...]
> > Which reminds me, this plugin is targeted towards HTML-based web apps
> > that want to expose their information in machine-readable ways (XML
> > and JSON),
>
>
> I presume yo
Don Brown wrote:
3. Your private remote API is your public API - your Ajax app is just
another consumer of your remote api. This makes tools like mashups
possible with no extra work. DWR endpoints aren't meant to be
consumed externally.
I think this point especially is where the value of this
On 10/21/07, Don Brown <[EMAIL PROTECTED]> wrote:
> Therefore, I'd like to propose we add the Rest Plugin, now residing
> in the Struts sandbox, to the list of bundled Struts 2 plugins.
I'd like to put together a RESTful Mailreader first. I can try and do
that over the course of the week. We alrea
On 10/21/07, Don Brown <[EMAIL PROTECTED]> wrote:
>
> [...]
> Which reminds me, this plugin is targeted towards HTML-based web apps
> that want to expose their information in machine-readable ways (XML
> and JSON),
I presume you mean DOM-based apps; some of us don't use HTML any more. ;-)
but an
Howdy,
Just wondering there's an S2 sub-interface of XWork's
NoParameters; if it doesn't add any functionality
could we remove it for 2.1 to avoid confusion?
Thanks,
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
Without getting into a Rest vs RPC debate, Rest, and this plugin
specificially, has these advantages:
1. Unified architecture - your machine interfaces (Ajax) endpoints are
just another Struts action
2. Multiple content types - Data is exposed via XML and JSON
automatically, and XHTML with the cor
Don Brown wrote:
Completely agree. A lot of Struts developers have started moving to
more Ajax-centric approaches where the server-side is mostly static
html and DWR. I think that Rest provides a more useful and ultimately
flexible solution, especially if you get things like XML and JSON
encodi
On 10/22/07, Matt Raible <[EMAIL PROTECTED]> wrote:
> One thing I think we should change is /orders/{id};edit to /orders/{id}/edit
> - much like Rails 2.0 supports.
Yep, shouldn't be too hard to support both really.
> Also, is "Resource" required as the suffix for classes? I think this is
> somet
On 10/21/07, Don Brown <[EMAIL PROTECTED]> wrote:
>
> The more I study Rest [1] and now having used it in a production
> application, the more I'm convinced Struts 2 needs to be the premier
> way to write Restful web applications. The HTTP-based Rest theory is
> well-suited to the action-based Mode
The more I study Rest [1] and now having used it in a production
application, the more I'm convinced Struts 2 needs to be the premier
way to write Restful web applications. The HTTP-based Rest theory is
well-suited to the action-based Model 2 design as makes it easy to
write naturally Restful appli
13 matches
Mail list logo
