[JBoss JIRA] (ARTIF-625) Support Target#otherAttributes
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-625?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on ARTIF-625:
-----------------------------------
Ensure adequate coverage of the following queries
A's that own a relationship named "relName" and that relationship includes the "a" otherAttribute.
A[relName[s-ramp:getRelationshipAttribute(.,"a")=1]]
A's that own a relationship named "relName" and that relationship includes the "a" otherAttribute. The relationship also must target a B with the UUID "foo".
A[relName[s-ramp:getRelationshipAttribute(.,"a")=1 and @uuid="foo"]]
B's that are targeted by a relationship, owned by A w/ the given predicates, named "relName" and that relationship includes the "a" otherAttribute.
A[predicates]/relName[s-ramp:getRelationshipAttribute(.,"a")=1]
All the above also apply to getTargetAttribute (otherAttributes on the Relationship#Target).
Other examples from [~lkrejci], all of which should be supported:
/s-ramp/ext/Vertex[@uuid=A]/r[s-ramp:getTargetAttribute(.,"a")=1]
/s-ramp/ext/Vertex[r[s-ramp:getTargetAttribute(.,"a")=1 and @uuid="B"]]
> Support Target#otherAttributes
> ------------------------------
>
> Key: ARTIF-625
> URL: https://issues.jboss.org/browse/ARTIF-625
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0
>
>
> Target is currently mapped directly on the sramp:relationship node type, through the following:
> {code}
> - sramp:targetType (string) multiple
> - sramp:relationshipTarget (weakreference) multiple < 'sramp:baseArtifactType'
> {code}
> Instead, that needs pulled out into a separate sramp:target type. Then, also include the following, necessary for Target#otherAttributes:
> {code}
> - * (string)
> - * (string) multiple
> {code}
> Add support for storing Target#otherAttributes in the visitors. See Relationship#otherAttributes and SRAMP-622.
> This needs to wait till 1.0 as it's a breaking change in the CND.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-16) Eclipse IDE: S-RAMP tooling
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-16?page=com.atlassian.jira.plugin.s... ]
Brett Meyer commented on ARTIF-16:
----------------------------------
Correct, thanks!
> Eclipse IDE: S-RAMP tooling
> ---------------------------
>
> Key: ARTIF-16
> URL: https://issues.jboss.org/browse/ARTIF-16
> Project: Artificer
> 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.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-16) Eclipse IDE: S-RAMP tooling
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/ARTIF-16?page=com.atlassian.jira.plugin.s... ]
Stefan Bunciak commented on ARTIF-16:
-------------------------------------
You want us to send the PR to https://github.com/ArtificerRepo/artificer repo right?
> Eclipse IDE: S-RAMP tooling
> ---------------------------
>
> Key: ARTIF-16
> URL: https://issues.jboss.org/browse/ARTIF-16
> Project: Artificer
> 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.11#6341)
9 years, 11 months
[JBoss JIRA] (RTGOV-639) Support fasterxml jackson annotations
by Gary Brown (JIRA)
Gary Brown created RTGOV-639:
--------------------------------
Summary: Support fasterxml jackson annotations
Key: RTGOV-639
URL: https://issues.jboss.org/browse/RTGOV-639
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Beta2
Models used with json currently support the older jackson annotations. These models also need to support the fasterxml version, e.g. as used by camel.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months