[JBoss JIRA] (SRAMP-533) Wire ZipToSrampArchiveProvider#getArchiveTypeHints up to the UI
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-533:
---------------------------------
Summary: Wire ZipToSrampArchiveProvider#getArchiveTypeHints up to the UI
Key: SRAMP-533
URL: https://issues.jboss.org/browse/SRAMP-533
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
Uploading an artifact through the UI doesn't kick off ZipToSrampArchiveProvider#getArchiveTypeHints to go through all the integration projects and attempt to discover what to use. Make it so!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (SRAMP-531) Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-531?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-531:
-------------------------------------
I'm in favor of this in general. I think it's very problematic to have it working client-side. The advantage of course would be that our clients would provide the expander feature regardless of the server impl. Not sure that's much of one.
> Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side
> ---------------------------------------------------------------------------
>
> Key: SRAMP-531
> URL: https://issues.jboss.org/browse/SRAMP-531
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Currently, artifacts are expanded w/ ZipToSrampArchiveRegistry/ZipToSrampArchive in multiple locations client-side. See:
> - shell's UploadArtifactCommand and DeployCommand
> - ui's ArtifactUploadServlet
> - wagon's SrampWagon
> - server's Maven facade (MavenRepositoryServiceImpl)
> Consider moving the expansion somewhere central and server-side.
> If the concern was that it's not spec-compliant, consider moving the expanders out of the atom module and create something isolated.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (SRAMP-532) Tag RTGov deployable artifacts with appropriate type
by Gary Brown (JIRA)
Gary Brown created SRAMP-532:
--------------------------------
Summary: Tag RTGov deployable artifacts with appropriate type
Key: SRAMP-532
URL: https://issues.jboss.org/browse/SRAMP-532
Project: S-RAMP
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Brett Meyer
Fix For: 0.5.0.Beta4
RTGov deployable artifacts can be created as jars (for OSGi) and wars (for JEE).
There are four types of artifact, identified by a JSON file in their root:
Event Processor Network - epn.json
Activity Validator - av.json
Information Processor - ip.json
Active Collection Source - acs.json
If each of these types can have a classification.
Additionally, as part of the RTGov tooling work, a templating approach is likely to be used to help create instances of these deployable artifacts from parameterised versions. These templated instances would need to be classified differently. To identify a templated approach, a "-template.json" name will be used, e.g. the Event Processor Network template would be "epn-template.json".
So if each of these file names could be used to classify the templated versions.
Therefore 8 classifications in total should be catered for.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-548) Create maven archetypes for RTGov
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-548?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-548:
----------------------------------
Initially should create pom's using the sramp wagon (if the user wants to deploy to sramp and then can also be requested to enter the sramp URL). Instructions here: http://docs.jboss.org/overlord/sramp/0.5.0.Beta3/html/_overlord_s_ramp_ma...
> Create maven archetypes for RTGov
> ---------------------------------
>
> Key: RTGOV-548
> URL: https://issues.jboss.org/browse/RTGOV-548
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: David virgil naranjo
> Fix For: 2.1.0.Final
>
>
> Create maven archetypes for the RTGov governance artifacts for JEE and OSGi.
> The archetypes intended for JEE will create war files, the ones intended for OSGi will create jars. The samples can be used to identify the contents of these wars/jars.
> The archetypes will be required to create a basic template for the Event Processor Networks (EPN), Activity Validators (AV), Information Processors (IP) and Active Collection Sources (ACS). Users will then add specific details manually, including details in the relevant json files, and any additional dependencies.
> One specific note - when a war is deployed in EAP (and eventually WildFly), it will use the dependency (currently defined in the manifest) on overlord-rtgov.war to obtain its dependencies. When we support other JEE containers, then we may need to ask the user for the specific container and change the created maven project accordingly.
> So this work can either create a single archetype which requests details about which artifact is being created, and whether OSGi or JEE, or could be separate archetypes.
> I think my preference currently is a single archetype that asks questions to determine what should be created, as this can then easily evolve as changes are required.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (SRAMP-531) Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-531?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-531:
-----------------------------------
[~eric.wittmann], any other thoughts?
> Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side
> ---------------------------------------------------------------------------
>
> Key: SRAMP-531
> URL: https://issues.jboss.org/browse/SRAMP-531
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Currently, artifacts are expanded w/ ZipToSrampArchiveRegistry/ZipToSrampArchive in multiple locations client-side. See:
> - shell's UploadArtifactCommand and DeployCommand
> - ui's ArtifactUploadServlet
> - wagon's SrampWagon
> - server's Maven facade (MavenRepositoryServiceImpl)
> Consider moving the expansion somewhere central and server-side.
> If the concern was that it's not spec-compliant, consider moving the expanders out of the atom module and create something isolated.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (SRAMP-531) Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-531:
---------------------------------
Summary: Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side
Key: SRAMP-531
URL: https://issues.jboss.org/browse/SRAMP-531
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
Currently, artifacts are expanded w/ ZipToSrampArchiveRegistry/ZipToSrampArchive in multiple locations client-side. See:
- shell's UploadArtifactCommand and DeployCommand
- ui's ArtifactUploadServlet
- wagon's SrampWagon
- server's Maven facade (MavenRepositoryServiceImpl)
Consider moving the expansion somewhere central and server-side.
If the concern was that it's not spec-compliant, consider moving the expanders out of the atom module and create something isolated.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months