You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Brian Pontarelli <br...@pontarelli.com> on 2007/02/08 01:04:30 UTC

Structs 2 feedback

Hey all. I wanted to drop the developers a few notes regarding my recent 
experience with Struts2. I've been a Struts/WebWork user for quite some 
time and recently attempted a stab at the Struts 2 switch because I'm 
planning on using Struts 2 for building client sites for the company I 
work for. Also, I definitely am trying to be very constructive and if I 
come off badly I do apologize. Okay on to the info:

1. Arrived at the Struts homepage and Struts 2 almost looked dead. No 
activity since October and no news or release information. Adding some 
news every few weeks will help keep new comers from bailing.

2. Tried to download the release using the release navigation. Here I 
was presented with the fact that there was a 2.0.1 BETA, which is the 
latest development release. I spent the next while looking for the 2.0.0 
release, figuring that was the last stable release. Couldn't find it 
obviously. The versioning currently looks to the outside to be a 
complete mess and it is very confusing and non standard. I would not 
release a patch version (major.minor.patch) until the major version is 
released. Therefore all the references to 2.0.1 through 2.0.6 are very 
confusing because these are not really final releases, but all BETAs. 
Plus, there is talk about 2.0.1 BETA and 2.0.4 and 2.0.6 and this is all 
quite confusing. I would probably fix the version into a standard alpha, 
beta, release candidate model. So, currently it would be something like 
2.0.0-RC6 or the like working towards a final release of 2.0.0.

3. The documentation for Struts 2 contains references to zero 
configuration and the web.xml configuration file also contains this 
stuff. There are also a number of references to all the annotations. 
These are not available in the 2.0.1BETA JAR files and therefore I had a 
hard time using them ;) I did find them in the nightly snapshots, which 
aren't functional. I would keep the documentation inline with the latest 
beta and not the latest nightly snapshot. Anyone who wants bleeding edge 
will be willing to look at the source to see new stuff or build the 
latest snapshot docs themselves.

4. The tutorials reference a hybrid of WebWork 2 configuration, classes, 
tags and files and Struts2 configuration and files. This would 
definitely be confusing for a newcomer. I would probably keep the 
tutorials using only struts2 configuration, classes, tags and files 
since that is what the latest beta release uses. I would in turn direct 
folks to the WebWork wiki for running WebWork 2 if they don't want to 
use the BETA release.

5. There is really no getting started document for Struts2. It would be 
a bit of a stumbling block for a newcomer to have various JAR files in 
the distribution without any clue on which to use or what the 
'struts2-all' jar contains. There should be a true Struts2 getting 
started document that contains a complete step by step to getting an 
application running. This could start with the CRUD made easy tutorial 
for WW2 and make it more complete for Struts2.

6. From the guide perspective, it is very difficult to figure out how to 
write actions. This information is buried in the Struts Configuration 
Elements guide and in the Action Configuration guide under that. In fact 
many of the top level and nested guides are a bit confusing and don't 
necessarily follow the standard path developers will take when getting 
started as well as when trying new things. The top level components 
should be items will be working on when building an application such as 
AJAX, Actions, Validation, etc. rather than items like "Struts 
Configuration Elements" Under these headings would be the configuration, 
the code, the interfaces, examples, etc. This will be how most folks are 
going to be using Struts2. They'll be creating an action, adding 
validation, handling action results, adding interceptors, etc. There are 
a number of guides that are on the right track.

7. I had a bit of trouble figuring out how to grab the code because the 
link is on the main Struts page. Adding a link to the Struts2 page will 
help a lot.

8. Running the unit tests from the subversion repository causes out of 
memory errors on my machine using the standard 16M of memory that maven 
defaults to run with. I found that after the tests had run it required 
almost 150M of memory to run the tests. I gave maven 512M, but this was 
a stumbling block. This seems like a rather incorrect behavior for tests 
since after each test there should be very little on the heap. Is there 
a memory leak or some reason very large objects are hanging about?

9. This is a bit nit picky.... The current code in subversion is broken 
therefore I was unable to run from sources. One of the things I really 
like about many frameworks I've worked with and coded on was the fact 
that a clean checkout was almost guaranteed to compile, test and run. 
This helps a lot for folks that want the bleeding edge and to start 
contributing.

I'll try to keep looking around in source code and grabbing the latest 
code to see how things are progressing. I'm also slated to have a large 
amount of time at work devoted to getting the companies frameworks and 
documentation up to the newest architecture I've created and would be 
willing to help on Struts 2 work whenever possible. I'm particularly 
interested in minimizing ramp up time as well as making application 
development time minimal (zero config kinda stuff).

Thanks,
Brian Pontarelli


Re: Structs 2 feedback

Posted by Philip Luppens <ph...@gmail.com>.
Musachy,

Sure, no problem. I'll contact you off-list. Thanks !

Cheers,

Phil

On 2/9/07, Musachy Barroso <mu...@gmail.com> wrote:
> Instead of complaining I will actually do something :). Let me know where
> you are going to set this up on the wiki so I can help you.
>
> regards
> musachy
>
> On 2/9/07, Philip Luppens <ph...@gmail.com> wrote:
> >
> > I've assigned some documentation issues to myself. I'm starting this
> > weekend on a User Guide (blatantly copying the structure from Struts 1
> > where appropriate). The CRUD tutorial from WW has been on my todo list
> > for a long time, I'll take care of it.
> >
> > Phil
> >
> > On 2/9/07, Ted Husted <hu...@apache.org> wrote:
> > > On 2/7/07, Brian Pontarelli <br...@pontarelli.com> wrote:
> > > >
> > > > 1. Arrived at the Struts homepage and Struts 2 almost looked dead. No
> > > > activity since October and no news or release information. Adding some
> > > > news every few weeks will help keep new comers from bailing.
> > >
> > > There is now  a link to a browseable archive of User Mailing List to
> > > the top of the page, which is where a lot of the action happens :)
> > >
> > > Other than the same old, same old, there really hasn't been much news,
> > > except the XWork 2.0.0 release. I added a mention of that on a trial
> > > basis. But, I'm not sure if we want to announce other people's
> > > releases here or not.
> > >
> > > We've been creating test builds, but those were not ready for
> > > consumption by the general public, and citing them on the welcome page
> > > would be inappropriate. Happily, now that we have a stable XWork 2,
> > > the perpetual-beta state should change, and there will be more to
> > > announce!
> > >
> > >
> > > > 2. Tried to download the release using the release navigation. Here I
> > > > was presented with the fact that there was a 2.0.1 BETA, which is the
> > > > latest development release. I spent the next while looking for the
> > 2.0.0
> > > > release, figuring that was the last stable release. Couldn't find it
> > > > obviously. The versioning currently looks to the outside to be a
> > > > complete mess and it is very confusing and non standard. I would not
> > > > release a patch version (major.minor.patch) until the major version is
> > > > released. Therefore all the references to 2.0.1 through 2.0.6 are very
> > > > confusing because these are not really final releases, but all BETAs.
> > > > Plus, there is talk about 2.0.1 BETA and 2.0.4 and 2.0.6 and this is
> > all
> > > > quite confusing. I would probably fix the version into a standard
> > alpha,
> > > > beta, release candidate model. So, currently it would be something
> > like
> > > > 2.0.0-RC6 or the like working towards a final release of 2.0.0.
> > >
> > > There's a new FAQ, with a link from the release page.
> > >
> > >  * http://struts.apache.org/kickstart.html#releases
> > >
> > > Much of this is driven by the need to track changes to the codebase as
> > > it is being developed, live and direct. We also do not keep internal
> > > versions or secret roadmaps. What's on the web site is our one and
> > > only copy of everything.
> > >
> > > In practice, we don't do "final" releases, because in an active
> > > development environment, nothing is ever really final. A particular
> > > set of bits may be good enough for public consumption, but we reserve
> > > the right to make backwardly compatible changes to a release series,
> > > and to use the simplest possible versioning system: straight
> > > milestones that also represent tags in the code repository.
> > >
> > >
> > > >
> > > > 3. The documentation for Struts 2 contains references to zero
> > > > configuration and the web.xml configuration file also contains this
> > > > stuff. There are also a number of references to all the annotations.
> > > > These are not available in the 2.0.1BETA JAR files and therefore I had
> > a
> > > > hard time using them ;) I did find them in the nightly snapshots,
> > which
> > > > aren't functional. I would keep the documentation inline with the
> > latest
> > > > beta and not the latest nightly snapshot. Anyone who wants bleeding
> > edge
> > > > will be willing to look at the source to see new stuff or build the
> > > > latest snapshot docs themselves.
> > >
> > > Once Struts 2 has a GA release, it will be archived on the site, along
> > > with all the others (Struts 1.35, Struts 1.2.9, et cetera, going all
> > > the way back to Struts 1.0).  Then, the Struts 2 links will point that
> > > archive rather than the draft site. But, right now, it's a chicken and
> > > egg scenario.
> > >
> > > We haven't been publishing archives of betas on the web site, because,
> > > well, they're betas, and the full documentation for the beta is
> > > included in the download. Though, since most beta to end up being GA
> > > releases, perhaps we should start archiving the docs for a version as
> > > soon as it goes beta.
> > >
> > > In the meantime, what is on the site is the draft documentation for
> > > the nightly build, which will become the next milestone. Last week,
> > > that was Struts 2.0.5-DEV, and now it's Struts 2.0.6-DEV.
> > >
> > > Again, this is our one and only website. This is the site that we use
> > > to create the next release, and so it has to contain whatever we want
> > > the upcoming release to include. I wish we had the resources to
> > > maintain a second development site, but, AFAIK, everyone here is a
> > > volunteer, working in our unpaid, spare time.
> > >
> > >
> > > > 4. The tutorials reference a hybrid of WebWork 2 configuration,
> > classes,
> > > > tags and files and Struts2 configuration and files. This would
> > > > definitely be confusing for a newcomer. I would probably keep the
> > > > tutorials using only struts2 configuration, classes, tags and files
> > > > since that is what the latest beta release uses. I would in turn
> > direct
> > > > folks to the WebWork wiki for running WebWork 2 if they don't want to
> > > > use the BETA release.
> > >
> > > We adopted the WebWork documentation, along with the codebase. Our
> > > intention has been to replace references to WebWork classes with the
> > > corresponding reference to Struts 2 classes.
> > >
> > > Do you mean hybrid of Struts 2 and XWork classes?
> > >
> > > If so, we really don't know what to do about that. We depend on XWork
> > > as a base platform, the same way many frameworks depend on Java's
> > > HTTP.
> > >
> > >
> > > > 5. There is really no getting started document for Struts2. It would
> > be
> > > > a bit of a stumbling block for a newcomer to have various JAR files in
> > > > the distribution without any clue on which to use or what the
> > > > 'struts2-all' jar contains. There should be a true Struts2 getting
> > > > started document that contains a complete step by step to getting an
> > > > application running. This could start with the CRUD made easy tutorial
> > > > for WW2 and make it more complete for Struts2.
> > >
> > > There's now a "Impatient?" link at the top of the Getting Started page
> > > pointing to the Bootstrap tutorial and MailReader Tour. The
> > > PlanetStruts site is down right now, but I'll take care of that after
> > > work tonight, before announcing the new beta to the user list.
> > >
> > > Yes, it would be great if someone ported the CRUD tutorial for WW2 and
> > > made it more complete for Struts 2. Any responsible person who files a
> > > CLA is welcome to work on the documentation.
> > >
> > > * http://www.apache.org/licenses/icla.txt
> > >
> > >
> > > > 6. From the guide perspective, it is very difficult to figure out how
> > to
> > > > write actions. This information is buried in the Struts Configuration
> > > > Elements guide and in the Action Configuration guide under that. In
> > fact
> > > > many of the top level and nested guides are a bit confusing and don't
> > > > necessarily follow the standard path developers will take when getting
> > > > started as well as when trying new things. The top level components
> > > > should be items will be working on when building an application such
> > as
> > > > AJAX, Actions, Validation, etc. rather than items like "Struts
> > > > Configuration Elements" Under these headings would be the
> > configuration,
> > > > the code, the interfaces, examples, etc. This will be how most folks
> > are
> > > > going to be using Struts2. They'll be creating an action, adding
> > > > validation, handling action results, adding interceptors, etc. There
> > are
> > > > a number of guides that are on the right track.
> > >
> > > Yes, we could really use some help here. We started with the WW wiki,
> > > and I think we've made some progress, but there is still much to be
> > > done. I did as much as I could over the summer, but unfortunately,
> > > it's not something I can spend much time on myself this year.
> > > Hopefully, someone will pickup the torch.
> > >
> > > Again, any responsible person who files a CLA is welcome to help with
> > > the documentation.
> > >
> > >
> > > > 7. I had a bit of trouble figuring out how to grab the code because
> > the
> > > > link is on the main Struts page. Adding a link to the Struts2 page
> > will
> > > > help a lot.
> > >
> > > We didn't do that at first since most of the development materials are
> > > under site, and so would not be in the Struts 2 documentation bundle.
> > > But, I copied the development menu over and made the links absolute.
> > >
> > > Thanks for the feedback!. It's already lead to several positive changes.
> > >
> > > -Ted.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
> >
> > --
> > iDTV System Engineer
> > "Always code as if the guy who ends up maintaining your code will be a
> > violent psychopath who knows where you live." - John F. Woods
> >
> > ---------------------------------------------------------------------
> > 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
>


