failing to init some beans #2

Closed
sheehan opened this Issue Sep 6, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@sheehan

sheehan commented Sep 6, 2013

I recently had an issue with the plugin failing to initialize some beans. The problem occurred somewhat randomly in our websphere environment.

The annotated properties of these bean were null. I went in and verified that the bean's hashCode was in GrailsConfigAnnotationInitializer.initialized. When I manually ran GrailsConfigAnnotationHandler.initObject, the properties populated correctly. Not sure how that happens, but my fix was to add another BeanPostProcessor that always inits the object and that seems to be working so far.

@fedotxxl

This comment has been minimized.

Show comment
Hide comment
@fedotxxl

fedotxxl Sep 6, 2013

Owner

This was implemented following way to improve performance. I've benchmarked code and it looks like it pretty fast and we can remove initObjectWhenRequired method. I hope to release new version in 3-4 days

Owner

fedotxxl commented Sep 6, 2013

This was implemented following way to improve performance. I've benchmarked code and it looks like it pretty fast and we can remove initObjectWhenRequired method. I hope to release new version in 3-4 days

@fedotxxl

This comment has been minimized.

Show comment
Hide comment
@fedotxxl

fedotxxl Sep 14, 2013

Owner

Hi. Updated plugin to version 1.1. Pls check it - it should fix your issue

Owner

fedotxxl commented Sep 14, 2013

Hi. Updated plugin to version 1.1. Pls check it - it should fix your issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment