Comments for PermGen error

Comment on Spring 3 RESTful Web Services by Sunray

Sunray — Sun, 06 May 2012 01:43:11 +0000

This is a great examples with tiles also

Comment on Eclipse Galileo – Cannot nest src folder by Luis

Luis — Wed, 02 May 2012 16:05:23 +0000

That works. Actually, I removed the file completely

Comment on Spring 3 RESTful Web Services by Kamal

Kamal — Wed, 25 Apr 2012 22:36:25 +0000

Hi,
I am a newbie here, I follwed all the steps of this tutorial but when I run it :

http://localhost:8080/SpringRestfulExample/app/students
It only showed :

-
Class One
-
1
Student One

-
2
Student Two

But not the JSP page.

Thanks, your help is appreciated.

Comment on Eclipse Galileo – Cannot nest src folder by Sam

Sam — Wed, 25 Apr 2012 04:37:25 +0000

Very Very Useful.. thanks a lot…

Comment on Spring Forms, Dynamic Lists and Ajax by Chris

Chris — Tue, 03 Apr 2012 21:36:57 +0000

I implemented a solution using a boolean flag that indicates whether a dynamically added element should be removed or not. You can find that solution there: http://stackoverflow.com/questions/9671640/spring-3-mvc-managing-a-one-to-many-relation-within-a-dynamic-form-using-a

Comment on Eclipse Galileo – Cannot nest src folder by mina

mina — Thu, 29 Mar 2012 04:24:48 +0000

i want to know why this error occured.
please email..

Comment on GWT 2, JSONP and Javascript Overlays with JsonpRequestBuilder by Quan

Quan — Mon, 30 Jan 2012 00:48:29 +0000

OMG! I love you! I was battling SOP for quite a while now, but thanks to your post I could finally get it done. Thanks a lot!

Comment on Spring annotation based AOP and intercepting the ball by admin

admin — Sat, 28 Jan 2012 21:14:29 +0000

To Expand a little on what Alex means. Spring AOP is proxy based and method calls to this.doSomething() will not be wrapped as you’d expect.

Info from the Spring docs:

The key thing to understand here is that the client code inside the main(..) of the Main class has a reference to the proxy. This means that method calls on that object reference will be calls on the proxy, and as such the proxy will be able to delegate to all of the interceptors (advice) that are relevant to that particular method call. However, once the call has finally reached the target object, the SimplePojo reference in this case, any method calls that it may make on itself, such as this.bar() or this.foo(), are going to be invoked against the this reference, and not the proxy. This has important implications. It means that self-invocation is not going to result in the advice associated with a method invocation getting a chance to execute.

More info on this can be found here:

http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/aop.html#aop-understanding-aop-proxies

Comment on Spring annotation based AOP and intercepting the ball by Alex

Alex — Fri, 27 Jan 2012 15:50:25 +0000

Or even more often situation. Class X with two methods methodA and methodB. Only methodB is annotated. If methodB is invoked from methodA, than logAction() will never be invoked.

Comment on Spring annotation based AOP and intercepting the ball by Alex

Alex — Fri, 27 Jan 2012 15:45:51 +0000

Hi.

You forgot to mention that if two annotated methods are in one class(methodA and methodB) and methodA is invoking methodB than logAction(…) will be invoked only once…