2016-03-29 12:34 GMT+02:00 Johannes Geppert :
> I was never using this but instead of dropping, we could maybe move this to
> an own plugin in version 3.0?
It won't be that easy - it's basically an aspect programming done manually :(
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
I was never using this but instead of dropping, we could maybe move this to
an own plugin in version 3.0?
Best Regards
Johannes
#
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep
2016-03-29 10:19 GMT+02:00 Christoph Nenning
:
> >
> Does anybody is using this? I'm not sure how useful it is when there
> are other very good tools (JProfiler, YourKit, etc). I think it adds a
> bit of a performance overhead which can be dropped.
>
> https://struts.apache.org/docs/profiling.html
>
>
did not even know that it existed ;)
+1 fo
+1 for performance :)
On 26 March 2016 at 13:29, Lukasz Lenart wrote:
> Does anybody is using this? I'm not sure how useful it is when there
> are other very good tools (JProfiler, YourKit, etc). I think it adds a
> bit of a performance overhead which can be dropped.
>
> https://struts.apache
Does anybody is using this? I'm not sure how useful it is when there
are other very good tools (JProfiler, YourKit, etc). I think it adds a
bit of a performance overhead which can be dropped.
https://struts.apache.org/docs/profiling.html
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.
That sounds reasonable. I will remove it.
musachy
On Sun, Aug 16, 2009 at 4:06 AM, Rainer Hermanns wrote:
> You are right, the builtin profiling support is not what someone will
> use to satisfy professional requirements.
> However, for some it might be quite useful as it is now.
>
+1 to your idea of removing from default stack.
On Sun, Aug 16, 2009 at 7:06 AM, Rainer Hermanns wrote:
> You are right, the builtin profiling support is not what someone will
> use to satisfy professional requirements.
> However, for some it might be quite useful as it is now.
>
You are right, the builtin profiling support is not what someone will
use to satisfy professional requirements.
However, for some it might be quite useful as it is now.
What I would suggest, is to get the profiling interceptor out of the
default stack configurations and leave it as a plugin
15 August 2009 19:39
To: Struts Developers List
Subject: profiling
Although the idea of builtin profiling sounds good in theory, how
useful is this thing nowadays? Profilers are very good and there are
many free ones, including one distributed with Sun's JDK. I would say
we get rid of this
Although the idea of builtin profiling sounds good in theory, how
useful is this thing nowadays? Profilers are very good and there are
many free ones, including one distributed with Sun's JDK. I would say
we get rid of this builtin profiling, is anyone using this at all?
musachy
--
&qu
Yeah, then make sure you include the "debugging" and "profiling"
interceptors as well, if you want to use their functionality. I'd put
them before the "params" interceptor, since they try to clean their
parameters out of the request before they are applie
On 10/25/06, Don Brown <[EMAIL PROTECTED]> wrote:
Hmm...it looks like you don't have the debugging and profiling
interceptors in your stack for that action. Otherwise, the console and
profiling properties would be removed correctly from the parameters and
you wouldn't see that
Hmm...it looks like you don't have the debugging and profiling
interceptors in your stack for that action. Otherwise, the console and
profiling properties would be removed correctly from the parameters and
you wouldn't see that output. Are you extending the "struts-default"
SimpleNode.java:177)
at ognl.SimpleNode.setValue(SimpleNode.java:246)
Adding at the top of my page doesn't seem to help. Neither
does disabling sitemesh.
If I add ?profiling=yes, I get:
ERROR - ParametersInterceptor.setParameters(180) | Developer
Notification (set webwork.devMode to false to disa
What is puzzling is that profiling isn't working. When you append
"profiling=yes" to the query string, Struts will start printing out
profiling information to the log. If you have a lot of logging
messages, these profiling statements might be lost among the clutter.
Fo
the starter archetype app, which also uses
Sitemesh, so it can work.
Maybe it's an issue with Prototype/Scriptaculous? I tried removing
Scripaculous, but no dice.
Also, check that Struts 2 has devMode=true set in struts.properties in
WEB-INF/classes. The debugging and profiling support
Also, check that Struts 2 has devMode=true set in struts.properties in
WEB-INF/classes. The debugging and profiling support are only enabled
in dev mode.
Don
Matt Raible wrote:
I'm trying to use some features I found in Don Brown's presentation on
Struts 2.0 at ApacheCon. Using de
I'm trying to use some features I found in Don Brown's presentation on
Struts 2.0 at ApacheCon. Using debug=console and profiling=yes
doesn't seem to work.
When I use debug=console, I get:
ERROR - ParametersInterceptor.setParameters(180) | Developer
Notification (set webwork.d
18 matches
Mail list logo
