On 10/21/07, Don Brown [EMAIL PROTECTED] wrote:
The rest plugin heavily depends on the current codebehind plugin, so
if we are going to merge them, we should do it as soon as possible.
Could someone outline what exactly the changes would look like?
I'm going to get started on the RESTful
Possible to implement the application, or clone the implementation?
Personally, I'd also like to implement some of the Rails examples,
though maybe not in the Apache Struts repository. (Which was the
original idea behind the SourceForge site: a place to host other
example applications.)
-Ted.
James is tied-up, so I'm going to finish this release tonight.
On 10/16/07, Ted Husted [EMAIL PROTECTED] wrote:
We have three (James, Rainer, and mine). James just hasn't called it.
All that we need to do is move the files from /www/p.a.o/builds/struts
to /www/www.apache.org/dist/struts, wait
Bringing together a couple of other threads, for Struts 2.1.x (or
even Struts 2.2.x), we seem to be talking about
* Creating a plugin artifact, along the lines of the apps
artifact, which would include all the plugins we maintain in the
Struts repository
* Creating a struts2-core-plugin
On 10/21/07, Don Brown [EMAIL PROTECTED] wrote:
[2] http://cwiki.apache.org/S2PLUGINS/rest-plugin.html
100% follow Ruby on Rails-style Rest URL conventions
Is there a cannonical reference as to the conventions, especially one
that would be accessible to people who haven't written a Rails
I was going off the free rest pdf linked to in the documentation, but
I hear it has changed slightly for 2.0.
Don
On 10/22/07, Ted Husted [EMAIL PROTECTED] wrote:
On 10/21/07, Don Brown [EMAIL PROTECTED] wrote:
[2] http://cwiki.apache.org/S2PLUGINS/rest-plugin.html
100% follow Ruby on
The PDF link is broken now.
On 10/22/07, Don Brown [EMAIL PROTECTED] wrote:
I was going off the free rest pdf linked to in the documentation, but
I hear it has changed slightly for 2.0.
Don
On 10/22/07, Ted Husted [EMAIL PROTECTED] wrote:
On 10/21/07, Don Brown [EMAIL PROTECTED] wrote:
Really? I just loaded it. It is a page that has links to the english
and italian versions, and the english one works at least.
Don
On 10/22/07, Ted Husted [EMAIL PROTECTED] wrote:
The PDF link is broken now.
On 10/22/07, Don Brown [EMAIL PROTECTED] wrote:
I was going off the free rest pdf
s/Italian/German and Spanish/
On 10/22/07, Don Brown [EMAIL PROTECTED] wrote:
Really? I just loaded it. It is a page that has links to the english
and italian versions, and the english one works at least.
Don
On 10/22/07, Ted Husted [EMAIL PROTECTED] wrote:
The PDF link is broken now.
There must be a DNS glitch from where I am.
On 10/22/07, Don Brown [EMAIL PROTECTED] wrote:
Really? I just loaded it. It is a page that has links to the english
and italian versions, and the english one works at least.
Don
On 10/22/07, Ted Husted [EMAIL PROTECTED] wrote:
The PDF link is
Sorry for the late reply. Busy happenings lately.
Don Brown wrote:
Hmm..I'm a bit leary about this component talk. I'd like to keep
Struts 2 simple and I see the goal of this is to define a plugin that:
* Builds configuration based on annotations
* Defines default results when none specified
Piero Sartini wrote:
Am Mittwoch, 17. Oktober 2007 23:49:33 schrieb Jim Cushing:
For different renderings/mimetypes, I think it'd make sense, if
possible, to use a dot-extension (e.g., foo.pdf instead of foo/
pdf), since this is a common and well understood convention.
Is there a
On Mon, October 22, 2007 6:48 am, Ted Husted wrote:
Arguably, we could also include an Ajax plugin in the standard
array, but I would like to explore alternatives to the Dojo plugin. I
think we should maintain a Dojo plugin, just as we plan to maintain a
Spring plugin, but I'd also like to try
On 10/22/07, Frank W. Zammetti [EMAIL PROTECTED] wrote:
I'm still not 100% convinced there's a ton of benefit to this plugin
frankly, other than perhaps visibility, but it's there now in any case.
That how I feel too with most of the plugins I've written. I wish we
could add a plugin
On 10/22/07, Frank W. Zammetti [EMAIL PROTECTED] wrote:
I'm still not 100% convinced there's a ton of benefit to this plugin
frankly, other than perhaps visibility, but it's there now in any case.
The benefit of the Dojo plugin isn't that it enables Dojo, but that it
enables some of the Struts
* Creating a struts2-core-plugin artifact that would include the
plugins that are needed to write a typical Struts 2 application.
I like this most :-)
To have a standard way of doing things makes development a lot faster and
easier.
I haven't looked into yet, but we might also consider a
Ted Husted wrote:
On 10/22/07, Frank W. Zammetti [EMAIL PROTECTED] wrote:
I'm still not 100% convinced there's a ton of benefit to this plugin
frankly, other than perhaps visibility, but it's there now in any case.
The benefit of the Dojo plugin isn't that it enables Dojo, but that it
enables
On 10/22/07, Ted Husted [EMAIL PROTECTED] wrote:
Bringing together a couple of other threads, for Struts 2.1.x (or
even Struts 2.2.x), we seem to be talking about
* Creating a plugin artifact, along the lines of the apps
artifact, which would include all the plugins we maintain in the
It might be interesting to have several bundles:
* Core - codebehind, dojo
* Starter - codebehind, dojo, spring, jpa
* Rest - codebehind, rest, dojo
Of course, the value of this bundle concept is low for those that use
Maven 2 or any other transitive dependency system. For my rest
example
19 matches
Mail list logo
