[OT] Survey - Tell me what you think about Struts.

[James Mitchell <jm...@apache.org>]

I'll be speaking at a developer conference this month and as an addition to 
the current outline, I would like to put together a list of common pitfalls 
(with respect to development with Struts) that developers find themselves 
battling on a daily basis.  Is it misconfiguration?  Is it constantly having 
to restart your container?  What is it that bugs you the most about 
development with Struts?

On the plus side, if you have a success story you are dying to tell.  I'd 
love to hear about it.



--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
678.910.8017
AIM:   jmitchtx
Yahoo: jmitchtx
MSN:   jmitchell@apache.org






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

Re: [OT] Survey - Tell me what you think about Struts.

[Adam Hardy <ah...@cyberspaceroad.com>]

On 01/05/05 13:13 Simon Chappell wrote:
>>What is it that bugs you the most about development with Struts?
> 
> Trying to work with the struts-config.xml without a dedicated editor.
> I have a small, three actions, project that I'm tinkering with and I
> figured that it was small enough that I didn't need to worry and I
> could just edit struts-config.xml using a text editor. Ouch.

Dedicated editors are a bane for me. The fact that they automatically 
format the whole file according to their xml whitespace, indenting and 
new line rules means that every line can change when a 2nd developer 
edits the file, which really stuffs up any useful CVS functionality.

My biggest issue with struts is the large number of obtuse servlet 
exceptions or plain empty pages that newbies can cause by doing 
something wrong.

Linked to that is the large amount of definitions in xml where the 
correctness is uncheckable until runtime. One silly typo and I have to 
compile, deploy, restart and navigate into the app to check it works. 
Perhaps there's some junit testing I should be doing to check it all in 
one click, but I haven't worked it out yet.

Adam

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

Re: [OT] Survey - Tell me what you think about Struts.

[Simon Chappell <si...@gmail.com>]

James,

Here's a couple:

> What is it that bugs you the most about development with Struts?

Trying to work with the struts-config.xml without a dedicated editor.
I have a small, three actions, project that I'm tinkering with and I
figured that it was small enough that I didn't need to worry and I
could just edit struts-config.xml using a text editor. Ouch.

Also, it's good that Struts is so configurable, but with everything in
one file it gets unworkable sooner rather than later.

Also, be careful to keep your business logic out of your actions and
keep your servlet context out of your business logic. This is not
really Strut's fault, but it's still a good warning for newbies.

> On the plus side, if you have a success story you are dying to tell.  I'd
> love to hear about it.

I'm sure people are fed up of me bragging on the project I did at
Lands' End, so I won't say too much, except that Struts rocks and is
suitable for large projects and is gracefully handling some very close
to real-time kind of response times.

Simon

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