JMS Message Filter - Transacted field could be a choice of true and false instead of a text input field ------------------------------------------------------------------------------------------------------- Key: JBIDE-3212 URL: https://jira.jboss.org/jira/browse/JBIDE-3212 Project: Tools (JBoss Tools) Issue Type: Task Components: esb Reporter: Daniel Bevenius The transacted input field is of type text, but restricted to true/false. The declaration in the xsd is actually of the boolean type. Note that this is not true for the jca-gatway. Its transacted field is of type string. This Jira will take care of that jca-gateway field issue:https://jira.jboss.org/jira/browse/JBESB-2180 In esb.meta the jms-message-filter transacted field is declared like this: <XModelAttribute PROPERTIES="category=advanced;id=true" name="transacted" xmlname="transacted"> <Constraint loader="List"> <value/> <value name="true"/> <value name="false"/> </Constraint> <Editor name="Lit"/> </XModelAttribute> Changing that to: <XModelAttribute PROPERTIES="category=advanced" name="transacted" xmlname="transacted"> <Constraint loader="ListString"> <value/> <value name="true"/> <value name="false"/> </Constraint> <Editor name="ListString"/> </XModelAttribute> worked for me. -- 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