[JBoss JIRA] Created: (SWITCHYARD-212) Support a catalog file for schema resolution in configuration documents
by Keith Babo (JIRA)
Support a catalog file for schema resolution in configuration documents
-----------------------------------------------------------------------
Key: SWITCHYARD-212
URL: https://issues.jboss.org/browse/SWITCHYARD-212
Project: SwitchYard
Issue Type: Enhancement
Components: configuration
Reporter: Keith Babo
It seems pretty likely that we will run into situations where schema referenced in a SwitchYard configuration needs to be resolved through a different path. The schema may be using a URN which needs to be mapped to a network or file system URL. Or the schema location could be URL-based, but a connection fails (due to client or server issue) during parsing/validation. It would be nice to provide a user-accessible catalog file that can be used to map a systemId to a local path. This way, if additional schema are used in a particular setup that are not part of what we ship in the project, the user can update the catalog to point to the correct spot.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (SWITCHYARD-207) Complete configuration support for file binding
by Keith Babo (JIRA)
Complete configuration support for file binding
-----------------------------------------------
Key: SWITCHYARD-207
URL: https://issues.jboss.org/browse/SWITCHYARD-207
Project: SwitchYard
Issue Type: Task
Components: component-camel
Reporter: Keith Babo
Fix For: 0.1
The camel file binding currently supports a single configuration value. We need to create a complete XSD and config model for file binding to see how everything sticks together. The nice thing is that the framework and initial implementation are already there, so this is more of an exercise in finding all the configuration values and adding them to the XSD and config model that are already in place in the Camel component.
The current Camel configuration schema looks like this:
{noformat}
<element name="binding.file" type="camel:CamelFileBindingType" substitutionGroup="sca:binding"/>
<complexType name="CamelFileBindingType" >
<complexContent>
<extension base="sca:Binding">
<sequence>
<element name="operationSelector" type="camel:CamelOperationSelectorType"/>
<element name="inputDir" type="string"/>
</sequence>
</extension>
</complexContent>
</complexType>
{noformat}
The complete list of configuration options for file endpoints in Camel can be found here:
http://camel.apache.org/file2.html
It would be nice if we could take a first quick pass at this to get some feedback on how everything works. If some configuration items turn out to be challenging, let's just make a note of it and resolve them in a separate JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months