@tho2003: I'm trying to use smooks within an ejb deployed to glassfish but the deployment fails due to the dependency of freemarker used by smooks. The ejb is developed as a maven project in Netbeans. Below is the output from glassfish during deployment of the ejb that uses smooks. I'm successful in using smooks within a java desktop application developed using the Netbeans Platform. [#|2019 To do so, right click on Smooks configuration xml (smooks-config-xmltoxml) & select Run As > Smooks Run Configuration as shown in Figure 12.At the same time make sure you added the Smooks jars as mentioned earlier. Figure 12. If your mapping was successful it will create the output as shown in figure 13. Figure 13. It is a general purpose processing tool capable of interpreting fragments of a message. It uses visitor logic to accomplish this. It allows you to implement your transformation logic in XSLT or Java and provides a management framework through which you can centrally manage the transformation logic for your message-set. Something to note when looking at this example is that Smooks doesn't perform this EDI-to-Java transform in a 2 step "pipeline" like process. It doesn't generate and intermediate XML, which it then It can be used purely as a Java binding framework for XML, EDI, CSV and so forth. However, Smooks' Java binding capabilities are also the cornerstone of many other capabilities. This is because Smooks makes the Java objects it creates (and to which it binds data) available through the BeanContext class. Smooks is a Java Framework/Engine for processing XML and non XML data. For example: Press Enter to execute the command. Press Ctrl+Alt+F1 to switch to the first virtual terminal. Press Ctrl+Alt+F7 to return to your X-Windows session. The first sentence highlights the particular key cap to press. The second highlights two sets of three key caps, each set pressed simultaneously. Examples Example 1: Performance tuning. Smooks can be used to split a file and send split results to a JMS endpoint. In this case, having a value other than -1 for jms:highWaterMark in the Smooks configuration file can result in a low throughput for message publishing, since Smooks will spend resources on message counting while the messages are being published. In this particular example, Smooks uses the SAX processing model, which means no intermediate object model is constructed for populating the target Java Object Graph. Instead, we go straight from the source Java Object Graph, to a stream of SAX events, which are used to populate the target Java Object Graph.