-- 
iDTV System Engineer
"Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live." - John F. Woods

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Musachy Barroso <mu...@gmail.com>.
Instead of complaining I will actually do something :). Let me know where
you are going to set this up on the wiki so I can help you.

regards
musachy

On 2/9/07, Philip Luppens <ph...@gmail.com> wrote:
>
> I've assigned some documentation issues to myself. I'm starting this
> weekend on a User Guide (blatantly copying the structure from Struts 1
> where appropriate). The CRUD tutorial from WW has been on my todo list
> for a long time, I'll take care of it.
>
> Phil
>
> On 2/9/07, Ted Husted <hu...@apache.org> wrote:
> > On 2/7/07, Brian Pontarelli <br...@pontarelli.com> wrote:
> > >
> > > 1. Arrived at the Struts homepage and Struts 2 almost looked dead. No
> > > activity since October and no news or release information. Adding some
> > > news every few weeks will help keep new comers from bailing.
> >
> > There is now  a link to a browseable archive of User Mailing List to
> > the top of the page, which is where a lot of the action happens :)
> >
> > Other than the same old, same old, there really hasn't been much news,
> > except the XWork 2.0.0 release. I added a mention of that on a trial
> > basis. But, I'm not sure if we want to announce other people's
> > releases here or not.
> >
> > We've been creating test builds, but those were not ready for
> > consumption by the general public, and citing them on the welcome page
> > would be inappropriate. Happily, now that we have a stable XWork 2,
> > the perpetual-beta state should change, and there will be more to
> > announce!
> >
> >
> > > 2. Tried to download the release using the release navigation. Here I
> > > was presented with the fact that there was a 2.0.1 BETA, which is the
> > > latest development release. I spent the next while looking for the
> 2.0.0
> > > release, figuring that was the last stable release. Couldn't find it
> > > obviously. The versioning currently looks to the outside to be a
> > > complete mess and it is very confusing and non standard. I would not
> > > release a patch version (major.minor.patch) until the major version is
> > > released. Therefore all the references to 2.0.1 through 2.0.6 are very
> > > confusing because these are not really final releases, but all BETAs.
> > > Plus, there is talk about 2.0.1 BETA and 2.0.4 and 2.0.6 and this is
> all
> > > quite confusing. I would probably fix the version into a standard
> alpha,
> > > beta, release candidate model. So, currently it would be something
> like
> > > 2.0.0-RC6 or the like working towards a final release of 2.0.0.
> >
> > There's a new FAQ, with a link from the release page.
> >
> >  * http://struts.apache.org/kickstart.html#releases
> >
> > Much of this is driven by the need to track changes to the codebase as
> > it is being developed, live and direct. We also do not keep internal
> > versions or secret roadmaps. What's on the web site is our one and
> > only copy of everything.
> >
> > In practice, we don't do "final" releases, because in an active
> > development environment, nothing is ever really final. A particular
> > set of bits may be good enough for public consumption, but we reserve
> > the right to make backwardly compatible changes to a release series,
> > and to use the simplest possible versioning system: straight
> > milestones that also represent tags in the code repository.
> >
> >
> > >
> > > 3. The documentation for Struts 2 contains references to zero
> > > configuration and the web.xml configuration file also contains this
> > > stuff. There are also a number of references to all the annotations.
> > > These are not available in the 2.0.1BETA JAR files and therefore I had
> a
> > > hard time using them ;) I did find them in the nightly snapshots,
> which
> > > aren't functional. I would keep the documentation inline with the
> latest
> > > beta and not the latest nightly snapshot. Anyone who wants bleeding
> edge
> > > will be willing to look at the source to see new stuff or build the
> > > latest snapshot docs themselves.
> >
> > Once Struts 2 has a GA release, it will be archived on the site, along
> > with all the others (Struts 1.35, Struts 1.2.9, et cetera, going all
> > the way back to Struts 1.0).  Then, the Struts 2 links will point that
> > archive rather than the draft site. But, right now, it's a chicken and
> > egg scenario.
> >
> > We haven't been publishing archives of betas on the web site, because,
> > well, they're betas, and the full documentation for the beta is
> > included in the download. Though, since most beta to end up being GA
> > releases, perhaps we should start archiving the docs for a version as
> > soon as it goes beta.
> >
> > In the meantime, what is on the site is the draft documentation for
> > the nightly build, which will become the next milestone. Last week,
> > that was Struts 2.0.5-DEV, and now it's Struts 2.0.6-DEV.
> >
> > Again, this is our one and only website. This is the site that we use
> > to create the next release, and so it has to contain whatever we want
> > the upcoming release to include. I wish we had the resources to
> > maintain a second development site, but, AFAIK, everyone here is a
> > volunteer, working in our unpaid, spare time.
> >
> >
> > > 4. The tutorials reference a hybrid of WebWork 2 configuration,
> classes,
> > > tags and files and Struts2 configuration and files. This would
> > > definitely be confusing for a newcomer. I would probably keep the
> > > tutorials using only struts2 configuration, classes, tags and files
> > > since that is what the latest beta release uses. I would in turn
> direct
> > > folks to the WebWork wiki for running WebWork 2 if they don't want to
> > > use the BETA release.
> >
> > We adopted the WebWork documentation, along with the codebase. Our
> > intention has been to replace references to WebWork classes with the
> > corresponding reference to Struts 2 classes.
> >
> > Do you mean hybrid of Struts 2 and XWork classes?
> >
> > If so, we really don't know what to do about that. We depend on XWork
> > as a base platform, the same way many frameworks depend on Java's
> > HTTP.
> >
> >
> > > 5. There is really no getting started document for Struts2. It would
> be
> > > a bit of a stumbling block for a newcomer to have various JAR files in
> > > the distribution without any clue on which to use or what the
> > > 'struts2-all' jar contains. There should be a true Struts2 getting
> > > started document that contains a complete step by step to getting an
> > > application running. This could start with the CRUD made easy tutorial
> > > for WW2 and make it more complete for Struts2.
> >
> > There's now a "Impatient?" link at the top of the Getting Started page
> > pointing to the Bootstrap tutorial and MailReader Tour. The
> > PlanetStruts site is down right now, but I'll take care of that after
> > work tonight, before announcing the new beta to the user list.
> >
> > Yes, it would be great if someone ported the CRUD tutorial for WW2 and
> > made it more complete for Struts 2. Any responsible person who files a
> > CLA is welcome to work on the documentation.
> >
> > * http://www.apache.org/licenses/icla.txt
> >
> >
> > > 6. From the guide perspective, it is very difficult to figure out how
> to
> > > write actions. This information is buried in the Struts Configuration
> > > Elements guide and in the Action Configuration guide under that. In
> fact
> > > many of the top level and nested guides are a bit confusing and don't
> > > necessarily follow the standard path developers will take when getting
> > > started as well as when trying new things. The top level components
> > > should be items will be working on when building an application such
> as
> > > AJAX, Actions, Validation, etc. rather than items like "Struts
> > > Configuration Elements" Under these headings would be the
> configuration,
> > > the code, the interfaces, examples, etc. This will be how most folks
> are
> > > going to be using Struts2. They'll be creating an action, adding
> > > validation, handling action results, adding interceptors, etc. There
> are
> > > a number of guides that are on the right track.
> >
> > Yes, we could really use some help here. We started with the WW wiki,
> > and I think we've made some progress, but there is still much to be
> > done. I did as much as I could over the summer, but unfortunately,
> > it's not something I can spend much time on myself this year.
> > Hopefully, someone will pickup the torch.
> >
> > Again, any responsible person who files a CLA is welcome to help with
> > the documentation.
> >
> >
> > > 7. I had a bit of trouble figuring out how to grab the code because
> the
> > > link is on the main Struts page. Adding a link to the Struts2 page
> will
> > > help a lot.
> >
> > We didn't do that at first since most of the development materials are
> > under site, and so would not be in the Struts 2 documentation bundle.
> > But, I copied the development menu over and made the links absolute.
> >
> > Thanks for the feedback!. It's already lead to several positive changes.
> >
> > -Ted.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> iDTV System Engineer
> "Always code as if the guy who ends up maintaining your code will be a
> violent psychopath who knows where you live." - John F. Woods
>
> ---------------------------------------------------------------------
> 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: Structs 2 feedback

Posted by Philip Luppens <ph...@gmail.com>.
I've assigned some documentation issues to myself. I'm starting this
weekend on a User Guide (blatantly copying the structure from Struts 1
where appropriate). The CRUD tutorial from WW has been on my todo list
for a long time, I'll take care of it.

Phil

On 2/9/07, Ted Husted <hu...@apache.org> wrote:
> On 2/7/07, Brian Pontarelli <br...@pontarelli.com> wrote:
> >
> > 1. Arrived at the Struts homepage and Struts 2 almost looked dead. No
> > activity since October and no news or release information. Adding some
> > news every few weeks will help keep new comers from bailing.
>
> There is now  a link to a browseable archive of User Mailing List to
> the top of the page, which is where a lot of the action happens :)
>
> Other than the same old, same old, there really hasn't been much news,
> except the XWork 2.0.0 release. I added a mention of that on a trial
> basis. But, I'm not sure if we want to announce other people's
> releases here or not.
>
> We've been creating test builds, but those were not ready for
> consumption by the general public, and citing them on the welcome page
> would be inappropriate. Happily, now that we have a stable XWork 2,
> the perpetual-beta state should change, and there will be more to
> announce!
>
>
> > 2. Tried to download the release using the release navigation. Here I
> > was presented with the fact that there was a 2.0.1 BETA, which is the
> > latest development release. I spent the next while looking for the 2.0.0
> > release, figuring that was the last stable release. Couldn't find it
> > obviously. The versioning currently looks to the outside to be a
> > complete mess and it is very confusing and non standard. I would not
> > release a patch version (major.minor.patch) until the major version is
> > released. Therefore all the references to 2.0.1 through 2.0.6 are very
> > confusing because these are not really final releases, but all BETAs.
> > Plus, there is talk about 2.0.1 BETA and 2.0.4 and 2.0.6 and this is all
> > quite confusing. I would probably fix the version into a standard alpha,
> > beta, release candidate model. So, currently it would be something like
> > 2.0.0-RC6 or the like working towards a final release of 2.0.0.
>
> There's a new FAQ, with a link from the release page.
>
>  * http://struts.apache.org/kickstart.html#releases
>
> Much of this is driven by the need to track changes to the codebase as
> it is being developed, live and direct. We also do not keep internal
> versions or secret roadmaps. What's on the web site is our one and
> only copy of everything.
>
> In practice, we don't do "final" releases, because in an active
> development environment, nothing is ever really final. A particular
> set of bits may be good enough for public consumption, but we reserve
> the right to make backwardly compatible changes to a release series,
> and to use the simplest possible versioning system: straight
> milestones that also represent tags in the code repository.
>
>
> >
> > 3. The documentation for Struts 2 contains references to zero
> > configuration and the web.xml configuration file also contains this
> > stuff. There are also a number of references to all the annotations.
> > These are not available in the 2.0.1BETA JAR files and therefore I had a
> > hard time using them ;) I did find them in the nightly snapshots, which
> > aren't functional. I would keep the documentation inline with the latest
> > beta and not the latest nightly snapshot. Anyone who wants bleeding edge
> > will be willing to look at the source to see new stuff or build the
> > latest snapshot docs themselves.
>
> Once Struts 2 has a GA release, it will be archived on the site, along
> with all the others (Struts 1.35, Struts 1.2.9, et cetera, going all
> the way back to Struts 1.0).  Then, the Struts 2 links will point that
> archive rather than the draft site. But, right now, it's a chicken and
> egg scenario.
>
> We haven't been publishing archives of betas on the web site, because,
> well, they're betas, and the full documentation for the beta is
> included in the download. Though, since most beta to end up being GA
> releases, perhaps we should start archiving the docs for a version as
> soon as it goes beta.
>
> In the meantime, what is on the site is the draft documentation for
> the nightly build, which will become the next milestone. Last week,
> that was Struts 2.0.5-DEV, and now it's Struts 2.0.6-DEV.
>
> Again, this is our one and only website. This is the site that we use
> to create the next release, and so it has to contain whatever we want
> the upcoming release to include. I wish we had the resources to
> maintain a second development site, but, AFAIK, everyone here is a
> volunteer, working in our unpaid, spare time.
>
>
> > 4. The tutorials reference a hybrid of WebWork 2 configuration, classes,
> > tags and files and Struts2 configuration and files. This would
> > definitely be confusing for a newcomer. I would probably keep the
> > tutorials using only struts2 configuration, classes, tags and files
> > since that is what the latest beta release uses. I would in turn direct
> > folks to the WebWork wiki for running WebWork 2 if they don't want to
> > use the BETA release.
>
> We adopted the WebWork documentation, along with the codebase. Our
> intention has been to replace references to WebWork classes with the
> corresponding reference to Struts 2 classes.
>
> Do you mean hybrid of Struts 2 and XWork classes?
>
> If so, we really don't know what to do about that. We depend on XWork
> as a base platform, the same way many frameworks depend on Java's
> HTTP.
>
>
> > 5. There is really no getting started document for Struts2. It would be
> > a bit of a stumbling block for a newcomer to have various JAR files in
> > the distribution without any clue on which to use or what the
> > 'struts2-all' jar contains. There should be a true Struts2 getting
> > started document that contains a complete step by step to getting an
> > application running. This could start with the CRUD made easy tutorial
> > for WW2 and make it more complete for Struts2.
>
> There's now a "Impatient?" link at the top of the Getting Started page
> pointing to the Bootstrap tutorial and MailReader Tour. The
> PlanetStruts site is down right now, but I'll take care of that after
> work tonight, before announcing the new beta to the user list.
>
> Yes, it would be great if someone ported the CRUD tutorial for WW2 and
> made it more complete for Struts 2. Any responsible person who files a
> CLA is welcome to work on the documentation.
>
> * http://www.apache.org/licenses/icla.txt
>
>
> > 6. From the guide perspective, it is very difficult to figure out how to
> > write actions. This information is buried in the Struts Configuration
> > Elements guide and in the Action Configuration guide under that. In fact
> > many of the top level and nested guides are a bit confusing and don't
> > necessarily follow the standard path developers will take when getting
> > started as well as when trying new things. The top level components
> > should be items will be working on when building an application such as
> > AJAX, Actions, Validation, etc. rather than items like "Struts
> > Configuration Elements" Under these headings would be the configuration,
> > the code, the interfaces, examples, etc. This will be how most folks are
> > going to be using Struts2. They'll be creating an action, adding
> > validation, handling action results, adding interceptors, etc. There are
> > a number of guides that are on the right track.
>
> Yes, we could really use some help here. We started with the WW wiki,
> and I think we've made some progress, but there is still much to be
> done. I did as much as I could over the summer, but unfortunately,
> it's not something I can spend much time on myself this year.
> Hopefully, someone will pickup the torch.
>
> Again, any responsible person who files a CLA is welcome to help with
> the documentation.
>
>
> > 7. I had a bit of trouble figuring out how to grab the code because the
> > link is on the main Struts page. Adding a link to the Struts2 page will
> > help a lot.
>
> We didn't do that at first since most of the development materials are
> under site, and so would not be in the Struts 2 documentation bundle.
> But, I copied the development menu over and made the links absolute.
>
> Thanks for the feedback!. It's already lead to several positive changes.
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


-- 
iDTV System Engineer
"Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live." - John F. Woods

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Ted Husted <hu...@apache.org>.
On 2/9/07, Musachy Barroso <mu...@gmail.com> wrote:
> >
> > Again, this is our one and only website. This is the site that we use
> > to create the next release, and so it has to contain whatever we want
> > the upcoming release to include.
>
> I  agree with that, but there is no reason why there should be a "Release
> Notes" on the home page, pointing to something that has not been released
> yet, or will probably never be released, like 2.0.6.

Once we have a GA "best available" release, it will be pointing to the
archived documentation for the release, not the draft version, as it
is now.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Musachy Barroso <mu...@gmail.com>.
>
> Again, this is our one and only website. This is the site that we use
> to create the next release, and so it has to contain whatever we want
> the upcoming release to include.


I  agree with that, but there is no reason why there should be a "Release
Notes" on the home page, pointing to something that has not been released
yet, or will probably never be released, like 2.0.6.

musachy

-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: Structs 2 feedback

Posted by Ted Husted <hu...@apache.org>.
On 2/7/07, Brian Pontarelli <br...@pontarelli.com> wrote:
>
> 1. Arrived at the Struts homepage and Struts 2 almost looked dead. No
> activity since October and no news or release information. Adding some
> news every few weeks will help keep new comers from bailing.

