March 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Kurt Stam edited comment on SRAMP-113 at 3/4/13 11:39 AM: ---------------------------------------------------------- Yeah that's exactly what I was wondering in my first comment. I'm leaning towards proposing to adding it to the spec. I think it may be of interest for clients to access this piece of information. was (Author: kurtstam): Yeah that's exactly what I was wondering in my first comment. I'm leaning towards proposing to adding it to the spec. I think it may be of interest for client to access this piece of information. > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Kurt Stam commented on SRAMP-113: --------------------------------- Yeah that's exactly what I was wondering in my first comment. I'm leaning towards proposing to adding it to the spec. I think it may be of interest for client to access this piece of information. > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-113: ------------------------------------- Right, sorry - that's what I meant by "core property". It would need to be a pre-defined core property/attribute on the base artifact. I agree with all that. I guess I'm asking whether it should be in the spec (only needed if we want the value accessible to clients) or can be internal-only. If the latter, then we don't need to change the spec, and it becomes something that's implementation-specific. > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Kurt Stam commented on SRAMP-113: --------------------------------- I don't think it can be a property, or we'd have to create readonly properties. I think it needs to be an attribute on probably baseArtifactType which is set by the server and readonly for clients. > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-113: ------------------------------------- I've been thinking about artifact resolution and scoping. I think it's worth starting a thread on the dev forum for this. To your question about the hash key - should that be part of the spec or possibly an internal detail that's up to each impl? If it's used exclusively to find references (e.g. wsdl relationships), then I think it's reasonable to assume the latter. Perhaps the hash would be useful as a real property that can be consumed by clients, in which case adding it as a core property is necessary. Thoughts? > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Kurt Stam commented on SRAMP-113: --------------------------------- We should probable default to looking for "artifact in the repository" by checking the name, file size, version (if available) and hash key. If all three match, then link to that artifact rather then adding a new one. Do we need to propose hash key to be on the baseArtifactType in the spec? > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-113: ---------------------------- Fix Version/s: 0.2.0 - Milestone 4 (was: 0.3.0 - Future (Unscheduled)) > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-29) Add support for Stored Queries

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-29?page=com.atlassian.jira.plugin.s... ] Kurt Stam updated SRAMP-29: --------------------------- Fix Version/s: 0.2.0 - Milestone 4 (was: 0.3.0 - Future (Unscheduled)) Affects Version/s: (was: 0.3.0 - Future (Unscheduled)) > Add support for Stored Queries > ------------------------------ > > Key: SRAMP-29 > URL: https://issues.jboss.org/browse/SRAMP-29 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Section 4.6 of the S-RAMP spec discusses stored queries. We need to add support for them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-40) Implement support for s-ramp properties

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-40?page=com.atlassian.jira.plugin.s... ] Eric Wittmann resolved SRAMP-40. -------------------------------- Resolution: Done All sub-tasks have been completed. > Implement support for s-ramp properties > --------------------------------------- > > Key: SRAMP-40 > URL: https://issues.jboss.org/browse/SRAMP-40 > Project: S-RAMP > Issue Type: Feature Request > Components: Atom Binding, Core, Persistence > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.2.0 - Milestone 4 > > > We need to add support for s-ramp properties. See the s-ramp specification (atom binding and foundation document) for details about properties. We need support in the following places: > 1) persistence layer > 2) artifact update > 3) get full artifact details > 4) query filtering > 5) artifact feed via ad-hoc query and specified extra properties (see atom api binding doc, section 3.2) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-40) Implement support for s-ramp properties

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-40?page=com.atlassian.jira.plugin.s... ] Eric Wittmann closed SRAMP-40. ------------------------------ > Implement support for s-ramp properties > --------------------------------------- > > Key: SRAMP-40 > URL: https://issues.jboss.org/browse/SRAMP-40 > Project: S-RAMP > Issue Type: Feature Request > Components: Atom Binding, Core, Persistence > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.2.0 - Milestone 4 > > > We need to add support for s-ramp properties. See the s-ramp specification (atom binding and foundation document) for details about properties. We need support in the following places: > 1) persistence layer > 2) artifact update > 3) get full artifact details > 4) query filtering > 5) artifact feed via ad-hoc query and specified extra properties (see atom api binding doc, section 3.2) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2013