October 2014 - overlord-issues - Jboss List Archives

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

9 years, 11 months

1
0
0 / 0

[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: ------------------------------ Summary: Support derived relationships (was: Support built-in relationships) > 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. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-547) Support built-in 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 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. 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; > Support built-in 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. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-466) Better utilize batch mode for relationship resolution

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-466?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-466: ----------------------------------- SRAMP-547 could also be improved with this. For instance, includedXsds with relative paths could be resolved. Rather than stripping the path, check to see if it exists in the archive. > Better utilize batch mode for relationship resolution > ----------------------------------------------------- > > Key: SRAMP-466 > URL: https://issues.jboss.org/browse/SRAMP-466 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Better utilize "batch mode" during relationship resolution. Links within the batch would take priority over existing artifacts in the repo. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-547) Support built-in 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; was: XsdDocument: protected List<XsdDocumentTarget> importedXsds; protected List<XsdDocumentTarget> includedXsds; protected List<XsdDocumentTarget> redefinedXsds; WsdlService: protected List<PortTarget> port; WsdlDocument: protected List<XsdDocumentTarget> importedXsds; protected List<XsdDocumentTarget> includedXsds; protected List<XsdDocumentTarget> redefinedXsds; protected List<WsdlDocumentTarget> importedWsdls; Port: protected BindingTarget binding; Part: protected XsdTypeTarget type; protected ElementTarget element; OperationOutput: protected MessageTarget message; OperationInput: protected MessageTarget message; Operation: protected OperationInputTarget input; protected OperationOutputTarget output; protected List<FaultTarget> fault; Message: protected List<PartTarget> part; Fault: protected MessageTarget message; BindingOperation: protected List<BindingOperationFaultTarget> fault; protected BindingOperationInputTarget input; protected BindingOperationOutputTarget output; protected OperationTarget operation; Binding: protected List<BindingOperationTarget> bindingOperation; protected PortTypeTarget portType; > Support built-in 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; -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Giorgi Modebadze (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Giorgi Modebadze updated SRAMP-606: ----------------------------------- Description: I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. E.g. PUT call to Rest Service: http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... As a result, artifact with the given UUID will have property with name key and value Testvalue. Here is the simple code that accepts REST calls: https://gist.github.com/anonymous/469be08cc2610e727517 Here's the pom.xml https://gist.github.com/anonymous/08a3c91163c682cc6cd0 The error from EAP: https://gist.github.com/anonymous/b6422e498a3a90f4c28c Predefined URLs for updating metadata work alright on EAP. E.g. http://localhost:8080/dtgov/rest/update/name/value/uuid Problem is produced on custom Rest calls only. Everything works fine on Jetty, error is produced on EAP. was: I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. E.g. PUT call to Rest Service: http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... As a result, artifact with the given UUID will have property with name key and value Testvalue. Here is the simple code that accepts REST calls: https://gist.github.com/anonymous/469be08cc2610e727517 Here's the pom.xml https://gist.github.com/anonymous/08a3c91163c682cc6cd0 The error from EAP: https://gist.github.com/anonymous/b6422e498a3a90f4c28c Predefined URLs for updating metadata work alright on EAP. E.g. http://localhost:8080/dtgov/rest/update/{name}/{value}/{uuid} Problem is produced on custom Rest calls only. Everything works fine on Jetty, error is produced on EAP. > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/name/value/uuid > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Giorgi Modebadze (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Giorgi Modebadze updated SRAMP-606: ----------------------------------- Description: I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. E.g. PUT call to Rest Service: http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... As a result, artifact with the given UUID will have property with name key and value Testvalue. Here is the simple code that accepts REST calls: https://gist.github.com/anonymous/469be08cc2610e727517 Here's the pom.xml https://gist.github.com/anonymous/08a3c91163c682cc6cd0 The error from EAP: https://gist.github.com/anonymous/b6422e498a3a90f4c28c Predefined URLs for updating metadata work alright on EAP. E.g. http://localhost:8080/dtgov/rest/update/{name}/{value}/{uuid} Problem is produced on custom Rest calls only. Everything works fine on Jetty, error is produced on EAP. was: I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. E.g. PUT call to Rest Service: http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... As a result, artifact with the given UUID will have property with name key and value Testvalue. Here is the simple code that accepts REST calls: https://gist.github.com/anonymous/469be08cc2610e727517 Here's the pom.xml https://gist.github.com/anonymous/08a3c91163c682cc6cd0 The error from EAP: https://gist.github.com/anonymous/b6422e498a3a90f4c28c Predefined URLs for updating metadata work alright on EAP. E.g. http://localhost:8080/dtgov/rest/update/ {name}/ {value}/ {uuid} Problem is produced on custom Rest calls only. Everything works fine on Jetty, error is produced on EAP. > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/{name}/{value}/{uuid} > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Giorgi Modebadze (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Giorgi Modebadze updated SRAMP-606: ----------------------------------- Description: I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. E.g. PUT call to Rest Service: http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... As a result, artifact with the given UUID will have property with name key and value Testvalue. Here is the simple code that accepts REST calls: https://gist.github.com/anonymous/469be08cc2610e727517 Here's the pom.xml https://gist.github.com/anonymous/08a3c91163c682cc6cd0 The error from EAP: https://gist.github.com/anonymous/b6422e498a3a90f4c28c Predefined URLs for updating metadata work alright on EAP. E.g. http://localhost:8080/dtgov/rest/update/ {name}/ {value}/ {uuid} Problem is produced on custom Rest calls only. Everything works fine on Jetty, error is produced on EAP. was: I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. E.g. PUT call to Rest Service: http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... As a result, artifact with the given UUID will have property with name key and value Testvalue. Here is the simple code that accepts REST calls: https://gist.github.com/anonymous/469be08cc2610e727517 Here's the pom.xml https://gist.github.com/anonymous/08a3c91163c682cc6cd0 The error from EAP: https://gist.github.com/anonymous/b6422e498a3a90f4c28c Predefined URLs for updating metadata work alright on EAP. E.g. http://localhost:8080/dtgov/rest/update/{name}/{value}/{uuid} Problem is produced on custom Rest calls only. Everything works fine on Jetty, error is produced on EAP. > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/ {name}/ {value}/ {uuid} > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-606) Unable to use update custom metadata using REST call

by Giorgi Modebadze (JIRA)

[ https://issues.jboss.org/browse/SRAMP-606?page=com.atlassian.jira.plugin.... ] Giorgi Modebadze updated SRAMP-606: ----------------------------------- Description: I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. E.g. PUT call to Rest Service: http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... As a result, artifact with the given UUID will have property with name key and value Testvalue. Here is the simple code that accepts REST calls: https://gist.github.com/anonymous/469be08cc2610e727517 Here's the pom.xml https://gist.github.com/anonymous/08a3c91163c682cc6cd0 The error from EAP: https://gist.github.com/anonymous/b6422e498a3a90f4c28c Predefined URLs for updating metadata work alright on EAP. E.g. http://localhost:8080/dtgov/rest/update/{name}/{value}/{uuid} Problem is produced on custom Rest calls only. Everything works fine on Jetty, error is produced on EAP. was: I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. E.g. PUT call to Rest Service: http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... As a result, artifact with the given UUID will have property with name key and value Testvalue. Here is the simple code that accepts REST calls: https://gist.github.com/anonymous/469be08cc2610e727517 Here's the pom.xml https://gist.github.com/anonymous/08a3c91163c682cc6cd0 The error from EAP: https://gist.github.com/anonymous/b6422e498a3a90f4c28c Everything works fine on Jetty, problem is produced on EAP. > Unable to use update custom metadata using REST call > ---------------------------------------------------- > > Key: SRAMP-606 > URL: https://issues.jboss.org/browse/SRAMP-606 > Project: S-RAMP > Issue Type: Bug > Components: Atom Binding, S-RAMP API > Affects Versions: 0.6.0.Final > Reporter: Giorgi Modebadze > Assignee: Brett Meyer > > I created my own work item handler and deployed it on EAP. My modified UpdateMetaDataResource adds custom properties to artifact on S-RAMP according to some key value. > E.g. PUT call to Rest Service: > http://localhost:8080/s-ramp-adapter/rest/update/property/key/Testvalue/d... > As a result, artifact with the given UUID will have property with name key and value Testvalue. > Here is the simple code that accepts REST calls: > https://gist.github.com/anonymous/469be08cc2610e727517 > Here's the pom.xml > https://gist.github.com/anonymous/08a3c91163c682cc6cd0 > The error from EAP: > https://gist.github.com/anonymous/b6422e498a3a90f4c28c > Predefined URLs for updating metadata work alright on EAP. E.g. > http://localhost:8080/dtgov/rest/update/{name}/{value}/{uuid} > Problem is produced on custom Rest calls only. > Everything works fine on Jetty, error is produced on EAP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-547) Support built-in 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; WsdlService: protected List<PortTarget> port; WsdlDocument: protected List<XsdDocumentTarget> importedXsds; protected List<XsdDocumentTarget> includedXsds; protected List<XsdDocumentTarget> redefinedXsds; protected List<WsdlDocumentTarget> importedWsdls; Port: protected BindingTarget binding; Part: protected XsdTypeTarget type; protected ElementTarget element; OperationOutput: protected MessageTarget message; OperationInput: protected MessageTarget message; Operation: protected OperationInputTarget input; protected OperationOutputTarget output; protected List<FaultTarget> fault; Message: protected List<PartTarget> part; Fault: protected MessageTarget message; BindingOperation: protected List<BindingOperationFaultTarget> fault; protected BindingOperationInputTarget input; protected BindingOperationOutputTarget output; protected OperationTarget operation; Binding: protected List<BindingOperationTarget> bindingOperation; protected PortTypeTarget portType; was:WsdlDocument, XsdDocument, etc. do not currently include support for importedXsds, includedXsds, redefinedXsds, importedWsdls, etc. > Support built-in 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; > WsdlService: > protected List<PortTarget> port; > WsdlDocument: > protected List<XsdDocumentTarget> importedXsds; > protected List<XsdDocumentTarget> includedXsds; > protected List<XsdDocumentTarget> redefinedXsds; > protected List<WsdlDocumentTarget> importedWsdls; > Port: > protected BindingTarget binding; > Part: > protected XsdTypeTarget type; > protected ElementTarget element; > OperationOutput: > protected MessageTarget message; > OperationInput: > protected MessageTarget message; > Operation: > protected OperationInputTarget input; > protected OperationOutputTarget output; > protected List<FaultTarget> fault; > Message: > protected List<PartTarget> part; > Fault: > protected MessageTarget message; > BindingOperation: > protected List<BindingOperationFaultTarget> fault; > protected BindingOperationInputTarget input; > protected BindingOperationOutputTarget output; > protected OperationTarget operation; > Binding: > protected List<BindingOperationTarget> bindingOperation; > protected PortTypeTarget portType; -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2014