Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Stardust/Knowledge Base/Testing/Standalone Spring
< Stardust | Knowledge Base | Testing
Revision as of 16:16, 9 November 2011 by Vikram.kodak.sungard.com (Talk | contribs) (New page: == Purpose<br> == It is possible to bootstrap an Stardust engine without any server component in a plain Spring context.<br> == Description<br> == Download Example Project<br> The ...)
Contents
Purpose
It is possible to bootstrap an Stardust engine without any server component in a plain Spring context.
Description
Download Example Project
The context provides an In-Memory Derby-database, In-Memory ActiveMQ (JMS) and In-Memory Jackrabbit (JCR). Therefore you can use (nearly) all Stardust features.
Due to the excluded server components the context is started within seconds with a full-functional Stardust engine.
This is very useful for unit testing etc. Also included are some helper classes to do unit testing.
Notice
There are also some drawbacks which should be noticed:
- EJB-Application type is not working
- No Spring-Remoting/Webservice-Remoting. Therefore you have to use the ServiceFactroyLocator to communicate with the Engine.
All libraries are fetched via Maven. We tried to use only libraries already used by Stardust. For some features this was not an option:
- A more current version of Derby is included to allow InMemory usage. This is fetched via Maven Central
- SpringTesting was included to use Spring-JUnit templates
- SpringModules for JCR was included to provide a JCA connection without JNDI/server components.
Usage
- Import the attached ZIP-file as project into you Eclipse workspace (Eclipse with Maven Plugin).
- Check pom.xml Execute
- JUnitTest to verify setup
- Adopt/Enhance/Customize as per your requirement.