[
https://issues.jboss.org/browse/SRAMP-547?page=com.atlassian.jira.plugin....
]
Brett Meyer updated SRAMP-547:
------------------------------
Description:
XsdDocument:
protected List<XsdDocumentTarget> importedXsds;
protected List<XsdDocumentTarget> includedXsds;
protected List<XsdDocumentTarget> redefinedXsds;
WsdlDocument:
protected List<XsdDocumentTarget> importedXsds;
protected List<XsdDocumentTarget> includedXsds;
protected List<XsdDocumentTarget> redefinedXsds;
protected List<WsdlDocumentTarget> importedWsdls;
Things to note in the docs:
- Import targets must already exist in the repo or be included in the uploaded
artifact/batch. Target determined by namespace -> targetNamespace.
- Include targets will be parsed. Any derived content will be attached to the parent.
- Include targets including a full URL will be downloaded. If that fails, we'll
attempt to match the *filename* to an existing artifact. Note that relative paths will be
stripped, so conflicts could occur. But, once SRAMP-466 is finished, relative paths could
be checked against the archive.
- Redefined targets will work exactly like includes (including the above caveats). Only
difference is their derived artifacts will supersede any found in the includes.
was:
XsdDocument:
protected List<XsdDocumentTarget> importedXsds;
protected List<XsdDocumentTarget> includedXsds;
protected List<XsdDocumentTarget> redefinedXsds;
WsdlDocument:
protected List<XsdDocumentTarget> importedXsds;
protected List<XsdDocumentTarget> includedXsds;
protected List<XsdDocumentTarget> redefinedXsds;
protected List<WsdlDocumentTarget> importedWsdls;
Things to note in the docs:
- Import targets must already exist in the repo or be included in the uploaded
artifact/batch. Target determined by namespace -> targetNamespace.
- Include targets will be parsed. Any derived content will be attached to the parent.
- Include targets including a full URL will be downloaded. If that fails, we'll
attempt to match the *filename* to an existing artifact. Note that relative paths will be
stripped, so conflicts could occur. But, once SRAMP-466 is finished, relative paths could
be checked against the archive.
Support derived relationships
-----------------------------
Key: SRAMP-547
URL:
https://issues.jboss.org/browse/SRAMP-547
Project: S-RAMP
Issue Type: Sub-task
Reporter: Brett Meyer
Assignee: Brett Meyer
XsdDocument:
protected List<XsdDocumentTarget> importedXsds;
protected List<XsdDocumentTarget> includedXsds;
protected List<XsdDocumentTarget> redefinedXsds;
WsdlDocument:
protected List<XsdDocumentTarget> importedXsds;
protected List<XsdDocumentTarget> includedXsds;
protected List<XsdDocumentTarget> redefinedXsds;
protected List<WsdlDocumentTarget> importedWsdls;
Things to note in the docs:
- Import targets must already exist in the repo or be included in the uploaded
artifact/batch. Target determined by namespace -> targetNamespace.
- Include targets will be parsed. Any derived content will be attached to the parent.
- Include targets including a full URL will be downloaded. If that fails, we'll
attempt to match the *filename* to an existing artifact. Note that relative paths will be
stripped, so conflicts could occur. But, once SRAMP-466 is finished, relative paths could
be checked against the archive.
- Redefined targets will work exactly like includes (including the above caveats). Only
difference is their derived artifacts will supersede any found in the includes.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)