Comments on: Struts2 Documentation http://www.symphonious.net/2007/05/26/struts2-documentation/ Living in a state of accord. Wed, 03 Dec 2008 01:37:16 +0000 http://wordpress.org/?v=2.6.5 By: Sudheendra http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-173441 Sudheendra Thu, 23 Oct 2008 14:13:59 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-173441 I started on Struts2 a month ago. I first did some samples in Roseindia - http://www.roseindia.net/struts/struts2/ which is quite a good start. But there are a lot of things which I still havent got working or knowing if it is an implemented feature or not. For example, if I wanted to have a radio button in a table, which is working UI wise but I am unable to get information in the action class as to which radio was selected. I am now trying to figure out how can CMS be implemented. Guess it is just digging out on google :( I started on Struts2 a month ago. I first did some samples in Roseindia - http://www.roseindia.net/struts/struts2/ which is quite a good start.
But there are a lot of things which I still havent got working or knowing if it is an implemented feature or not.
For example, if I wanted to have a radio button in a table, which is working UI wise but I am unable to get information in the action class as to which radio was selected.

I am now trying to figure out how can CMS be implemented. Guess it is just digging out on google :(

]]> By: davey boy http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-98944 davey boy Thu, 19 Jul 2007 12:02:36 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-98944 I've been trying to code a simple content management system in struts 2 for 3 months now. The documentation is just not good enough, with hardly any useful examples. It's just pathetic, and a real shame as struts 2 is obviously very powerful. I give up, I'll use php instead. I’ve been trying to code a simple content management system in struts 2 for 3 months now. The documentation is just not good enough, with hardly any useful examples. It’s just pathetic, and a real shame as struts 2 is obviously very powerful. I give up, I’ll use php instead.

]]> By: Wes W http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-97085 Wes W Mon, 09 Jul 2007 04:35:18 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-97085 I have a set of articles I wrote to help people learn Struts2. Check it out at http://www.wantii.com. It is a work in progress, but my goal is to be a helpful resource for people learning from the ground up. There are also tutorials at www.roseindia.com that are helpful. I have a set of articles I wrote to help people learn Struts2. Check it out at http://www.wantii.com. It is a work in progress, but my goal is to be a helpful resource for people learning from the ground up. There are also tutorials at http://www.roseindia.com that are helpful.

]]> By: Nisarg http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-92788 Nisarg Sat, 23 Jun 2007 04:53:04 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-92788 Hey do you have an ebook link for struts2 ??? pls send it on nisarg1184@gmail.com Thanks!! Hey do you have an ebook link for struts2 ???

pls send it on nisarg1184@gmail.com

Thanks!!

]]> By: Adrian Sutton http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-82033 Adrian Sutton Sun, 27 May 2007 06:07:46 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-82033 Don, The wiki doesn't contain useful information as it stands - it's simply awful. It shows all the indications of something that people think someone else will contribute to. It's really very clear by trying to use it as a source of information that noone is actually making useful contributions to it. It's not functioning well in any of the modes that documentation is needed - reference, tutorial or recipe/solutions. The fact that the source code can be in SVN confluence is completely useless - the actual explanation is what's important and that would get out of date even if the code snippets automatically update. I'm not sure that professionally produced books will necessarily solve the problem either unless they are focussed at the various areas required, particularly tutorials/getting started and reference information. There needs to be an actual effort made by the core team and it needs to be a priority - currently it clearly isn't and it's drastically reducing the value of the work they're doing. Don,
The wiki doesn’t contain useful information as it stands - it’s simply awful. It shows all the indications of something that people think someone else will contribute to. It’s really very clear by trying to use it as a source of information that noone is actually making useful contributions to it. It’s not functioning well in any of the modes that documentation is needed - reference, tutorial or recipe/solutions. The fact that the source code can be in SVN confluence is completely useless - the actual explanation is what’s important and that would get out of date even if the code snippets automatically update.

