[jboss-jira] [JBoss JIRA] Closed: (JBESB-119) Parameter loading doesn't check for XML validity

[Kurt Stam (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-119?page=all ]

Kurt Stam closed JBESB-119.
---------------------------

    Resolution: Done

The jbossesb.xml is monitored by the ConfigurationController. When the timestamp on this file changes, the file is validated against the jbossesb-1.0.xsd. If it passed validation, it is given to the Generator, to generate the jbossesb-listener.xml and jbossesb.gateway.xml. The latter two files are read into the esb engine, and they have no xsd, since they are pretty much free format.

> 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.

-- 
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