springframework-developer

[Springframework-developer] [ANN] JSF integration - initial release

[Thomas J. <tho...@mi...>]

While discussing the issue of integrating Spring and JSF on the JSF space in
the wiki, we developed a preliminary version of the glue code and finally
released it on Sourceforge. At first, we did so within a separate project,
but according to Jürgen Höller and Rod Johnson, JSF integration should be
part of one of the next minor releases of Spring.

The goals of our development were:
- JSF/JSP developers should be able to access beans managed
  by Spring as if they'd be managed by JSF.
- JSF managed beans should be able to integrate into Spring.
- RequestHandledEvents should be published to Spring like
  it's done by Spring's DispatcherServlet.

You can download our code and a sample web application from:
http://sourceforge.net/projects/jsf-spring
The javadoc is accessible online at:
http://jsf-spring.sourceforge.net/

Please review and comment on our code so that we can come up with a commonly
agreed solution to integrate Spring and JSF as soon as possible.

Cheers,
Thomas

[Springframework-developer] JSF integration - second release

[Thomas J. <tho...@mi...>]

There's a new version on sourceforge: http://jsf-spring.sourceforge.net/

The new version integrates the two frameworks more tightly by providing a
WebApplicationContext implementation that interprets JSFs bean configuration
and thus merging JSF and Spring managed beans. This is a major enhancement
code wise, though the API hasn't changed much. Please review the code and
tell us what you think so that we can agree on a final version that could be
integrated into Spring quite soon. Also have a look at the javadoc for an
explanation.

Cheers,
Thomas

[Springframework-developer] Strategies for resolving circular dependencies

[James C. <jim...@do...>]

We have a typical (?) situation where Bean A depends on Bean B. Bean B
depends on Bean C. Bean C depends on Bean A.

I doubt there are any strategies we can employ if each of these beans
requires the other at initialization. But, if one of the beans is not needed
until runtime, are there any techniques we might be able to use?

Currently, we are making one of the beans ApplicationContextAware and
looking up the dependency at runtime.