Search:

After a long development and testing phase, the latest version of RSF, version 0.7, is finally released. This is a major features release, as well as contributing numerous improvements to...

OK... I didn't really consider that this really was a point that is JIRA-able, but I guess it is! I have written up the basic points as
...

Cheers for the props, Colin :P

So, are you planning to do anything about it, Mister Spring Team? :P

Unless you are using the new web-scoped beans from Spring 2.0 (request and session beans), or using SpringMVC, *no* Spring framework code in general will execute at runtime for your app. Therefore...

And as well as just considering LOC arguments, you have to bear in mind that Spring configuration is not *code*. The Spring XML "language" is minimally complex and expressive, and very amenable to...

I think we all agree - you are talking about *desirable* semantics of the domain model driving the use of the aspect/injection system, which is exactly how it should be. All that concerns me is the...

Well, I can suggest that Spring users in particular take a look at RSF (http://www2.caret.cam.ac.uk/rsfwiki ) - since unlike other view techs that merely "integrate" with Spring, it is built entirely...

I really can't understand the current enthusiasm, *especially* amongst the Spring community, for annotations applied to the domain model since they do represent a direct Spring dependency....

Take a look at this thread, where this issue is discussed in some depth:

http://forum.springframework.org/showthread.php?t=15294

Yes, it's true that the benefits of OSIV+lazy come at some...

Well, if we're specifically talking about folks starting out, assuming this is not an application of some unreasonable size, and with a relatively clear slate, I would consider to steer clear of...

I think a point missing from this debate is a characterisation of the different styles of applications. I think there is a natural measure of the "shape" of an application derived by comparing the...

Lots of ways to "swap" a bean implementation using Spring configuration only.

You could simply use an <alias> definition to point a given name at differing beans depending only on configuration.
...

RSF is an open source web programming framework based on Spring, with roughly the same scope as Sun's JSF. Unlike many other frameworks which simply offer "integration" with Spring, RSF is built...

No, you can't "set" the whole user object, since it has already been constructed by Spring. What you can do is set a property of the object, as you see in your "does work" case. I.e. the solution is...

Well, this sounds very cool, although IMO it would be "cleaner" to stay with the IoC idiom amongst component files as well as within them. My current concept is simply to assign a "dependence order"...

Could we please have a 1.3.3 release for this fix? The IDE is pretty unusable for me with this bug, since around half the context is filled with errors.

Well, it's a bit of a conceptual shift, but you will (eventually/hopefully :) come to see the world turn round in such a way that you use Spring/IoC essentially for *everything*, and not worry about...

Sneider - it looks like you have pretty much the correct standard pattern. Here is a more detailed explanation of the "non-Spring beans gaining access to Spring" issues:

Any access to Spring beans...

That's exactly what I am trying to avoid.

The point is that the artefacts should be autonomous, and not incur costs in web.xml proportional to the number of modules being used. The problem is now...

See subject. All I can find on the wiki is assertion that it "should be" compatible. Is it?

(Callisto A.K.A Eclipse 3.2)

As a compromise, you may wish to structure the WAR so that it contains only interfaces and non-stateful definitions from the components, and acts as a broker between the implementations in the JARs....

robbo - This issue is very similar to the one surrounding "autowire-by-type" beans in Spring, for example. When I implemented request-scope beans for RSF, I faced just the design question that you...

This very recent article by Kevlin Henney is quite relevant to this issue:

"Building cohesion into programming"

http://www.regdeveloper.co.uk/2006/06/27/getting_together_time/

In general, "vanilla Spring" is most suited to a design where those things which are injected are singletons. You should be able to rework your design such that either it consists of these entirely,...

In general the thread-safety issue is best attacked through simply not using prototypes. If you can rewrite your service beans to this model, you probably should - the "base" Spring idiom is to...