Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Can Smooks be extended to support other transformation/processing technologies?

April 26, 2017extended smooks support technologies Transformation

0

Posted

Can Smooks be extended to support other transformation/processing technologies?

1 Answer

0

Posted

Sure. To add support for another transformation or processing technology, you need to implement a ContentHandlerFactory for that technology. As examples, see the following ContentHandlerFactory implementations: • XslContentHandlerFactory : Adds support for XSLT. • StringTemplateContentHandlerFactory : Adds support for the StringTemplate templating framework. • GroovyContentHandlerFactory : Adds support for Groovy scripted resource. Hooking the content delivery unit creator implementation into Smooks is a matter of specifying a Smooks resource for the content delivery creator. See the configurations file for the above templating “CDU Creators”. Note how the selector for all CDU Creators is always “cdu-creator”. This is how Smooks looks up all the CDU Creators targeted at a message profile. Also note how each of the CDU Creator configurations has a “restype” parameter denoting the resource type. Smooks uses this to select the appropriate CDU Creator for a given resource. NOTE : Since Smo