SIRIUS provides a set of components used to build modular and scalable Java applications.
SIRIUS was created by scireum GmbH as foundation of our web based Applications. Being advocates of open source software, we decided that a stable and reliable framework, used in production environments might be useful to others. The library is split into several modules to make it useful for different audiences.GitHub JavaDoc
SIRIUS can be started in any IDE/Debugger just like any normal Java appplication. As no classloader or bytecode magic is used, class reloading in the VM works a treat.
To further save precious developer time, the framework starts ultra fast. Having a server up and running in less than two seconds drives productivity above level 9000!
Running critical servers in production environments forces you to instantly know, what's going on in the system. The exception handling system provided by SIRIUS provides excellent insight, while neither getting jammed by reoccurring errors nor missing any important message. Leveraging the dependency injection framework, every application creator can decide where and how to collect those errors.
Using the built-in profiler, central activities can be profiled in running production systems with almost no overhead.
Provides common tool classes, core frameworks and the microkernel based dependency injector.
The app module is quite big and currently depends on a servlet container. Therefore it will take some time to port it. Therefore no features are ready yet - just some parts of the servlet emulation layer.
The easiest and best way to include SIRIUS is to check it out as git sub module in the folder /sirius. Depending on which modules you plan to used, add the appropriate src and resources folders as java source folders.
Next create an Ant build file (build.xml) in a new sub folder "build" referencing the build-base.xml of SIRIUS. (Have a look at the example S3ninja: build.xml).
Now create an Ivy build file (ivy.xml) in the build folder, referencing the ivy files of the modules used. Yes, this is a bit ugly as you have to used XML entities, but it works. (See: ivy.xml for inspiration).
Finally run the ivy target using ANT to retrieve all required dependencies. This will create a lib folder beneath the build folder, which needs to be added to be build path. For internal projects, we even commit this folder to git, so that no one needs to go through that process again, unless the dependencies change.
Once a new feature of SIRIUS is available you're interested in, simply update the sub module to point to the specific commit (tag, branch, ...) and you're done.
The MIT License (MIT) Copyright (c) 2013 scireum GmbH Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.