Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.0 The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: David DeGroff Priority: Critical Fix For: 4.0 The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: David DeGroff Priority: Critical Fix For: 4.0 Attachments: jbesb-config.xsd, jbossesb-1_0.xsd The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: David DeGroff Priority: Critical Fix For: 4.0 Attachments: jbesb-config.xsd, jbossesb-1_0.xsd Time Spent: 5 hours Remaining Estimate: 1 day, 2 hours The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: David DeGroff Priority: Critical Fix For: 4.0 Attachments: FileMoverConfigExample.xml, jbesb-config.xsd, jbossesb-1_0.xsd, LoanBrokerConfig.xml Time Spent: 5 hours Remaining Estimate: 1 day, 2 hours The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: David DeGroff Priority: Critical Fix For: 4.0 RC1 Attachments: aREADME, FileMoverConfigExample.xml, jbesb-config.xsd, jbossesb-1_0.xsd, LoanBrokerConfig.xml Time Spent: 5 hours Remaining Estimate: 1 day, 2 hours The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: David DeGroff Priority: Critical Fix For: 4.0 RC1 Attachments: aREADME, FileMoverConfigExample.xml, jbesb-config.xsd, jbossesb-1_0.xsd, LoanBrokerConfig.xml Time Spent: 5 hours Remaining Estimate: 1 day, 2 hours The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: David DeGroff Priority: Critical Fix For: 4.0 RC1 Attachments: aREADME, FileMoverConfigExample.xml, jbesb-config.xsd, jbossesb-1_0.xsd, LoanBrokerConfig.xml Time Spent: 5 hours Remaining Estimate: 1 day, 2 hours The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.0 RC1 Attachments: aREADME, FileMoverConfigExample.xml, jbesb-config.xsd, jbossesb-1_0.xsd, LoanBrokerConfig.xml Time Spent: 5 hours Remaining Estimate: 1 day, 2 hours The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.

Parameter loading doesn't check for XML validity ------------------------------------------------ Key: JBESB-119 URL: http://jira.jboss.com/jira/browse/JBESB-119 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.0 Attachments: aREADME, FileMoverConfigExample.xml, jbesb-config.xsd, jbossesb-1_0.xsd, LoanBrokerConfig.xml Time Spent: 5 hours Remaining Estimate: 1 day, 2 hours The current ParamRepository approach has a File implementation. It all appears to work on Strings (with the comments indicating how the strings should be formatted for structured attributes). However, some user classes assume the String is XML. Parameters should be provided to application classes through name/value pairs. How those pairs are loaded into the system (XML, strings, file, etc.) should be hidden. We also need an ESB schema.