[JBoss JIRA] (SRAMP-609) Create a new ArtifactBuilder concept
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-609?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-609:
------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/508
> Create a new ArtifactBuilder concept
> ------------------------------------
>
> Key: SRAMP-609
> URL: https://issues.jboss.org/browse/SRAMP-609
> Project: S-RAMP
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> The Deriver and Linker concepts are necessary, but are somewhat inflexible and unextenadble. For SRAMP-547, SRAMP-465, SRAMP-466, etc., a better solution is needed.
> Replace with an ArtifactBuilder that is in charge of building up the primary artifact and its set of derived artifacts. The set of available builders will be chained together, allowing devs to extend the build-in capabilities.
> When building, if a relationship target is not available in the current set of primary/derived artifacts, a new mediation layer, RelationshipSource, will be given enough information to define the target value in a later step. This information could include a QName, etc.
> After the artifacts are persisted in JCR, the builders are re-called to process any RelationshipSources. Technically, this could be combined with the above into one single step. However, due to the chaining, we want to provide visibility into the entire set of artifacts provided by the whole chain. The alternative, passing the list of artifacts through the chain, is brittle and would require knowing required ordering ahead of time. This idea will be vital for SRAMP-466
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (SRAMP-547) Support derived relationships
by Brett Meyer (JIRA)
[ 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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
- Since we're checking the filename, uploaded XSDs *must* include the slug *or* manually set the artifact name to the filename.
- Note that relative paths will be stripped from the filenames, so conflicts could occur.
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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
- Since we're checking the filename, uploaded XSDs *must* include the slug *or* manually set the artifact name to the filename.
- Note that relative paths will be stripped from the filenames, 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 be generated.
> 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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
> - Since we're checking the filename, uploaded XSDs *must* include the slug *or* manually set the artifact name to the filename.
> - Note that relative paths will be stripped from the filenames, so conflicts could occur.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (SRAMP-547) Support derived relationships
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-547?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-547:
------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/508
> 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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
> - Since we're checking the filename, uploaded XSDs *must* include the slug *or* manually set the artifact name to the filename.
> - Note that relative paths will be stripped from the filenames, 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 be generated.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (SRAMP-547) Support derived relationships
by Brett Meyer (JIRA)
[ 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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
- Since we're checking the filename, uploaded XSDs *must* include the slug *or* manually set the artifact name to the filename.
- Note that relative paths will be stripped from the filenames, 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 be generated.
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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
- Note that relative paths will be stripped from the filenames, 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 be generated.
> 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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
> - Since we're checking the filename, uploaded XSDs *must* include the slug *or* manually set the artifact name to the filename.
> - Note that relative paths will be stripped from the filenames, 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 be generated.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (SRAMP-547) Support derived relationships
by Brett Meyer (JIRA)
[ 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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
- Note that relative paths will be stripped from the filenames, 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 be generated.
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.
- Redefined targets will work exactly like includes (including the above caveats). Only difference is their derived artifacts will supersede any found in the includes.
> 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/include/redefine targets must already exist in the repo or be included in the uploaded artifact/batch. Target determined by namespace -> targetNamespace and filename.
> - Note that relative paths will be stripped from the filenames, 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 be generated.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (SRAMP-610) Remove the old Deriver concepts
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-610:
---------------------------------
Summary: Remove the old Deriver concepts
Key: SRAMP-610
URL: https://issues.jboss.org/browse/SRAMP-610
Project: S-RAMP
Issue Type: Task
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 1.0
SRAMP-609 deprecated the old Deriver concepts and completely replaced it with ArtifactBuilder. Eventually remove the following:
org.overlord.sramp.common.derived.*
temp code in ArtifactBuilderFactory
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s... ]
Brett Meyer commented on SRAMP-16:
----------------------------------
[~bouskaj], great start! I think that's plenty to start with. Our UI is always changing and we'll probably keep this in sync as it does. However, this looks like a fine place to get going. Good work!
> Eclipse IDE: S-RAMP tooling
> ---------------------------
>
> Key: SRAMP-16
> URL: https://issues.jboss.org/browse/SRAMP-16
> Project: S-RAMP
> Issue Type: Task
> Components: IDE Integration
> Affects Versions: 0.6.0.Final
> Reporter: Kurt Stam
> Assignee: Brett Meyer
> Attachments: UIMockup.gliffy, UImockup.gliffy
>
>
> Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. For instance, allowing an app developer to search for a WSDL in S-RAMP, then pull it down into his/her project (all from within the IDE) would be powerful.
> One idea would be to look into writing this as a JBoss Forge plugin. Not only would we gain Eclipse support, but also any other Forge-supported environment. The unknown is how to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the Forge shell.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months