Product build bug: leaves out the "scripts" folder when producing jbossesb-rosetta.jar -------------------------------------------------------------------------------------- Key: JBESB-824 URL: http://jira.jboss.com/jira/browse/JBESB-824 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 3 Reporter: Burr Sutter Assigned To: Mark Little Priority: Critical Fix For: 4.2 The current jbossesb-rosetta.jar file "drops" the org\jboss\soa\esb\listeners\gateway\scripts folder from the final distro. The Groovy gateway uses this script: rosetta\src\org\jboss\soa\esb\listeners\gateway\scripts\MessageInjectionConsole.groovy This script should be available to this jboss-esb.xml when using the Groovy "gateway" <service category="MyGroovy" name="ACustomService" description="EPR Description" > <listeners> <groovy-listener name="groovy-client" script="MessageInjectionConsole.groovy" is-gateway="true" /> <jms-listener name="ESBListener" busidref="quickstartEsbChannel" maxThreads="1"/> </listeners> <actions> <action name="first" class="org.jboss.soa.esb.samples.quickstart.groovygateway.MyBasicAction" process="displayMessage" > <property name="exceptionMethod" value="exceptionHandler" /> </action> </actions> </service> My workaround for now is to copy that .groovy file into my .esb archive since it is missing from the base product's jars. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira