[esb-issues] [JBoss JIRA] Commented: (JBESB-1910) Smooks does not report error in configuration

[Tom Fennelly (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12424376#action_12424376 ] 

Tom Fennelly commented on JBESB-1910:
-------------------------------------

This is a known "feature" of how Smooks v1.0 (and before) works - a resource element value can be anything, not just a reference to a class.  The Extended Configuration model being added for v1.1 will remove this as an issue because you won't need to specify the resource type, or if you do, we will know that it should def be a class, or a file on the CP/Filesys etc.

In Smooks v1.0 and before, when it processes a configuration, it looks at all of the resources defined in the config and if it doesn't recognize a particular resource as being a java class (i.e. it can't load it because of a typo), it just leaves it alone and assumes that it is some other type of resource that's not applied directly to the data event stream.  For more info: http://milyn.codehaus.org/Smooks+User+Guide#SmooksUserGuide-SmooksResources

This information is actually available from the runtime by getting Smooks to generate an Execution Report (http://milyn.codehaus.org/Smooks+User+Guide#SmooksUserGuide-CheckingtheSmooksExecutionProcess).  On the SmooksAction, you can generate a report by setting the "reportPath" property - see the Message Actions Guide docs.

> Smooks does not report error in configuration
> ---------------------------------------------
>
>                 Key: JBESB-1910
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1910
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transformation Service
>    Affects Versions: 4.4
>            Reporter: Jiri Pechanec
>             Fix For: 4.4 CP1
>
>
> If the typo or wrong value in Smoks resource config, element resource the Smooks transformer did not complain for incorrect configuration. It just does not modify message payload. This can be particulary nast as it can take considerable amount of work to find where the problem is originating.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira