From issues at jboss.org Wed Jul 1 06:33:02 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 1 Jul 2015 06:33:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-734) Adding Ontology does not show up in the list In-Reply-To: References: Message-ID: Gary Brown created ARTIF-734: -------------------------------- Summary: Adding Ontology does not show up in the list Key: ARTIF-734 URL: https://issues.jboss.org/browse/ARTIF-734 Project: Artificer Issue Type: Bug Affects Versions: 1.0.0.Beta2 Environment: Wildfly 8.2, Firefox and Chrome Reporter: Gary Brown Assignee: Brett Meyer Tried adding an Ontology. Selecting the New button, filled in the namespace, ID and label, selected Add - it displayed a message saying Ontology with ID ... added. However the Ontology list does not show anything - even on refresh. This was in Firefox, so accessed artificer with Chrome and still didn't see anything in the Ontology list. There are no errors in the console or server.log. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 11:13:07 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 11:13:07 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-734) Adding Ontology does not show up in the list In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-734: ------------------------------ Fix Version/s: 1.0.0.Beta3 > Adding Ontology does not show up in the list > -------------------------------------------- > > Key: ARTIF-734 > URL: https://issues.jboss.org/browse/ARTIF-734 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Beta2 > Environment: Wildfly 8.2, Firefox and Chrome > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > Tried adding an Ontology. Selecting the New button, filled in the namespace, ID and label, selected Add - it displayed a message saying Ontology with ID ... added. > However the Ontology list does not show anything - even on refresh. This was in Firefox, so accessed artificer with Chrome and still didn't see anything in the Ontology list. > There are no errors in the console or server.log. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 11:39:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 11:39:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-734) Adding Ontology does not show up in the list In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTIF-734 started by Brett Meyer. ----------------------------------------- > Adding Ontology does not show up in the list > -------------------------------------------- > > Key: ARTIF-734 > URL: https://issues.jboss.org/browse/ARTIF-734 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Beta2 > Environment: Wildfly 8.2, Firefox and Chrome > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > Tried adding an Ontology. Selecting the New button, filled in the namespace, ID and label, selected Add - it displayed a message saying Ontology with ID ... added. > However the Ontology list does not show anything - even on refresh. This was in Firefox, so accessed artificer with Chrome and still didn't see anything in the Ontology list. > There are no errors in the console or server.log. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 11:41:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 11:41:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-734) Adding Ontology does not show up in the list In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-734. ------------------------------- Resolution: Done #getOntologies query was using an inner join on its root classes, rather than a left join (prevented new ontologies with no classes from showing up). Good catch... > Adding Ontology does not show up in the list > -------------------------------------------- > > Key: ARTIF-734 > URL: https://issues.jboss.org/browse/ARTIF-734 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Beta2 > Environment: Wildfly 8.2, Firefox and Chrome > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > Tried adding an Ontology. Selecting the New button, filled in the namespace, ID and label, selected Add - it displayed a message saying Ontology with ID ... added. > However the Ontology list does not show anything - even on refresh. This was in Firefox, so accessed artificer with Chrome and still didn't see anything in the Ontology list. > There are no errors in the console or server.log. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 11:57:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 11:57:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-735) Batch uploads do not create JMS events In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-735: --------------------------------- Summary: Batch uploads do not create JMS events Key: ARTIF-735 URL: https://issues.jboss.org/browse/ARTIF-735 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 Currently, JMS events are sent only for single uploads. They're entirely skipped for batches. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 12:35:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 12:35:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-735) Archive uploads do not create JMS events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-735: ------------------------------ Summary: Archive uploads do not create JMS events (was: Batch uploads do not create JMS events) > Archive uploads do not create JMS events > ---------------------------------------- > > Key: ARTIF-735 > URL: https://issues.jboss.org/browse/ARTIF-735 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > Currently, JMS events are sent only for single uploads. They're entirely skipped for batches. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 12:36:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 12:36:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-735) Archive uploads do not create JMS events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-735: ------------------------------ Description: Currently, JMS events are sent only for single uploads. They're entirely skipped for artifacts expanded from within an archive. (was: Currently, JMS events are sent only for single uploads. They're entirely skipped for batches.) > Archive uploads do not create JMS events > ---------------------------------------- > > Key: ARTIF-735 > URL: https://issues.jboss.org/browse/ARTIF-735 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > Currently, JMS events are sent only for single uploads. They're entirely skipped for artifacts expanded from within an archive. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 16:11:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 16:11:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-736) Support local-file upload optimization in web UI In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-736: --------------------------------- Summary: Support local-file upload optimization in web UI Key: ARTIF-736 URL: https://issues.jboss.org/browse/ARTIF-736 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer ARTIF-728 added server endpoints that allow a file, available to the Artificer server (local file, network storage, etc), to be persisted without passing the actual contents through HTTP. However, due to the web UI's use of HTML forms and servlets, this poses a challenge. I'm not sure that we could handle that in Errai, deciding between sending the content to the servlet or instead processing the form input's absolute path. Instead, it might be best to hold off on this until the UI is converted to Angular. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 16:13:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 16:13:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-728) Add upload endpoint that takes a local file path In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-728: ------------------------------ Fix Version/s: 1.0.0.Beta3 > Add upload endpoint that takes a local file path > ------------------------------------------------ > > Key: ARTIF-728 > URL: https://issues.jboss.org/browse/ARTIF-728 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > On the server and all clients, add a new upload endpoint that takes a local file path, instead of an InputStream/byte[]. If the file is available on/to the server's machine, there should be no reason why we can't simply use it, rather than pass it through the web service. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 16:13:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 16:13:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-728) Add upload endpoint that takes a local file path In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-728. ------------------------------- Resolution: Done > Add upload endpoint that takes a local file path > ------------------------------------------------ > > Key: ARTIF-728 > URL: https://issues.jboss.org/browse/ARTIF-728 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > On the server and all clients, add a new upload endpoint that takes a local file path, instead of an InputStream/byte[]. If the file is available on/to the server's machine, there should be no reason why we can't simply use it, rather than pass it through the web service. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 19:39:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 1 Jul 2015 19:39:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-735) Archive uploads do not create JMS events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-735. ------------------------------- Resolution: Done > Archive uploads do not create JMS events > ---------------------------------------- > > Key: ARTIF-735 > URL: https://issues.jboss.org/browse/ARTIF-735 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > Currently, JMS events are sent only for single uploads. They're entirely skipped for artifacts expanded from within an archive. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 11:41:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 2 Jul 2015 11:41:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-737) Execute batch persist in single transaction In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-737: --------------------------------- Summary: Execute batch persist in single transaction Key: ARTIF-737 URL: https://issues.jboss.org/browse/ARTIF-737 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 If any piece of a batch (and therefore, expanded archives, etc.) persist fails, the entire thing should be rolled back. Currently, each artifact in the batch is persisted in its own transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 11:44:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 2 Jul 2015 11:44:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-738) Make filesystem content storage the default In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-738: --------------------------------- Summary: Make filesystem content storage the default Key: ARTIF-738 URL: https://issues.jboss.org/browse/ARTIF-738 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 Blob as the default is already causing heap space issues (Hibernate uses a lot to write out the Blob, etc.). I think it makes a lot more sense to use the filesystem as the default. Update the docs as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 12:02:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 2 Jul 2015 12:02:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-738) Make filesystem content storage the default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer deleted ARTIF-738: ------------------------------ > Make filesystem content storage the default > ------------------------------------------- > > Key: ARTIF-738 > URL: https://issues.jboss.org/browse/ARTIF-738 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Blob as the default is already causing heap space issues (Hibernate uses a lot to write out the Blob, etc.). I think it makes a lot more sense to use the filesystem as the default. Update the docs as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 13:15:05 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 2 Jul 2015 13:15:05 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-732) Allow nested artifact expansion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-732: ------------------------------ Fix Version/s: (was: 1.0.0.Beta3) > Allow nested artifact expansion > ------------------------------- > > Key: ARTIF-732 > URL: https://issues.jboss.org/browse/ARTIF-732 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Ex: Upload a dist ZIP which contains two WARs. Currently, the root ZIP will be the "expandedFromArchive" target for all artifacts, even the artifacts expanded from the WARs. Instead, ArtifactServiceImpl#upload should allow nested expansion, where each level of "expandedFromArchive" relationship creates an expansion chain. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 13:17:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 2 Jul 2015 13:17:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-732) Allow nested artifact expansion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-732: ------------------------------ Description: Ex: A distro ZIP that contains multiple WARs. 1.) Do we want to allow those WARs to become primary artifacts? Currently, nested archives are not supported -- they'll be ignored. 2.) If yes to #1, any restrictions, or should that happen by default? 3.) If yes to #1, should those nested archives also be expanded themselves? My gut says "no" to all of them. But, if someone has a reason why nested archives should be supported, I'm all ears. was:Ex: Upload a dist ZIP which contains two WARs. Currently, the root ZIP will be the "expandedFromArchive" target for all artifacts, even the artifacts expanded from the WARs. Instead, ArtifactServiceImpl#upload should allow nested expansion, where each level of "expandedFromArchive" relationship creates an expansion chain. > Allow nested artifact expansion > ------------------------------- > > Key: ARTIF-732 > URL: https://issues.jboss.org/browse/ARTIF-732 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Ex: A distro ZIP that contains multiple WARs. 1.) Do we want to allow those WARs to become primary artifacts? Currently, nested archives are not supported -- they'll be ignored. 2.) If yes to #1, any restrictions, or should that happen by default? 3.) If yes to #1, should those nested archives also be expanded themselves? > My gut says "no" to all of them. But, if someone has a reason why nested archives should be supported, I'm all ears. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 13:17:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 2 Jul 2015 13:17:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-732) Allow nested archive expansion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-732: ------------------------------ Summary: Allow nested archive expansion (was: Allow nested artifact expansion) > Allow nested archive expansion > ------------------------------ > > Key: ARTIF-732 > URL: https://issues.jboss.org/browse/ARTIF-732 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Ex: A distro ZIP that contains multiple WARs. 1.) Do we want to allow those WARs to become primary artifacts? Currently, nested archives are not supported -- they'll be ignored. 2.) If yes to #1, any restrictions, or should that happen by default? 3.) If yes to #1, should those nested archives also be expanded themselves? > My gut says "no" to all of them. But, if someone has a reason why nested archives should be supported, I'm all ears. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 14:08:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 2 Jul 2015 14:08:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-737) Execute batch persist in single transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-737. ------------------------------- Resolution: Done > Execute batch persist in single transaction > ------------------------------------------- > > Key: ARTIF-737 > URL: https://issues.jboss.org/browse/ARTIF-737 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > If any piece of a batch (and therefore, expanded archives, etc.) persist fails, the entire thing should be rolled back. Currently, each artifact in the batch is persisted in its own transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 14:09:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 6 Jul 2015 14:09:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-739) Upgrade Keycloak to 1.3.x In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-739: --------------------------------- Summary: Upgrade Keycloak to 1.3.x Key: ARTIF-739 URL: https://issues.jboss.org/browse/ARTIF-739 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 15:30:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 6 Jul 2015 15:30:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-675) Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-675: ------------------------------ Description: Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. Ideas (from various sources): - Provides a catalog of information, what services exist and are available for use - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. - Provides information about the version of the services - Allows you to record and retrieve multiple versions of the same service - Allows you to dynamically refer to the latest version of the service - Allows dynamically at runtime to search and select end-point chosen service - Collects information who and what services are used - Provides information that services are repeatedly used and which are not - Determining the impact of changes the services to existing dependent services - Providing information to consumers of the services about ongoing or planned changes to of the services - Identify the environments (OS, app server, etc.) supported by the artifact - Differentiate between front and back end artifacts - Security: what version of SSL is used, etc. (extremely valuable for security audits) - "Deployment" - "RESTFulApplication" was: Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. Ideas (from various sources): - Provides a catalog of information, what services exist and are available for use - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. - Provides information about the version of the services - Allows you to record and retrieve multiple versions of the same service - Allows you to dynamically refer to the latest version of the service - Allows dynamically at runtime to search and select end-point chosen service - Collects information who and what services are used - Provides information that services are repeatedly used and which are not - Determining the impact of changes the services to existing dependent services - Providing information to consumers of the services about ongoing or planned changes to of the services - Identify the environments (OS, app server, etc.) supported by the artifact - Differentiate between front and back end artifacts - Security: what version of SSL is used, etc. (extremely valuable for security audits) > Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services" > ------------------------------------------------------------------------------------ > > Key: ARTIF-675 > URL: https://issues.jboss.org/browse/ARTIF-675 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. > Ideas (from various sources): > - Provides a catalog of information, what services exist and are available for use > - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. > - Provides information about the version of the services > - Allows you to record and retrieve multiple versions of the same service > - Allows you to dynamically refer to the latest version of the service > - Allows dynamically at runtime to search and select end-point chosen service > - Collects information who and what services are used > - Provides information that services are repeatedly used and which are not > - Determining the impact of changes the services to existing dependent services > - Providing information to consumers of the services about ongoing or planned changes to of the services > - Identify the environments (OS, app server, etc.) supported by the artifact > - Differentiate between front and back end artifacts > - Security: what version of SSL is used, etc. (extremely valuable for security audits) > - "Deployment" > - "RESTFulApplication" -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 15:47:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 6 Jul 2015 15:47:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-740) Automatically create "deployment" artifacts from Fabric8 events In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-740: --------------------------------- Summary: Automatically create "deployment" artifacts from Fabric8 events Key: ARTIF-740 URL: https://issues.jboss.org/browse/ARTIF-740 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 15:48:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 6 Jul 2015 15:48:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-741) Automatically create "deployment" artifacts from Wildfly events (DMR or MBean) In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-741: --------------------------------- Summary: Automatically create "deployment" artifacts from Wildfly events (DMR or MBean) Key: ARTIF-741 URL: https://issues.jboss.org/browse/ARTIF-741 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 15:50:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 6 Jul 2015 15:50:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-670) Support "forced deletes" (no constraint checks) in the UIs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-670: ------------------------------ Summary: Support "forced deletes" (no constraint checks) in the UIs (was: Support both "Move to Trash" and "Permanently Delete" in the UIs) > Support "forced deletes" (no constraint checks) in the UIs > ---------------------------------------------------------- > > Key: ARTIF-670 > URL: https://issues.jboss.org/browse/ARTIF-670 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > ARTIF-678 created "forced deletes". Once role-based access is in place (ARTIF-163), support the capability in the UIs. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 15:55:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 6 Jul 2015 15:55:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-648) New artifact type: DDL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086886#comment-13086886 ] Brett Meyer commented on ARTIF-648: ----------------------------------- Initially, keep it simple. 2 extended types: SQLScript DDLSQLScript (assume this is the case if any 'create table' exists) > New artifact type: DDL > ---------------------- > > Key: ARTIF-648 > URL: https://issues.jboss.org/browse/ARTIF-648 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:11:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 12:11:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-23) Statically validate a parsed S-RAMP Query In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087479#comment-13087479 ] Brett Meyer commented on ARTIF-23: ---------------------------------- I'd argue that this may be better built into the grammar parser itself, paired with adequate/unique Exception messages. > Statically validate a parsed S-RAMP Query > ----------------------------------------- > > Key: ARTIF-23 > URL: https://issues.jboss.org/browse/ARTIF-23 > Project: Artificer > Issue Type: Feature Request > Components: Core > Affects Versions: 0.6.0.Final > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > Implement a validator that can take an S-RAMP Query and ensure that it is valid (does not violate any of the restrictions imposed by the S-RAMP Query API specification). > The result should simply be a validator that accepts a parsed S-RAMP Query and throws an exception if the Query is invalid. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:13:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 12:13:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-214: ------------------------------ Summary: When uploading a jar - upload a text file with the output of jar tf (was: When uploading a jar - upload a text file with the output of jar tv) > When uploading a jar - upload a text file with the output of jar tf > ------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:14:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 12:14:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tvf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-214: ------------------------------ Summary: When uploading a jar - upload a text file with the output of jar tvf (was: When uploading a jar - upload a text file with the output of jar tf) > When uploading a jar - upload a text file with the output of jar tvf > -------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:14:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 12:14:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tvf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-214: ------------------------------ Description: It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf > jar-content.txt file and upload that to s-ramp too (was: It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tf > jar-content.txt file and upload that to s-ramp too) > When uploading a jar - upload a text file with the output of jar tvf > -------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:16:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 12:16:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tvf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087480#comment-13087480 ] Brett Meyer commented on ARTIF-214: ----------------------------------- Alternative: store the text file, but not as an artifact. Archive artifacts would have both their real content, as well as a "content list" stored. Both would be available through separate endpoints. The latter would also be available through a new UI tab. > When uploading a jar - upload a text file with the output of jar tvf > -------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:18:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 12:18:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tvf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087480#comment-13087480 ] Brett Meyer edited comment on ARTIF-214 at 7/7/15 12:17 PM: ------------------------------------------------------------ Alternative: store the text file, but not as an artifact. Archive artifacts would have both their real content, as well as a "content list" stored. Both would be available through separate endpoints. The latter would also be available through a new UI tab. In general, I'm trying to avoid new derived artifact types if they are not useful on their own. In this case, it's purely additional metadata for an archive artifact, so I'd prefer to stick to a new field. Thoughts? was (Author: brmeyer): Alternative: store the text file, but not as an artifact. Archive artifacts would have both their real content, as well as a "content list" stored. Both would be available through separate endpoints. The latter would also be available through a new UI tab. > When uploading a jar - upload a text file with the output of jar tvf > -------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:22:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 12:22:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-742) Implement Liquibase strategy for DDL upgrades In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-742: --------------------------------- Summary: Implement Liquibase strategy for DDL upgrades Key: ARTIF-742 URL: https://issues.jboss.org/browse/ARTIF-742 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:24:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 12:24:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tvf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087482#comment-13087482 ] Brett Meyer commented on ARTIF-214: ----------------------------------- Blocked by ARTIF-742. Need Liquibase in place before I can add new DDL fields. > When uploading a jar - upload a text file with the output of jar tvf > -------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:17:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:17:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-743) CLI audit:showAuditTrail returns nothing, even after updateMetaData In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-743: --------------------------------- Summary: CLI audit:showAuditTrail returns nothing, even after updateMetaData Key: ARTIF-743 URL: https://issues.jboss.org/browse/ARTIF-743 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:17:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:17:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-744) CLI: GetContentCommand's --help doesn't work In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-744: --------------------------------- Summary: CLI: GetContentCommand's --help doesn't work Key: ARTIF-744 URL: https://issues.jboss.org/browse/ARTIF-744 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 May need to debug Aesh or its logs to figure out why -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:18:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:18:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-745) CLI: GetContentCommand won't overwrite an existing file In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-745: --------------------------------- Summary: CLI: GetContentCommand won't overwrite an existing file Key: ARTIF-745 URL: https://issues.jboss.org/browse/ARTIF-745 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:18:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:18:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-746) CLI: GetContentCommand's output file should be optional In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-746: --------------------------------- Summary: CLI: GetContentCommand's output file should be optional Key: ARTIF-746 URL: https://issues.jboss.org/browse/ARTIF-746 Project: Artificer Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer Default to printing to the console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:20:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:20:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-747) CLI: StatusCommand missing i18n values In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-747: --------------------------------- Summary: CLI: StatusCommand missing i18n values Key: ARTIF-747 URL: https://issues.jboss.org/browse/ARTIF-747 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 artificer> status Artificer Connection: http://localhost:8080/artificer-server Artificer Artifact: wsrm-1.1-wsdl-200702e1.wsdl WsdlDocument !!Status.Status6!! -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:24:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:24:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-744) CLI: GetContentCommand's --help doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087529#comment-13087529 ] Brett Meyer commented on ARTIF-744: ----------------------------------- Ditto for storedQuery create and storedQuery update, but the rest of the storedQuery commands work > CLI: GetContentCommand's --help doesn't work > -------------------------------------------- > > Key: ARTIF-744 > URL: https://issues.jboss.org/browse/ARTIF-744 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > May need to debug Aesh or its logs to figure out why -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:27:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:27:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Keycloak's token expires really quickly In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-748: --------------------------------- Summary: Keycloak's token expires really quickly Key: ARTIF-748 URL: https://issues.jboss.org/browse/ARTIF-748 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 Happens in a matter of minutes 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:46:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:46:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-747) CLI: StatusCommand missing i18n values In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-747. ------------------------------- Resolution: Done > CLI: StatusCommand missing i18n values > -------------------------------------- > > Key: ARTIF-747 > URL: https://issues.jboss.org/browse/ARTIF-747 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > artificer> status > Artificer Connection: http://localhost:8080/artificer-server > Artificer Artifact: wsrm-1.1-wsdl-200702e1.wsdl WsdlDocument > !!Status.Status6!! -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:50:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 14:50:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-743) CLI audit:showAuditTrail returns nothing, even after updateMetaData In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer deleted ARTIF-743: ------------------------------ > CLI audit:showAuditTrail returns nothing, even after updateMetaData > ------------------------------------------------------------------- > > Key: ARTIF-743 > URL: https://issues.jboss.org/browse/ARTIF-743 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 15:40:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 15:40:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-749) HibernateAuditor fails to handle property/classifier updates In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-749: --------------------------------- Summary: HibernateAuditor fails to handle property/classifier updates Key: ARTIF-749 URL: https://issues.jboss.org/browse/ARTIF-749 Project: Artificer Issue Type: Bug Affects Versions: 1.0.0.Beta2 Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 When the original ArtificerArtifact is given to HibernateAuditor, it incorrectly uses the actual collection references as its snapshot. When these are changed, the references change as well, so the diff doesn't see the modifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 15:46:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 15:46:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-749) HibernateAuditor fails to handle property/classifier updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-749. ------------------------------- Resolution: Done > HibernateAuditor fails to handle property/classifier updates > ------------------------------------------------------------ > > Key: ARTIF-749 > URL: https://issues.jboss.org/browse/ARTIF-749 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Beta2 > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > When the original ArtificerArtifact is given to HibernateAuditor, it incorrectly uses the actual collection references as its snapshot. When these are changed, the references change as well, so the diff doesn't see the modifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 16:51:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 16:51:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-748: ------------------------------ Description: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} Errai then reports an uncaught was: Happens in a matter of minutes 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > If the token expires, the server spits out: > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > Errai then reports an uncaught -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 16:51:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 16:51:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-748: ------------------------------ Summary: Web UI: Refresh to /login when Keycloak token expires (was: Keycloak's token expires really quickly) > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > Happens in a matter of minutes > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 16:55:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 16:55:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-748: ------------------------------ Description: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan uses was: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} Errai then reports an uncaught > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > If the token expires, the server spits out: > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan uses -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 16:57:08 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 16:57:08 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-748: ------------------------------ Description: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. Idea: Have a pure Javascript loop "ping" the UI services and check the response. was: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan uses > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > If the token expires, the server spits out: > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 16:57:08 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 16:57:08 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-748: ------------------------------ Fix Version/s: (was: 1.0.0.Beta3) > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 16:58:08 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 16:58:08 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087554#comment-13087554 ] Brett Meyer commented on ARTIF-748: ----------------------------------- [~eric.wittmann], thanks again for the help. Am I missing anything here? > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 16:58:10 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 16:58:10 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-748: ------------------------------ Description: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. Idea: Have a pure Javascript loop "ping" the UI services and check the response. was: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. Idea: Have a pure Javascript loop "ping" the UI services and check the response. > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 17:19:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 17:19:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-746) CLI: GetContentCommand's output file should be optional In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-746: ------------------------------ Fix Version/s: 1.0.0.Beta3 > CLI: GetContentCommand's output file should be optional > ------------------------------------------------------- > > Key: ARTIF-746 > URL: https://issues.jboss.org/browse/ARTIF-746 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > > Default to printing to the console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 17:19:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 17:19:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-745) CLI: GetContentCommand won't overwrite an existing file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-745: ------------------------------ Fix Version/s: 1.0.0.Beta3 > CLI: GetContentCommand won't overwrite an existing file > ------------------------------------------------------- > > Key: ARTIF-745 > URL: https://issues.jboss.org/browse/ARTIF-745 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 17:21:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 17:21:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-744) CLI: GetContentCommand's --help doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087558#comment-13087558 ] Brett Meyer commented on ARTIF-744: ----------------------------------- Only affected commands with required options. --help simply needed 'overrideRequired = true' on its @Option. > CLI: GetContentCommand's --help doesn't work > -------------------------------------------- > > Key: ARTIF-744 > URL: https://issues.jboss.org/browse/ARTIF-744 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > > May need to debug Aesh or its logs to figure out why -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 17:21:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 17:21:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-744) CLI: GetContentCommand's --help doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-744. ------------------------------- Resolution: Done > CLI: GetContentCommand's --help doesn't work > -------------------------------------------- > > Key: ARTIF-744 > URL: https://issues.jboss.org/browse/ARTIF-744 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > > May need to debug Aesh or its logs to figure out why -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 17:32:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 17:32:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-745) CLI: GetContentCommand won't overwrite an existing file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-745. ------------------------------- Resolution: Done > CLI: GetContentCommand won't overwrite an existing file > ------------------------------------------------------- > > Key: ARTIF-745 > URL: https://issues.jboss.org/browse/ARTIF-745 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 17:41:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 17:41:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-746) CLI: GetContentCommand's output file should be optional In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-746. ------------------------------- Resolution: Done > CLI: GetContentCommand's output file should be optional > ------------------------------------------------------- > > Key: ARTIF-746 > URL: https://issues.jboss.org/browse/ARTIF-746 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > > Default to printing to the console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 18:11:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 18:11:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-730) Support Wildfly 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-730: ------------------------------ Fix Version/s: 1.1.0.Final (was: 1.0.0.Final) > Support Wildfly 9 > ----------------- > > Key: ARTIF-730 > URL: https://issues.jboss.org/browse/ARTIF-730 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 18:12:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 7 Jul 2015 18:12:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-739) Upgrade Keycloak to 1.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-739: ------------------------------ Fix Version/s: 1.1.0.Final (was: 1.0.0.Final) > Upgrade Keycloak to 1.3.x > ------------------------- > > Key: ARTIF-739 > URL: https://issues.jboss.org/browse/ARTIF-739 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 10:51:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 8 Jul 2015 10:51:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-750) Create artifact "Staging" concept In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-750: --------------------------------- Summary: Create artifact "Staging" concept Key: ARTIF-750 URL: https://issues.jboss.org/browse/ARTIF-750 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Similar to Nexus, allow artifact uploads to be staged (optionally) for inspection, prior to releasing. Staged artifacts could be dropped (deleted permanently), rather than trashing. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 15:31:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 8 Jul 2015 15:31:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-518) s-ramp-dev-server 404's the UI root context In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-518. ------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) Fix Version/s: 1.1.0.Final Resolution: Done > s-ramp-dev-server 404's the UI root context > ------------------------------------------- > > Key: ARTIF-518 > URL: https://issues.jboss.org/browse/ARTIF-518 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Optional > Fix For: 1.1.0.Final > > > 404: http://localhost:8080/s-ramp-ui > works: http://localhost:8080/s-ramp-ui/index.html > Really, really low priority, but we could probably make the root context work. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 15:32:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 8 Jul 2015 15:32:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-518) dev-server 404's the UI root context In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-518: ------------------------------ Summary: dev-server 404's the UI root context (was: s-ramp-dev-server 404's the UI root context) > dev-server 404's the UI root context > ------------------------------------ > > Key: ARTIF-518 > URL: https://issues.jboss.org/browse/ARTIF-518 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Optional > Fix For: 1.1.0.Final > > > 404: http://localhost:8080/s-ramp-ui > works: http://localhost:8080/s-ramp-ui/index.html > Really, really low priority, but we could probably make the root context work. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 16:23:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 8 Jul 2015 16:23:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-575. ------------------------------- Fix Version/s: 1.1.0.Final Resolution: Done > Support stored query templates/parameter-substitution > ----------------------------------------------------- > > Key: ARTIF-575 > URL: https://issues.jboss.org/browse/ARTIF-575 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > From the Atom Binding spec, 3.3.1: > {quote} > Stored Query Entry documents MAY also be used as templates, allowing simple substitution of client specified parameter values during execution. The syntax for parameter substitution follows the XPath2 style to represent a variable within the query filter: > > $\{var-name\} > > A value for the var-name can then be specified as part of the query invocation. Default values are not supported. > {quote} > {code}s-ramp/serviceImplementation/ServiceInstance[@version >= ${MINVERSION}]>{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 16:24:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 8 Jul 2015 16:24:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087983#comment-13087983 ] Brett Meyer commented on ARTIF-575: ----------------------------------- Just went with what I suggested on the spec: query/{queryName}/results?param1=value¶m2=value > Support stored query templates/parameter-substitution > ----------------------------------------------------- > > Key: ARTIF-575 > URL: https://issues.jboss.org/browse/ARTIF-575 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > From the Atom Binding spec, 3.3.1: > {quote} > Stored Query Entry documents MAY also be used as templates, allowing simple substitution of client specified parameter values during execution. The syntax for parameter substitution follows the XPath2 style to represent a variable within the query filter: > > $\{var-name\} > > A value for the var-name can then be specified as part of the query invocation. Default values are not supported. > {quote} > {code}s-ramp/serviceImplementation/ServiceInstance[@version >= ${MINVERSION}]>{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 12:08:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 9 Jul 2015 12:08:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-225) CLI Query: option to print the next page in a query In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTIF-225 started by Brett Meyer. ----------------------------------------- > CLI Query: option to print the next page in a query > --------------------------------------------------- > > Key: ARTIF-225 > URL: https://issues.jboss.org/browse/ARTIF-225 > Project: Artificer > Issue Type: Enhancement > Components: Shell > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The CLI query command currently prints the first 100 items from the query results. It would be nice to have an option to show the next page. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 12:08:04 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 9 Jul 2015 12:08:04 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-225) CLI Query: option to print the next page in a query In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088270#comment-13088270 ] Brett Meyer commented on ARTIF-225: ----------------------------------- Adding full paging support: {code} @Option(name = "startIndex", hasValue = true, required = false, description = "Paging: start index (begins at 0)") private Integer startIndex; @Option(name = "count", hasValue = true, required = false, description = "Paging: count (# to include on page)") private Integer count; @Option(name = "page", hasValue = true, required = false, description = "Paging: page # (assumes 0 startIndex and 100 count, unless startIndex/count provided now or in the past)") private Integer page; @Option(name = "orderBy", hasValue = true, required = false, description = "Sort by this field (defaults to uuid)", defaultValue = "uuid") private String orderBy; @Option(name = "ascending", hasValue = false, required = false, description = "Sort ascending (default)") private Boolean ascending; @Option(name = "descending", hasValue = false, required = false, description = "Sort descending") private Boolean descending; {code} > CLI Query: option to print the next page in a query > --------------------------------------------------- > > Key: ARTIF-225 > URL: https://issues.jboss.org/browse/ARTIF-225 > Project: Artificer > Issue Type: Enhancement > Components: Shell > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The CLI query command currently prints the first 100 items from the query results. It would be nice to have an option to show the next page. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 13:39:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 9 Jul 2015 13:39:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-225) CLI Query: option to print the next page in a query In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-225. ------------------------------- Fix Version/s: 1.1.0.Final Resolution: Done > CLI Query: option to print the next page in a query > --------------------------------------------------- > > Key: ARTIF-225 > URL: https://issues.jboss.org/browse/ARTIF-225 > Project: Artificer > Issue Type: Enhancement > Components: Shell > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > The CLI query command currently prints the first 100 items from the query results. It would be nice to have an option to show the next page. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 13:57:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 9 Jul 2015 13:57:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-140) Create unit tests for shell commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088298#comment-13088298 ] Brett Meyer commented on ARTIF-140: ----------------------------------- For now, use aesh-extension's AeshTestCommons as the backbone. See any of the extension command's tests for examples. > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.1.0.Final > > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 10 14:50:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 10 Jul 2015 14:50:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-140) Create unit tests for shell commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088654#comment-13088654 ] Brett Meyer commented on ARTIF-140: ----------------------------------- We already fully cover (or should be fully covering) the Java client through integration tests. So for the CLI tests, I'm making them true *unit* tests by using Mockito to mock out the Java client and assert calls made to it. > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.1.0.Final > > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 12:01:03 2015 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Mon, 13 Jul 2015 12:01:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wittmann updated ARTIF-748: -------------------------------- Description: If the token expires, the server spits out: {code} 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} {code} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. Idea: Have a pure Javascript loop "ping" the UI services and check the response. was: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. Idea: Have a pure Javascript loop "ping" the UI services and check the response. > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > {code} > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > {code} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 12:04:02 2015 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Mon, 13 Jul 2015 12:04:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088957#comment-13088957 ] Eric Wittmann commented on ARTIF-748: ------------------------------------- Looks right to me. Although I thought there might be interceptors you could use either in GWT or Errai which might be able to kick in early enough for you to catch this error. Something to explore perhaps. http://docs.jboss.org/errai/2.1.0.CR1/errai/reference/html/sid-19398997.html#sid-50233520 Not sure if it's helpful or not. :( > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > {code} > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > {code} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 14:57:03 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 13 Jul 2015 14:57:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089021#comment-13089021 ] Brett Meyer commented on ARTIF-748: ----------------------------------- Thanks [~eric.wittmann]. [~csa], any thoughts on that? See my comment on KEYCLOAK-1539. Essentially, a call to JSON REST using Errai's Caller may be unauthorized. But instead of returning a 401 (or anything helpful), KeyCloak returns a login page's HTML. GWT's JSON marshallers, of course, fall over themselves. However, I was a little surprised that the error didn't hit the Caller's ErrorHandler *at all*. Should it? I'll need to play with it again to come up with a stacktrace. But regardless, if a GWT marshaller throws an exception on a REST call, could that bubble up to the ErrorHandler somehow? Or, is there a way to deal with this with some sort of Interceptor, like Eric suggested? > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > {code} > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > {code} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 14:58:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 13 Jul 2015 14:58:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089022#comment-13089022 ] Brett Meyer commented on ARTIF-748: ----------------------------------- Primarily caused by KEYCLOAK-1539. If we could configure the realm to simply respond with 401, rather than the login HTML, I'm guessing this would be a lot more straight forward... > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > {code} > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > {code} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 16:25:02 2015 From: issues at jboss.org (Christian Sadilek (JIRA)) Date: Mon, 13 Jul 2015 16:25:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089046#comment-13089046 ] Christian Sadilek commented on ARTIF-748: ----------------------------------------- [~brmeyer], I agree with your summary. Since the response code is 200 OK, Errai will try to demarshall the response which it expects to be JSON-based, as specified in @Consumes and @Produces. So, the server is really returning an invalid response and you will see an unhandled exception. Interceptors are probably not an ideal solution here as you don't know which REST call will fail after the token expired, so you'd have to intercept them all. I could easily add error handling for this case to Errai 3.2, if needed. BTW, did you already upgrade to 3.2 and GWT 2.7? > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > {code} > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > {code} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 11:14:04 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 14 Jul 2015 11:14:04 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089336#comment-13089336 ] Brett Meyer commented on ARTIF-748: ----------------------------------- [~csa], thanks much for that. I'd rather address the issues with Keycloak, rather than spin your gears on workarounds. But, thanks for ensuring I hadn't completely lost my mind ;) And yes, Artificer upgraded to Errai 3 a while back. > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > {code} > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > {code} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 15:12:04 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 14 Jul 2015 15:12:04 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-730) Support Wildfly 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089445#comment-13089445 ] Brett Meyer commented on ARTIF-730: ----------------------------------- Completed in https://github.com/brmeyer/s-ramp/tree/wildfly9. But, for now, holding. The server overlay from ARTIF-739's Keycloak upgrade no longer supports WF 8 or EAP 6, so we'd have to follow suit and drop them. Not sure if 1.1.0.Final is the place to do that -- how soon is too soon? > Support Wildfly 9 > ----------------- > > Key: ARTIF-730 > URL: https://issues.jboss.org/browse/ARTIF-730 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 22:32:01 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 14 Jul 2015 22:32:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-751) CLI: Not able to create stored query with parameters In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-751: --------------------------------- Summary: CLI: Not able to create stored query with parameters Key: ARTIF-751 URL: https://issues.jboss.org/browse/ARTIF-751 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer See description on AESH-324. There's not currently a way to provide parameters on a stored query without aesh clobbering them. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 17 04:04:03 2015 From: issues at jboss.org (Sascha Dirbach (JIRA)) Date: Fri, 17 Jul 2015 04:04:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-663) Nested SwitchYard service calls are not logged correctly In-Reply-To: References: Message-ID: Sascha Dirbach created RTGOV-663: ------------------------------------ Summary: Nested SwitchYard service calls are not logged correctly Key: RTGOV-663 URL: https://issues.jboss.org/browse/RTGOV-663 Project: RTGov (Run Time Governance) Issue Type: Bug Components: Activity Collector Affects Versions: 2.1.0.Beta1 Environment: Tested on: JBoss FSW 6.0.0 with RTGov UI Version 2 and RTGov Distribution with SwithchYard 2 & JBoss EAP 6.4 Reporter: Sascha Dirbach Assignee: Gary Brown Attachments: sy-sca-rtgov.zip When I have a SwitchYard Project with a nested service call in the same Thread (e.g. same-machine SCA service) the outer invocation information is lost in the activity collector, as the ActivityUnit is kept in a ThreadLocal member variable of org.overlord.rtgov.activity.collector.AbstractActivityCollector. By calling the nested service, the previous (outer) ActivityUnit is lost. The source code comments & documentation state that nested calls of startScope & endScope are not supported, but I think SwitchYard services with nested service calls in the same Thread are not uncommon. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 17 04:04:03 2015 From: issues at jboss.org (Sascha Dirbach (JIRA)) Date: Fri, 17 Jul 2015 04:04:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-663) Nested SwitchYard service calls are not logged correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Dirbach updated RTGOV-663: --------------------------------- Attachment: sy-sca-rtgov.zip Reproducer > Nested SwitchYard service calls are not logged correctly > -------------------------------------------------------- > > Key: RTGOV-663 > URL: https://issues.jboss.org/browse/RTGOV-663 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Activity Collector > Affects Versions: 2.1.0.Beta1 > Environment: Tested on: > JBoss FSW 6.0.0 with RTGov UI Version 2 and > RTGov Distribution with SwithchYard 2 & JBoss EAP 6.4 > Reporter: Sascha Dirbach > Assignee: Gary Brown > Attachments: sy-sca-rtgov.zip > > > When I have a SwitchYard Project with a nested service call in the same Thread (e.g. same-machine SCA service) the outer invocation information is lost in the activity collector, as the ActivityUnit is kept in a ThreadLocal member variable of org.overlord.rtgov.activity.collector.AbstractActivityCollector. By calling the nested service, the previous (outer) ActivityUnit is lost. > The source code comments & documentation state that nested calls of startScope & endScope are not supported, but I think SwitchYard services with nested service calls in the same Thread are not uncommon. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 17 04:22:03 2015 From: issues at jboss.org (Sascha Dirbach (JIRA)) Date: Fri, 17 Jul 2015 04:22:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-663) Nested SwitchYard service calls are not logged correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Dirbach updated RTGOV-663: --------------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/309 > Nested SwitchYard service calls are not logged correctly > -------------------------------------------------------- > > Key: RTGOV-663 > URL: https://issues.jboss.org/browse/RTGOV-663 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Activity Collector > Affects Versions: 2.1.0.Beta1 > Environment: Tested on: > JBoss FSW 6.0.0 with RTGov UI Version 2 and > RTGov Distribution with SwithchYard 2 & JBoss EAP 6.4 > Reporter: Sascha Dirbach > Assignee: Gary Brown > Attachments: sy-sca-rtgov.zip > > > When I have a SwitchYard Project with a nested service call in the same Thread (e.g. same-machine SCA service) the outer invocation information is lost in the activity collector, as the ActivityUnit is kept in a ThreadLocal member variable of org.overlord.rtgov.activity.collector.AbstractActivityCollector. By calling the nested service, the previous (outer) ActivityUnit is lost. > The source code comments & documentation state that nested calls of startScope & endScope are not supported, but I think SwitchYard services with nested service calls in the same Thread are not uncommon. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 20 04:49:02 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 20 Jul 2015 04:49:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-663) Nested SwitchYard service calls are not logged correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-663. ------------------------------ Resolution: Done Thanks for the contribution. > Nested SwitchYard service calls are not logged correctly > -------------------------------------------------------- > > Key: RTGOV-663 > URL: https://issues.jboss.org/browse/RTGOV-663 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Activity Collector > Affects Versions: 2.1.0.Beta1 > Environment: Tested on: > JBoss FSW 6.0.0 with RTGov UI Version 2 and > RTGov Distribution with SwithchYard 2 & JBoss EAP 6.4 > Reporter: Sascha Dirbach > Assignee: Gary Brown > Attachments: sy-sca-rtgov.zip > > > When I have a SwitchYard Project with a nested service call in the same Thread (e.g. same-machine SCA service) the outer invocation information is lost in the activity collector, as the ActivityUnit is kept in a ThreadLocal member variable of org.overlord.rtgov.activity.collector.AbstractActivityCollector. By calling the nested service, the previous (outer) ActivityUnit is lost. > The source code comments & documentation state that nested calls of startScope & endScope are not supported, but I think SwitchYard services with nested service calls in the same Thread are not uncommon. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 14:09:02 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 22 Jul 2015 14:09:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-645: ----------------------------- Fix Version/s: 2.2.0 (was: 2.1.0.Final) > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 14:09:02 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 22 Jul 2015 14:09:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-636) Enable integration tests to run on EAP and/or Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-636: ----------------------------- Fix Version/s: 2.2.0 (was: 2.1.0.Final) > 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.2.0 > > > 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.15#6346) From issues at jboss.org Wed Jul 29 03:18:02 2015 From: issues at jboss.org (Viliam Kasala (JIRA)) Date: Wed, 29 Jul 2015 03:18:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name In-Reply-To: References: Message-ID: Viliam Kasala created ARTIF-752: ----------------------------------- Summary: Change of the artificer datasource configuration does not change datasource name Key: ARTIF-752 URL: https://issues.jboss.org/browse/ARTIF-752 Project: Artificer Issue Type: Bug Affects Versions: 1.0.0.Final Reporter: Viliam Kasala Assignee: Brett Meyer Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 29 03:20:03 2015 From: issues at jboss.org (Viliam Kasala (JIRA)) Date: Wed, 29 Jul 2015 03:20:03 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093755#comment-13093755 ] Viliam Kasala commented on ARTIF-752: ------------------------------------- How would be possible to change database, when new installer (overlay) of S-RAMP will ready? There is a requirement to test all the possible supported database instances. > Change of the artificer datasource configuration does not change datasource name > -------------------------------------------------------------------------------- > > Key: ARTIF-752 > URL: https://issues.jboss.org/browse/ARTIF-752 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Final > Reporter: Viliam Kasala > Assignee: Brett Meyer > > Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 29 10:32:02 2015 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Wed, 29 Jul 2015 10:32:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093961#comment-13093961 ] Eric Wittmann commented on ARTIF-752: ------------------------------------- If you want to change the database being used, you will need to swap out the datasource file that is installed by default with one that is configured for the database you wish to test. The default datasource file is configured for H2. If you want to test using mysql, for example, you will need to remove the `artificer-h2-ds.xml` file and replace it with something like artificer-mysql-ds.xml. Additionally, you will need to manually change some properties in the `artificer.properties` file. Specifically you will need to change these values: https://github.com/ArtificerRepo/artificer/blob/master/installer/src/main/resources/updates/artificer.properties#L29-L31 The installer likely will never support anything but the default H2 configuration. So alternative DBs will always need to be configured manually. > Change of the artificer datasource configuration does not change datasource name > -------------------------------------------------------------------------------- > > Key: ARTIF-752 > URL: https://issues.jboss.org/browse/ARTIF-752 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Final > Reporter: Viliam Kasala > Assignee: Brett Meyer > > Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 31 04:44:01 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 31 Jul 2015 04:44:01 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-664) Provide a gateway to translate hawkular BTM fragments into RTGov activity events In-Reply-To: References: Message-ID: Gary Brown created RTGOV-664: -------------------------------- Summary: Provide a gateway to translate hawkular BTM fragments into RTGov activity events Key: RTGOV-664 URL: https://issues.jboss.org/browse/RTGOV-664 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.2.0 Translate any Service nodes, from BTM business transaction fragments, into Activity Events. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 31 05:03:02 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 31 Jul 2015 05:03:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-664) Provide a gateway to translate hawkular BTM fragments into RTGov activity events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-664: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/311 > Provide a gateway to translate hawkular BTM fragments into RTGov activity events > -------------------------------------------------------------------------------- > > Key: RTGOV-664 > URL: https://issues.jboss.org/browse/RTGOV-664 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > Translate any Service nodes, from BTM business transaction fragments, into Activity Events. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 31 05:03:02 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 31 Jul 2015 05:03:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-664) Provide a gateway to translate hawkular BTM fragments into RTGov activity events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-664. ------------------------------ Resolution: Done > Provide a gateway to translate hawkular BTM fragments into RTGov activity events > -------------------------------------------------------------------------------- > > Key: RTGOV-664 > URL: https://issues.jboss.org/browse/RTGOV-664 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > Translate any Service nodes, from BTM business transaction fragments, into Activity Events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)