July 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-500) Improve the S-RAMP demo README files

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-500: ----------------------------------- Summary: Improve the S-RAMP demo README files Key: SRAMP-500 URL: https://issues.jboss.org/browse/SRAMP-500 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Brett Meyer >From David via his 0.5.0.Beta1 Testing: S-ramp DEMO README files. The majority of them are a copy/paste (not always). Here what can happen to user is that as you realized about the copy paste, then you do not read the README files, and they are not useful. I think we could explain little bit more in detail what the test is doing in terms of: - 2 files are uploaded: specify the names. - Then a query that checks the property name 'xxx' is executed... This can give more value to the good tests we have, and the user would read the README file. That for me is very important. A good example of Test Output is the s-ramp-demos-simple-client: {code} Uploading some XML schemas... Uploading artifact ws-humantask.xsd...done. Updating meta-data for artifact ws-humantask.xsd...done. Uploading artifact ws-humantask-context.xsd...done. Updating meta-data for artifact ws-humantask-context.xsd...done. Uploading artifact ws-humantask-policy.xsd...done. Updating meta-data for artifact ws-humantask-policy.xsd...done. Uploading artifact ws-humantask-types.xsd...done. Updating meta-data for artifact ws-humantask-types.xsd...done. Uploading artifact ws-humantask-leantask-api.wsdl...done. Updating meta-data for artifact ws-humantask-leantask-api.wsdl...done. Uploading artifact ws-humantask-protocol.wsdl...done. Updating meta-data for artifact ws-humantask-protocol.wsdl...done. Querying the S-RAMP repository for Schemas...success: 11 Schemas found: * address.xsd (b885aebb-9f84-424d-af1e-84e335163be7) * person.xsd (895719d6-0daa-448b-87c8-6085021e29ba) * ws-humantask-context.xsd (fb253cc7-d576-4127-b331-cc384218bc06) * ws-humantask-policy.xsd (2eebffe7-2e02-4985-b04f-24e6025489c3) * ws-humantask-types.xsd (cfa90bea-c27c-49bb-8ac2-604f2a3763f3) * ws-humantask.xsd (a3bc7c9f-54fa-489e-845c-a328ab968bd9) * wsrm-1.1-schema-200702.xsd (54731483-c7d1-40d6-b152-f332bebf17d1) * wsrmp-1.2-schema-200702.xsd (f3007bee-353e-4e1b-a79d-0aea85c7b1ed) * wss-wssecurity-secext-1.0.xsd (8cef7a73-e284-411e-9af9-9b1ada31f623) * wss-wssecurity-utility-1.0.xsd (cee6023f-e26f-4240-baa6-594d1eea4928) * wstx-wsba-1.1-schema-200701.xsd (30246422-dc4e-4bc6-8317-8d58a73e3c64) {code} It gives explanations about the files uploaded and the queries done. In other tests just it is said 2 files uploaded, and then query done sucessfully. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-499) Include another filter for Expanded (similar to Derived)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-499?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-499: ------------------------------------- I would prefer a solution that merged these two concepts in the UI. In other words, the filter section would add "Expanded" as an option alongside Derived - perhaps changing them to checkboxes instead of radio buttons. The existing derived column could be relabeled and the value could be one of: primary, expanded, derived Only primary artifacts would be shown by default (the filter would default to primary). > Include another filter for Expanded (similar to Derived) > -------------------------------------------------------- > > Key: SRAMP-499 > URL: https://issues.jboss.org/browse/SRAMP-499 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Reported by David via his 0.5.0.Beta1 testing: > "S-ramp Artifacts --> include another column called Expanded. > Then with this we can filter the original items (for example jars, war) from the files that are expanded from those Original Artifacts uploaded. > I continue thinking that when there are many artifadts uploaded it is difficult to filter and have an easy understanding of the artifact result list. For example you see a file kmodule.xml, and you do not know to what artifact it belongs. You need to enter in the artifact to have this information. And when the number of artifacts in s-ramp is so big, then you see many many files, that you have no idea about them. > If we include this expanded column and also filter field then we could have a view of the original artifacts (with no artifact parent property). > I will prepare a html mock with my idea..." -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-499) Include another filter for Expanded (similar to Derived)

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-499: ----------------------------------- Summary: Include another filter for Expanded (similar to Derived) Key: SRAMP-499 URL: https://issues.jboss.org/browse/SRAMP-499 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Brett Meyer Reported by David via his 0.5.0.Beta1 testing: "S-ramp Artifacts --> include another column called Expanded. Then with this we can filter the original items (for example jars, war) from the files that are expanded from those Original Artifacts uploaded. I continue thinking that when there are many artifadts uploaded it is difficult to filter and have an easy understanding of the artifact result list. For example you see a file kmodule.xml, and you do not know to what artifact it belongs. You need to enter in the artifact to have this information. And when the number of artifacts in s-ramp is so big, then you see many many files, that you have no idea about them. If we include this expanded column and also filter field then we could have a view of the original artifacts (with no artifact parent property). I will prepare a html mock with my idea..." -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-498) Provide a mechanism to consume "seed data"

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-498: ----------------------------------- Summary: Provide a mechanism to consume "seed data" Key: SRAMP-498 URL: https://issues.jboss.org/browse/SRAMP-498 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Brett Meyer This is a feature request from David based on his testing of 1.3.0.Beta1 of dtgov: "Would be very nice for the user, that the first time dtgov is executed, the cli-commands file is loaded and all the dtgov artifacts are installed in s-ramp." I think the idea is that currently the user must do this manually after installing and launching s-ramp/dtgov. Instead, it would be interesting to have a way to consume this data on startup. I'm adding this as a suggested enhancment to s-ramp. If we decide this feature is not appropriate for s-ramp, then we should move it to a DTGov feature request and consider it in that context. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-497) Exclude s-ramp-demos-assembly from all distro zips

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-497: ----------------------------------- Summary: Exclude s-ramp-demos-assembly from all distro zips Key: SRAMP-497 URL: https://issues.jboss.org/browse/SRAMP-497 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Distro Reporter: Eric Wittmann Assignee: Brett Meyer Fix For: 0.5.0 Reported by David (0.5.0.Beta1 Testing): This is not a demo, but rather a packaging of the other demos. It should be excluded from all zips. Ensure that it is. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-496) Maven Facade not working for artifacts with classifier (sources, tests, etc)

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-496: ----------------------------------- Summary: Maven Facade not working for artifacts with classifier (sources, tests, etc) Key: SRAMP-496 URL: https://issues.jboss.org/browse/SRAMP-496 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: David virgil naranjo Fix For: 0.5.0 Reported by David (0.5.0.Beta1 Testing): Maven repository servlet --> Not working in case of files that contains a classifier in its name, like sources or test. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-495) Artifact Content (download) link not working in s-ramp

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-495: ----------------------------------- Summary: Artifact Content (download) link not working in s-ramp Key: SRAMP-495 URL: https://issues.jboss.org/browse/SRAMP-495 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: S-RAMP API, UI Reporter: Eric Wittmann Assignee: Brett Meyer Fix For: 0.5.0 Reported by David (Beta1 testing): The artifact content link in the s-ramp artifact details is not working: Image related: artifact_content_link.jpeg Link not working: http://localhost:8080/s-ramp-server/s-ramp/ext/DtgovWorkflowQuery/9e62a3a... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-494) Allow the installer's password prompt to be skipped

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-494?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-494: ------------------------------ Fix Version/s: 0.5.0 > Allow the installer's password prompt to be skipped > --------------------------------------------------- > > Key: SRAMP-494 > URL: https://issues.jboss.org/browse/SRAMP-494 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0 > > > The integration tests, automated installers, etc., move the password prompt into a separate target. Skip it if the password property is already set. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-494) Allow the installer's password prompt to be skipped

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-494: --------------------------------- Summary: Allow the installer's password prompt to be skipped Key: SRAMP-494 URL: https://issues.jboss.org/browse/SRAMP-494 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer The integration tests, automated installers, etc., move the password prompt into a separate target. Skip it if the password property is already set. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-518) Deploy RTGov server as a Vertx module

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-518?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-518: ----------------------------- Assignee: Marc Savy (was: Gary Brown) > Deploy RTGov server as a Vertx module > ------------------------------------- > > Key: RTGOV-518 > URL: https://issues.jboss.org/browse/RTGOV-518 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Marc Savy > Fix For: 2.1.0.Final > > > Enable the RTGov server to be used as a Vertx module. > Although the complete server could be encapsulated in a module, it may be better to separate out the main server components (e.g. ActivityStore, Event Process Network Manager, Active Collection Manager) as separate modules with appropriate inter-communication. > Also some of the existing REST services should be made available as modules. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2014