[JBoss JIRA] (SRAMP-472) Selenium UI tests
by David virgil naranjo (JIRA)
David virgil naranjo created SRAMP-472:
------------------------------------------
Summary: Selenium UI tests
Key: SRAMP-472
URL: https://issues.jboss.org/browse/SRAMP-472
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: David virgil naranjo
Assignee: Brett Meyer
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (SRAMP-182) Make artifact type detection less generic (atom layer)
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-182?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-182:
--------------------------------
Fix Version/s: 0.6.0
(was: 0.5.0.Final)
> Make artifact type detection less generic (atom layer)
> ------------------------------------------------------
>
> Key: SRAMP-182
> URL: https://issues.jboss.org/browse/SRAMP-182
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Atom Binding, Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.6.0
>
>
> Currently the artifact type detection methods are very generic and do not consider the context. There are two basic scenarios where an artifact type must be detected from an Atom Entry:
> 1) atom summary entries
> 2) full atom entries
> In the former case we need to figure out the type based on meta-data in the Entry, such as the URL, or from the 'x-s-ramp:2010:type' Category (for example)
> In the latter case, we should look at the wrapped artifact itself (there will be an <artifact> custom element in the Atom Entry with a single child - that single child is the full artifact meta-data, and the element name will indicate the type).
> Currently we just try both under all circumstances. I want to change from "getArtifactTypeFromEntry" to two methods:
> getArtifactTypeFromSummaryEntry
> getArtifactTypeFromFullEntry
> Callers must know what they have (summary or full). This should be known in all cases.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (SRAMP-170) Atom feeds do not work very well in exisiting clients
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-170?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-170:
--------------------------------
Fix Version/s: 0.6.0
(was: 0.5.0.Final)
> Atom feeds do not work very well in exisiting clients
> -----------------------------------------------------
>
> Key: SRAMP-170
> URL: https://issues.jboss.org/browse/SRAMP-170
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Atom Binding
> Affects Versions: 0.1.1 - Workflow Demo
> Reporter: Kurt Stam
> Assignee: Brett Meyer
> Priority: Minor
> Fix For: 0.6.0
>
> Attachments: Screen Shot 2013-03-10 at 12.08.22 PM.png
>
>
> When using exiting atom clients our feed don't work very well. I think one should be able to follow links down into an entry for example, but the link is not populated. We should investigate why this is.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (SRAMP-161) S-RAMP Client: obey endpoints found in /servicedocument
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-161?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-161:
--------------------------------
Fix Version/s: 0.6.0
(was: 0.5.0.Final)
> S-RAMP Client: obey endpoints found in /servicedocument
> -------------------------------------------------------
>
> Key: SRAMP-161
> URL: https://issues.jboss.org/browse/SRAMP-161
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: S-RAMP API
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.6.0
>
>
> Currently we use the non-normative URL formats suggested in the S-RAMP Atom Binding document as presumptive endpoints for the various artifact types. Instead, the Atom API Java client should obey the endpoints it finds in the /servicedocument. This means it will *always* query that service document.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (SRAMP-202) The not() function doesn't quite work with relationships
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-202?page=com.atlassian.jira.plugin.... ]
Eric Wittmann reassigned SRAMP-202:
-----------------------------------
Assignee: Brett Meyer (was: Eric Wittmann)
> The not() function doesn't quite work with relationships
> --------------------------------------------------------
>
> Key: SRAMP-202
> URL: https://issues.jboss.org/browse/SRAMP-202
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Priority: Minor
> Fix For: 0.5.0.Final
>
>
> The not() function works well with properties, but not quite with relationships. An example of what doesn't work:
> /s-ramp/wsdl/Part[not(element)]
> That should return all Parts that do *not* have an element relationship. Since relationships are found by doing a JOIN, it's actually tricky to invert. Right now I think the query engine will produce something that would return all Parts that have some *other* relationship - but it won't return Parts without any relationships at all. I'm not sure how to do the latter other than by using an IN with a subquery (which is supported by ModeShape but is non-standard).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months