https://github.com/dykstrom/spring-and-bsaf
Spring and BSAF working together
https://github.com/dykstrom/spring-and-bsaf
java spring swing
Last synced: about 1 year ago
JSON representation
Spring and BSAF working together
- Host: GitHub
- URL: https://github.com/dykstrom/spring-and-bsaf
- Owner: dykstrom
- License: gpl-3.0
- Created: 2017-06-09T19:36:14.000Z (about 9 years ago)
- Default Branch: master
- Last Pushed: 2024-01-13T14:16:23.000Z (over 2 years ago)
- Last Synced: 2024-01-13T23:54:27.151Z (over 2 years ago)
- Topics: java, spring, swing
- Language: Java
- Size: 208 KB
- Stars: 1
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# spring-and-bsaf
This small application demonstrates how to make the
[Spring Framework](https://spring.io/projects/spring-framework) and the
[Better Swing Application Framework (BSAF)](https://sourceforge.net/projects/bsaf)
work together. We leave the question of _why_ you would like to do that
to another time. ;-)
The problem with combining the two frameworks is that they both want to create
the singleton instance of the main application class. BSAF requires you to
create and run your Application subclass by calling the static _launch_ method.
Spring of course wants to create all managed beans as part of the application
context.
The solution is to introduce a @Configuration class with a method that creates
a Spring bean from the BSAF application instance. In the Application subclass,
you let BSAF create the application:
```java
public static void main(String[] args) {
// Create the singleton application instance using BSAF here
launch(BsafApplication.class, args);
}
```
In the @Configuration class, you create a bean that just returns the singleton
instance:
```java
@Bean
public BsafApplication application() {
// Return the singleton application instance as a Spring bean here
return (BsafApplication) Application.getInstance();
}
```
This enables the application instance to be injected into other classes, even
though it was created before the application context was loaded. You just have
to be careful to not access the application bean before the application instance
has been created by calling _launch_. Otherwise, BSAF will create a dummy instance
that is not compatible with your real Application subclass.
For a Kotlin version of this project, please see
[spring-and-bsaf-kotlin](https://github.com/dykstrom/spring-and-bsaf-kotlin).