Is Across free to use? Yes. Across Framework as well as all modules built by the same team are published under the Apache 2.0 license. The source code can be found on the Foreach Bitbucket space. What experience do I need to get started with Across? You need a good grasp of Java (8) and Spring Framework. Spring MVC experience is strongly advised, and some Spring Boot knowledge might be helpful.

What is an Across module? An Across module bundles technical or business domain functionality, most often the latter. It represents a single Spring ApplicationContext that holds all the components the module defines and - optionally - makes these components available to other modules. Across modules can depend on other modules. These dependencies will determine the relative order of a module versus other modules in the same application. A module will start (or ‘bootstrap’) after all the modules it depends on have already started.

What is the meaning of the project structure created by Across Initializr? Update 2024-02-11: Across Initializr is no longer available. Across Initializr generates a typical project structure for an Across application. Which structure gets created exactly depends on the options you checked when generating the project. It will create both a Java package structure and a structure for the embedded resources. At first glance some part of it might seem bloated (especially the resources).

How can I create a module to share between multiple projects? Declaring a module only requires you to define a valid module descriptor. To be able to share it across multiple projects, simply move all components and the descriptor to a shared JAR. A module usually corresponds to a single JAR, but this is not a requirement. See the reference documentation section on Development Across modules for general information on developing modules.

I try to wire a bean in my application, but while I know it gets created, I still get an exception. This is perhaps the most common problem when working with Across modules. It usually has one of the following causes: The bean gets created in another module and is not exposed. The most likely fix here is to expose that bean. See the question Can I manually expose existing beans from another module?

How is Across different from Spring Boot? Across builds much more on top of Spring Framework than on Spring Boot. Across applications execute as a Spring Boot application and use some features provided by Spring Boot (like embedded webserver, YAML configuration and devtools). Auto-configuration, however, is not supported, which means simply adding a starter to your project will not be enough. Many available configuration classes from Spring Boot will also not work in an Across application, because they are setup for a single ApplicationContext, whereas Across uses a different hierarchy.