The default implementation of the component accepts InOut MEPs (ADD LINK TO FURTHER READING CONCERNING MEPs) and return the input content as the out message. This is already nearly what we want. OUTLINE for further work: - Get Messages
- read Messages
Wiki Markup |
---|
count the bytes
Maybe easiest by XSLT endpoint (can be used to apply an XSLT stylesheet to the incoming exchange and will return the transformed result as the output message.) see \[ servicemix-saxon\|servicemix-saxon\] |
- send a message back
- Configure SA so that the example receives messages
create & populate C:\hello-world-SE-SU-SA\hello-world-SU\src\main\resources\servicemix.xml - as MyDeployer extends AbstractXBeanDeployer create xbean.xml for SU
- make something send messages (eg quartz timer, HTTP POST,...) and dump the answer (eg TraceComponent, FireWriter, EIP,...)
- add a chapter what user may do now / "how to continue when having the working example"
Classpath for SU to include manually till v3.1, see mail manually editing http://goopen.org/confluence/display/SM/Working+with+Service+Units manually editing http://www.servicemix.org/site/working-with-service-assemblies.html use the SU archetype like in http://www.servicemix.org/site/creating-a-protocol-bridge.html use the SA archetype like in http://www.servicemix.org/site/creating-a-protocol-bridge.html |