[
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