Greg-
RhinoScript only works with JS files (not ftl or jsp)
Your Best option is to configure in jspc task thru ant using the compiler
option
http://tomcat.apache.org/tomcat-5.5-doc/jasper-howto.html
a must have for the build engineer who will want to assure clean jsp pages
before deploying
Anyone else?
Martin
----- Original Message -----
From: "Greg Lindholm" <[EMAIL PROTECTED]>
To: <user@struts.apache.org>
Sent: Saturday, June 21, 2008 11:01 PM
Subject: Re: [OT] What slows you down?
When I read this I was being slowed down by constant stopping
and starting of Tomcat from within Eclipse...
- make a change in an action class
- start tomcat
- test it... not working
- stop tomcat
- make a java change
- repeat....
In this case I was working on validation logic with annotations.
How else do you test validation logic? Can you unit test validation
logic? Is there a better way? [1]
Part of this problem was I wasn't sure if my OGNL expression was correct.
How do you test/debug OGNL expressions when they will depend on
the ValueStack? [2]
Another part of the problem is the doc for FieldExpressionValidator
doesn't
bother to tell you which direction (true or false) the expression should
return to pass or fail the validation. [3]
BTW: I really really like Struts 2. Over the years I've went from Struts
1,
to JSF, and now Struts 2, and S2 is by far the best and easiest and
most enjoyable.
The thing that slowed me down the most was the learning curve. I started
with
the online tutorials, and the "Starting Struts 2" pdf book, then I had to
start
working on my application. It was very rough going at first, I spent a
lot
of time
in the debugger trying to figure out what the hell was going on. Then I
read
"Struts 2 Design and Programming" and felt better, went back and fixed
some
of the bad designs I started with but still was lacking much knowledge.
Finally
"Struts 2 in Action" was released and I got time to read it **.
I finally feel comfortable, and figure I understand how Struts 2 really
works.
Now I'm going back again and fixing more early bad designs. [4]
One more, un-versioned online documentation.
Under the URL http://struts.apache.org/2.0.11.1/docs (which anyone would
reasonably believe is documentation for Struts 2.0.11) is documentation
that
only applies to release 2.1.x. More then a couple of times I've had a
problem
searched for a solution found it in the 2.0.11.1 docs started implementing
it
only to discover it was only for 2.1.x. (very frustrating.) [5]
[1] Unit testing validation logic
[2] Debugging OGNL expressions
[3] Poor or incomplete documentation, lack or real-world examples and use
cases
[4] Learning curve
[5] Un-versioned docs.
** Struts 2 in Action is a really good book, highly recommend it. However,
I
don't think I would have got nearly as much out of it if I hadn't already
gone
through the other books and hand's on struggles before I read it.
Ted Husted wrote:
Since it's friday, let me pose a question to the group ...
Even with rock-solid frameworks like Apache Struts, it still seems
like web application development takes longer than it should. Some
frameworks, like Ruby on Rails, speak directly to "time to market"
concerns and have been gathering many followers.
But why does web application still seem so difficult or so
time-consuming? Are there time bandits that still suck days or weeks
out of your development schedule? Are there time gremlins that
"nickel-and-dime" you every hour of every day? Is there anything more
that frameworks like Apache Struts can do to help? Or are just there
intractable problems with web development itself?
Thoughts? :)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/-OT--What-slows-you-down--tp18027912p18050807.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
