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.
Difference between revisions of "Stardust/Knowledge Base/Testing/Standalone Spring"
< Stardust | Knowledge Base | Testing
m (STP/Stardust/KnowledgeBase/Testing/Standalone-Spring moved to Stardust/KnowledgeBase/Testing/Standalone-Spring: STP is terminated) |
(→Usage) |
||
Line 28: | Line 28: | ||
== Usage<br> == | == Usage<br> == | ||
− | #Import the attached ZIP-file as project into you Eclipse workspace (install the [[ | + | #Import the attached ZIP-file as project into you Eclipse workspace (install the [[Stardust/Knowledge_Base/Build_and_Change_Management/Maven|M2 Eclipse Maven Plugin]]). |
#Check pom.xml Execute | #Check pom.xml Execute | ||
#JUnitTest to verify setup | #JUnitTest to verify setup |
Revision as of 05:51, 28 June 2013
Example Spring Test Project
It is possible to bootstrap an Stardust engine without any server component in a plain Spring context. 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. This is very useful for unit testing etc. Also included are some helper classes to do unit testing.
Note
There are also some drawbacks which should be noticed:
- EJB-Application type is not working
- No Spring-Remoting/Webservice-Remoting. You have to use the ServiceFactoryLocator 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 in-Memory 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 (install the M2 Eclipse Maven Plugin).
- Check pom.xml Execute
- JUnitTest to verify setup
- Adopt/Enhance/Customize as per your requirement.