I’m not sure that professionally produced books will necessarily solve the problem either unless they are focussed at the various areas required, particularly tutorials/getting started and reference information. There needs to be an actual effort made by the core team and it needs to be a priority - currently it clearly isn’t and it’s drastically reducing the value of the work they’re doing.

]]> By: Don Brown http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-82024 Don Brown Sun, 27 May 2007 05:19:45 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-82024 I don't think anyone is under the delusion that just by putting up a wiki, every user will immediately contribute to it, creating high quality documentation. What it does is make it easier to modify, even just for the developers. If the Struts 2 docs were a Word doc, for example, I can just about promise you it wouldn't be accurate, if it were maintained at all. With a wiki, particularly Confluence, we can do things like the use the Snippet Plugin [1] so our code snippets can be in our source code, yet also be included in the documentation. Also, it is an easy way, for the few users that choose to, improve the docs themselves, and yes, that does happen in the Struts 2 docs. Mainly, I've found the wiki is a place where the lessons learned from the lists generally are canonized, and that in itself is valuable, IMO. As far as professional books, I know of at least four books coming out this year, two of which are free, so hopefully we'll get the best of both worlds. [1] http://confluence.atlassian.com/display/CONFEXT/Snippet+Plugin I don’t think anyone is under the delusion that just by putting up a wiki, every user will immediately contribute to it, creating high quality documentation. What it does is make it easier to modify, even just for the developers. If the Struts 2 docs were a Word doc, for example, I can just about promise you it wouldn’t be accurate, if it were maintained at all. With a wiki, particularly Confluence, we can do things like the use the Snippet Plugin [1] so our code snippets can be in our source code, yet also be included in the documentation. Also, it is an easy way, for the few users that choose to, improve the docs themselves, and yes, that does happen in the Struts 2 docs. Mainly, I’ve found the wiki is a place where the lessons learned from the lists generally are canonized, and that in itself is valuable, IMO. As far as professional books, I know of at least four books coming out this year, two of which are free, so hopefully we’ll get the best of both worlds.

[1] http://confluence.atlassian.com/display/CONFEXT/Snippet+Plugin

]]> By: Adrian Sutton http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-82020 Adrian Sutton Sun, 27 May 2007 04:31:37 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-82020 Don, Thanks for the link to the minibook, it still doesn't give any real useful information on how to actually use struts2. Lots of architectural overview and specific examples but still nothing on what actual options are available etc. As for the wiki, it doesn't matter how easy it is to contribute if the result is useless. The struts2 wiki hardly even got started with providing useful documentation let alone being complete and then kept up to date. It's unfortunate that so many projects make the mistake of thinking that wikis are easy for people to get started editing (generally the need to login and learn wiki markup turns people off) and that putting up a wiki will suddenly cause documentation to spring up out of nowhere. The reality is that regardless of how easy a wiki might make it to contribute, the hardest part is still actually taking the time to write up good documentation. The only people in a place to do that are the developers - noone else has the knowledge of how to use the project and they can't get that knowledge without good documentation. Don,
Thanks for the link to the minibook, it still doesn’t give any real useful information on how to actually use struts2. Lots of architectural overview and specific examples but still nothing on what actual options are available etc. As for the wiki, it doesn’t matter how easy it is to contribute if the result is useless. The struts2 wiki hardly even got started with providing useful documentation let alone being complete and then kept up to date. It’s unfortunate that so many projects make the mistake of thinking that wikis are easy for people to get started editing (generally the need to login and learn wiki markup turns people off) and that putting up a wiki will suddenly cause documentation to spring up out of nowhere. The reality is that regardless of how easy a wiki might make it to contribute, the hardest part is still actually taking the time to write up good documentation. The only people in a place to do that are the developers - noone else has the knowledge of how to use the project and they can’t get that knowledge without good documentation.

]]> By: Ben Fowler http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-81965 Ben Fowler Sat, 26 May 2007 22:17:19 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-81965 It's deja vu all over again. Years ago back in the early days of Struts, when I had to built an application for my employer at the time, I remember encountering similar issues with the scant documentation on the web for Strut's tag libraries, which I felt at the time, were not very robust when used improperly. You either got the usage right, or you spent hours, or even days scratching your head, aided only by a couple of web pages as a token effort by the developers to supply some documentations, or if you're lucky, a handful of forum posts from people as confused as yourself. It goes to show that free software is only 'free' if your time is worthless. It’s deja vu all over again.

Years ago back in the early days of Struts, when I had to built an application for my employer at the time, I remember encountering similar issues with the scant documentation on the web for Strut’s tag libraries, which I felt at the time, were not very robust when used improperly. You either got the usage right, or you spent hours, or even days scratching your head, aided only by a couple of web pages as a token effort by the developers to supply some documentations, or if you’re lucky, a handful of forum posts from people as confused as yourself.

It goes to show that free software is only ‘free’ if your time is worthless.

]]> By: Don Brown http://www.symphonious.net/2007/05/26/struts2-documentation/#comment-81732 Don Brown Sat, 26 May 2007 01:05:59 +0000 https://www.symphonious.net/2007/05/26/struts2-documentation/#comment-81732 You might find this useful: http://www.infoq.com/minibooks/starting-struts2 As for the wiki docs, I agree that professional docs should be done in a different way, but for an open source community, the wiki format is much easier to maintain on a casual basis, and the easier things are to maintain, the more likely they will stay up-to-date. You might find this useful: http://www.infoq.com/minibooks/starting-struts2 As for the wiki docs, I agree that professional docs should be done in a different way, but for an open source community, the wiki format is much easier to maintain on a casual basis, and the easier things are to maintain, the more likely they will stay up-to-date.

]]>