There is now  a link to a browseable archive of User Mailing List to
the top of the page, which is where a lot of the action happens :)

Other than the same old, same old, there really hasn't been much news,
except the XWork 2.0.0 release. I added a mention of that on a trial
basis. But, I'm not sure if we want to announce other people's
releases here or not.

We've been creating test builds, but those were not ready for
consumption by the general public, and citing them on the welcome page
would be inappropriate. Happily, now that we have a stable XWork 2,
the perpetual-beta state should change, and there will be more to
announce!


> 2. Tried to download the release using the release navigation. Here I
> was presented with the fact that there was a 2.0.1 BETA, which is the
> latest development release. I spent the next while looking for the 2.0.0
> release, figuring that was the last stable release. Couldn't find it
> obviously. The versioning currently looks to the outside to be a
> complete mess and it is very confusing and non standard. I would not
> release a patch version (major.minor.patch) until the major version is
> released. Therefore all the references to 2.0.1 through 2.0.6 are very
> confusing because these are not really final releases, but all BETAs.
> Plus, there is talk about 2.0.1 BETA and 2.0.4 and 2.0.6 and this is all
> quite confusing. I would probably fix the version into a standard alpha,
> beta, release candidate model. So, currently it would be something like
> 2.0.0-RC6 or the like working towards a final release of 2.0.0.

There's a new FAQ, with a link from the release page.

 * http://struts.apache.org/kickstart.html#releases

Much of this is driven by the need to track changes to the codebase as
it is being developed, live and direct. We also do not keep internal
versions or secret roadmaps. What's on the web site is our one and
only copy of everything.

In practice, we don't do "final" releases, because in an active
development environment, nothing is ever really final. A particular
set of bits may be good enough for public consumption, but we reserve
the right to make backwardly compatible changes to a release series,
and to use the simplest possible versioning system: straight
milestones that also represent tags in the code repository.


>
> 3. The documentation for Struts 2 contains references to zero
> configuration and the web.xml configuration file also contains this
> stuff. There are also a number of references to all the annotations.
> These are not available in the 2.0.1BETA JAR files and therefore I had a
> hard time using them ;) I did find them in the nightly snapshots, which
> aren't functional. I would keep the documentation inline with the latest
> beta and not the latest nightly snapshot. Anyone who wants bleeding edge
> will be willing to look at the source to see new stuff or build the
> latest snapshot docs themselves.

Once Struts 2 has a GA release, it will be archived on the site, along
with all the others (Struts 1.35, Struts 1.2.9, et cetera, going all
the way back to Struts 1.0).  Then, the Struts 2 links will point that
archive rather than the draft site. But, right now, it's a chicken and
egg scenario.

We haven't been publishing archives of betas on the web site, because,
well, they're betas, and the full documentation for the beta is
included in the download. Though, since most beta to end up being GA
releases, perhaps we should start archiving the docs for a version as
soon as it goes beta.

In the meantime, what is on the site is the draft documentation for
the nightly build, which will become the next milestone. Last week,
that was Struts 2.0.5-DEV, and now it's Struts 2.0.6-DEV.

Again, this is our one and only website. This is the site that we use
to create the next release, and so it has to contain whatever we want
the upcoming release to include. I wish we had the resources to
maintain a second development site, but, AFAIK, everyone here is a
volunteer, working in our unpaid, spare time.


> 4. The tutorials reference a hybrid of WebWork 2 configuration, classes,
> tags and files and Struts2 configuration and files. This would
> definitely be confusing for a newcomer. I would probably keep the
> tutorials using only struts2 configuration, classes, tags and files
> since that is what the latest beta release uses. I would in turn direct
> folks to the WebWork wiki for running WebWork 2 if they don't want to
> use the BETA release.

We adopted the WebWork documentation, along with the codebase. Our
intention has been to replace references to WebWork classes with the
corresponding reference to Struts 2 classes.

Do you mean hybrid of Struts 2 and XWork classes?

If so, we really don't know what to do about that. We depend on XWork
as a base platform, the same way many frameworks depend on Java's
HTTP.


> 5. There is really no getting started document for Struts2. It would be
> a bit of a stumbling block for a newcomer to have various JAR files in
> the distribution without any clue on which to use or what the
> 'struts2-all' jar contains. There should be a true Struts2 getting
> started document that contains a complete step by step to getting an
> application running. This could start with the CRUD made easy tutorial
> for WW2 and make it more complete for Struts2.

There's now a "Impatient?" link at the top of the Getting Started page
pointing to the Bootstrap tutorial and MailReader Tour. The
PlanetStruts site is down right now, but I'll take care of that after
work tonight, before announcing the new beta to the user list.

Yes, it would be great if someone ported the CRUD tutorial for WW2 and
made it more complete for Struts 2. Any responsible person who files a
CLA is welcome to work on the documentation.

* http://www.apache.org/licenses/icla.txt


> 6. From the guide perspective, it is very difficult to figure out how to
> write actions. This information is buried in the Struts Configuration
> Elements guide and in the Action Configuration guide under that. In fact
> many of the top level and nested guides are a bit confusing and don't
> necessarily follow the standard path developers will take when getting
> started as well as when trying new things. The top level components
> should be items will be working on when building an application such as
> AJAX, Actions, Validation, etc. rather than items like "Struts
> Configuration Elements" Under these headings would be the configuration,
> the code, the interfaces, examples, etc. This will be how most folks are
> going to be using Struts2. They'll be creating an action, adding
> validation, handling action results, adding interceptors, etc. There are
> a number of guides that are on the right track.

Yes, we could really use some help here. We started with the WW wiki,
and I think we've made some progress, but there is still much to be
done. I did as much as I could over the summer, but unfortunately,
it's not something I can spend much time on myself this year.
Hopefully, someone will pickup the torch.

Again, any responsible person who files a CLA is welcome to help with
the documentation.


> 7. I had a bit of trouble figuring out how to grab the code because the
> link is on the main Struts page. Adding a link to the Struts2 page will
> help a lot.

We didn't do that at first since most of the development materials are
under site, and so would not be in the Struts 2 documentation bundle.
But, I copied the development menu over and made the links absolute.

Thanks for the feedback!. It's already lead to several positive changes.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Musachy Barroso <mu...@gmail.com>.
Following up on this, I added the images to the home page. The "version"
text needs to be updated for the release.

regards
musachy

On 2/9/07, Ted Husted <hu...@apache.org> wrote:
>
> Works for me.
>
> On 2/8/07, Musachy Barroso <mu...@gmail.com> wrote:
> > Because I'm artistically challenged I got help from a friend of mine to
> get
> > mockup done, check it out here:
> >
> > http://picasaweb.google.com/musachy/
> >
> > that's an idea of what I had in mind.
> >
> > thanks Vlad!
> > musachy
>
> ---------------------------------------------------------------------
> 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: Structs 2 feedback

Posted by Ted Husted <hu...@apache.org>.
Works for me.

On 2/8/07, Musachy Barroso <mu...@gmail.com> wrote:
> Because I'm artistically challenged I got help from a friend of mine to get
> mockup done, check it out here:
>
> http://picasaweb.google.com/musachy/
>
> that's an idea of what I had in mind.
>
> thanks Vlad!
> musachy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Musachy Barroso <mu...@gmail.com>.
Because I'm artistically challenged I got help from a friend of mine to get
mockup done, check it out here:

http://picasaweb.google.com/musachy/

that's an idea of what I had in mind.

thanks Vlad!
musachy

