New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FeatureProxyFactory bean should not through an exception while not initialized. #76
Comments
Thanks for reporting this. I think this is already resolved in the latest snapshots. Could you perhaps give https://oss.sonatype.org/content/repositories/snapshots Thanks |
The latest snapshot still has the code that creates the error. I suggest to change the code as follows private Class<?> getEffectiveProxyType() {
|
Could you perhaps post the full stacktrace? I actually think the code is correct as it is. |
I just added an additional check that verifies that |
Below find the full stack trace as thrown in 2.0.0. I had a look into the code for 2.1.0-SNAPSHOT and it seemed to be a problem still. However I trust that it is easily enough fixed (or simply overlooked it). :-). 2014-02-19 17:46:31,704 WARN [main] FactoryBeanRegistrySupport:70 - FactoryBean threw exception from getObjectType, despite the contract saying that it should return null if the type of its object cannot be determined yet |
Yeah, with Togglz 2.0.0.Final you will get such an exception. As mentioned before this is a known issue. But this error should be fixed in the snapshots. Could you try the latest 2.1.0-SNAPSHOT and post a stacktrace again? |
Should be fixed with 2.1.0.Final |
The bean should not through an exception while it is still uninitialized. Spring will complain with a warning that states that a proxy bean should return null when its type is not yet known.
The text was updated successfully, but these errors were encountered: