Hello everyone.
After the release of Struts 2.1 as GA (in 2.1.6) I decided to write a
quite simple tutorial about creating a basic application that uses the
features of Struts2 Rest Plugin and some of Convention Plugin.
If someone might be interested, here you can read it:
http
;>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Wesley Wannemacher
>>>>>> President, Head Engineer/Consultant
>>>>>> WanTii, Inc.
>>>>>> http://www.wantii.c
t;>>>>>
>>>>>> --
>>>>>> Wesley Wannemacher
>>>>>> President, Head Engineer/Consultant
>>>>>> WanTii, Inc.
>>>>>> http://www.wanti
t;>> President, Head Engineer/Consultant
>>>>> WanTii, Inc.
>>>>> http://www.wantii.com
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail:
>
> Oh! Multiple UnknownHandler = Convention in 2.1.3 right? If only.
>
Yes...still pushing for it :)
musachy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
gt;>>
>>>>>
>>>>>
>>>>> --
>>>>> Wesley Wannemacher
>>>>> President, Head Engineer/Consultant
>>>>> WanTii, Inc.
>>>>> http://www.wantii.com
>>>>>
>>>>> -
Yeah guys, let's roll...
I think we sould stick our heads together with Rainer to get a hands on
XWork release tutorial :)
For the S2 release, we might still have some small pain points with the
documentation, doing a release together will help to get it in best
possible shape.
Cheers,
- Re
Ah, cool, I assumed you were backed up. Is the 2.1.3 filter up to date
in xwork? I will take a look and see which ones I can fix. When you
have a chance take another look at
http://jira.opensymphony.com/browse/XW-640 (yeah I am really annoying
:) ), and if it looks good I can commit it.
regards
mu
Musachy,
I'm available for releases as well (especially XWork) and soon will have
more spare time
I'd like to spent on xw/s2.
cheers,
Rainer
On Tue, 2 Dec 2008 10:12:39 -0500, "Musachy Barroso" <[EMAIL PROTECTED]>
wrote:
> I want to fix the problem with the empty spaces in the param names,
> a
I want to fix the problem with the empty spaces in the param names,
and then head to xwork and see if there are any blocking bugs open,
and try to help there. I am trying to get Rene to do the xwork
release, and me and Wes will step thru the Struts release, so there is
more people involved with the
Yes, see the Struts home page for the following info:
=
The latest release of Struts 2 is Struts 2.1.2, which was promoted to "Beta"
on 26 March 2008. For the latest production release ("General
Availability"), see Struts 2.0.14.
=
On Tue, Dec 2, 2008 at 9:58 AM, Wes Wannemacher <[EMAIL
Was 2.1.2 a BETA?
-Wes
On Tue, Dec 2, 2008 at 9:53 AM, James Holmes <[EMAIL PROTECTED]> wrote:
> It looks like we're almost there! Musachy is killing it!
>
> From what I can tell the only real outstanding issue left for the 2.1.3
> release is:
>
> https://issues.apache.org/struts/browse/WW-2197
>
It looks like we're almost there! Musachy is killing it!
>From what I can tell the only real outstanding issue left for the 2.1.3
release is:
https://issues.apache.org/struts/browse/WW-2197
That said, what is the plan to get 2.1 to GA? Are we going to close out the
last 2 or 3 2.1.3 bugs and mak
Hello,
I would also like to know about the Struts 2.1 official (GA) release! Any
plans?
Thanks,
Fabiano Franz
Bruno Ghisi wrote:
>
> Hello,
>
> I was wondering if there is a roadmap around Struts releases. I mean, when
> will be the official release of Struts 2.1.2 and als
Please post your questions on the user mailing list; this list is for
the development of the framework itself.
musachy
On Fri, Jul 4, 2008 at 12:13 PM, Ish <[EMAIL PROTECTED]> wrote:
> Hi
>
>
> I am using struts 2 and jsp in my project. I have jsp page, which uses data
> in ajson format.
> I ha
Hi
I am using struts 2 and jsp in my project. I have jsp page, which uses data in
ajson format.
I have created
my Actiion look like this
JSONObject obj=new JSONObject();
obj.put("StartDate","2008-02-26 12:00:00");
obj.put("GoogleRef","61.92411, 25.748151");
obj.put("Element","DVD/Topcover");
this message in context:
http://www.nabble.com/Struts-2.1-release-tp18266050p18266050.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
2.x. Does this mean the
>> intention is not to fix the bug which means that compilation fails if you
>> update the dependency?
>>
>> Al.
>>
>> Don Brown wrote:
>>>
>>> I officially declare the Struts 2.1 bug hunting season open! In orde
intention is not to fix the bug which means that compilation fails if you
> update the dependency?
>
> Al.
>
> Don Brown wrote:
>>
>> I officially declare the Struts 2.1 bug hunting season open! In order
>> to ensure a high-quality 2.1 GA release, I've gone th
+2
On Thu, Jun 12, 2008 at 10:30 PM, Don Brown <[EMAIL PROTECTED]> wrote:
> I officially declare the Struts 2.1 bug hunting season open! In order
> to ensure a high-quality 2.1 GA release, I've gone through the tickets
> and assigned most open bugs to the 2.1.3
Struts 2.1 bug hunting season open! In order
to ensure a high-quality 2.1 GA release, I've gone through the tickets
and assigned most open bugs to the 2.1.3 version:
https://issues.apache.org/struts/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=pr
I officially declare the Struts 2.1 bug hunting season open! In order
to ensure a high-quality 2.1 GA release, I've gone through the tickets
and assigned most open bugs to the 2.1.3 version:
https://issues.apache.org/struts/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/orde
ly
> love to have it.
>
> - Original Message - From: "James Holmes" <[EMAIL PROTECTED]>
> To: "Struts Developers List"
> Sent: Thursday, May 15, 2008 3:58 PM
>
> Subject: Re: [VOTE] upgrade Struts 2.1.x FreeMarker dependency to 2.3.13
>
>
>
3:58 PM
Subject: Re: [VOTE] upgrade Struts 2.1.x FreeMarker dependency to 2.3.13
Yes, good point. I noticed after I sent out the email that 2.3.13 wasn't
in
Maven yet. I'm going to send them an email to nudge that along.
The 2.3.13 release appears that it could dramatically improve pe
Struts Developers List"
> Sent: Thursday, May 15, 2008 3:30 PM
> Subject: Re: [VOTE] upgrade Struts 2.1.x FreeMarker dependency to 2.3.13
>
>
>
> +1
>>
>> On Thu, May 15, 2008 at 10:23 AM, James Holmes <[EMAIL PROTECTED]>
>> wrote:
>>
>>> +1
+1 once 2.3.13 has made distributed to the maven repositories.
- Original Message -
From: "Musachy Barroso" <[EMAIL PROTECTED]>
To: "Struts Developers List"
Sent: Thursday, May 15, 2008 3:30 PM
Subject: Re: [VOTE] upgrade Struts 2.1.x FreeMarker dependency to
+1
On Thu, May 15, 2008 at 10:23 AM, James Holmes <[EMAIL PROTECTED]> wrote:
> +1
>
> On Thu, May 15, 2008 at 10:23 AM, James Holmes <[EMAIL PROTECTED]>
> wrote:
>
>> Currently Struts 2.1.x depends on FreeMarker 2.3.12. I propose to upgrade
>> the de
+1
On Thu, May 15, 2008 at 10:23 AM, James Holmes <[EMAIL PROTECTED]>
wrote:
> Currently Struts 2.1.x depends on FreeMarker 2.3.12. I propose to upgrade
> the dependency to 2.3.13 to take advantage of performance improvements and
> bug fixes.
>
> See this link for
Currently Struts 2.1.x depends on FreeMarker 2.3.12. I propose to upgrade
the dependency to 2.3.13 to take advantage of performance improvements and
bug fixes.
See this link for release notes:
http://freemarker.sourceforge.net/docs/versions_2_3_13.html
[ ] Yes, upgrade the dependency to 2.3.13
2008/5/1 Jeromy Evans <[EMAIL PROTECTED]>:
> Jay Bose wrote:
>
> > Thanks Antonio, that solved it.
> >
> >
> >
> >
> Just wondering, how does one know that before attempting "mvn
> assembly:assembly", they must run the release,all,alljars,j4 and
> pre-assembly profiles?
> Is it just a matter of d
Jay Bose wrote:
Thanks Antonio, that solved it.
Just wondering, how does one know that before attempting "mvn
assembly:assembly", they must run the release,all,alljars,j4 and
pre-assembly profiles?
Is it just a matter of digging through the pom until you find the right
profiles?
(It's n
Thanks Antonio, that solved it.
--- Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> 2008/4/30 Jay Bose <[EMAIL PROTECTED]>:
> > I'm upgrading from WebWork-2 to the most recent Struts-2(.1.x) that
> > contains a
> working
> > instance of Dojo. Following the directions on
> > http://struts.apache
2008/4/30 Jay Bose <[EMAIL PROTECTED]>:
> I'm upgrading from WebWork-2 to the most recent Struts-2(.1.x) that contains
> a working
> instance of Dojo. Following the directions on
> http://struts.apache.org/2.x/docs/building-the-framework-from-source.html and
> http://struts.apache.org/2.x/docs/
I'm upgrading from WebWork-2 to the most recent Struts-2(.1.x) that contains a
working
instance of Dojo. Following the directions on
http://struts.apache.org/2.x/docs/building-the-framework-from-source.html and
http://struts.apache.org/2.x/docs/building-with-maven.html, I successfully ran
this
co
Hi,
Will the DWR validator and associated js files be retained in
Struts 2.1.x where it'll be using Dojo instead? . From usage
perspective, i'm assuming that the dependency is on
org.apache.struts2.validators.DWRValidator class and ajax/
validation.js . Please confirm.
Thank
2007/9/7, Wendy Smoak <[EMAIL PROTECTED]>:
>
> And just in general, we use the release plugin at Maven, have used it
> at MyFaces, and at work we use the release management feature in
> Continuum (which is based on the same thing).
You forgot to mention Tiles :-)
Antonio
On 9/7/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> I'm nervous since there doesn't seem to be a way to try a "dry run" on
> 2.1.x. Though, since there is no hurry for 2.0.10, if you have time to
> apply the patch to the branch, we might as well try it there first.
Jim pointed out the -DdryRun=tru
2007/9/7, Jim <[EMAIL PROTECTED]>:
>
> Fortunately, you can do a dry run:
>
> mvn release:prepare -DdryRun=true
> After running the dry run, use this to cleanup:
>
> mvn release:clean
>
> See the heading "Do a Dry Run" for the Maven 2 release plugin
> documentation:
>
> http://maven.apache.org/plug
Fortunately, you can do a dry run:
mvn release:prepare -DdryRun=true
After running the dry run, use this to cleanup:
mvn release:clean
See the heading "Do a Dry Run" for the Maven 2 release plugin
documentation:
http://maven.apache.org/plugins/maven-release-plugin/usage.html
On Sep 7, 20
I'm nervous since there doesn't seem to be a way to try a "dry run" on
2.1.x. Though, since there is no hurry for 2.0.10, if you have time to
apply the patch to the branch, we might as well try it there first.
-Ted.
On 9/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> 2007/9/7, Ted Husted <[E
2007/9/7, Ted Husted <[EMAIL PROTECTED]>:
>
> Does step 2 " Tag the release by using the "release:prepare" goal of
> Maven:" actually tag the release in SVN? (How does it know what symbol
> to use?) Or is the word tag being used in another sense?
The sense is right :-) But the "release:prepare"
2007/9/6, Ted Husted <[EMAIL PROTECTED]>:
>
> I just wanted to try a dry-run on 2.1.x first, later tonight (after I
> get some actual work done!).
Just to be complete: the release process won't work until all the snapshot
dependencies are resolved. In particular, there is a dependency to xwork
2
all
> I am in the process of finish configuring the Maven Release plugin for
> Struts 2 (I think that I have finished, but I need to test it to be
> sure).
> In the meantime, I prepared a wiki page that shows how the release
> process will look like:
> http://cwiki.apache.org/confluen
I just wanted to try a dry-run on 2.1.x first, later tonight (after I
get some actual work done!).
-Ted.
On 9/6/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> 2007/9/6, Ted Husted <[EMAIL PROTECTED]>:
> > Is there any reason why it's labeled for Struts 2.1.x? Co
2007/9/6, Ted Husted <[EMAIL PROTECTED]>:
> Is there any reason why it's labeled for Struts 2.1.x? Could we also
> try it for 2.0.10?
Ted, sorry to disturb you, but you did not answer if you want me to
backport the release plugin configuration t
> >
> > 2007/9/6, Ted Husted <[EMAIL PROTECTED]>:
> > >
> > > Is there any reason why it's labeled for Struts 2.1.x? Could we also
> > > try it for 2.0.10?
> >
> >
> >
> > In fact I committed the changes only for the trunk and I did n
7, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> >
> > 2007/9/6, Ted Husted <[EMAIL PROTECTED]>:
> > >
> > > Is there any reason why it's labeled for Struts 2.1.x? Could we also
> > > try it for 2.0.10?
> >
> >
> >
> >
s.org after every release.
Paul
On 9/6/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> 2007/9/6, Ted Husted <[EMAIL PROTECTED]>:
> >
> > Is there any reason why it's labeled for Struts 2.1.x? Could we also
> > try it for 2.0.10?
>
>
>
> In
2007/9/6, Ted Husted <[EMAIL PROTECTED]>:
>
> Is there any reason why it's labeled for Struts 2.1.x? Could we also
> try it for 2.0.10?
In fact I committed the changes only for the trunk and I did not backport it
to the 2_0_X branch. If you want I can merge it to the branch
This looks great, Antonio!
Is there any reason why it's labeled for Struts 2.1.x? Could we also
try it for 2.0.10?
If so, I'll give it a whirl on Sunday (unless someone else would like
to give it a try!).
We're also still in need of volunteers to shepard the 2.1.0.
* http://st
+and+Signing+a+Struts+2.1.x+Distribution
Notice that it needs some cleaning, but anyway I wish to share your ideas.
Ciao
Antonio
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'd say open a ticket and give it a try. The sooner we try it, the
sooner we'll know that it works :)
-Ted.
On 8/22/07, James Holmes <[EMAIL PROTECTED]> wrote:
> I'm in favor of changing the dependency in Struts 2.1 from OGNL 2.6.1 to 2.7.
> This would better position
I'm in favor of changing the dependency in Struts 2.1 from OGNL 2.6.1 to 2.7.
This would better position us once we work on updating the Struts 2/XWork code
to
take advantage of the performance improvements.
I'm happy to make POM changes if everyone agrees.
James
On Wed Aug 22 14
rences between Struts 2.0.8 and Struts 2.1 . When Struts
2.1 is coming out ? Struts 2.1 is not ready for use ?
For a new project, I can use struts 2.1 yet or I need to use struts 2.0.8?
Thanks
Herrera
--
View this message in context:
http://www.nabble.com/struts-2.1-tf4044805.html#a11489563
Sent
What are the differences between Struts 2.0.8 and Struts 2.1 . When Struts
2.1 is coming out ? Struts 2.1 is not ready for use ?
For a new project, I can use struts 2.1 yet or I need to use struts 2.0.8 ?
Thanks
Herrera
--
View this message in context:
http://www.nabble.com/struts-2.1
From: Don Brown [mailto:[EMAIL PROTECTED]
> > How much overhead does the default interceptor stack introduce?
> Very, very little if the interceptors behave properly.
Fair enough; that was my assumption. It's low-hanging fruit for
out-of-the-box performance if there's stuff in there some folks wo
A user found a pretty big bug in XWork 2 that will need to be fixed
before it can go final. I'm working on it now and should hopefully be
done with it in the next few days. I think for this release Rainer will
use the Struts 2-style release process so we could upgrade the quality
if we are ha
Dave Newton wrote:
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Obviously, S2/WW2 does perform well enough in production: witness
Confluence and Jive. But, we need to recognize that the bloggers will
be all over the benchmark numbers, and we might want to be proactive.
Don't forget about this:
http://forums.opensymphony.com/thread.jspa?threadID=52734&tstart=0&start=15
Still a work in progress, but theoretically this will allow us to plug
in MVEL. (Or anything else for that matter)
Tom
David H. DeWolf wrote:
Ted Husted wrote:
I'd be happy to roll Struts 2.
Ted Husted wrote:
I'd be happy to roll Struts 2.0.3 as soon as there's a new XWork 2.
Then perhaps we should dub the head 2.1.x for the Ajax tag
reorganization, since there will be backward compatibility concerns.
+1
I do wonder if we should bring up Don's Java template plugin
+1
from
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Obviously, S2/WW2 does perform well enough in production: witness
> Confluence and Jive. But, we need to recognize that the bloggers will
> be all over the benchmark numbers, and we might want to be proactive.
Darn bloggers.
How muc
I'd be happy to roll Struts 2.0.3 as soon as there's a new XWork 2.
Then perhaps we should dub the head 2.1.x for the Ajax tag
reorganization, since there will be backward compatibility concerns.
If we need any more releases in the Struts 2.0.x series, we can always
go back and branch at 2.0.3. T
shouldn't wait to start realizing the Ti vision, so I propose we start
the Struts 2.1 branch in Subversion, and seed it with Able. Let 2.1 be
a breeding ground for innovative, convention-based code. We need to
foster continued, forward-looking development, while stabilizing what we
have
on movements, culminating in Ted's proposal to combine
efforts completely.
Should Able go into the code base now? No, I think we should take what
we have, get it stable, and get it out there to our users. However, we
shouldn't wait to start realizing the Ti vision, so I propose we start
th
go into the code base now? No, I think we should take what
we have, get it stable, and get it out there to our users. However, we
shouldn't wait to start realizing the Ti vision, so I propose we start
the Struts 2.1 branch in Subversion, and seed it with Able. Let 2.1 be
a breeding grou
65 matches
Mail list logo