On 2/8/07, Musachy Barroso <mu...@gmail.com> wrote:
>
> Phil is right, what I meant with "open to anyone", was, open to anyone
> that wants to help :).
>
> I think some of the most important things for new users are:
>
> 1. Features List
> These are on the home page, quite visible, no problem.
>
> 2. Getting started
> The whole difference between "Tutorial" and "Guides" is rather confusing
> for new users, and navigating the wiki is not a simple task. There is also
> the idea of "Documentation" whose home page, is the getting started.
>
> I think the links under documentation on the homepage should be:
> Getting Started -> Bootstrap tutorial    (I'll try to spend time on this
> one, pulling content from the wiki, help wanted :) )
> Tutorials           -> Keep current link     (We should link to Matt's
> tutorial on that page)
> FAQ                   -> Keep current link
> Developers Guide -> Keep the link       (I know it is just a rename, but
> at least a user will note the difference between it and the "Getting
> Started")
> Wiki Pages            -> Link to wiki          (currently, it is under
> "Support")
>
> The "Release Notes" should be a link, where the download is, for each
> download, not under documentation. Right now if you click on the release
> notes you will see the release notes for 2.0.6, but you won't find a
> download for 2.0.6 anywhere.
>
> 3. Downloads
> Clicking on the "Releases" link will take you to a page, that has releases
> for both S1, and S2, but the user was already on S2, no reason why he/she
> should be seeing S1 releases listed there. I think there should be a
> "Downloads" category on the menu with these links:
> Latest Stable Release     -> Link to download page for the latest stable
> release, which has a link to the release notes.
> Older Releases                -> Other builds, releases, etc (just S2)
>
> On the home page, there should be a "Download Now" and a "Get Started"
> image , that pops out of the page (to the eye). Open Office's website is a
> good example: http://www.openoffice.org/. If you are a new user, you will
> find the links to what you need easily (Download + Getting Started), if you
> are a user already, you will find your way around the navigation menu.
>
> that was more than 2 cents right? :)
>
> regards
> musachy
>
> On 2/8/07, Philip Luppens <philip.luppens@gmail.com > wrote:
> >
> > The wiki's not open to anyone - you need the karma ;-)
> >
> > But you're right, Musachy. The docs might indeed be geared towards
> > experienced developers rather than newcomers. I've heard from quite a
> > few they like the S1 user documentation - maybe we can copy its
> > structure ? I'm all for it [1].
> >
> > Cheers,
> >
> > Phil
> >
> > [1] https://issues.apache.org/struts/browse/WW-1721
> >
> > On 2/8/07, Musachy Barroso <mu...@gmail.com> wrote:
> > > About the documentation I'd like to point out that I had a similar
> > > experience. The wiki is great for users that already know the
> > framework and
> > > are looking for a reference, or specific information, but for new
> > users it
> > > is quite hard, I always found the "User Guide" on S1 quite useful. The
> > good
> > > thing is that the information is there already (on the wiki), it is
> > the
> > > structure the one that is not easy to follow for new users. The wiki
> > is open
> > > to anyone, so help is welcome :)
> > >
> > > regards
> > > musachy
> > >
> > > On 2/7/07, Brian Pontarelli <br...@pontarelli.com> wrote:
> > > >
> > > >
> > > > Looks like it could be an issue with the xwork2 2.0-beta1 JAR file
> > from
> > > > the 2.0.1 beta bundle conflicting with the nightly because there
> > doesn't
> > > > seem to be an xwork JAR in with the nightlys. Again, this is pretty
> > > > cumbersome to get working because of the numerous JAR files floating
> >
> > > > around and the versioning and dependency management. I'll grab the
> > final
> > > > XWork 2.0 release from OpenSymphony and try it with the nightlys,
> > but I
> > > > would suggest creating nightly bundles if the dependencies are
> > tightly
> > > > coupled.
> > > >
> > > > However, last night the build was broken in subversion, so I'm not
> > sure
> > > > how the nightlys are working. I'll try the build again tonight or
> > > > tomorrow morning to make sure I'm not smoking crack or anything.
> > There
> > > > isn't much build information that I could find except for the 'mvn
> > > > install' command from the 'Source Code' page, so I could be missing
> > > > something there as well. Could also be beneficial to have some build
> >
> > > > info in the docs if there are more steps. Plus, with the memory
> > issue
> > > > I've encountered, might be nice to have something on that if it
> > isn't a
> > > > bug and builders do need to increase the maven memory maximum to
> > around
> > > > 256M.
> > > >
> > > > -bp
> > > >
> > > >
> > > > Nate Drake wrote:
> > > > > Brian Pontarelli <brian <at> pontarelli.com> writes:
> > > > >
> > > > >
> > > > >> 3. The documentation for Struts 2 contains references to zero
> > > > >> configuration and the web.xml configuration file also contains
> > this
> > > > >> stuff. There are also a number of references to all the
> > annotations.
> > > > >> These are not available in the 2.0.1BETA JAR files and therefore
> > I had
> > > > a
> > > > >> hard time using them ;) I did find them in the nightly snapshots,
> > which
> > > > >> aren't functional. I would keep the documentation inline with the
> >
> > > > latest
> > > > >> beta and not the latest nightly snapshot. Anyone who wants
> > bleeding
> > > > edge
> > > > >> will be willing to look at the source to see new stuff or build
> > the
> > > > >> latest snapshot docs themselves.
> > > > >>
> > > > >
> > > > > What seems to be broken with the nightlies?  Zero configuration is
> > > > working
> > > > > ok for us with the 2.0.5 build.
> > > > >
> > > > >
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > 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
> > >
> >
> >
> > --
> > iDTV System Engineer
> > "Always code as if the guy who ends up maintaining your code will be a
> > violent psychopath who knows where you live." - John F. Woods
> >
> > ---------------------------------------------------------------------
> > 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
>



-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: Structs 2 feedback

Posted by Musachy Barroso <mu...@gmail.com>.
Phil is right, what I meant with "open to anyone", was, open to anyone that
wants to help :).

I think some of the most important things for new users are:

1. Features List
These are on the home page, quite visible, no problem.

2. Getting started
The whole difference between "Tutorial" and "Guides" is rather confusing for
new users, and navigating the wiki is not a simple task. There is also the
idea of "Documentation" whose home page, is the getting started.

I think the links under documentation on the homepage should be:
Getting Started -> Bootstrap tutorial    (I'll try to spend time on this
one, pulling content from the wiki, help wanted :) )
Tutorials           -> Keep current link     (We should link to Matt's
tutorial on that page)
FAQ                   -> Keep current link
Developers Guide -> Keep the link       (I know it is just a rename, but at
least a user will note the difference between it and the "Getting Started")
Wiki Pages            -> Link to wiki          (currently, it is under
"Support")

The "Release Notes" should be a link, where the download is, for each
download, not under documentation. Right now if you click on the release
notes you will see the release notes for 2.0.6, but you won't find a
download for 2.0.6 anywhere.

3. Downloads
Clicking on the "Releases" link will take you to a page, that has releases
for both S1, and S2, but the user was already on S2, no reason why he/she
should be seeing S1 releases listed there. I think there should be a
"Downloads" category on the menu with these links:
Latest Stable Release     -> Link to download page for the latest stable
release, which has a link to the release notes.
Older Releases                -> Other builds, releases, etc (just S2)

On the home page, there should be a "Download Now" and a "Get Started" image
, that pops out of the page (to the eye). Open Office's website is a good
example: http://www.openoffice.org/. If you are a new user, you will find
the links to what you need easily (Download + Getting Started), if you are a
user already, you will find your way around the navigation menu.

that was more than 2 cents right? :)

regards
musachy

On 2/8/07, Philip Luppens <ph...@gmail.com> wrote:
>
> The wiki's not open to anyone - you need the karma ;-)
>
> But you're right, Musachy. The docs might indeed be geared towards
> experienced developers rather than newcomers. I've heard from quite a
> few they like the S1 user documentation - maybe we can copy its
> structure ? I'm all for it [1].
>
> Cheers,
>
> Phil
>
> [1] https://issues.apache.org/struts/browse/WW-1721
>
> On 2/8/07, Musachy Barroso <mu...@gmail.com> wrote:
> > About the documentation I'd like to point out that I had a similar
> > experience. The wiki is great for users that already know the framework
> and
> > are looking for a reference, or specific information, but for new users
> it
> > is quite hard, I always found the "User Guide" on S1 quite useful. The
> good
> > thing is that the information is there already (on the wiki), it is the
> > structure the one that is not easy to follow for new users. The wiki is
> open
> > to anyone, so help is welcome :)
> >
> > regards
> > musachy
> >
> > On 2/7/07, Brian Pontarelli <br...@pontarelli.com> wrote:
> > >
> > >
> > > Looks like it could be an issue with the xwork2 2.0-beta1 JAR file
> from
> > > the 2.0.1 beta bundle conflicting with the nightly because there
> doesn't
> > > seem to be an xwork JAR in with the nightlys. Again, this is pretty
> > > cumbersome to get working because of the numerous JAR files floating
> > > around and the versioning and dependency management. I'll grab the
> final
> > > XWork 2.0 release from OpenSymphony and try it with the nightlys, but
> I
> > > would suggest creating nightly bundles if the dependencies are tightly
> > > coupled.
> > >
> > > However, last night the build was broken in subversion, so I'm not
> sure
> > > how the nightlys are working. I'll try the build again tonight or
> > > tomorrow morning to make sure I'm not smoking crack or anything. There
> > > isn't much build information that I could find except for the 'mvn
> > > install' command from the 'Source Code' page, so I could be missing
> > > something there as well. Could also be beneficial to have some build
> > > info in the docs if there are more steps. Plus, with the memory issue
> > > I've encountered, might be nice to have something on that if it isn't
> a
> > > bug and builders do need to increase the maven memory maximum to
> around
> > > 256M.
> > >
> > > -bp
> > >
> > >
> > > Nate Drake wrote:
> > > > Brian Pontarelli <brian <at> pontarelli.com> writes:
> > > >
> > > >
> > > >> 3. The documentation for Struts 2 contains references to zero
> > > >> configuration and the web.xml configuration file also contains this
> > > >> stuff. There are also a number of references to all the
> annotations.
> > > >> These are not available in the 2.0.1BETA JAR files and therefore I
> had
> > > a
> > > >> hard time using them ;) I did find them in the nightly snapshots,
> which
> > > >> aren't functional. I would keep the documentation inline with the
> > > latest
> > > >> beta and not the latest nightly snapshot. Anyone who wants bleeding
> > > edge
> > > >> will be willing to look at the source to see new stuff or build the
> > > >> latest snapshot docs themselves.
> > > >>
> > > >
> > > > What seems to be broken with the nightlies?  Zero configuration is
> > > working
> > > > ok for us with the 2.0.5 build.
> > > >
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > 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
> >
>
>
> --
> iDTV System Engineer
> "Always code as if the guy who ends up maintaining your code will be a
> violent psychopath who knows where you live." - John F. Woods
>
> ---------------------------------------------------------------------
> 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: Structs 2 feedback

Posted by Philip Luppens <ph...@gmail.com>.
The wiki's not open to anyone - you need the karma ;-)

But you're right, Musachy. The docs might indeed be geared towards
experienced developers rather than newcomers. I've heard from quite a
few they like the S1 user documentation - maybe we can copy its
structure ? I'm all for it [1].

Cheers,

Phil

[1] https://issues.apache.org/struts/browse/WW-1721

