From issues at jboss.org Mon Dec 1 09:14:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 1 Dec 2014 09:14:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-620) Support basic auth for REST services using users configured in KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-620: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/242 > Support basic auth for REST services using users configured in KeyCloak > ----------------------------------------------------------------------- > > Key: RTGOV-620 > URL: https://issues.jboss.org/browse/RTGOV-620 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > KeyCloak SSO support is being added in RTGOV-609. However it is currently not possible to have a REST service both support KeyCloak bearer tokens and basic auth (using KeyCloak's configured users). > Need to find way to support basic auth for REST services to maintain backward compatible usage. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 09:14:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 1 Dec 2014 09:14:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-620) Support basic auth for REST services using users configured in KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-620. ------------------------------ Resolution: Done > Support basic auth for REST services using users configured in KeyCloak > ----------------------------------------------------------------------- > > Key: RTGOV-620 > URL: https://issues.jboss.org/browse/RTGOV-620 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > KeyCloak SSO support is being added in RTGOV-609. However it is currently not possible to have a REST service both support KeyCloak bearer tokens and basic auth (using KeyCloak's configured users). > Need to find way to support basic auth for REST services to maintain backward compatible usage. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 10:07:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 1 Dec 2014 10:07:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-595) List of services can't be refreshed on EAP/Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-595: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/243 > List of services can't be refreshed on EAP/Fuse > ----------------------------------------------- > > Key: RTGOV-595 > URL: https://issues.jboss.org/browse/RTGOV-595 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: EAP 6.3 + switchyard 2.0.0.Alpha2 + rtgov 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > If you access the services page, the deployed services are immediately listed correctly. When you hit the refresh button, the list of services can't be refreshed - it will hang on Finding services, please wait... (no result even after 2 mins) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 10:07:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 1 Dec 2014 10:07:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-595) List of services can't be refreshed on EAP/Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-595. ------------------------------ Resolution: Done > List of services can't be refreshed on EAP/Fuse > ----------------------------------------------- > > Key: RTGOV-595 > URL: https://issues.jboss.org/browse/RTGOV-595 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: EAP 6.3 + switchyard 2.0.0.Alpha2 + rtgov 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > If you access the services page, the deployed services are immediately listed correctly. When you hit the refresh button, the list of services can't be refreshed - it will hang on Finding services, please wait... (no result even after 2 mins) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 10:16:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 1 Dec 2014 10:16:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-627) Separate out governance from rtgov config for KeyCloak In-Reply-To: References: Message-ID: Gary Brown created RTGOV-627: -------------------------------- Summary: Separate out governance from rtgov config for KeyCloak Key: RTGOV-627 URL: https://issues.jboss.org/browse/RTGOV-627 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Currently there are two XSLT transformations, one used when there is no keycloak installed, and the other to create the config for the governance and rtgov specific details. To enable rtgov to be installed where keycloak and the governance realm have already been installed, we should separate out the governance realm creation. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 10:18:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 1 Dec 2014 10:18:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-622: ------------------------------ Summary: Relationship.getOtherAttributes() should be persisted and queryable (was: Relationship.getOtherAttributes() not persisted) > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 10:19:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 1 Dec 2014 10:19:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024166#comment-13024166 ] Brett Meyer commented on SRAMP-622: ----------------------------------- These also need to be queryable. Suggestion: /s-ramp/wsdl/WsdlDocument[includedXsds[s-ramp:getRelationshipAttribute(., 'someAttribute') = 'true]] > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 10:30:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 1 Dec 2014 10:30:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-623) Expand Java classes if referenced by WSDL, beans.xml, etc. In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-623: --------------------------------- Summary: Expand Java classes if referenced by WSDL, beans.xml, etc. Key: SRAMP-623 URL: https://issues.jboss.org/browse/SRAMP-623 Project: S-RAMP Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Currently, Java classes are expanded only if referenced by switchyard.xml. It would also be useful to expand if referenced in other ways: WSDL, beans.xml, etc. Also consider adding a config property that would expand *all* classes, regardless of references (but default to false). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 12:16:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 1 Dec 2014 12:16:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-627) Separate out governance from rtgov config for KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-627: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/244 > Separate out governance from rtgov config for KeyCloak > ------------------------------------------------------ > > Key: RTGOV-627 > URL: https://issues.jboss.org/browse/RTGOV-627 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > Currently there are two XSLT transformations, one used when there is no keycloak installed, and the other to create the config for the governance and rtgov specific details. > To enable rtgov to be installed where keycloak and the governance realm have already been installed, we should separate out the governance realm creation. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 12:16:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 1 Dec 2014 12:16:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-627) Separate out governance from rtgov config for KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-627. ------------------------------ Resolution: Done > Separate out governance from rtgov config for KeyCloak > ------------------------------------------------------ > > Key: RTGOV-627 > URL: https://issues.jboss.org/browse/RTGOV-627 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > Currently there are two XSLT transformations, one used when there is no keycloak installed, and the other to create the config for the governance and rtgov specific details. > To enable rtgov to be installed where keycloak and the governance realm have already been installed, we should separate out the governance realm creation. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 16:05:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 1 Dec 2014 16:05:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-624) Handle expanded artifacts in updateContent/deleteContent In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-624: --------------------------------- Summary: Handle expanded artifacts in updateContent/deleteContent Key: SRAMP-624 URL: https://issues.jboss.org/browse/SRAMP-624 Project: S-RAMP Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer updateContent/deleteContent currently clears out the artifacts derived from the given artifact. What if an archive is updated/deleted? Should all of its expanded artifacts also be removed? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 17:44:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 1 Dec 2014 17:44:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-580) Server-side autodetection of artifact types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-580. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Server-side autodetection of artifact types > ------------------------------------------- > > Key: SRAMP-580 > URL: https://issues.jboss.org/browse/SRAMP-580 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Currently, artifact type autodetection exists in multiple forms, nearly all of them client-side. The Maven Wagon inspects the deployment URL and makes assumptions. The UI checks file extensions. > Instead, move a more complete set of artifact-inspection logic server-side. Some semblance of this already exists, to a certain degree. For example, ZipToSrampArchiveProvider#accept(ArtifactType) already exists, but is currently used only to determine which module should expand the artifact. But, the concept could be used to define the artifact type based on the new artifact. It would require a hierarchy of sorts where the most "specialized" integrations (Switchyard, RTGov, DTGov, etc.) are considered first. If none of those "accept" the artifact, the next tier (more generic types) are considered. > The logic could be a mix of filename regex, archive inspection (ex: look for switchyard.xml), etc. > This should completely replace all other types of client-side logic. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 1 17:44:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 1 Dec 2014 17:44:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-531) Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-531. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side > --------------------------------------------------------------------------- > > Key: SRAMP-531 > URL: https://issues.jboss.org/browse/SRAMP-531 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Currently, artifacts are expanded w/ ZipToSrampArchiveRegistry/ZipToSrampArchive in multiple locations client-side. See: > - shell's UploadArtifactCommand and DeployCommand > - ui's ArtifactUploadServlet > - wagon's SrampWagon > - server's Maven facade (MavenRepositoryServiceImpl) > Consider moving the expansion somewhere central and server-side. > If the concern was that it's not spec-compliant, consider moving the expanders out of the atom module and create something isolated. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 2 07:07:39 2014 From: issues at jboss.org (Lukas Krejci (JIRA)) Date: Tue, 2 Dec 2014 07:07:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024376#comment-13024376 ] Lukas Krejci commented on SRAMP-622: ------------------------------------ Tangentially to this, Target also has "other attributes". Querying using the getRelationshipAttribute or getTargetAttribute makes even more sense in that light. > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 2 10:24:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 2 Dec 2014 10:24:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-517) Support Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned SRAMP-517: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > Support Wildfly > --------------- > > Key: SRAMP-517 > URL: https://issues.jboss.org/browse/SRAMP-517 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 2 10:52:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 2 Dec 2014 10:52:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024475#comment-13024475 ] Brett Meyer commented on SRAMP-622: ----------------------------------- I might need to hold off on the Target#otherAttributes and follow that up later. Relationship#otherAttributes is easy since it's simply an additional property on the sramp:relationship node type. But, since Target is not currently mapped in its own wrapper node type, working in open-ended attributes will be dirty. I've meant to introduce the wrapper type, but won't be able to until 1.0 (breaking change). > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 2 10:56:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 2 Dec 2014 10:56:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-625) Support Target#otherAttributes In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-625: --------------------------------- Summary: Support Target#otherAttributes Key: SRAMP-625 URL: https://issues.jboss.org/browse/SRAMP-625 Project: S-RAMP 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.8#6338) From issues at jboss.org Tue Dec 2 18:25:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 2 Dec 2014 18:25:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-626) Trim down the size of s-ramp-client's transitive dependencies In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-626: --------------------------------- Summary: Trim down the size of s-ramp-client's transitive dependencies Key: SRAMP-626 URL: https://issues.jboss.org/browse/SRAMP-626 Project: S-RAMP Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer See discussion on SRAMP-16. Add excludes for as much of s-ramp-common and s-ramp-atom's transitives as possible. Further, this will be helpful to *any* users of the client. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 2 18:26:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 2 Dec 2014 18:26:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024582#comment-13024582 ] Brett Meyer commented on SRAMP-16: ---------------------------------- Apologies for the delayed response! {quote} My suggestion is to create a s-ramp-client plugin that could be installed into the target platform/eclipse and S-RAMP IDE plugin could just reference it in its MANIFEST as required bundle. {quote} I guess I'm not quite following as to why that would be an improvement. Doesn't that simply introduce another installation step and maintain the same overall download size (between the 2 plugins)? That being said, I'm sure I could trim down the size of s-ramp-client. It currently pulls in s-ramp-common and s-ramp-atom in their entirety -- both have fairly large transitive trees. I'll take a look under SRAMP-626. > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Tue Dec 2 18:27:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 2 Dec 2014 18:27:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024583#comment-13024583 ] Brett Meyer commented on SRAMP-16: ---------------------------------- Can you bump sramp.version up to 0.6.0.Final or, even better, 0.7.0-SNAPSHOT? > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Tue Dec 2 22:01:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 2 Dec 2014 22:01:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024597#comment-13024597 ] Brett Meyer commented on SRAMP-16: ---------------------------------- I did finally have a chance to build and install the plugin. Very, very impressive for a proof of concept! Once polished, this is going to be a huge win for the project and a really useful tool. Good work! Are you guys interested in any feedback, yet? Really, it's just a few nitpicky improvements for the look and feel. Functionality wise, this is great. Once you're satistifed with where it's at, I'd say let's go ahead and integrate it as a module in the actual project, but within a branch until it's "finished". > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Wed Dec 3 04:27:39 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Wed, 3 Dec 2014 04:27:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024629#comment-13024629 ] Stefan Bunciak commented on SRAMP-16: ------------------------------------- SRAMP-626 is going to be a big deal of help. Thanks! {quote} Can you bump sramp.version up to 0.6.0.Final or, even better, 0.7.0-SNAPSHOT? {quote} Sure. {quote} Are you guys interested in any feedback, yet? Really, it's just a few nitpicky improvements for the look and feel. Functionality wise, this is great. {quote} Of course we are ;-) {quote} Once you're satistifed with where it's at, I'd say let's go ahead and integrate it as a module in the actual project, but within a branch until it's "finished". {quote} I suppose we could consider it finished later this month. It depends on how much feedback will you give us, but basically from functionality perspective I think we are done for now. So, once we incorporate your feedback we can send a pull request. > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Wed Dec 3 09:23:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 3 Dec 2014 09:23:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024752#comment-13024752 ] Brett Meyer commented on SRAMP-16: ---------------------------------- Sounds good. Can you guys bump the version up to 0.7.0-SNAPSHOT and re-test? I hit at least one error -- attempting to download a WSDL and import it into a project resulted in an exception on the server. When you're satistifed, I'll give it another in-depth go. Thanks! > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Wed Dec 3 12:40:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 3 Dec 2014 12:40:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024166#comment-13024166 ] Brett Meyer edited comment on SRAMP-622 at 12/3/14 12:39 PM: ------------------------------------------------------------- These also need to be queryable. Suggestion: /s-ramp/wsdl/WsdlDocument[someRelationship[s-ramp:getRelationshipAttribute(., 'someAttribute') = 'true']] was (Author: brmeyer): These also need to be queryable. Suggestion: /s-ramp/wsdl/WsdlDocument[includedXsds[s-ramp:getRelationshipAttribute(., 'someAttribute') = 'true]] > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 13:50:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 3 Dec 2014 13:50:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-627) Use ModeShape AST objects in SrampToJcrSql2QueryVisitor In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-627: --------------------------------- Summary: Use ModeShape AST objects in SrampToJcrSql2QueryVisitor Key: SRAMP-627 URL: https://issues.jboss.org/browse/SRAMP-627 Project: S-RAMP Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. Attempt to use ModeShape's AST objects: https://docs.jboss.org/author/display/MODE40/JCR-JQOM ModeShape also has a builder class, but it's not public and may pose additional issues. {quote} (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 13:57:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 3 Dec 2014 13:57:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024914#comment-13024914 ] Brett Meyer commented on SRAMP-622: ----------------------------------- Alright, here's where this landed. Relationship#getOtherAttributes is now persisted. The following queries are available: /s-ramp/xsd/XsdDocument[someRelationship[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue']] /s-ramp/xsd/XsdDocument[someRelationship[s-ramp:getRelationshipAttribute(., 'FooKey')]] /s-ramp/xsd/XsdDocument[someRelationship[s-ramp:getRelationshipAttribute(., 'InvalidKey')]] The last 2 essentially create a "hasRelationshipAttribute". CAVEAT! Technically, something like the following should be supported: /s-ramp/xsd/XsdDocument[someRelationship[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] That would return an XSD with a relationship containing the FooKey attribute *and* the targeted artifact containing the @FooProperty. Obviously, those would affect 2 different portions of the eventual query. However, I'm learning how brittle and fragile our current query builder really is. Under SRAMP-627, I'll be working on using an actual Builder pattern (and most likely AST objects, provided by ModeShape) that would allow that type of query. Until then, getRelationshipAttribute must be used *by itself* in a relationship predicate. Pairing it with others simply will not work. If others are needed, clients will need to omit getRelationshipAttribute, then filter using the attribute *in memory*. Hopefully that's not too limiting in the short-term. > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 15:05:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 3 Dec 2014 15:05:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-622: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/512 > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 15:05:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 3 Dec 2014 15:05:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-622. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 15:20:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 3 Dec 2014 15:20:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-628) Completely remove Fuse/Jetty/OSGi concepts In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-628: --------------------------------- Summary: Completely remove Fuse/Jetty/OSGi concepts Key: SRAMP-628 URL: https://issues.jboss.org/browse/SRAMP-628 Project: S-RAMP Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0 SRAMP-620 deprecated Fuse and Jetty support. In 1.0, take it further: 1.) completely remove the modules 2.) remove all OSGi dependencies 3.) remove Felix annotations 4.) replace "bundle" packaging with "jar" -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 09:50:39 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Thu, 4 Dec 2014 09:50:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025192#comment-13025192 ] Stefan Bunciak commented on SRAMP-16: ------------------------------------- Version updated, wsdl issue fixed (problem was when importing derived artifacts). You can give it another try ;-) Do you have some estimate when SRAMP-626 could be fixed? I suppose you target it to 0.7.0, right? > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Thu Dec 4 13:48:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 4 Dec 2014 13:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-611) Reimplement rtgov UI situation notifications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-611: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/245 > Reimplement rtgov UI situation notifications > -------------------------------------------- > > Key: RTGOV-611 > URL: https://issues.jboss.org/browse/RTGOV-611 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Current mechanism uses Errai bus to send situation created notifications to the RTGov UI. This has been disabled when moving from Errai RPC services to JAX-RS (RTGOV-610). > So this task will be to implement this same mechanism using an alternative approach (possibly websockets). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 13:48:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 4 Dec 2014 13:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-611) Reimplement rtgov UI situation notifications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-611. ------------------------------ Resolution: Done > Reimplement rtgov UI situation notifications > -------------------------------------------- > > Key: RTGOV-611 > URL: https://issues.jboss.org/browse/RTGOV-611 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Current mechanism uses Errai bus to send situation created notifications to the RTGov UI. This has been disabled when moving from Errai RPC services to JAX-RS (RTGOV-610). > So this task will be to implement this same mechanism using an alternative approach (possibly websockets). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 13:51:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 4 Dec 2014 13:51:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-628) Situation notification via websocket not working on EAP 6.3 In-Reply-To: References: Message-ID: Gary Brown created RTGOV-628: -------------------------------- Summary: Situation notification via websocket not working on EAP 6.3 Key: RTGOV-628 URL: https://issues.jboss.org/browse/RTGOV-628 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.2.0.Final Changed notification from Errai bus to websocket in RTGOV-611. It works on Wildfly, but the websocket connection results in an error on EAP 6.3, despite it apparently being supported (https://weblogs.java.net/blog/arungupta/archive/2014/05/07/websocket-jboss-eap-63-tech-tip-22). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 14:14:39 2014 From: issues at jboss.org (=?UTF-8?Q?Jan_Bou=C5=A1ka_=28JIRA=29?=) Date: Thu, 4 Dec 2014 14:14:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025292#comment-13025292 ] Jan Bou?ka commented on SRAMP-16: --------------------------------- [~brmeyer] PoC folder is not actual. Look at https://github.com/bouskaJ/-S-RAMP_repository_browser/tree/master/final/SrampRepositoryBrowser . > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Thu Dec 4 14:26:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 4 Dec 2014 14:26:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-629) Convert auth to Keycloak In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-629: --------------------------------- Summary: Convert auth to Keycloak Key: SRAMP-629 URL: https://issues.jboss.org/browse/SRAMP-629 Project: S-RAMP Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Dec 5 05:26:40 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 5 Dec 2014 05:26:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-605) Document additional properties on DroolsEventProcessor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-605: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/247 > Document additional properties on DroolsEventProcessor > ------------------------------------------------------ > > Key: RTGOV-605 > URL: https://issues.jboss.org/browse/RTGOV-605 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Document the new 'eventProcessingMode' and 'asynchronous' attributes on the Drools event processor. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Dec 5 05:27:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 5 Dec 2014 05:27:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-605) Document additional properties on DroolsEventProcessor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-605. ------------------------------ Resolution: Done > Document additional properties on DroolsEventProcessor > ------------------------------------------------------ > > Key: RTGOV-605 > URL: https://issues.jboss.org/browse/RTGOV-605 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Document the new 'eventProcessingMode' and 'asynchronous' attributes on the Drools event processor. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Dec 5 06:10:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 5 Dec 2014 06:10:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-629) Add service registry to rtgov In-Reply-To: References: Message-ID: Gary Brown created RTGOV-629: -------------------------------- Summary: Add service registry to rtgov Key: RTGOV-629 URL: https://issues.jboss.org/browse/RTGOV-629 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Copy the service registry mechanism from overlord-commons into rtgov (commons) as a step towards removing dependency on overlord commons. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Dec 5 12:31:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 5 Dec 2014 12:31:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-162) Spec: allow properties to be defined on a relationship In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-162. ----------------------------- Resolution: Duplicate Issue > Spec: allow properties to be defined on a relationship > ------------------------------------------------------ > > Key: SRAMP-162 > URL: https://issues.jboss.org/browse/SRAMP-162 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Kurt Stam > > Not necessarily for version 1.0 of the spec, but wanted to record this as a placeholder for the requirement. > Specific use-case in mind is where a relationship between a BPMN2 choreography and a BPMN2 process model needs to describe which participant the process model represents in the choreography. > Although this particular case could be addressed simply by having the same name, there may be other artifact types (i.e. not BPMN2 process models) that represent endpoint behaviour, and need to be related to the choreography with additional context (i.e. the participant name). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 09:49:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 8 Dec 2014 09:49:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-630) Exception when accessing service details from UI on EAP 6.3 In-Reply-To: References: Message-ID: Gary Brown created RTGOV-630: -------------------------------- Summary: Exception when accessing service details from UI on EAP 6.3 Key: RTGOV-630 URL: https://issues.jboss.org/browse/RTGOV-630 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final When viewing the service list, and then selecting the service, the server throws the following exception: {noformat} Caused by: java.net.URISyntaxException: Illegal character in query at index 56: http://localhost:8080/rtgov-ui/rest/services/service?id={urn\:switchyard-quickstart-demo\:orders\:0.1.0}orders:{urn\:switchyard-quickstart-demo\:orders\:0.1.0}OrderService {noformat} Also the assignment does not work on EAP 6.3, which may or may not be related. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 09:53:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 8 Dec 2014 09:53:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-629) Add service registry to rtgov In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-629: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/248 > Add service registry to rtgov > ----------------------------- > > Key: RTGOV-629 > URL: https://issues.jboss.org/browse/RTGOV-629 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Copy the service registry mechanism from overlord-commons into rtgov (commons) as a step towards removing dependency on overlord commons. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 09:53:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 8 Dec 2014 09:53:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-629) Add service registry to rtgov In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-629. ------------------------------ Resolution: Done > Add service registry to rtgov > ----------------------------- > > Key: RTGOV-629 > URL: https://issues.jboss.org/browse/RTGOV-629 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Copy the service registry mechanism from overlord-commons into rtgov (commons) as a step towards removing dependency on overlord commons. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 09:56:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 8 Dec 2014 09:56:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-631) Fix integration tests to work with KeyCloak In-Reply-To: References: Message-ID: Gary Brown created RTGOV-631: -------------------------------- Summary: Fix integration tests to work with KeyCloak Key: RTGOV-631 URL: https://issues.jboss.org/browse/RTGOV-631 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Currently integration tests don't work because installation of rtgov into EAP requires an extra manual step of uploading the governance realm. Started looking into automating this in the integration test scripts, but the problem is that the KeyCloak admin REST API (http://docs.jboss.org/keycloak/docs/1.1.0.Beta2/rest-api/admin/realms/index.html) does not explicit mention what security is used, but is likely to be bearer tokens. Ideally needs to also support basic auth. Need to see if this can be added to kc beta3. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 14:42:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 8 Dec 2014 14:42:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-626) Trim down the size of s-ramp-client's transitive dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-626 started by Brett Meyer. ----------------------------------------- > Trim down the size of s-ramp-client's transitive dependencies > ------------------------------------------------------------- > > Key: SRAMP-626 > URL: https://issues.jboss.org/browse/SRAMP-626 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > See discussion on SRAMP-16. Add excludes for as much of s-ramp-common and s-ramp-atom's transitives as possible. Further, this will be helpful to *any* users of the client. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 14:49:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 8 Dec 2014 14:49:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-626) Trim down the size of s-ramp-client's transitive dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026027#comment-13026027 ] Brett Meyer commented on SRAMP-626: ----------------------------------- Was able to trim this down to around 36.5 MB. That's probably as good as it can get... > Trim down the size of s-ramp-client's transitive dependencies > ------------------------------------------------------------- > > Key: SRAMP-626 > URL: https://issues.jboss.org/browse/SRAMP-626 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > See discussion on SRAMP-16. Add excludes for as much of s-ramp-common and s-ramp-atom's transitives as possible. Further, this will be helpful to *any* users of the client. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 14:53:18 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 8 Dec 2014 14:53:18 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-626) Trim down the size of s-ramp-client's transitive dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-626. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Trim down the size of s-ramp-client's transitive dependencies > ------------------------------------------------------------- > > Key: SRAMP-626 > URL: https://issues.jboss.org/browse/SRAMP-626 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > See discussion on SRAMP-16. Add excludes for as much of s-ramp-common and s-ramp-atom's transitives as possible. Further, this will be helpful to *any* users of the client. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 14:53:19 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 8 Dec 2014 14:53:19 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-626) Trim down the size of s-ramp-client's transitive dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026027#comment-13026027 ] Brett Meyer commented on SRAMP-626: ----------------------------------- Was able to trim this down to around 36.5 MB. That's probably as good as it can get... > Trim down the size of s-ramp-client's transitive dependencies > ------------------------------------------------------------- > > Key: SRAMP-626 > URL: https://issues.jboss.org/browse/SRAMP-626 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > See discussion on SRAMP-16. Add excludes for as much of s-ramp-common and s-ramp-atom's transitives as possible. Further, this will be helpful to *any* users of the client. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 15:07:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 8 Dec 2014 15:07:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-624) Handle expanded artifacts in updateContent/deleteContent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-624. ----------------------------- Resolution: Won't Fix For now, not fixing this. Since the expanded artifacts are themselves *primary*, imo it's different than automatically deleting derived artifacts. Clients can always query on the expandedFromDocument relationship and delete, if necessary. > Handle expanded artifacts in updateContent/deleteContent > -------------------------------------------------------- > > Key: SRAMP-624 > URL: https://issues.jboss.org/browse/SRAMP-624 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > updateContent/deleteContent currently clears out the artifacts derived from the given artifact. What if an archive is updated/deleted? Should all of its expanded artifacts also be removed? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 20:18:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 8 Dec 2014 20:18:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026088#comment-13026088 ] Brett Meyer commented on SRAMP-16: ---------------------------------- FYI, I'm releasing 0.7.0.Final, which includes SRAMP-626 > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Tue Dec 9 06:32:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 9 Dec 2014 06:32:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-630) Exception when accessing service details from UI on EAP 6.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-630: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/249 > Exception when accessing service details from UI on EAP 6.3 > ----------------------------------------------------------- > > Key: RTGOV-630 > URL: https://issues.jboss.org/browse/RTGOV-630 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When viewing the service list, and then selecting the service, the server throws the following exception: > {noformat} > Caused by: java.net.URISyntaxException: Illegal character in query at index 56: http://localhost:8080/rtgov-ui/rest/services/service?id={urn\:switchyard-quickstart-demo\:orders\:0.1.0}orders:{urn\:switchyard-quickstart-demo\:orders\:0.1.0}OrderService > {noformat} > Also the assignment does not work on EAP 6.3, which may or may not be related. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 9 06:32:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 9 Dec 2014 06:32:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-630) Exception when accessing service details from UI on EAP 6.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-630. ------------------------------ Resolution: Done > Exception when accessing service details from UI on EAP 6.3 > ----------------------------------------------------------- > > Key: RTGOV-630 > URL: https://issues.jboss.org/browse/RTGOV-630 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When viewing the service list, and then selecting the service, the server throws the following exception: > {noformat} > Caused by: java.net.URISyntaxException: Illegal character in query at index 56: http://localhost:8080/rtgov-ui/rest/services/service?id={urn\:switchyard-quickstart-demo\:orders\:0.1.0}orders:{urn\:switchyard-quickstart-demo\:orders\:0.1.0}OrderService > {noformat} > Also the assignment does not work on EAP 6.3, which may or may not be related. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 9 06:45:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 9 Dec 2014 06:45:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty In-Reply-To: References: Message-ID: Gary Brown created RTGOV-632: -------------------------------- Summary: Initial display of service list on EAP is empty Key: RTGOV-632 URL: https://issues.jboss.org/browse/RTGOV-632 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final When navigating to the 'Services' page initially, the list of services is empty. This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 9 06:48:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 9 Dec 2014 06:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP In-Reply-To: References: Message-ID: Gary Brown created RTGOV-633: -------------------------------- Summary: Situation lifecycle buttons don't react properly on EAP Key: RTGOV-633 URL: https://issues.jboss.org/browse/RTGOV-633 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action. Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 9 06:49:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 9 Dec 2014 06:49:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026211#comment-13026211 ] Gary Brown commented on RTGOV-632: ---------------------------------- When the problem occurs, this warning is shown in the console: https://github.com/keycloak/keycloak/blob/master/integration/adapter-core/src/main/java/org/keycloak/adapters/OAuthRequestAuthenticator.java#L180-L185 > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 9 06:51:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 9 Dec 2014 06:51:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026214#comment-13026214 ] Gary Brown commented on RTGOV-632: ---------------------------------- {noformat} 11:53:19,107 WARN [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-1) state parameter invalid 11:53:19,108 WARN [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-1) cookie: 90/32f24cad-0359-43d7-b333-4d84964c4522 11:53:19,108 WARN [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-1) queryParam: 89/fd66988a-e136-4502-b66d-1faa2c920112 {noformat} > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 9 07:24:40 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 9 Dec 2014 07:24:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026235#comment-13026235 ] Gary Brown commented on RTGOV-632: ---------------------------------- Further information from keycloak tracing: {noformat} 12:18:50,487 TRACE [org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (http-localhost.localdomain/127.0.0.1:8080-2) invoke 12:18:50,487 DEBUG [org.keycloak.adapters.PreAuthActionsHandler] (http-localhost.localdomain/127.0.0.1:8080-2) adminRequest http://localhost:8080/rtgov-ui/rest/services/search 12:18:50,488 TRACE [org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (http-localhost.localdomain/127.0.0.1:8080-2) *** authenticate 12:18:50,488 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) --> authenticate() 12:18:50,489 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) try bearer 12:18:50,489 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) try oauth 12:18:50,489 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) there was no code 12:18:50,489 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) redirecting to auth server 12:18:50,489 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) callback uri: http://localhost:8080/rtgov-ui/rest/services/search 12:18:50,490 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) Sending redirect to login page: http://localhost:8080/auth/realms/governance/protocol/openid-connect/login?client_id=rtgov-ui&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2Frtgov-ui%2Frest%2Fservices%2Fsearch&state=1%2Fb454c445-f576-4178-beb0-46dcc5a354e3&login=true 12:18:50,492 TRACE [org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (http-localhost.localdomain/127.0.0.1:8080-3) invoke 12:18:50,492 DEBUG [org.keycloak.adapters.PreAuthActionsHandler] (http-localhost.localdomain/127.0.0.1:8080-3) adminRequest http://localhost:8080/rtgov-ui/rest/services/applications 12:18:50,492 TRACE [org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (http-localhost.localdomain/127.0.0.1:8080-3) *** authenticate 12:18:50,492 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) --> authenticate() 12:18:50,492 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) try bearer 12:18:50,492 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) try oauth 12:18:50,493 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) there was no code 12:18:50,493 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) redirecting to auth server 12:18:50,493 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) callback uri: http://localhost:8080/rtgov-ui/rest/services/applications 12:18:50,493 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) Sending redirect to login page: http://localhost:8080/auth/realms/governance/protocol/openid-connect/login?client_id=rtgov-ui&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2Frtgov-ui%2Frest%2Fservices%2Fapplications&state=2%2F472f59e6-d801-4c73-ba21-c4b23e40df87&login=true 12:18:50,628 DEBUG [org.jboss.resteasy.core.SynchronousDispatcher] (http-localhost.localdomain/127.0.0.1:8080-3) PathInfo: /realms/governance/protocol/openid-connect/login 12:18:50,628 DEBUG [org.jboss.resteasy.core.SynchronousDispatcher] (http-localhost.localdomain/127.0.0.1:8080-2) PathInfo: /realms/governance/protocol/openid-connect/login 12:18:50,630 WARN [org.jboss.resteasy.core.ResourceLocator] (http-localhost.localdomain/127.0.0.1:8080-3) Field providers of subresource org.keycloak.protocol.oidc.OpenIDConnectService will not be injected according to spec 12:18:50,630 WARN [org.jboss.resteasy.core.ResourceLocator] (http-localhost.localdomain/127.0.0.1:8080-2) Field providers of subresource org.keycloak.protocol.oidc.OpenIDConnectService will not be injected according to spec 12:18:50,631 WARN [org.jboss.resteasy.core.ResourceLocator] (http-localhost.localdomain/127.0.0.1:8080-3) Field securityContext of subresource org.keycloak.protocol.oidc.OpenIDConnectService will not be injected according to spec 12:18:50,631 WARN [org.jboss.resteasy.core.ResourceLocator] (http-localhost.localdomain/127.0.0.1:8080-2) Field securityContext of subresource org.keycloak.protocol.oidc.OpenIDConnectService will not be injected according to spec {noformat} This would suggest that the token is not being carried by the browser (chrome) but then it should also cause problems on wildfly. > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 10 08:43:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 10 Dec 2014 08:43:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-631) Fix integration tests to work with KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-631: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/251 > Fix integration tests to work with KeyCloak > ------------------------------------------- > > Key: RTGOV-631 > URL: https://issues.jboss.org/browse/RTGOV-631 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Currently integration tests don't work because installation of rtgov into EAP requires an extra manual step of uploading the governance realm. > Started looking into automating this in the integration test scripts, but the problem is that the KeyCloak admin REST API (http://docs.jboss.org/keycloak/docs/1.1.0.Beta2/rest-api/admin/realms/index.html) does not explicit mention what security is used, but is likely to be bearer tokens. Ideally needs to also support basic auth. Need to see if this can be added to kc beta3. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 10 08:43:40 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 10 Dec 2014 08:43:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-631) Fix integration tests to work with KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-631. ------------------------------ Resolution: Done > Fix integration tests to work with KeyCloak > ------------------------------------------- > > Key: RTGOV-631 > URL: https://issues.jboss.org/browse/RTGOV-631 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Currently integration tests don't work because installation of rtgov into EAP requires an extra manual step of uploading the governance realm. > Started looking into automating this in the integration test scripts, but the problem is that the KeyCloak admin REST API (http://docs.jboss.org/keycloak/docs/1.1.0.Beta2/rest-api/admin/realms/index.html) does not explicit mention what security is used, but is likely to be bearer tokens. Ideally needs to also support basic auth. Need to see if this can be added to kc beta3. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 10 10:14:39 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Wed, 10 Dec 2014 10:14:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026729#comment-13026729 ] Stefan Bunciak commented on SRAMP-16: ------------------------------------- [~bouskaj] increased S-RAMP version to 0.7.0.Final. You can give it another test ride ;-) If you consider it good enough to create a pull request we can do so. > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > 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.8#6338) From issues at jboss.org Thu Dec 11 09:47:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 11 Dec 2014 09:47:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-629) Convert auth to Keycloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-629 started by Brett Meyer. ----------------------------------------- > Convert auth to Keycloak > ------------------------ > > Key: SRAMP-629 > URL: https://issues.jboss.org/browse/SRAMP-629 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 11 09:47:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 11 Dec 2014 09:47:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-517) Support Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-517 started by Brett Meyer. ----------------------------------------- > Support Wildfly > --------------- > > Key: SRAMP-517 > URL: https://issues.jboss.org/browse/SRAMP-517 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 11 13:22:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 11 Dec 2014 13:22:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027166#comment-13027166 ] Gary Brown commented on RTGOV-632: ---------------------------------- KeyCloak issue reported as: https://issues.jboss.org/browse/KEYCLOAK-873 > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 11 13:22:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 11 Dec 2014 13:22:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-632: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/253 > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 11 13:23:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 11 Dec 2014 13:23:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-632. ------------------------------ Resolution: Done Worked around KeyCloak/EAP issue by serializing the REST invocations from the RTGov UI - specifically found the issue when retrieving the initial service and situations lists. > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 04:21:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 04:21:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-633: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/254 > Situation lifecycle buttons don't react properly on EAP > ------------------------------------------------------- > > Key: RTGOV-633 > URL: https://issues.jboss.org/browse/RTGOV-633 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action. > Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 04:22:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 04:22:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-633. ------------------------------ Resolution: Done > Situation lifecycle buttons don't react properly on EAP > ------------------------------------------------------- > > Key: RTGOV-633 > URL: https://issues.jboss.org/browse/RTGOV-633 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action. > Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 04:22:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 04:22:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027249#comment-13027249 ] Gary Brown commented on RTGOV-633: ---------------------------------- Fixed by changing PUT methods to POST. > Situation lifecycle buttons don't react properly on EAP > ------------------------------------------------------- > > Key: RTGOV-633 > URL: https://issues.jboss.org/browse/RTGOV-633 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action. > Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 04:34:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 04:34:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027253#comment-13027253 ] Gary Brown commented on RTGOV-633: ---------------------------------- Created KEYCLOAK-878 to report the underlying issue. > Situation lifecycle buttons don't react properly on EAP > ------------------------------------------------------- > > Key: RTGOV-633 > URL: https://issues.jboss.org/browse/RTGOV-633 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action. > Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 05:34:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 05:34:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-634) Remove Fuse/Fabric support In-Reply-To: References: Message-ID: Gary Brown created RTGOV-634: -------------------------------- Summary: Remove Fuse/Fabric support Key: RTGOV-634 URL: https://issues.jboss.org/browse/RTGOV-634 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Following a review of the current supported platforms, it has been decided to focus on Wildfly and EAP in the short/medium term and re-assess how best to support other platforms (such as Karaf/Fuse/Fabric) - possibly just providing a 'client side integration' only. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 06:09:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 06:09:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-575) endex custom loading of index mappings per .epn deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-575: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/255 > endex custom loading of index mappings per .epn deployment > ----------------------------------------------------------- > > Key: RTGOV-575 > URL: https://issues.jboss.org/browse/RTGOV-575 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Event Processor > Reporter: ivan mckinley > Assignee: Gary Brown > Labels: elasticsearch > Fix For: 2.1.0.Final > > > Prior to the karaf integration it was possible to deploy a epn with a elasticsearch store configured for a separate index as rtogv. > 1: developer would deploy a custom epn with a ElasticsearchKeyValueStore configured for a custom index and type. > 2: the elastisearchclient class would look for a file name $index-mapping.json on the path > The concept is developers can store business data they extracted from the activity events and store in ES for later analysis via kibana or what ever > unfortunately the following line > Thread.currentThread().setContextClassLoader(TransportClient.class.getClassLoader()); > in ElasticsearchClient that was added for the karaf intergration means that the classloader can not longer see any bundled $index-mappings.json file that accompany the deployed epns (.war) > one solution would be to switch to the same mechanism used to to load ip.json or epn.json files -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 06:11:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 06:11:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-575) endex custom loading of index mappings per .epn deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-575. ------------------------------ Resolution: Done [~imckinle] I've currently disabled the thread context class loader as we are dropping support for OSGi for now. However it would be useful to have a quickstart showing use of a custom Elasticsearch index, which I can then build an integration test around, to make sure this capability is supported in future. Would you be able to provide such a quickstart? (no urgent) > endex custom loading of index mappings per .epn deployment > ----------------------------------------------------------- > > Key: RTGOV-575 > URL: https://issues.jboss.org/browse/RTGOV-575 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Event Processor > Reporter: ivan mckinley > Assignee: Gary Brown > Labels: elasticsearch > Fix For: 2.1.0.Final > > > Prior to the karaf integration it was possible to deploy a epn with a elasticsearch store configured for a separate index as rtogv. > 1: developer would deploy a custom epn with a ElasticsearchKeyValueStore configured for a custom index and type. > 2: the elastisearchclient class would look for a file name $index-mapping.json on the path > The concept is developers can store business data they extracted from the activity events and store in ES for later analysis via kibana or what ever > unfortunately the following line > Thread.currentThread().setContextClassLoader(TransportClient.class.getClassLoader()); > in ElasticsearchClient that was added for the karaf intergration means that the classloader can not longer see any bundled $index-mappings.json file that accompany the deployed epns (.war) > one solution would be to switch to the same mechanism used to to load ip.json or epn.json files -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 07:02:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 07:02:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-634) Remove Fuse/Fabric support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-634: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/256 > Remove Fuse/Fabric support > -------------------------- > > Key: RTGOV-634 > URL: https://issues.jboss.org/browse/RTGOV-634 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > Following a review of the current supported platforms, it has been decided to focus on Wildfly and EAP in the short/medium term and re-assess how best to support other platforms (such as Karaf/Fuse/Fabric) - possibly just providing a 'client side integration' only. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 07:02:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 07:02:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-634) Remove Fuse/Fabric support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-634. ------------------------------ Resolution: Done > Remove Fuse/Fabric support > -------------------------- > > Key: RTGOV-634 > URL: https://issues.jboss.org/browse/RTGOV-634 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > Following a review of the current supported platforms, it has been decided to focus on Wildfly and EAP in the short/medium term and re-assess how best to support other platforms (such as Karaf/Fuse/Fabric) - possibly just providing a 'client side integration' only. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 07:06:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 07:06:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-635) Update to overlord-commons 3 In-Reply-To: References: Message-ID: Gary Brown created RTGOV-635: -------------------------------- Summary: Update to overlord-commons 3 Key: RTGOV-635 URL: https://issues.jboss.org/browse/RTGOV-635 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 10:40:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 10:40:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-635) Update to overlord-commons 3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-635: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/257 > Update to overlord-commons 3 > ---------------------------- > > Key: RTGOV-635 > URL: https://issues.jboss.org/browse/RTGOV-635 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 10:40:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 10:40:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-635) Update to overlord-commons 3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-635. ------------------------------ Resolution: Done > Update to overlord-commons 3 > ---------------------------- > > Key: RTGOV-635 > URL: https://issues.jboss.org/browse/RTGOV-635 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 11:22:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 11:22:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-567) [resubmit] missing security context propagation with RemoteMessage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-567: ----------------------------- Fix Version/s: 2.2.0.Final (was: 2.1.0.Final) > [resubmit] missing security context propagation with RemoteMessage > ------------------------------------------------------------------ > > Key: RTGOV-567 > URL: https://issues.jboss.org/browse/RTGOV-567 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Michael Clay > Assignee: Gary Brown > Fix For: 2.2.0.Final > > > currently there is no way to retry/resubmit switchyard services with a clientAuthentication policy because the context is not propagated. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 12:10:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 12 Dec 2014 12:10:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-628) Completely remove Fuse/Jetty/OSGi concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-628: ------------------------------ Fix Version/s: (was: 1.0) > Completely remove Fuse/Jetty/OSGi concepts > ------------------------------------------ > > Key: SRAMP-628 > URL: https://issues.jboss.org/browse/SRAMP-628 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > SRAMP-620 deprecated Fuse and Jetty support. In 1.0, take it further: > 1.) completely remove the modules > 2.) remove all OSGi dependencies > 3.) remove Felix annotations > 4.) replace "bundle" packaging with "jar" -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 12:10:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 12 Dec 2014 12:10:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-628) Completely remove Fuse/Jetty/OSGi concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-628 started by Brett Meyer. ----------------------------------------- > Completely remove Fuse/Jetty/OSGi concepts > ------------------------------------------ > > Key: SRAMP-628 > URL: https://issues.jboss.org/browse/SRAMP-628 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > SRAMP-620 deprecated Fuse and Jetty support. In 1.0, take it further: > 1.) completely remove the modules > 2.) remove all OSGi dependencies > 3.) remove Felix annotations > 4.) replace "bundle" packaging with "jar" -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 12:23:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 12:23:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-636) Enable integration tests to run on EAP and/or Wildfly In-Reply-To: References: Message-ID: Gary Brown created RTGOV-636: -------------------------------- Summary: Enable integration tests to run on EAP and/or Wildfly Key: RTGOV-636 URL: https://issues.jboss.org/browse/RTGOV-636 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta2 Currently integration tests only run against a pre-downloaded EAP. Now that Wildfly is supported, enable integration tests to be run against it, and download Wildfly if not available. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 13:11:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 13:11:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-637) Kibana console not working on EAP with KeyCloak In-Reply-To: References: Message-ID: Gary Brown created RTGOV-637: -------------------------------- Summary: Kibana console not working on EAP with KeyCloak Key: RTGOV-637 URL: https://issues.jboss.org/browse/RTGOV-637 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Dec 12 13:14:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 12 Dec 2014 13:14:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-638) Warning messages/exceptions about Errai classes not found In-Reply-To: References: Message-ID: Gary Brown created RTGOV-638: -------------------------------- Summary: Warning messages/exceptions about Errai classes not found Key: RTGOV-638 URL: https://issues.jboss.org/browse/RTGOV-638 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta1 Appears that some Errai client side classes are being scanned for by weld: Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.client.api.Marshaller from [Module "deployment.overlord-rtgov-ui.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Dec 15 18:21:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 15 Dec 2014 18:21:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-630) SRAMP-626 broke the ability to pull from the S-RAMP wagon In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-630: --------------------------------- Summary: SRAMP-626 broke the ability to pull from the S-RAMP wagon Key: SRAMP-630 URL: https://issues.jboss.org/browse/SRAMP-630 Project: S-RAMP Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer SRAMP-626 was a little overzealous and broke the ability to pull from the Maven Wagon. Remove the exclusion of commons-compress -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Dec 15 18:22:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 15 Dec 2014 18:22:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-630) SRAMP-626 broke the ability to pull from the S-RAMP wagon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-630: ------------------------------ Fix Version/s: 0.8.0.Final > SRAMP-626 broke the ability to pull from the S-RAMP wagon > --------------------------------------------------------- > > Key: SRAMP-630 > URL: https://issues.jboss.org/browse/SRAMP-630 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > SRAMP-626 was a little overzealous and broke the ability to pull from the Maven Wagon. Remove the exclusion of commons-compress -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Dec 15 18:25:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 15 Dec 2014 18:25:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-630) SRAMP-626 broke the ability to pull from the S-RAMP wagon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-630. ------------------------------- Resolution: Done > SRAMP-626 broke the ability to pull from the S-RAMP wagon > --------------------------------------------------------- > > Key: SRAMP-630 > URL: https://issues.jboss.org/browse/SRAMP-630 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > SRAMP-626 was a little overzealous and broke the ability to pull from the Maven Wagon. Remove the exclusion of commons-compress -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Dec 16 17:00:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 16 Dec 2014 17:00:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-599) Batch upload through linked artifacts in a multipart POST/PUT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-599: ------------------------------ Summary: Batch upload through linked artifacts in a multipart POST/PUT (was: Batch upload through linked artifacts in a multipart POST) > Batch upload through linked artifacts in a multipart POST/PUT > ------------------------------------------------------------- > > Key: SRAMP-599 > URL: https://issues.jboss.org/browse/SRAMP-599 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > {quote} > 2.3.5.2.1 Using Batch POST > RFC 2387, "The MIME Multipart/Related Content-type" describes how to perform a multipart POST of binary documents. S-RAMP builds on this RFC to extend the IETF draft document "ATOM Multi-part Media Resource Creation" to support the simultaneous publishing of a collection of non-dependent and dependent resources and their associated metadata. With this approach it is possible, for example, to publish an XSD document which imports two other XSD documents by including it as well as its dependencies in a single POST to the repository. > The Batch POST method requires an atom entry document as the root body part. This root atom entry document points to any dependent atom entry documents contained in other body parts using atom:link elements with an href attribute whose value is the Content-ID of the relevant body part. It also points at the actual document content by specifying the Content-ID of the relevant body part as the value of the src attribute in the atom:content element of the atom entry document. This approach provides complete linkage between a document and its dependencies and all corresponding binary resources. > {quote} > Although we implement the archive-based method of batch uploading, we do not currently support plain multipart for multiple artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Dec 16 17:00:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 16 Dec 2014 17:00:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-599) Batch upload through linked artifacts in a multipart POST/PUT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-599: ------------------------------ Description: {quote} 2.3.5.2.1 Using Batch POST RFC 2387, "The MIME Multipart/Related Content-type" describes how to perform a multipart POST of binary documents. S-RAMP builds on this RFC to extend the IETF draft document "ATOM Multi-part Media Resource Creation" to support the simultaneous publishing of a collection of non-dependent and dependent resources and their associated metadata. With this approach it is possible, for example, to publish an XSD document which imports two other XSD documents by including it as well as its dependencies in a single POST to the repository. The Batch POST method requires an atom entry document as the root body part. This root atom entry document points to any dependent atom entry documents contained in other body parts using atom:link elements with an href attribute whose value is the Content-ID of the relevant body part. It also points at the actual document content by specifying the Content-ID of the relevant body part as the value of the src attribute in the atom:content element of the atom entry document. This approach provides complete linkage between a document and its dependencies and all corresponding binary resources. {quote} Although we implement the archive-based method of batch uploading, we do not currently support plain multipart for multiple artifacts. Support for both POST and updating through PUT is necessary. was: {quote} 2.3.5.2.1 Using Batch POST RFC 2387, "The MIME Multipart/Related Content-type" describes how to perform a multipart POST of binary documents. S-RAMP builds on this RFC to extend the IETF draft document "ATOM Multi-part Media Resource Creation" to support the simultaneous publishing of a collection of non-dependent and dependent resources and their associated metadata. With this approach it is possible, for example, to publish an XSD document which imports two other XSD documents by including it as well as its dependencies in a single POST to the repository. The Batch POST method requires an atom entry document as the root body part. This root atom entry document points to any dependent atom entry documents contained in other body parts using atom:link elements with an href attribute whose value is the Content-ID of the relevant body part. It also points at the actual document content by specifying the Content-ID of the relevant body part as the value of the src attribute in the atom:content element of the atom entry document. This approach provides complete linkage between a document and its dependencies and all corresponding binary resources. {quote} Although we implement the archive-based method of batch uploading, we do not currently support plain multipart for multiple artifacts. > Batch upload through linked artifacts in a multipart POST/PUT > ------------------------------------------------------------- > > Key: SRAMP-599 > URL: https://issues.jboss.org/browse/SRAMP-599 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > {quote} > 2.3.5.2.1 Using Batch POST > RFC 2387, "The MIME Multipart/Related Content-type" describes how to perform a multipart POST of binary documents. S-RAMP builds on this RFC to extend the IETF draft document "ATOM Multi-part Media Resource Creation" to support the simultaneous publishing of a collection of non-dependent and dependent resources and their associated metadata. With this approach it is possible, for example, to publish an XSD document which imports two other XSD documents by including it as well as its dependencies in a single POST to the repository. > The Batch POST method requires an atom entry document as the root body part. This root atom entry document points to any dependent atom entry documents contained in other body parts using atom:link elements with an href attribute whose value is the Content-ID of the relevant body part. It also points at the actual document content by specifying the Content-ID of the relevant body part as the value of the src attribute in the atom:content element of the atom entry document. This approach provides complete linkage between a document and its dependencies and all corresponding binary resources. > {quote} > Although we implement the archive-based method of batch uploading, we do not currently support plain multipart for multiple artifacts. > Support for both POST and updating through PUT is necessary. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Dec 16 17:01:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 16 Dec 2014 17:01:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-600) Support batch archive updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-600: ------------------------------ Summary: Support batch archive updates (was: Support batch updates) > Support batch archive updates > ----------------------------- > > Key: SRAMP-600 > URL: https://issues.jboss.org/browse/SRAMP-600 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > BatchResource allows batch uploads through an archive. SRAMP-599 will support batch uploads though multipart. > However, both mechanisms must also support PUT for updating artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Dec 16 17:01:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 16 Dec 2014 17:01:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-600) Support batch archive updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-600: ------------------------------ Description: BatchResource allows batch uploads through an archive, but supporting PUT for updating artifacts is also required. (was: BatchResource allows batch uploads through an archive. SRAMP-599 will support batch uploads though multipart. However, both mechanisms must also support PUT for updating artifacts.) > Support batch archive updates > ----------------------------- > > Key: SRAMP-600 > URL: https://issues.jboss.org/browse/SRAMP-600 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > BatchResource allows batch uploads through an archive, but supporting PUT for updating artifacts is also required. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Dec 16 17:02:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 16 Dec 2014 17:02:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-599) Batch upload through linked artifacts in a multipart POST/PUT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028112#comment-13028112 ] Brett Meyer commented on SRAMP-599: ----------------------------------- Pulling this out of spec-compliance tracking -- going to push back on several related items with the TC. > Batch upload through linked artifacts in a multipart POST/PUT > ------------------------------------------------------------- > > Key: SRAMP-599 > URL: https://issues.jboss.org/browse/SRAMP-599 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > {quote} > 2.3.5.2.1 Using Batch POST > RFC 2387, "The MIME Multipart/Related Content-type" describes how to perform a multipart POST of binary documents. S-RAMP builds on this RFC to extend the IETF draft document "ATOM Multi-part Media Resource Creation" to support the simultaneous publishing of a collection of non-dependent and dependent resources and their associated metadata. With this approach it is possible, for example, to publish an XSD document which imports two other XSD documents by including it as well as its dependencies in a single POST to the repository. > The Batch POST method requires an atom entry document as the root body part. This root atom entry document points to any dependent atom entry documents contained in other body parts using atom:link elements with an href attribute whose value is the Content-ID of the relevant body part. It also points at the actual document content by specifying the Content-ID of the relevant body part as the value of the src attribute in the atom:content element of the atom entry document. This approach provides complete linkage between a document and its dependencies and all corresponding binary resources. > {quote} > Although we implement the archive-based method of batch uploading, we do not currently support plain multipart for multiple artifacts. > Support for both POST and updating through PUT is necessary. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Dec 16 17:03:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 16 Dec 2014 17:03:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-599) Batch upload through linked artifacts in a multipart POST/PUT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-599: ------------------------------ Parent: (was: SRAMP-462) Issue Type: Feature Request (was: Sub-task) > Batch upload through linked artifacts in a multipart POST/PUT > ------------------------------------------------------------- > > Key: SRAMP-599 > URL: https://issues.jboss.org/browse/SRAMP-599 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > {quote} > 2.3.5.2.1 Using Batch POST > RFC 2387, "The MIME Multipart/Related Content-type" describes how to perform a multipart POST of binary documents. S-RAMP builds on this RFC to extend the IETF draft document "ATOM Multi-part Media Resource Creation" to support the simultaneous publishing of a collection of non-dependent and dependent resources and their associated metadata. With this approach it is possible, for example, to publish an XSD document which imports two other XSD documents by including it as well as its dependencies in a single POST to the repository. > The Batch POST method requires an atom entry document as the root body part. This root atom entry document points to any dependent atom entry documents contained in other body parts using atom:link elements with an href attribute whose value is the Content-ID of the relevant body part. It also points at the actual document content by specifying the Content-ID of the relevant body part as the value of the src attribute in the atom:content element of the atom entry document. This approach provides complete linkage between a document and its dependencies and all corresponding binary resources. > {quote} > Although we implement the archive-based method of batch uploading, we do not currently support plain multipart for multiple artifacts. > Support for both POST and updating through PUT is necessary. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Dec 16 18:01:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 16 Dec 2014 18:01:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-89) Create Policy derived artifact handler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-89: ----------------------------- Parent: SRAMP-462 Issue Type: Sub-task (was: Feature Request) > Create Policy derived artifact handler > -------------------------------------- > > Key: SRAMP-89 > URL: https://issues.jboss.org/browse/SRAMP-89 > Project: S-RAMP > Issue Type: Sub-task > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 18 15:58:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 18 Dec 2014 15:58:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-600) Support batch archive updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028844#comment-13028844 ] Brett Meyer commented on SRAMP-600: ----------------------------------- BatchResource already handles updates. Simply need to support PUT > Support batch archive updates > ----------------------------- > > Key: SRAMP-600 > URL: https://issues.jboss.org/browse/SRAMP-600 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > BatchResource allows batch uploads through an archive, but supporting PUT for updating artifacts is also required. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 18 15:59:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 18 Dec 2014 15:59:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-600) Support batch archive updates through PUT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-600: ------------------------------ Summary: Support batch archive updates through PUT (was: Support batch archive updates) > Support batch archive updates through PUT > ----------------------------------------- > > Key: SRAMP-600 > URL: https://issues.jboss.org/browse/SRAMP-600 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > BatchResource allows batch uploads through an archive, but supporting PUT for updating artifacts is also required. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 18 16:00:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 18 Dec 2014 16:00:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-600) Support batch archive updates through PUT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-600. ------------------------------- Fix Version/s: 0.8.0.Final Resolution: Done > Support batch archive updates through PUT > ----------------------------------------- > > Key: SRAMP-600 > URL: https://issues.jboss.org/browse/SRAMP-600 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > BatchResource allows batch uploads through an archive, but supporting PUT for updating artifacts is also required. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 18 16:00:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 18 Dec 2014 16:00:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-552) Support relationships with no target In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-552: ------------------------------ Parent: (was: SRAMP-90) Issue Type: Feature Request (was: Sub-task) > Support relationships with no target > ------------------------------------ > > Key: SRAMP-552 > URL: https://issues.jboss.org/browse/SRAMP-552 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.1.2 > "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target." > Currently, this causes: > {code} > Caused by: javax.jcr.PathNotFoundException: No item exists at path sramp:relationshipType relative to /s-ramp/artifacts/4a/97/7b/bd-ab9b-4f00-b7b5-25f62f04eb45/sramp-relationships:null in workspace "default" > at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:346) > at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:108) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.updateGenericRelationships(ArtifactToJCRNodeVisitor.java:267) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visitBase(ArtifactToJCRNodeVisitor.java:128) > at org.overlord.sramp.common.visitors.HierarchicalArtifactVisitorAdapter.visit(HierarchicalArtifactVisitorAdapter.java:209) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visit(ArtifactToJCRNodeVisitor.java:310) > at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.overlord.sramp.common.visitors.ArtifactVisitorHelper.visitArtifact(ArtifactVisitorHelper.java:41) > at org.overlord.sramp.repository.jcr.JCRArtifactPersister.persistArtifactPhase1(JCRArtifactPersister.java:138) > at org.overlord.sramp.repository.jcr.JCRPersistence.persistArtifact(JCRPersistence.java:177) > ... 47 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Dec 18 16:01:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 18 Dec 2014 16:01:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-90) Support for Relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-90. ------------------------------ Fix Version/s: 0.7.0.Final Resolution: Done > Support for Relationships > ------------------------- > > Key: SRAMP-90 > URL: https://issues.jboss.org/browse/SRAMP-90 > Project: S-RAMP > Issue Type: Task > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 0.7.0.Final > > > Create support for relationships in s-ramp. -- This message was sent by Atlassian JIRA (v6.3.11#6341)