[overlord-issues] [JBoss JIRA] (SRAMP-531) Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side
[
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)