On 2/8/07, Musachy Barroso <mu...@gmail.com> wrote:
> About the documentation I'd like to point out that I had a similar
> experience. The wiki is great for users that already know the framework and
> are looking for a reference, or specific information, but for new users it
> is quite hard, I always found the "User Guide" on S1 quite useful. The good
> thing is that the information is there already (on the wiki), it is the
> structure the one that is not easy to follow for new users. The wiki is open
> to anyone, so help is welcome :)
>
> regards
> musachy
>
> On 2/7/07, Brian Pontarelli <br...@pontarelli.com> wrote:
> >
> >
> > Looks like it could be an issue with the xwork2 2.0-beta1 JAR file from
> > the 2.0.1 beta bundle conflicting with the nightly because there doesn't
> > seem to be an xwork JAR in with the nightlys. Again, this is pretty
> > cumbersome to get working because of the numerous JAR files floating
> > around and the versioning and dependency management. I'll grab the final
> > XWork 2.0 release from OpenSymphony and try it with the nightlys, but I
> > would suggest creating nightly bundles if the dependencies are tightly
> > coupled.
> >
> > However, last night the build was broken in subversion, so I'm not sure
> > how the nightlys are working. I'll try the build again tonight or
> > tomorrow morning to make sure I'm not smoking crack or anything. There
> > isn't much build information that I could find except for the 'mvn
> > install' command from the 'Source Code' page, so I could be missing
> > something there as well. Could also be beneficial to have some build
> > info in the docs if there are more steps. Plus, with the memory issue
> > I've encountered, might be nice to have something on that if it isn't a
> > bug and builders do need to increase the maven memory maximum to around
> > 256M.
> >
> > -bp
> >
> >
> > Nate Drake wrote:
> > > Brian Pontarelli <brian <at> pontarelli.com> writes:
> > >
> > >
> > >> 3. The documentation for Struts 2 contains references to zero
> > >> configuration and the web.xml configuration file also contains this
> > >> stuff. There are also a number of references to all the annotations.
> > >> These are not available in the 2.0.1BETA JAR files and therefore I had
> > a
> > >> hard time using them ;) I did find them in the nightly snapshots, which
> > >> aren't functional. I would keep the documentation inline with the
> > latest
> > >> beta and not the latest nightly snapshot. Anyone who wants bleeding
> > edge
> > >> will be willing to look at the source to see new stuff or build the
> > >> latest snapshot docs themselves.
> > >>
> > >
> > > What seems to be broken with the nightlies?  Zero configuration is
> > working
> > > ok for us with the 2.0.5 build.
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
>


-- 
iDTV System Engineer
"Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live." - John F. Woods

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Musachy Barroso <mu...@gmail.com>.
About the documentation I'd like to point out that I had a similar
experience. The wiki is great for users that already know the framework and
are looking for a reference, or specific information, but for new users it
is quite hard, I always found the "User Guide" on S1 quite useful. The good
thing is that the information is there already (on the wiki), it is the
structure the one that is not easy to follow for new users. The wiki is open
to anyone, so help is welcome :)

regards
musachy

On 2/7/07, Brian Pontarelli <br...@pontarelli.com> wrote:
>
>
> Looks like it could be an issue with the xwork2 2.0-beta1 JAR file from
> the 2.0.1 beta bundle conflicting with the nightly because there doesn't
> seem to be an xwork JAR in with the nightlys. Again, this is pretty
> cumbersome to get working because of the numerous JAR files floating
> around and the versioning and dependency management. I'll grab the final
> XWork 2.0 release from OpenSymphony and try it with the nightlys, but I
> would suggest creating nightly bundles if the dependencies are tightly
> coupled.
>
> However, last night the build was broken in subversion, so I'm not sure
> how the nightlys are working. I'll try the build again tonight or
> tomorrow morning to make sure I'm not smoking crack or anything. There
> isn't much build information that I could find except for the 'mvn
> install' command from the 'Source Code' page, so I could be missing
> something there as well. Could also be beneficial to have some build
> info in the docs if there are more steps. Plus, with the memory issue
> I've encountered, might be nice to have something on that if it isn't a
> bug and builders do need to increase the maven memory maximum to around
> 256M.
>
> -bp
>
>
> Nate Drake wrote:
> > Brian Pontarelli <brian <at> pontarelli.com> writes:
> >
> >
> >> 3. The documentation for Struts 2 contains references to zero
> >> configuration and the web.xml configuration file also contains this
> >> stuff. There are also a number of references to all the annotations.
> >> These are not available in the 2.0.1BETA JAR files and therefore I had
> a
> >> hard time using them ;) I did find them in the nightly snapshots, which
> >> aren't functional. I would keep the documentation inline with the
> latest
> >> beta and not the latest nightly snapshot. Anyone who wants bleeding
> edge
> >> will be willing to look at the source to see new stuff or build the
> >> latest snapshot docs themselves.
> >>
> >
> > What seems to be broken with the nightlies?  Zero configuration is
> working
> > ok for us with the 2.0.5 build.
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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: Structs 2 feedback

Posted by Brian Pontarelli <br...@pontarelli.com>.
Looks like it could be an issue with the xwork2 2.0-beta1 JAR file from 
the 2.0.1 beta bundle conflicting with the nightly because there doesn't 
seem to be an xwork JAR in with the nightlys. Again, this is pretty 
cumbersome to get working because of the numerous JAR files floating 
around and the versioning and dependency management. I'll grab the final 
XWork 2.0 release from OpenSymphony and try it with the nightlys, but I 
would suggest creating nightly bundles if the dependencies are tightly 
coupled.

However, last night the build was broken in subversion, so I'm not sure 
how the nightlys are working. I'll try the build again tonight or 
tomorrow morning to make sure I'm not smoking crack or anything. There 
isn't much build information that I could find except for the 'mvn 
install' command from the 'Source Code' page, so I could be missing 
something there as well. Could also be beneficial to have some build 
info in the docs if there are more steps. Plus, with the memory issue 
I've encountered, might be nice to have something on that if it isn't a 
bug and builders do need to increase the maven memory maximum to around 
256M.

-bp


Nate Drake wrote:
> Brian Pontarelli <brian <at> pontarelli.com> writes:
>
>   
>> 3. The documentation for Struts 2 contains references to zero 
>> configuration and the web.xml configuration file also contains this 
>> stuff. There are also a number of references to all the annotations. 
>> These are not available in the 2.0.1BETA JAR files and therefore I had a 
>> hard time using them ;) I did find them in the nightly snapshots, which 
>> aren't functional. I would keep the documentation inline with the latest 
>> beta and not the latest nightly snapshot. Anyone who wants bleeding edge 
>> will be willing to look at the source to see new stuff or build the 
>> latest snapshot docs themselves.
>>     
>
> What seems to be broken with the nightlies?  Zero configuration is working 
> ok for us with the 2.0.5 build.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>   


Re: Structs 2 feedback

Posted by Nate Drake <nd...@gmail.com>.
Brian Pontarelli <brian <at> pontarelli.com> writes:

> 3. The documentation for Struts 2 contains references to zero 
> configuration and the web.xml configuration file also contains this 
> stuff. There are also a number of references to all the annotations. 
> These are not available in the 2.0.1BETA JAR files and therefore I had a 
> hard time using them ;) I did find them in the nightly snapshots, which 
> aren't functional. I would keep the documentation inline with the latest 
> beta and not the latest nightly snapshot. Anyone who wants bleeding edge 
> will be willing to look at the source to see new stuff or build the 
> latest snapshot docs themselves.

What seems to be broken with the nightlies?  Zero configuration is working 
ok for us with the 2.0.5 build.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Brian Pontarelli <br...@pontarelli.com>.
>> Hmmmm... This is a tough one, but I would think that a version scheme
>> change discussion might be in order. It might be fruitless, but I think
>> that type of versioning is pretty rough. Plus, there are nearly zero
>> docs anywhere about it, not just with Struts2, but also with the Tomcat
>> and httpd. Plus, I could probably safely state that 95% or more of all
>> OS projects use the other model for versioning.
>
> Oh, I don't know. Aside from HTTPD and Tomcat, it's also used by MySQL
> and many, many others. It's less noticeable once there's been a GA
> release, and the subsequent builds tends to go GA as well. In a few
> more years, I'd expect that this will become the dominant open source
> release system. The process is very straight-forward. Here's a
> paragraph from our bylaws:
>
> "After a proposed release is built, it must be tested and classified
> before being released to the general public. The proposed release may
> be assigned "Alpha", "Beta" or "General Availability" classifications
> by majority vote. Once a release is classified by the PMC Members, it
> may be distributed to the general public on behalf of the Foundation.
> Distributions may be reclassified or withdrawn by majority vote, but
> the release number may not be reused by another distribution."

This is probably a religious thing and probably not worth going into too 
much just because some newcomer didn't like it ;) However, looking over 
all the projects I used during my last sizable project, looks 90% of 
them used the other approach. These are: asm, cobertura, easymock, 
junit, spring*, acegi, activation, google apis, axis, bluprints, cglib, 
commons* (I think), dom4j, jdom, freemarker, oro, java-net-commons, 
joda-time, log4j, lucene, xwork and a 2-3 others. So, as a Java 
developer heavily using OS, I seem to have a different perspective. BUT, 
I'm also intelligent enough not to make a huge deal out of it AND I'm 
not really in a position to do so. Just feedback from the outside 
looking in mostly.

>> One more thing is that
>> the versioning scheme doesn't appear to be followed because 2.0.2-2.0.6
>> aren't available for download in anything but a snapshot version. If the
>> model is that all "releases" receive a version than these should be
>> available to download unless what you are saying is that some test
>> builds never get released and therefore those version numbers become
>> effectively dead versions. Personally I try to avoid dead versions
>> numbers whenever possible.
>
> All builds receive version numbers, but not all builds graduate to
> public releases. The versions aren't dead, they just didn't make it
> past a test build. We use these same numbers in the JIRA tickets and
> notes, so it would be hard to simply bypass versions. Even though the
> builds are make public, many people still test them with us, and we
> refer to something being fixed or changed in 2.0.3 or 2.0.4.
>
> Again, this is only noticeable because we haven't been able to issue a
> GA release yet (mainly because our key dependency, XWork, only cam out
> of beta itself in January).
I think what I meant as dead is that you can't use them in production 
because they are not fully functional and tested. So, if I stumble 
across a 2.0.5 JAR floating about somewhere, I have no idea that 2.0.5 
is actually broken to some degree because the version appears to be the 
5th patch from the final release of 2.0. Again, I'm reading into this 
the versioning that I'm used to and that other projects use. That is 
where the main confusion comes from. Where on the other hand I stumble 
across a 2.0.0-beta5 JAR floating about, I immediately know that it is 
not production quality yet just from the naming.

Anyways, just some observations about versioning in general I guess...

-bp


Re: Structs 2 feedback

Posted by Ted Husted <hu...@apache.org>.
On 2/8/07, Brian Pontarelli <br...@pontarelli.com> wrote:
> Hmmmm... This is a tough one, but I would think that a version scheme
> change discussion might be in order. It might be fruitless, but I think
> that type of versioning is pretty rough. Plus, there are nearly zero
> docs anywhere about it, not just with Struts2, but also with the Tomcat
> and httpd. Plus, I could probably safely state that 95% or more of all
> OS projects use the other model for versioning.

Oh, I don't know. Aside from HTTPD and Tomcat, it's also used by MySQL
and many, many others. It's less noticeable once there's been a GA
release, and the subsequent builds tends to go GA as well. In a few
more years, I'd expect that this will become the dominant open source
release system. The process is very straight-forward. Here's a
paragraph from our bylaws:

"After a proposed release is built, it must be tested and classified
before being released to the general public. The proposed release may
be assigned "Alpha", "Beta" or "General Availability" classifications
by majority vote. Once a release is classified by the PMC Members, it
may be distributed to the general public on behalf of the Foundation.
Distributions may be reclassified or withdrawn by majority vote, but
the release number may not be reused by another distribution."


> One more thing is that
> the versioning scheme doesn't appear to be followed because 2.0.2-2.0.6
> aren't available for download in anything but a snapshot version. If the
> model is that all "releases" receive a version than these should be
> available to download unless what you are saying is that some test
> builds never get released and therefore those version numbers become
> effectively dead versions. Personally I try to avoid dead versions
> numbers whenever possible.

All builds receive version numbers, but not all builds graduate to
public releases. The versions aren't dead, they just didn't make it
past a test build. We use these same numbers in the JIRA tickets and
notes, so it would be hard to simply bypass versions. Even though the
builds are make public, many people still test them with us, and we
refer to something being fixed or changed in 2.0.3 or 2.0.4.

Again, this is only noticeable because we haven't been able to issue a
GA release yet (mainly because our key dependency, XWork, only cam out
of beta itself in January).

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Brian Pontarelli <br...@pontarelli.com>.
>> 1. Arrived at the Struts homepage and Struts 2 almost looked dead. No 
>> activity since October and no news or release information. Adding 
>> some news every few weeks will help keep new comers from bailing.
>
> We should probably look at automating the website deployment from 
> SVN.  This would allow us to more easily keep the website refreshed.  
> I like the idea of more frequent news items.  Maybe the front page 
> should display a few feeds such as latest documentation edits, 
> commits, or Struts 2 plugin announcements.  If we generated the 
> website from Maven each night, the material would stay pretty current.
>
> https://issues.apache.org/struts/browse/SITE-17
> https://issues.apache.org/struts/browse/SITE-18
This would help out a lot. We all know how projects come and go and 
although Struts is a pretty common name out there, it is still important 
to let folks know that development is very active.

>> 2. Tried to download the release using the release navigation. Here I 
>> was presented with the fact that there was a 2.0.1 BETA, which is the 
>> latest development release. I spent the next while looking for the 
>> 2.0.0 release, figuring that was the last stable release. Couldn't 
>> find it obviously. The versioning currently looks to the outside to 
>> be a complete mess and it is very confusing and non standard. I would 
>> not release a patch version (major.minor.patch) until the major 
>> version is released. Therefore all the references to 2.0.1 through 
>> 2.0.6 are very confusing because these are not really final releases, 
>> but all BETAs. Plus, there is talk about 2.0.1 BETA and 2.0.4 and 
>> 2.0.6 and this is all quite confusing. I would probably fix the 
>> version into a standard alpha, beta, release candidate model. So, 
>> currently it would be something like 2.0.0-RC6 or the like working 
>> towards a final release of 2.0.0.
>
> While I agree with you personally, Struts uses a different versioning 
> approach, similar to the one used by Tomcat and HTTPD.  Basically, 
> each "test build" gets a version.  After the "test build" is created, 
> the community votes on its quality.  Furthermore, a test build could 
> be voted on twice - once as beta than again as GA if no issues have 
> been found.  We should do a better job of explaining this system on 
> the download page.
Hmmmm... This is a tough one, but I would think that a version scheme 
change discussion might be in order. It might be fruitless, but I think 
that type of versioning is pretty rough. Plus, there are nearly zero 
docs anywhere about it, not just with Struts2, but also with the Tomcat 
and httpd. Plus, I could probably safely state that 95% or more of all 
OS projects use the other model for versioning. One more thing is that 
the versioning scheme doesn't appear to be followed because 2.0.2-2.0.6 
aren't available for download in anything but a snapshot version. If the 
model is that all "releases" receive a version than these should be 
available to download unless what you are saying is that some test 
builds never get released and therefore those version numbers become 
effectively dead versions. Personally I try to avoid dead versions 
numbers whenever possible.

If however this discussion doesn't occur or doesn't change anything, 
then I think this deserves its own page and a link from the download area.

>> 5. There is really no getting started document for Struts2. It would 
>> be a bit of a stumbling block for a newcomer to have various JAR 
>> files in the distribution without any clue on which to use or what 
>> the 'struts2-all' jar contains. There should be a true Struts2 
>> getting started document that contains a complete step by step to 
>> getting an application running. This could start with the CRUD made 
>> easy tutorial for WW2 and make it more complete for Struts2.
>
> We do have a bootstrap tutorial which covers this.  Is there a better 
> way we could highlight it?
Found it. I think that perhaps a more direct name would help. Something 
like "Step by step getting started guide" or "Getting started" or "Step 
1: Your first application". This would follow my thoughts on the 
organization of the docs in order to follow a more structured approach 
that developers will be taking towards S2.

>> 6. From the guide perspective, it is very difficult to figure out how 
>> to write actions. This information is buried in the Struts 
>> Configuration Elements guide and in the Action Configuration guide 
>> under that. In fact many of the top level and nested guides are a bit 
>> confusing and don't necessarily follow the standard path developers 
>> will take when getting started as well as when trying new things. The 
>> top level components should be items will be working on when building 
>> an application such as AJAX, Actions, Validation, etc. rather than 
>> items like "Struts Configuration Elements" Under these headings would 
>> be the configuration, the code, the interfaces, examples, etc. This 
>> will be how most folks are going to be using Struts2. They'll be 
>> creating an action, adding validation, handling action results, 
>> adding interceptors, etc. There are a number of guides that are on 
>> the right track.
>
> I'm open to a reorganization of the documentation.  If you'd like to 
> help out, file a Contributor License Agreement - 
> http://apache.org/licenses/cla.txt - and I'll give you access.
I'll send that over. Probably be able to help get this started next week.

>> 7. I had a bit of trouble figuring out how to grab the code because 
>> the link is on the main Struts page. Adding a link to the Struts2 
>> page will help a lot.
>
> I didn't follow this one.  Do you mean we need a better download link 
> on the Struts 2 page?
Exactly. There isn't any link or information there about the source.

>> 8. Running the unit tests from the subversion repository causes out 
>> of memory errors on my machine using the standard 16M of memory that 
>> maven defaults to run with. I found that after the tests had run it 
>> required almost 150M of memory to run the tests. I gave maven 512M, 
>> but this was a stumbling block. This seems like a rather incorrect 
>> behavior for tests since after each test there should be very little 
>> on the heap. Is there a memory leak or some reason very large objects 
>> are hanging about?
>
> Yeah, there must be a memory leak somewhere.
>
> https://issues.apache.org/struts/browse/WW-1720
I'll try and look into this if I get some time over the weekend and next 
week.

> As I said before, I really appreciate the time and effort that went 
> into this analysis.  The tickets should be a good way to ensure the 
> issue is resolved in some manner, but as always, if you'd like to jump 
> in and help, feel free to attach patches and/or suggestions on fixes.  
> Matt Raible mentioned Appfuse 2.0 in half-jest, but if you are looking 
> for an easy way to get started with Struts 2, I'd recommend taking a 
> look at it.
I definitely will be doing as much as I can since my company will be 
investing a lot into Struts2. I'm not really looking for an easy way to 
get up and running because the situation for me is that I'm going to be 
doing all of the work of ensuring Struts2 can be used on around 20-30 
web applications per year. I want to ensure that the core of it meets 
our needs. AppFuse might be something we'll use for getting projects 
started, but I'm also interested in Struts2 core functionality and the 
overall framework.

Thanks for the response and I'll let you know what all I can help with.

-bp

Re: Structs 2 feedback

Posted by Don Brown <mr...@twdata.org>.
Brian, thank you very much for this constructive feedback.  It can be 
confusing to new users to try to nagivate a project that a) hasn't 
released a GA quality release and b) is the product of a merger.  You 
raise very important issues that we need to address.  I'll discuss 
possible solutions one by one.  With each issue, I'll list the tickets, 
if applicable, that I either just created or already existed.

Brian Pontarelli wrote:

> 1. Arrived at the Struts homepage and Struts 2 almost looked dead. No 
> activity since October and no news or release information. Adding some 
> news every few weeks will help keep new comers from bailing.

We should probably look at automating the website deployment from SVN.  
This would allow us to more easily keep the website refreshed.  I like 
the idea of more frequent news items.  Maybe the front page should 
display a few feeds such as latest documentation edits, commits, or 
Struts 2 plugin announcements.  If we generated the website from Maven 
each night, the material would stay pretty current.

https://issues.apache.org/struts/browse/SITE-17
https://issues.apache.org/struts/browse/SITE-18

> 2. Tried to download the release using the release navigation. Here I 
> was presented with the fact that there was a 2.0.1 BETA, which is the 
> latest development release. I spent the next while looking for the 
> 2.0.0 release, figuring that was the last stable release. Couldn't 
> find it obviously. The versioning currently looks to the outside to be 
> a complete mess and it is very confusing and non standard. I would not 
> release a patch version (major.minor.patch) until the major version is 
> released. Therefore all the references to 2.0.1 through 2.0.6 are very 
> confusing because these are not really final releases, but all BETAs. 
> Plus, there is talk about 2.0.1 BETA and 2.0.4 and 2.0.6 and this is 
> all quite confusing. I would probably fix the version into a standard 
> alpha, beta, release candidate model. So, currently it would be 
> something like 2.0.0-RC6 or the like working towards a final release 
> of 2.0.0.

While I agree with you personally, Struts uses a different versioning 
approach, similar to the one used by Tomcat and HTTPD.  Basically, each 
"test build" gets a version.  After the "test build" is created, the 
community votes on its quality.  Furthermore, a test build could be 
voted on twice - once as beta than again as GA if no issues have been 
found.  We should do a better job of explaining this system on the 
download page.

