Search:

The problem with the static factory method solution is simply that the users have to specifiy factory-method="something" for each bean. If you have 5-10 beans in the container, it's a PITA (longer...

Well I know Spring only very roughly, so I don't see into this issue... As far as I see, the static method trick is almost the same as when you have a bean class that implements InitializingBean and...

Sure, this static method trick has some obfuscation effect, but now really, is that a significant problem in practice, especially compared to the benefits? How many of your users (I mean application...

I don't get the simile. That this proposed feature does is exactly the same as the init-method/destroy-method attributes or the BeanPostProcessor solution does, except that it happens transparently...

Simply, the name and argument list of that static method could be predefined. But see in my previous post, and in the first post.



Yes, I have considered this. It's unfortunatelly a real PITA,...

My point is that it is a needless complication for the users of the bean classes (not for the author of the bean classes), when the author of the bean classes wants to support the Spring container...

I'm talking about what will Spring users do, who are using the beans of my library. Everything in the library is fully configurable by setting bean properties, and it's is desigend with IoC in mind...

It's not acceptable in my case. This is a "generic library" that uses beans with init and destory methods. It needs an IoC container, and it has its own ultra-light-weight one. But if somebody uses...

The Reference discourages me from using InitializingBean and like, so I don't couple my code to Spring. I agree with that intention, but then, unless I miss a Spring feature, I think Spring misses...

Thanks for the answer, I believe it to you without further proofs, still, I would like to ask if this rule is documented somewhere, or even is a consequence of anything in the documenation? If it...

Is it guaranteed that when the Spring container calls the property setters or the constructor, then the objects passed in as arguments are already initialized? For example, if I have setFoo(Bar foo),...

I wasn't there when that decision was made, so I don't know... But I think that it's bascially just matter of taste. The featuritis approach (where you want to address all imaginable usecase right in...

You can nest MultiTemplateLoader-s into each other, that should work. I have even tried it (not with Spring, but that certainly doesn't mater).

The new keyword is superfluous with this syntax. I guess you have added it so it's more understandable for new users. I guess it doesn't worth it... there are lot of other deviations from the Java...

Take a closer look at the sample at the top of the page the current way of specifying this is...

<property name="foo" value="1"/>
[/quote]

Ops... this shortcut form was not possible when I...

Well I do have an opinion... the XML syntax is terribly verbose, so I agree very much that a specialized syntax should be added (and at least the XML scheme should be rationalized -- see later)....