[jboss-jira] [JBoss JIRA] Commented: (JBESB-122) Schema needed

[Tom Fennelly (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-122?page=comments#action_12349085 ] 
            
Tom Fennelly commented on JBESB-122:
------------------------------------

We're probably as far with this now as we're going to be for the GA.  The XSD: http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.xsd

So all listener types (JMS, FTP, File etc) can be configured from the basic XSD types <listener>, <bus> and <provider>.  We also have speciailised versions of these types for JMS to aid tighter validation + have easier tool support (<jms-listener>, <jms-bus> and <jms-provider>).  Would have been nice to get specialised versions for all channels, but time is running out and there are more important tasks to get sorted - we might try adding 1 or 2 if he have time.

Kurt is working on upgrading the TB to use the XSD configuration.

> Schema needed
> -------------
>
>                 Key: JBESB-122
>                 URL: http://jira.jboss.com/jira/browse/JBESB-122
>             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: FileMoverConfig.xsd, FileMoverConfigExample.xml, jbesb-config.xsd, jbossesb-1_0.xsd, LoanBrokerConfig.xml, LoanBrokerConfig.xsd
>
>
> XML is the configuration language of choice in Rosetta at the moment. There is no schema(s) for the various configuration files. Different classes have the attribute/element names hard coded into them. We should use the PropertyManager and have the schemas separated out of the implementation classes.

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