https://issues.apache.org/struts/browse/SITE-19

> 3. The documentation for Struts 2 contains references to zero 
> configuration and the web.xml configuration file also contains this 
> stuff. There are also a number of references to all the annotations. 
> These are not available in the 2.0.1BETA JAR files and therefore I had 
> a hard time using them ;) I did find them in the nightly snapshots, 
> which aren't functional. I would keep the documentation inline with 
> the latest beta and not the latest nightly snapshot. Anyone who wants 
> bleeding edge will be willing to look at the source to see new stuff 
> or build the latest snapshot docs themselves.

Good idea.  We should do a better job of archiving release documentation. 

https://issues.apache.org/struts/browse/SITE-8

> 4. The tutorials reference a hybrid of WebWork 2 configuration, 
> classes, tags and files and Struts2 configuration and files. This 
> would definitely be confusing for a newcomer. I would probably keep 
> the tutorials using only struts2 configuration, classes, tags and 
> files since that is what the latest beta release uses. I would in turn 
> direct folks to the WebWork wiki for running WebWork 2 if they don't 
> want to use the BETA release.

https://issues.apache.org/struts/browse/WW-1719

> 5. There is really no getting started document for Struts2. It would 
> be a bit of a stumbling block for a newcomer to have various JAR files 
> in the distribution without any clue on which to use or what the 
> 'struts2-all' jar contains. There should be a true Struts2 getting 
> started document that contains a complete step by step to getting an 
> application running. This could start with the CRUD made easy tutorial 
> for WW2 and make it more complete for Struts2.

We do have a bootstrap tutorial which covers this.  Is there a better 
way we could highlight it?

> 6. From the guide perspective, it is very difficult to figure out how 
> to write actions. This information is buried in the Struts 
> Configuration Elements guide and in the Action Configuration guide 
> under that. In fact many of the top level and nested guides are a bit 
> confusing and don't necessarily follow the standard path developers 
> will take when getting started as well as when trying new things. The 
> top level components should be items will be working on when building 
> an application such as AJAX, Actions, Validation, etc. rather than 
> items like "Struts Configuration Elements" Under these headings would 
> be the configuration, the code, the interfaces, examples, etc. This 
> will be how most folks are going to be using Struts2. They'll be 
> creating an action, adding validation, handling action results, adding 
> interceptors, etc. There are a number of guides that are on the right 
> track.

I'm open to a reorganization of the documentation.  If you'd like to 
help out, file a Contributor License Agreement - 
http://apache.org/licenses/cla.txt - and I'll give you access.

>
> 7. I had a bit of trouble figuring out how to grab the code because 
> the link is on the main Struts page. Adding a link to the Struts2 page 
> will help a lot.

I didn't follow this one.  Do you mean we need a better download link on 
the Struts 2 page?

>
> 8. Running the unit tests from the subversion repository causes out of 
> memory errors on my machine using the standard 16M of memory that 
> maven defaults to run with. I found that after the tests had run it 
> required almost 150M of memory to run the tests. I gave maven 512M, 
> but this was a stumbling block. This seems like a rather incorrect 
> behavior for tests since after each test there should be very little 
> on the heap. Is there a memory leak or some reason very large objects 
> are hanging about?

Yeah, there must be a memory leak somewhere.

https://issues.apache.org/struts/browse/WW-1720

>
> 9. This is a bit nit picky.... The current code in subversion is 
> broken therefore I was unable to run from sources. One of the things I 
> really like about many frameworks I've worked with and coded on was 
> the fact that a clean checkout was almost guaranteed to compile, test 
> and run. This helps a lot for folks that want the bleeding edge and to 
> start contributing.

Doh, yeah, this one is rather embarassing.  We usually do a pretty good 
job and keeping the build running smoothly but apprently it isn't at the 
moment.  We have a continuous integration server, Bamboo, that runs our 
builds, but it wasn't set to notify the list on failures.  We are in the 
process of configuring it to send notifications and the list to accept them.

As I said before, I really appreciate the time and effort that went into 
this analysis.  The tickets should be a good way to ensure the issue is 
resolved in some manner, but as always, if you'd like to jump in and 
help, feel free to attach patches and/or suggestions on fixes.  Matt 
Raible mentioned Appfuse 2.0 in half-jest, but if you are looking for an 
easy way to get started with Struts 2, I'd recommend taking a look at it.

Thanks again,

Don

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Structs 2 feedback

Posted by Brian Pontarelli <br...@pontarelli.com>.
> Sounds like you need AppFuse!
>
> http://appfuse.org/display/APF/Using+Struts+2
>
> Sorry - I couldn't resist. ;-)
>   
Haha! I'm looking into AppFuse 2 for bootstrapping. I'll let you know 
how it goes. :)

-bp

PS If I recall correctly, Jay says that we are neighbors now. I'm over 
in RedLeaf. We should meet up sometime.

Re: Structs 2 feedback

Posted by mraible <ma...@raibledesigns.com>.


Brian Pontarelli wrote:
> 
> 
> Hey all. I wanted to drop the developers a few notes regarding my recent 
> experience with Struts2. I've been a Struts/WebWork user for quite some 
> time and recently attempted a stab at the Struts 2 switch because I'm 
> planning on using Struts 2 for building client sites for the company I 
> work for. Also, I definitely am trying to be very constructive and if I 
> come off badly I do apologize. Okay on to the info:
> 
> 1. Arrived at the Struts homepage and Struts 2 almost looked dead. No 
> activity since October and no news or release information. Adding some 
> news every few weeks will help keep new comers from bailing.
> 
> 2. Tried to download the release using the release navigation. Here I 
> was presented with the fact that there was a 2.0.1 BETA, which is the 
> latest development release. I spent the next while looking for the 2.0.0 
> release, figuring that was the last stable release. Couldn't find it 
> obviously. The versioning currently looks to the outside to be a 
> complete mess and it is very confusing and non standard. I would not 
> release a patch version (major.minor.patch) until the major version is 
> released. Therefore all the references to 2.0.1 through 2.0.6 are very 
> confusing because these are not really final releases, but all BETAs. 
> Plus, there is talk about 2.0.1 BETA and 2.0.4 and 2.0.6 and this is all 
> quite confusing. I would probably fix the version into a standard alpha, 
> beta, release candidate model. So, currently it would be something like 
> 2.0.0-RC6 or the like working towards a final release of 2.0.0.
> 
> 3. The documentation for Struts 2 contains references to zero 
> configuration and the web.xml configuration file also contains this 
> stuff. There are also a number of references to all the annotations. 
> These are not available in the 2.0.1BETA JAR files and therefore I had a 
> hard time using them ;) I did find them in the nightly snapshots, which 
> aren't functional. I would keep the documentation inline with the latest 
> beta and not the latest nightly snapshot. Anyone who wants bleeding edge 
> will be willing to look at the source to see new stuff or build the 
> latest snapshot docs themselves.
> 
> 4. The tutorials reference a hybrid of WebWork 2 configuration, classes, 
> tags and files and Struts2 configuration and files. This would 
> definitely be confusing for a newcomer. I would probably keep the 
> tutorials using only struts2 configuration, classes, tags and files 
> since that is what the latest beta release uses. I would in turn direct 
> folks to the WebWork wiki for running WebWork 2 if they don't want to 
> use the BETA release.
> 
> 5. There is really no getting started document for Struts2. It would be 
> a bit of a stumbling block for a newcomer to have various JAR files in 
> the distribution without any clue on which to use or what the 
> 'struts2-all' jar contains. There should be a true Struts2 getting 
> started document that contains a complete step by step to getting an 
> application running. This could start with the CRUD made easy tutorial 
> for WW2 and make it more complete for Struts2.
> 
> 6. From the guide perspective, it is very difficult to figure out how to 
> write actions. This information is buried in the Struts Configuration 
> Elements guide and in the Action Configuration guide under that. In fact 
> many of the top level and nested guides are a bit confusing and don't 
> necessarily follow the standard path developers will take when getting 
> started as well as when trying new things. The top level components 
> should be items will be working on when building an application such as 
> AJAX, Actions, Validation, etc. rather than items like "Struts 
> Configuration Elements" Under these headings would be the configuration, 
> the code, the interfaces, examples, etc. This will be how most folks are 
> going to be using Struts2. They'll be creating an action, adding 
> validation, handling action results, adding interceptors, etc. There are 
> a number of guides that are on the right track.
> 
> 7. I had a bit of trouble figuring out how to grab the code because the 
> link is on the main Struts page. Adding a link to the Struts2 page will 
> help a lot.
> 
> 8. Running the unit tests from the subversion repository causes out of 
> memory errors on my machine using the standard 16M of memory that maven 
> defaults to run with. I found that after the tests had run it required 
> almost 150M of memory to run the tests. I gave maven 512M, but this was 
> a stumbling block. This seems like a rather incorrect behavior for tests 
> since after each test there should be very little on the heap. Is there 
> a memory leak or some reason very large objects are hanging about?
> 
> 9. This is a bit nit picky.... The current code in subversion is broken 
> therefore I was unable to run from sources. One of the things I really 
> like about many frameworks I've worked with and coded on was the fact 
> that a clean checkout was almost guaranteed to compile, test and run. 
> This helps a lot for folks that want the bleeding edge and to start 
> contributing.
> 
> I'll try to keep looking around in source code and grabbing the latest 
> code to see how things are progressing. I'm also slated to have a large 
> amount of time at work devoted to getting the companies frameworks and 
> documentation up to the newest architecture I've created and would be 
> willing to help on Struts 2 work whenever possible. I'm particularly 
> interested in minimizing ramp up time as well as making application 
> development time minimal (zero config kinda stuff).
> 
> Thanks,
> Brian Pontarelli
> 

Sounds like you need AppFuse!

http://appfuse.org/display/APF/Using+Struts+2

Sorry - I couldn't resist. ;-)

Matt

-- 
View this message in context: http://www.nabble.com/Structs-2-feedback-tf3190585.html#a8860356
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