You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Koen Serry <ko...@hotmail.com> on 2008/11/15 00:56:14 UTC
Struts2 and production apps
Hi all,
I'm having a bit of an issue here. I have this small app (based on struts2)
that I want to bring in production, however which version.
* Production, well beter not take 2.1 since we're still beta
* 2.0.13: seems to be in the fridge?
* 2.0.12: yes great GA, ah no it doesn't do static resources, so all client
side validations won't work....
* 2.0.11.2: ok second best: hey doesn't this contain security issues, maybe
not a good idea after all.
So, without pointing fingers here. I like stuts2 but given the current
status of the project (and taken a thourough look at the manifesto as well)
I'm not sure what to tell/give my customer right now. Please advise.
Thanks
--
View this message in context: http://www.nabble.com/Struts2-and-production-apps-tp20510477p20510477.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Piero Sartini <li...@pierosartini.de>.
Just my oppinion, but I would go with 2.1.2 beta release. My feeling is that
it is the best version available.
Piero
Am Samstag 15 November 2008 00:56:14 schrieb Koen Serry:
> Hi all,
>
> I'm having a bit of an issue here. I have this small app (based on struts2)
> that I want to bring in production, however which version.
>
> * Production, well beter not take 2.1 since we're still beta
> * 2.0.13: seems to be in the fridge?
> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all client
> side validations won't work....
> * 2.0.11.2: ok second best: hey doesn't this contain security issues, maybe
> not a good idea after all.
>
> So, without pointing fingers here. I like stuts2 but given the current
> status of the project (and taken a thourough look at the manifesto as well)
> I'm not sure what to tell/give my customer right now. Please advise.
>
> Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Rene Gielen <gi...@it-neering.net>.
This great news guy, both the XWork 2.0.7 release and the improvements
on the release process. I'll start now with the Struts 2.0.14 build
process, along with trying to backport the release process improvements.
Let's roll :)
Musachy Barroso schrieb:
> We are trying to get the release process in a better shape, so
> documenting/improving the xwork release process would be great. Is there any
> documentation for xwork releases? Feel free to add stuff here:
>
> http://struts.apache.org/2.x/docs/creating-and-signing-a-struts-21x-distribution-new.html
>
> I will volunteer for making S2.x releases on a regular fashion, after the
> docs are complete :)
>
> musachy
>
> On Sat, Nov 15, 2008 at 9:13 AM, Rainer Hermanns <he...@aixcept.de>wrote:
>
>> Hi,
>>
>> xwork 2.0.7 is released and you can kick off the S2.0.14 release process.
>>
>> I'd love to get more S2 developers into the XWork development process.
>> So, are there any S2 (or other interested) developers not yet involved in
>> XWork who'd like commit access? Please contact me by mail and I'll add
>> you.
>>
>> Regarding current production apps, I'd go with 2.1.X from trunk for
>> development projects with a target release in 1-3 months and 2.0.14
>> (yet to be released) for production ready apps.
>> I have several projects running based on S2 2.1.X in production use, but
>> with some patches applied. These patches will soon be added to XWork 2.1.X
>> and go into the S2 2.1.X codebase.
>>
>> As soon as my current project is finished in early December I will have
>> much more time to work on XWork and S2.1.X again.
>>
>> Thanks,
>> Rainer
>>
>>> I totally agree that this is currently a very bad situation. Jeromy's
>>> tip for static resources is a working fix for the 2.0.12 issue, as well
>>> as an uprgade to 2.0.13 testing version would be (this was no GA
>>> release). Please note that we fixed the static resource bug immediately
>>> when it was reported, and triggered the 2.0.13 build - but since there
>>> is still the conversion message issue, it will not become GA.
>>>
>>> For the needed 2.0.14, we are simply waiting on XWork to be released,
>>> because the said conversion error problem is not a Struts issue. The bug
>>> was fixed in XWork code immediately after reporting, but XWork has it's
>>> own release cycle. That's why it is not in our hand to get out a Struts
>>> 2.0.14 release candidate, which technically will be nothing more than a
>>> 2.0.13 with a current XWork build.
>>>
>>> I really hope that we will be getting a XWork release this weekend, and
>>> as soon as it is published, be sure that a 2.0.14 build will pushed out
>>> right away. And to all those out there using production apps, please
>>> feel invited to participate on the QA review and voting process for new
>>> releases with reporting integration test results, because that helps us
>>> to hunt down the real world issues before we consider a build GA.
>>>
>>> - René
>>>
>>> Jeromy Evans schrieb:
>>>> Koen Serry wrote:
>>>>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
>>>>> client
>>>>> side validations won't work....
>>>>>
>>>> Just a tip, if you're releasing a production app, you shouldn't be
>>>> serving static resources from the struts2 dispatcher. Extract them and
>>>> the problem is avoided.
>>>>
>>>> http://struts.apache.org/2.0.12/docs/performance-tuning.html
>>>>
>> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> --
>> Rainer Hermanns
>> aixcept
>> Willibrordstraße 82
>> 52134 Herzogenrath - Germany
>> w: http://aixcept.de/
>> t: +49 - 2406 - 979 22 11
>> f: +49 - 2406 - 979 22 13
>> m: +49 - 170 - 343 29 12
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
--
René Gielen
IT-Neering.net
Saarstrasse 100, 52062 Aachen, Germany
Tel: +49-(0)241-4010770
Fax: +49-(0)241-4010771
Cel: +49-(0)177-3194448
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Musachy Barroso <mu...@gmail.com>.
We are trying to get the release process in a better shape, so
documenting/improving the xwork release process would be great. Is there any
documentation for xwork releases? Feel free to add stuff here:
http://struts.apache.org/2.x/docs/creating-and-signing-a-struts-21x-distribution-new.html
I will volunteer for making S2.x releases on a regular fashion, after the
docs are complete :)
musachy
On Sat, Nov 15, 2008 at 9:13 AM, Rainer Hermanns <he...@aixcept.de>wrote:
> Hi,
>
> xwork 2.0.7 is released and you can kick off the S2.0.14 release process.
>
> I'd love to get more S2 developers into the XWork development process.
> So, are there any S2 (or other interested) developers not yet involved in
> XWork who'd like commit access? Please contact me by mail and I'll add
> you.
>
> Regarding current production apps, I'd go with 2.1.X from trunk for
> development projects with a target release in 1-3 months and 2.0.14
> (yet to be released) for production ready apps.
> I have several projects running based on S2 2.1.X in production use, but
> with some patches applied. These patches will soon be added to XWork 2.1.X
> and go into the S2 2.1.X codebase.
>
> As soon as my current project is finished in early December I will have
> much more time to work on XWork and S2.1.X again.
>
> Thanks,
> Rainer
>
> > I totally agree that this is currently a very bad situation. Jeromy's
> > tip for static resources is a working fix for the 2.0.12 issue, as well
> > as an uprgade to 2.0.13 testing version would be (this was no GA
> > release). Please note that we fixed the static resource bug immediately
> > when it was reported, and triggered the 2.0.13 build - but since there
> > is still the conversion message issue, it will not become GA.
> >
> > For the needed 2.0.14, we are simply waiting on XWork to be released,
> > because the said conversion error problem is not a Struts issue. The bug
> > was fixed in XWork code immediately after reporting, but XWork has it's
> > own release cycle. That's why it is not in our hand to get out a Struts
> > 2.0.14 release candidate, which technically will be nothing more than a
> > 2.0.13 with a current XWork build.
> >
> > I really hope that we will be getting a XWork release this weekend, and
> > as soon as it is published, be sure that a 2.0.14 build will pushed out
> > right away. And to all those out there using production apps, please
> > feel invited to participate on the QA review and voting process for new
> > releases with reporting integration test results, because that helps us
> > to hunt down the real world issues before we consider a build GA.
> >
> > - René
> >
> > Jeromy Evans schrieb:
> >> Koen Serry wrote:
> >>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
> >>> client
> >>> side validations won't work....
> >>>
> >>
> >> Just a tip, if you're releasing a production app, you shouldn't be
> >> serving static resources from the struts2 dispatcher. Extract them and
> >> the problem is avoided.
> >>
> >> http://struts.apache.org/2.0.12/docs/performance-tuning.html
> >>
> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> Rainer Hermanns
> aixcept
> Willibrordstraße 82
> 52134 Herzogenrath - Germany
> w: http://aixcept.de/
> t: +49 - 2406 - 979 22 11
> f: +49 - 2406 - 979 22 13
> m: +49 - 170 - 343 29 12
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
Re: Struts2 and production apps
Posted by Rainer Hermanns <he...@aixcept.de>.
Hi,
xwork 2.0.7 is released and you can kick off the S2.0.14 release process.
I'd love to get more S2 developers into the XWork development process.
So, are there any S2 (or other interested) developers not yet involved in
XWork who'd like commit access? Please contact me by mail and I'll add
you.
Regarding current production apps, I'd go with 2.1.X from trunk for
development projects with a target release in 1-3 months and 2.0.14
(yet to be released) for production ready apps.
I have several projects running based on S2 2.1.X in production use, but
with some patches applied. These patches will soon be added to XWork 2.1.X
and go into the S2 2.1.X codebase.
As soon as my current project is finished in early December I will have
much more time to work on XWork and S2.1.X again.
Thanks,
Rainer
> I totally agree that this is currently a very bad situation. Jeromy's
> tip for static resources is a working fix for the 2.0.12 issue, as well
> as an uprgade to 2.0.13 testing version would be (this was no GA
> release). Please note that we fixed the static resource bug immediately
> when it was reported, and triggered the 2.0.13 build - but since there
> is still the conversion message issue, it will not become GA.
>
> For the needed 2.0.14, we are simply waiting on XWork to be released,
> because the said conversion error problem is not a Struts issue. The bug
> was fixed in XWork code immediately after reporting, but XWork has it's
> own release cycle. That's why it is not in our hand to get out a Struts
> 2.0.14 release candidate, which technically will be nothing more than a
> 2.0.13 with a current XWork build.
>
> I really hope that we will be getting a XWork release this weekend, and
> as soon as it is published, be sure that a 2.0.14 build will pushed out
> right away. And to all those out there using production apps, please
> feel invited to participate on the QA review and voting process for new
> releases with reporting integration test results, because that helps us
> to hunt down the real world issues before we consider a build GA.
>
> - René
>
> Jeromy Evans schrieb:
>> Koen Serry wrote:
>>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
>>> client
>>> side validations won't work....
>>>
>>
>> Just a tip, if you're releasing a production app, you shouldn't be
>> serving static resources from the struts2 dispatcher. Extract them and
>> the problem is avoided.
>>
>> http://struts.apache.org/2.0.12/docs/performance-tuning.html
>> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Rainer Hermanns
aixcept
Willibrordstraße 82
52134 Herzogenrath - Germany
w: http://aixcept.de/
t: +49 - 2406 - 979 22 11
f: +49 - 2406 - 979 22 13
m: +49 - 170 - 343 29 12
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Martin Cooper <ma...@apache.org>.
On Sat, Nov 15, 2008 at 12:01 PM, Struts Two <st...@yahoo.ca> wrote:
> I count not help myself not to ask the queston and still wonder why it was
> decided to build struts 2 on XWork instead of directing the effort to come
> up with struts 2 using something home grown technologies like Command chains
> ( that is currently used in struts 1.3 +). It makes u wonder what happens if
> XWORK for some reason or other goes out of commission and there are no
> releases. I do not see how struts 2 and xwork can be considered a merge to
> create a new framework (struts 2) while xwork is an independant and fully
> functional framework (when there is a merge, the merge results in 1 new
> entity with merging old entities are gone)
I think you are confusing XWork and WebWork. WebWork came to the ASF and
became the basis of Struts 2. WebWork was built on XWork, and hence Struts 2
is built on XWork. We did discuss having the XWork project come to the ASF
as well, but they elected to stay where they were. That, of course, is their
decision, and that's perfectly fine.
XWork is licensed under the OpenSymphony Software License, which is a
variant of the Apache License, so it is conceivable that we could fork XWork
and bring the fork in-house under Struts. The more our progress on Struts 2
is held up by waiting for releases of XWork, the more I think about this.
However, even if we forked it here, we would still need people to work on
it. We've had multiple offers (including just today) to add new committers
to XWork, but I don't think the situation has improved, and I'm not
convinced that would change if we forked it here.
--
Martin Cooper
> I have been an avid user of struts 1 for past few years and have switched
> to struts 2 to keep up with struts hype but I have not been able to run any
> project in my case on Websphere (except 2.0.11) with any struts 2 release.
> Struts 1 used to run like charm.
>
> regards,
>
>
> ----- Original Message ----
> From: Rene Gielen <rg...@apache.org>
> To: Struts Developers List <de...@struts.apache.org>
> Sent: Saturday, November 15, 2008 4:22:01 AM
> Subject: Re: Struts2 and production apps
>
> I totally agree that this is currently a very bad situation. Jeromy's tip
> for static resources is a working fix for the 2.0.12 issue, as well as an
> uprgade to 2.0.13 testing version would be (this was no GA release). Please
> note that we fixed the static resource bug immediately when it was reported,
> and triggered the 2.0.13 build - but since there is still the conversion
> message issue, it will not become GA.
>
> For the needed 2.0.14, we are simply waiting on XWork to be released,
> because the said conversion error problem is not a Struts issue. The bug was
> fixed in XWork code immediately after reporting, but XWork has it's own
> release cycle. That's why it is not in our hand to get out a Struts 2.0.14
> release candidate, which technically will be nothing more than a 2.0.13 with
> a current XWork build.
>
> I really hope that we will be getting a XWork release this weekend, and as
> soon as it is published, be sure that a 2.0.14 build will pushed out right
> away. And to all those out there using production apps, please feel invited
> to participate on the QA review and voting process for new releases with
> reporting integration test results, because that helps us to hunt down the
> real world issues before we consider a build GA.
>
> - René
>
> Jeromy Evans schrieb:
> > Koen Serry wrote:
> >> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
> client
> >> side validations won't work....
> >>
> >
> > Just a tip, if you're releasing a production app, you shouldn't be
> serving static resources from the struts2 dispatcher. Extract them and the
> problem is avoided.
> >
> > http://struts.apache.org/2.0.12/docs/performance-tuning.html
> >
> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
> __________________________________________________________________
> Looking for the perfect gift? Give the gift of Flickr!
>
> http://www.flickr.com/gift/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Struts2 and production apps
Posted by Rainer Hermanns <he...@aixcept.de>.
Great news, thanks for your interest!
Your patches and feedback have been very helpful in the past,
I'm looking forward to get more :)
You'll receive a private message soon...
cheers,
Rainer
> On Sun, 2008-11-16 at 00:31 +0100, Rainer Hermanns wrote:
> [snip]
>> I wouldn't have a problem to move over XWork to the ASF and I am pretty
>> sure some other XWork developers would vote +1 for this step, but just
>> bringing over a project to the ASF without new volunteer developers
>> wouldn't solve the mentioned issue.
>>
>> So, if I could see a better future for XWork at Apache, I'd love to go
>> this way, but this is not a task for two or three developers, but for a
>> larger community. If some developers would like to participate either at
>> OpenSymphony or in/after an incubation to ASF let me and others know,
>> you
>> are welcome and your help would be much appreciated.
>>
>
>
> Rainer, I've been working off of trunk for both xwork and s2 for the
> examples in my upcoming book. I've worked with the xwork codebase and
> posted a few patches. As you mentioned, we all have day jobs, and right
> now, I've got a night-job too (the book), but I'd like to be able to
> make patches/changes to xwork when I come across things. I am not
> suggesting that my patches take too long to make their way in (since you
> and Musachy have been keeping up enough to keep me happy), but if you
> want some more help, I wouldn't mind.
>
> -Wes
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Rainer Hermanns
aixcept
Willibrordstraße 82
52134 Herzogenrath - Germany
w: http://aixcept.de/
t: +49 - 2406 - 979 22 11
f: +49 - 2406 - 979 22 13
m: +49 - 170 - 343 29 12
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Wes Wannemacher <we...@wantii.com>.
On Sun, 2008-11-16 at 00:31 +0100, Rainer Hermanns wrote:
[snip]
> I wouldn't have a problem to move over XWork to the ASF and I am pretty
> sure some other XWork developers would vote +1 for this step, but just
> bringing over a project to the ASF without new volunteer developers
> wouldn't solve the mentioned issue.
>
> So, if I could see a better future for XWork at Apache, I'd love to go
> this way, but this is not a task for two or three developers, but for a
> larger community. If some developers would like to participate either at
> OpenSymphony or in/after an incubation to ASF let me and others know, you
> are welcome and your help would be much appreciated.
>
Rainer, I've been working off of trunk for both xwork and s2 for the
examples in my upcoming book. I've worked with the xwork codebase and
posted a few patches. As you mentioned, we all have day jobs, and right
now, I've got a night-job too (the book), but I'd like to be able to
make patches/changes to xwork when I come across things. I am not
suggesting that my patches take too long to make their way in (since you
and Musachy have been keeping up enough to keep me happy), but if you
want some more help, I wouldn't mind.
-Wes
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Musachy Barroso <mu...@gmail.com>.
I missed that. I added a link to it in the "Contributors guide" (
http://struts.apache.org/2.x/docs/contributors-guide.html)
musachy
On Sun, Nov 16, 2008 at 4:49 AM, Rainer Hermanns <he...@aixcept.de>wrote:
> Musachy,
>
> it is already documented here:
> http://wiki.opensymphony.com/display/XW/Creating+a+distribution
>
> The document task could easily be upgraded to the same static export
> mechanism as we use at Struts.
>
> Thanks,
> Rainer
>
> > I agree with Rainer, commit rights to xwork have been granted to S2
> > committers on-demand (like me), where the project is, I don't think
> > matters
> > much. I am set on getting periodic S2 builds out, and then I will try to
> > do
> > the same with XWork, first I need to get Rainer and Rene to document the
> > process ;), hint hint.
> > musachy
> >
> > On Sat, Nov 15, 2008 at 6:31 PM, Rainer Hermanns
> > <he...@aixcept.de>wrote:
> >
> >> It is not true, that there are no releases of XWork.
> >> True is, that the releases are not that frequent as required.
> >> Currently only Musachy and me are working on XWork and applying patches.
> >> Both of us are Struts2 core developers and PMC members, so you can be
> >> sure
> >> that there will be XWork releases as required.
> >> But please keep in mind, that we are all working on XWork and Struts2 in
> >> our spare time free of charge.
> >> There will be soon new release managers for XWork, so that one can step
> >> in
> >> as required and releases should come out more regular.
> >> However, this still requires time of the developers after, before or
> >> beside their daytime jobs.
> >>
> >> It would be of great help, if more users would test the nightly and
> >> alpha/beta builds of S2/XWork and give their vivid feedback on the dev
> >> or
> >> user list or even in Jira. I am pretty sure your mentioned problem with
> >> websphere would have been solved before a release.
> >> We need your feedback to make XWork and Struts2 better and to meet your
> >> needs. Patches are also very welcome and maybe you are interested in
> >> getting involved.
> >>
> >> I wouldn't have a problem to move over XWork to the ASF and I am pretty
> >> sure some other XWork developers would vote +1 for this step, but just
> >> bringing over a project to the ASF without new volunteer developers
> >> wouldn't solve the mentioned issue.
> >>
> >> So, if I could see a better future for XWork at Apache, I'd love to go
> >> this way, but this is not a task for two or three developers, but for a
> >> larger community. If some developers would like to participate either at
> >> OpenSymphony or in/after an incubation to ASF let me and others know,
> >> you
> >> are welcome and your help would be much appreciated.
> >>
> >>
> >> cheers,
> >> Rainer
> >>
> >>
> >>
> >> > I count not help myself not to ask the queston and still wonder why it
> >> was
> >> > decided to build struts 2 on XWork instead of directing the effort to
> >> come
> >> > up with struts 2 using something home grown technologies like Command
> >> > chains ( that is currently used in struts 1.3 +). It makes u wonder
> >> what
> >> > happens if XWORK for some reason or other goes out of commission and
> >> there
> >> > are no releases. I do not see how struts 2 and xwork can be considered
> >> a
> >> > merge to create a new framework (struts 2) while xwork is an
> >> independant
> >> > and fully functional framework (when there is a merge, the merge
> >> results
> >> > in 1 new entity with merging old entities are gone)
> >> >
> >> > I have been an avid user of struts 1 for past few years and have
> >> switched
> >> > to struts 2 to keep up with struts hype but I have not been able to
> >> run
> >> > any project in my case on Websphere (except 2.0.11) with any struts 2
> >> > release. Struts 1 used to run like charm.
> >> >
> >> > regards,
> >> >
> >> >
> >> > ----- Original Message ----
> >> > From: Rene Gielen <rg...@apache.org>
> >> > To: Struts Developers List <de...@struts.apache.org>
> >> > Sent: Saturday, November 15, 2008 4:22:01 AM
> >> > Subject: Re: Struts2 and production apps
> >> >
> >> > I totally agree that this is currently a very bad situation. Jeromy's
> >> tip
> >> > for static resources is a working fix for the 2.0.12 issue, as well as
> >> an
> >> > uprgade to 2.0.13 testing version would be (this was no GA release).
> >> > Please note that we fixed the static resource bug immediately when it
> >> was
> >> > reported, and triggered the 2.0.13 build - but since there is still
> >> the
> >> > conversion message issue, it will not become GA.
> >> >
> >> > For the needed 2.0.14, we are simply waiting on XWork to be released,
> >> > because the said conversion error problem is not a Struts issue. The
> >> bug
> >> > was fixed in XWork code immediately after reporting, but XWork has
> >> it's
> >> > own release cycle. That's why it is not in our hand to get out a
> >> Struts
> >> > 2.0.14 release candidate, which technically will be nothing more than
> >> a
> >> > 2.0.13 with a current XWork build.
> >> >
> >> > I really hope that we will be getting a XWork release this weekend,
> >> and
> >> as
> >> > soon as it is published, be sure that a 2.0.14 build will pushed out
> >> right
> >> > away. And to all those out there using production apps, please feel
> >> > invited to participate on the QA review and voting process for new
> >> > releases with reporting integration test results, because that helps
> >> us
> >> to
> >> > hunt down the real world issues before we consider a build GA.
> >> >
> >> > - René
> >> >
> >> > Jeromy Evans schrieb:
> >> >> Koen Serry wrote:
> >> >>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
> >> >>> client
> >> >>> side validations won't work....
> >> >>>
> >> >>
> >> >> Just a tip, if you're releasing a production app, you shouldn't be
> >> >> serving static resources from the struts2 dispatcher. Extract them
> >> and
> >> >> the problem is avoided.
> >> >>
> >> >> http://struts.apache.org/2.0.12/docs/performance-tuning.html
> >> >>
> >>
> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
> >> >>
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> >> For additional commands, e-mail: dev-help@struts.apache.org
> >> >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > For additional commands, e-mail: dev-help@struts.apache.org
> >> >
> >> >
> >> >
> __________________________________________________________________
> >> > Looking for the perfect gift? Give the gift of Flickr!
> >> >
> >> > http://www.flickr.com/gift/
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > For additional commands, e-mail: dev-help@struts.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Rainer Hermanns
> >> aixcept
> >> Willibrordstraße 82
> >> 52134 Herzogenrath - Germany
> >> w: http://aixcept.de/
> >> t: +49 - 2406 - 979 22 11
> >> f: +49 - 2406 - 979 22 13
> >> m: +49 - 170 - 343 29 12
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >>
> >
> >
> > --
> > "Hey you! Would you help me to carry the stone?" Pink Floyd
> >
>
>
> --
> Rainer Hermanns
> aixcept
> Willibrordstraße 82
> 52134 Herzogenrath - Germany
> w: http://aixcept.de/
> t: +49 - 2406 - 979 22 11
> f: +49 - 2406 - 979 22 13
> m: +49 - 170 - 343 29 12
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
Re: Struts2 and production apps
Posted by Rainer Hermanns <he...@aixcept.de>.
Musachy,
it is already documented here:
http://wiki.opensymphony.com/display/XW/Creating+a+distribution
The document task could easily be upgraded to the same static export
mechanism as we use at Struts.
Thanks,
Rainer
> I agree with Rainer, commit rights to xwork have been granted to S2
> committers on-demand (like me), where the project is, I don't think
> matters
> much. I am set on getting periodic S2 builds out, and then I will try to
> do
> the same with XWork, first I need to get Rainer and Rene to document the
> process ;), hint hint.
> musachy
>
> On Sat, Nov 15, 2008 at 6:31 PM, Rainer Hermanns
> <he...@aixcept.de>wrote:
>
>> It is not true, that there are no releases of XWork.
>> True is, that the releases are not that frequent as required.
>> Currently only Musachy and me are working on XWork and applying patches.
>> Both of us are Struts2 core developers and PMC members, so you can be
>> sure
>> that there will be XWork releases as required.
>> But please keep in mind, that we are all working on XWork and Struts2 in
>> our spare time free of charge.
>> There will be soon new release managers for XWork, so that one can step
>> in
>> as required and releases should come out more regular.
>> However, this still requires time of the developers after, before or
>> beside their daytime jobs.
>>
>> It would be of great help, if more users would test the nightly and
>> alpha/beta builds of S2/XWork and give their vivid feedback on the dev
>> or
>> user list or even in Jira. I am pretty sure your mentioned problem with
>> websphere would have been solved before a release.
>> We need your feedback to make XWork and Struts2 better and to meet your
>> needs. Patches are also very welcome and maybe you are interested in
>> getting involved.
>>
>> I wouldn't have a problem to move over XWork to the ASF and I am pretty
>> sure some other XWork developers would vote +1 for this step, but just
>> bringing over a project to the ASF without new volunteer developers
>> wouldn't solve the mentioned issue.
>>
>> So, if I could see a better future for XWork at Apache, I'd love to go
>> this way, but this is not a task for two or three developers, but for a
>> larger community. If some developers would like to participate either at
>> OpenSymphony or in/after an incubation to ASF let me and others know,
>> you
>> are welcome and your help would be much appreciated.
>>
>>
>> cheers,
>> Rainer
>>
>>
>>
>> > I count not help myself not to ask the queston and still wonder why it
>> was
>> > decided to build struts 2 on XWork instead of directing the effort to
>> come
>> > up with struts 2 using something home grown technologies like Command
>> > chains ( that is currently used in struts 1.3 +). It makes u wonder
>> what
>> > happens if XWORK for some reason or other goes out of commission and
>> there
>> > are no releases. I do not see how struts 2 and xwork can be considered
>> a
>> > merge to create a new framework (struts 2) while xwork is an
>> independant
>> > and fully functional framework (when there is a merge, the merge
>> results
>> > in 1 new entity with merging old entities are gone)
>> >
>> > I have been an avid user of struts 1 for past few years and have
>> switched
>> > to struts 2 to keep up with struts hype but I have not been able to
>> run
>> > any project in my case on Websphere (except 2.0.11) with any struts 2
>> > release. Struts 1 used to run like charm.
>> >
>> > regards,
>> >
>> >
>> > ----- Original Message ----
>> > From: Rene Gielen <rg...@apache.org>
>> > To: Struts Developers List <de...@struts.apache.org>
>> > Sent: Saturday, November 15, 2008 4:22:01 AM
>> > Subject: Re: Struts2 and production apps
>> >
>> > I totally agree that this is currently a very bad situation. Jeromy's
>> tip
>> > for static resources is a working fix for the 2.0.12 issue, as well as
>> an
>> > uprgade to 2.0.13 testing version would be (this was no GA release).
>> > Please note that we fixed the static resource bug immediately when it
>> was
>> > reported, and triggered the 2.0.13 build - but since there is still
>> the
>> > conversion message issue, it will not become GA.
>> >
>> > For the needed 2.0.14, we are simply waiting on XWork to be released,
>> > because the said conversion error problem is not a Struts issue. The
>> bug
>> > was fixed in XWork code immediately after reporting, but XWork has
>> it's
>> > own release cycle. That's why it is not in our hand to get out a
>> Struts
>> > 2.0.14 release candidate, which technically will be nothing more than
>> a
>> > 2.0.13 with a current XWork build.
>> >
>> > I really hope that we will be getting a XWork release this weekend,
>> and
>> as
>> > soon as it is published, be sure that a 2.0.14 build will pushed out
>> right
>> > away. And to all those out there using production apps, please feel
>> > invited to participate on the QA review and voting process for new
>> > releases with reporting integration test results, because that helps
>> us
>> to
>> > hunt down the real world issues before we consider a build GA.
>> >
>> > - René
>> >
>> > Jeromy Evans schrieb:
>> >> Koen Serry wrote:
>> >>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
>> >>> client
>> >>> side validations won't work....
>> >>>
>> >>
>> >> Just a tip, if you're releasing a production app, you shouldn't be
>> >> serving static resources from the struts2 dispatcher. Extract them
>> and
>> >> the problem is avoided.
>> >>
>> >> http://struts.apache.org/2.0.12/docs/performance-tuning.html
>> >>
>> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> >> For additional commands, e-mail: dev-help@struts.apache.org
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > For additional commands, e-mail: dev-help@struts.apache.org
>> >
>> >
>> > __________________________________________________________________
>> > Looking for the perfect gift? Give the gift of Flickr!
>> >
>> > http://www.flickr.com/gift/
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > For additional commands, e-mail: dev-help@struts.apache.org
>> >
>> >
>>
>>
>> --
>> Rainer Hermanns
>> aixcept
>> Willibrordstraße 82
>> 52134 Herzogenrath - Germany
>> w: http://aixcept.de/
>> t: +49 - 2406 - 979 22 11
>> f: +49 - 2406 - 979 22 13
>> m: +49 - 170 - 343 29 12
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
> --
> "Hey you! Would you help me to carry the stone?" Pink Floyd
>
--
Rainer Hermanns
aixcept
Willibrordstraße 82
52134 Herzogenrath - Germany
w: http://aixcept.de/
t: +49 - 2406 - 979 22 11
f: +49 - 2406 - 979 22 13
m: +49 - 170 - 343 29 12
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Musachy Barroso <mu...@gmail.com>.
I agree with Rainer, commit rights to xwork have been granted to S2
committers on-demand (like me), where the project is, I don't think matters
much. I am set on getting periodic S2 builds out, and then I will try to do
the same with XWork, first I need to get Rainer and Rene to document the
process ;), hint hint.
musachy
On Sat, Nov 15, 2008 at 6:31 PM, Rainer Hermanns <he...@aixcept.de>wrote:
> It is not true, that there are no releases of XWork.
> True is, that the releases are not that frequent as required.
> Currently only Musachy and me are working on XWork and applying patches.
> Both of us are Struts2 core developers and PMC members, so you can be sure
> that there will be XWork releases as required.
> But please keep in mind, that we are all working on XWork and Struts2 in
> our spare time free of charge.
> There will be soon new release managers for XWork, so that one can step in
> as required and releases should come out more regular.
> However, this still requires time of the developers after, before or
> beside their daytime jobs.
>
> It would be of great help, if more users would test the nightly and
> alpha/beta builds of S2/XWork and give their vivid feedback on the dev or
> user list or even in Jira. I am pretty sure your mentioned problem with
> websphere would have been solved before a release.
> We need your feedback to make XWork and Struts2 better and to meet your
> needs. Patches are also very welcome and maybe you are interested in
> getting involved.
>
> I wouldn't have a problem to move over XWork to the ASF and I am pretty
> sure some other XWork developers would vote +1 for this step, but just
> bringing over a project to the ASF without new volunteer developers
> wouldn't solve the mentioned issue.
>
> So, if I could see a better future for XWork at Apache, I'd love to go
> this way, but this is not a task for two or three developers, but for a
> larger community. If some developers would like to participate either at
> OpenSymphony or in/after an incubation to ASF let me and others know, you
> are welcome and your help would be much appreciated.
>
>
> cheers,
> Rainer
>
>
>
> > I count not help myself not to ask the queston and still wonder why it
> was
> > decided to build struts 2 on XWork instead of directing the effort to
> come
> > up with struts 2 using something home grown technologies like Command
> > chains ( that is currently used in struts 1.3 +). It makes u wonder what
> > happens if XWORK for some reason or other goes out of commission and
> there
> > are no releases. I do not see how struts 2 and xwork can be considered a
> > merge to create a new framework (struts 2) while xwork is an independant
> > and fully functional framework (when there is a merge, the merge results
> > in 1 new entity with merging old entities are gone)
> >
> > I have been an avid user of struts 1 for past few years and have switched
> > to struts 2 to keep up with struts hype but I have not been able to run
> > any project in my case on Websphere (except 2.0.11) with any struts 2
> > release. Struts 1 used to run like charm.
> >
> > regards,
> >
> >
> > ----- Original Message ----
> > From: Rene Gielen <rg...@apache.org>
> > To: Struts Developers List <de...@struts.apache.org>
> > Sent: Saturday, November 15, 2008 4:22:01 AM
> > Subject: Re: Struts2 and production apps
> >
> > I totally agree that this is currently a very bad situation. Jeromy's tip
> > for static resources is a working fix for the 2.0.12 issue, as well as an
> > uprgade to 2.0.13 testing version would be (this was no GA release).
> > Please note that we fixed the static resource bug immediately when it was
> > reported, and triggered the 2.0.13 build - but since there is still the
> > conversion message issue, it will not become GA.
> >
> > For the needed 2.0.14, we are simply waiting on XWork to be released,
> > because the said conversion error problem is not a Struts issue. The bug
> > was fixed in XWork code immediately after reporting, but XWork has it's
> > own release cycle. That's why it is not in our hand to get out a Struts
> > 2.0.14 release candidate, which technically will be nothing more than a
> > 2.0.13 with a current XWork build.
> >
> > I really hope that we will be getting a XWork release this weekend, and
> as
> > soon as it is published, be sure that a 2.0.14 build will pushed out
> right
> > away. And to all those out there using production apps, please feel
> > invited to participate on the QA review and voting process for new
> > releases with reporting integration test results, because that helps us
> to
> > hunt down the real world issues before we consider a build GA.
> >
> > - René
> >
> > Jeromy Evans schrieb:
> >> Koen Serry wrote:
> >>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
> >>> client
> >>> side validations won't work....
> >>>
> >>
> >> Just a tip, if you're releasing a production app, you shouldn't be
> >> serving static resources from the struts2 dispatcher. Extract them and
> >> the problem is avoided.
> >>
> >> http://struts.apache.org/2.0.12/docs/performance-tuning.html
> >>
> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
> > __________________________________________________________________
> > Looking for the perfect gift? Give the gift of Flickr!
> >
> > http://www.flickr.com/gift/
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> Rainer Hermanns
> aixcept
> Willibrordstraße 82
> 52134 Herzogenrath - Germany
> w: http://aixcept.de/
> t: +49 - 2406 - 979 22 11
> f: +49 - 2406 - 979 22 13
> m: +49 - 170 - 343 29 12
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
Re: Struts2 and production apps
Posted by Rene Gielen <gi...@it-neering.net>.
The main problem for the XWork releases needed for the last Struts2 GA
versions was not that we had no patches in place for XWork specific
issues and enhancements, but to have an official release built and
pushed out. Since the opensymphony infrastucture clearly divides between
a developer and a release manager role, the problems arise when the few
release managers are hooked up by their day jobs and RL issues, which of
course always has to have priority over the volunteer work.
I think we are now seeing improvement on that issue in a first step with
the plan to grant more developers working on both projects the release
manager role on opensymphony, and that will help a lot for future
release cycles.
For a possible move of XWork to Apache, one of the pros would be that we
would not face such a problem any more, since the Apache infrastruture
enables any project commiter to do a release process. On the other hand,
I don't expect the commits to reach new peaks just by having XWork moved
over, and the incubation process is a time consuming business, as I
recall it from the WW incubation.
If we would come now into calmer waters when the Struts 2.0.14 build
will be pushed out today and hopefully proves to provide the stability
and production readiness we are all waiting for, the next big step would
be to regain momentum on the 2.1 release, and I personally plan to help
out on that topic on both the Stuts and XWork side.
- Rene
Rainer Hermanns schrieb:
> It is not true, that there are no releases of XWork.
> True is, that the releases are not that frequent as required.
> Currently only Musachy and me are working on XWork and applying patches.
> Both of us are Struts2 core developers and PMC members, so you can be sure
> that there will be XWork releases as required.
> But please keep in mind, that we are all working on XWork and Struts2 in
> our spare time free of charge.
> There will be soon new release managers for XWork, so that one can step in
> as required and releases should come out more regular.
> However, this still requires time of the developers after, before or
> beside their daytime jobs.
>
> It would be of great help, if more users would test the nightly and
> alpha/beta builds of S2/XWork and give their vivid feedback on the dev or
> user list or even in Jira. I am pretty sure your mentioned problem with
> websphere would have been solved before a release.
> We need your feedback to make XWork and Struts2 better and to meet your
> needs. Patches are also very welcome and maybe you are interested in
> getting involved.
>
> I wouldn't have a problem to move over XWork to the ASF and I am pretty
> sure some other XWork developers would vote +1 for this step, but just
> bringing over a project to the ASF without new volunteer developers
> wouldn't solve the mentioned issue.
>
> So, if I could see a better future for XWork at Apache, I'd love to go
> this way, but this is not a task for two or three developers, but for a
> larger community. If some developers would like to participate either at
> OpenSymphony or in/after an incubation to ASF let me and others know, you
> are welcome and your help would be much appreciated.
>
>
> cheers,
> Rainer
>
>
>
>> I count not help myself not to ask the queston and still wonder why it was
>> decided to build struts 2 on XWork instead of directing the effort to come
>> up with struts 2 using something home grown technologies like Command
>> chains ( that is currently used in struts 1.3 +). It makes u wonder what
>> happens if XWORK for some reason or other goes out of commission and there
>> are no releases. I do not see how struts 2 and xwork can be considered a
>> merge to create a new framework (struts 2) while xwork is an independant
>> and fully functional framework (when there is a merge, the merge results
>> in 1 new entity with merging old entities are gone)
>>
>> I have been an avid user of struts 1 for past few years and have switched
>> to struts 2 to keep up with struts hype but I have not been able to run
>> any project in my case on Websphere (except 2.0.11) with any struts 2
>> release. Struts 1 used to run like charm.
>>
>> regards,
>>
>>
>> ----- Original Message ----
>> From: Rene Gielen <rg...@apache.org>
>> To: Struts Developers List <de...@struts.apache.org>
>> Sent: Saturday, November 15, 2008 4:22:01 AM
>> Subject: Re: Struts2 and production apps
>>
>> I totally agree that this is currently a very bad situation. Jeromy's tip
>> for static resources is a working fix for the 2.0.12 issue, as well as an
>> uprgade to 2.0.13 testing version would be (this was no GA release).
>> Please note that we fixed the static resource bug immediately when it was
>> reported, and triggered the 2.0.13 build - but since there is still the
>> conversion message issue, it will not become GA.
>>
>> For the needed 2.0.14, we are simply waiting on XWork to be released,
>> because the said conversion error problem is not a Struts issue. The bug
>> was fixed in XWork code immediately after reporting, but XWork has it's
>> own release cycle. That's why it is not in our hand to get out a Struts
>> 2.0.14 release candidate, which technically will be nothing more than a
>> 2.0.13 with a current XWork build.
>>
>> I really hope that we will be getting a XWork release this weekend, and as
>> soon as it is published, be sure that a 2.0.14 build will pushed out right
>> away. And to all those out there using production apps, please feel
>> invited to participate on the QA review and voting process for new
>> releases with reporting integration test results, because that helps us to
>> hunt down the real world issues before we consider a build GA.
>>
>> - René
>>
>> Jeromy Evans schrieb:
>>> Koen Serry wrote:
>>>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
>>>> client
>>>> side validations won't work....
>>>>
>>> Just a tip, if you're releasing a production app, you shouldn't be
>>> serving static resources from the struts2 dispatcher. Extract them and
>>> the problem is avoided.
>>>
>>> http://struts.apache.org/2.0.12/docs/performance-tuning.html
>>> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>> __________________________________________________________________
>> Looking for the perfect gift? Give the gift of Flickr!
>>
>> http://www.flickr.com/gift/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Rainer Hermanns <he...@aixcept.de>.
It is not true, that there are no releases of XWork.
True is, that the releases are not that frequent as required.
Currently only Musachy and me are working on XWork and applying patches.
Both of us are Struts2 core developers and PMC members, so you can be sure
that there will be XWork releases as required.
But please keep in mind, that we are all working on XWork and Struts2 in
our spare time free of charge.
There will be soon new release managers for XWork, so that one can step in
as required and releases should come out more regular.
However, this still requires time of the developers after, before or
beside their daytime jobs.
It would be of great help, if more users would test the nightly and
alpha/beta builds of S2/XWork and give their vivid feedback on the dev or
user list or even in Jira. I am pretty sure your mentioned problem with
websphere would have been solved before a release.
We need your feedback to make XWork and Struts2 better and to meet your
needs. Patches are also very welcome and maybe you are interested in
getting involved.
I wouldn't have a problem to move over XWork to the ASF and I am pretty
sure some other XWork developers would vote +1 for this step, but just
bringing over a project to the ASF without new volunteer developers
wouldn't solve the mentioned issue.
So, if I could see a better future for XWork at Apache, I'd love to go
this way, but this is not a task for two or three developers, but for a
larger community. If some developers would like to participate either at
OpenSymphony or in/after an incubation to ASF let me and others know, you
are welcome and your help would be much appreciated.
cheers,
Rainer
> I count not help myself not to ask the queston and still wonder why it was
> decided to build struts 2 on XWork instead of directing the effort to come
> up with struts 2 using something home grown technologies like Command
> chains ( that is currently used in struts 1.3 +). It makes u wonder what
> happens if XWORK for some reason or other goes out of commission and there
> are no releases. I do not see how struts 2 and xwork can be considered a
> merge to create a new framework (struts 2) while xwork is an independant
> and fully functional framework (when there is a merge, the merge results
> in 1 new entity with merging old entities are gone)
>
> I have been an avid user of struts 1 for past few years and have switched
> to struts 2 to keep up with struts hype but I have not been able to run
> any project in my case on Websphere (except 2.0.11) with any struts 2
> release. Struts 1 used to run like charm.
>
> regards,
>
>
> ----- Original Message ----
> From: Rene Gielen <rg...@apache.org>
> To: Struts Developers List <de...@struts.apache.org>
> Sent: Saturday, November 15, 2008 4:22:01 AM
> Subject: Re: Struts2 and production apps
>
> I totally agree that this is currently a very bad situation. Jeromy's tip
> for static resources is a working fix for the 2.0.12 issue, as well as an
> uprgade to 2.0.13 testing version would be (this was no GA release).
> Please note that we fixed the static resource bug immediately when it was
> reported, and triggered the 2.0.13 build - but since there is still the
> conversion message issue, it will not become GA.
>
> For the needed 2.0.14, we are simply waiting on XWork to be released,
> because the said conversion error problem is not a Struts issue. The bug
> was fixed in XWork code immediately after reporting, but XWork has it's
> own release cycle. That's why it is not in our hand to get out a Struts
> 2.0.14 release candidate, which technically will be nothing more than a
> 2.0.13 with a current XWork build.
>
> I really hope that we will be getting a XWork release this weekend, and as
> soon as it is published, be sure that a 2.0.14 build will pushed out right
> away. And to all those out there using production apps, please feel
> invited to participate on the QA review and voting process for new
> releases with reporting integration test results, because that helps us to
> hunt down the real world issues before we consider a build GA.
>
> - René
>
> Jeromy Evans schrieb:
>> Koen Serry wrote:
>>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
>>> client
>>> side validations won't work....
>>>
>>
>> Just a tip, if you're releasing a production app, you shouldn't be
>> serving static resources from the struts2 dispatcher. Extract them and
>> the problem is avoided.
>>
>> http://struts.apache.org/2.0.12/docs/performance-tuning.html
>> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
> __________________________________________________________________
> Looking for the perfect gift? Give the gift of Flickr!
>
> http://www.flickr.com/gift/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Rainer Hermanns
aixcept
Willibrordstraße 82
52134 Herzogenrath - Germany
w: http://aixcept.de/
t: +49 - 2406 - 979 22 11
f: +49 - 2406 - 979 22 13
m: +49 - 170 - 343 29 12
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Dave Newton <ne...@yahoo.com>.
--- On Sat, 11/15/08, Struts Two <st...@yahoo.ca> wrote:
> It makes u wonder what happens if XWORK for some reason or
> other goes out of commission and there are no releases.
Besides the fact that there are a few S2 committers who are also XWork committers I think you've misunderstood how open source works.
The XWork license is derived from, and compatible with, the Apache license. The version of XWork being used by S2 will never "disappear" in a meaningful way.
> I have been an avid user of struts 1 for past few years and
> have switched to struts 2 to keep up with struts hype but I
> have not been able to run any project in my case on
> Websphere (except 2.0.11) with any struts 2 release.
That's weird; we're running multiple S2 apps on WebSphere and have been for some time (i.e. pre-2.0.11, although I think that's what we're running now).
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Struts Two <st...@yahoo.ca>.
I count not help myself not to ask the queston and still wonder why it was decided to build struts 2 on XWork instead of directing the effort to come up with struts 2 using something home grown technologies like Command chains ( that is currently used in struts 1.3 +). It makes u wonder what happens if XWORK for some reason or other goes out of commission and there are no releases. I do not see how struts 2 and xwork can be considered a merge to create a new framework (struts 2) while xwork is an independant and fully functional framework (when there is a merge, the merge results in 1 new entity with merging old entities are gone)
I have been an avid user of struts 1 for past few years and have switched to struts 2 to keep up with struts hype but I have not been able to run any project in my case on Websphere (except 2.0.11) with any struts 2 release. Struts 1 used to run like charm.
regards,
----- Original Message ----
From: Rene Gielen <rg...@apache.org>
To: Struts Developers List <de...@struts.apache.org>
Sent: Saturday, November 15, 2008 4:22:01 AM
Subject: Re: Struts2 and production apps
I totally agree that this is currently a very bad situation. Jeromy's tip for static resources is a working fix for the 2.0.12 issue, as well as an uprgade to 2.0.13 testing version would be (this was no GA release). Please note that we fixed the static resource bug immediately when it was reported, and triggered the 2.0.13 build - but since there is still the conversion message issue, it will not become GA.
For the needed 2.0.14, we are simply waiting on XWork to be released, because the said conversion error problem is not a Struts issue. The bug was fixed in XWork code immediately after reporting, but XWork has it's own release cycle. That's why it is not in our hand to get out a Struts 2.0.14 release candidate, which technically will be nothing more than a 2.0.13 with a current XWork build.
I really hope that we will be getting a XWork release this weekend, and as soon as it is published, be sure that a 2.0.14 build will pushed out right away. And to all those out there using production apps, please feel invited to participate on the QA review and voting process for new releases with reporting integration test results, because that helps us to hunt down the real world issues before we consider a build GA.
- René
Jeromy Evans schrieb:
> Koen Serry wrote:
>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all client
>> side validations won't work....
>>
>
> Just a tip, if you're releasing a production app, you shouldn't be serving static resources from the struts2 dispatcher. Extract them and the problem is avoided.
>
> http://struts.apache.org/2.0.12/docs/performance-tuning.html
> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Rene Gielen <rg...@apache.org>.
I totally agree that this is currently a very bad situation. Jeromy's
tip for static resources is a working fix for the 2.0.12 issue, as well
as an uprgade to 2.0.13 testing version would be (this was no GA
release). Please note that we fixed the static resource bug immediately
when it was reported, and triggered the 2.0.13 build - but since there
is still the conversion message issue, it will not become GA.
For the needed 2.0.14, we are simply waiting on XWork to be released,
because the said conversion error problem is not a Struts issue. The bug
was fixed in XWork code immediately after reporting, but XWork has it's
own release cycle. That's why it is not in our hand to get out a Struts
2.0.14 release candidate, which technically will be nothing more than a
2.0.13 with a current XWork build.
I really hope that we will be getting a XWork release this weekend, and
as soon as it is published, be sure that a 2.0.14 build will pushed out
right away. And to all those out there using production apps, please
feel invited to participate on the QA review and voting process for new
releases with reporting integration test results, because that helps us
to hunt down the real world issues before we consider a build GA.
- René
Jeromy Evans schrieb:
> Koen Serry wrote:
>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all
>> client
>> side validations won't work....
>>
>
> Just a tip, if you're releasing a production app, you shouldn't be
> serving static resources from the struts2 dispatcher. Extract them and
> the problem is avoided.
>
> http://struts.apache.org/2.0.12/docs/performance-tuning.html
> http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts2 and production apps
Posted by Jeromy Evans <je...@blueskyminds.com.au>.
Koen Serry wrote:
> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all client
> side validations won't work....
>
Just a tip, if you're releasing a production app, you shouldn't be
serving static resources from the struts2 dispatcher. Extract them and
the problem is avoided.
http://struts.apache.org/2.0.12/docs/performance-tuning.html
http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org