Releases: hprange/woinject
WOInject 1.3.0
Features
Replace Javassist dependency with Byte Buddy (#15)
The Byte Buddy library is more efficient than Javassist regarding CPU and memory usage. It's also a lot easier to use. This solution doesn't require a custom class loader, which is another advantage.
This change added a new requirement. You now have to create an application runner to start the application correctly. An application runner is a pure Java class containing only a main
method. See the WOInject
Javadoc for more information.
We might add more options to start an application with WOInject in the future.
Add an interface to facilitate the provision of EOEnterpriseObjects (#16)
The EOProvider
interface is a type of Provider
that receives an EOEditingContext
as a parameter and returns an instance of an EOEnterpriseObject
. This interface is useful when one needs to fetch enterprise objects or insert them into the specified editing context while provisioning.
WOInject 1.2.2
Bug Fixes
- Fix error while injecting Session scoped objects in Direct Actions.
WOInject 1.2.1
Bug Fixes
- Fix an error when the
SessionProvider
is unable to provide a session if the session hasn't been restored in context.
WOInject 1.2
Improvements
- Initialize WOInject using ServletContextListener instead of HttpServlet (issue #12)
WOInject 1.1.1
Bug Fixes
- Fix problem running WOInject applications with Java 8 (issue #11)
WOInject 1.1
Features
- Add support for WOInject in JEE environments (issue #8)
WOInject 1.0.1
Bug Fixes
- Fix error loading com.apple.* classes (issue #2)
WOInject 1.0
Initial version of WOInject.