Downloads of v 2.5.10:


Last Update:

15 Mar 2019

Package Maintainer(s):

Software Author(s):

  • Victor Meszaros - Nimirium Ltd


webswing java swing webapp

Webswing (Install)

  • 1
  • 2
  • 3

2.5.10 | Updated: 15 Mar 2019



Downloads of v 2.5.10:



Software Author(s):

  • Victor Meszaros - Nimirium Ltd

  • 1
  • 2
  • 3
Webswing (Install) 2.5.10

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


To install Webswing (Install), run the following command from the command line or from PowerShell:


To upgrade Webswing (Install), run the following command from the command line or from PowerShell:


To uninstall Webswing (Install), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade webswing -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade webswing -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure webswing installed
    name: webswing
    state: present
    version: 2.5.10
    source: STEP 3 URL

See docs at

chocolatey_package 'webswing' do
  action    :install
  version  '2.5.10'
  source   'STEP 3 URL'

See docs at

    Name: webswing,
    Version: 2.5.10,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller webswing
   Name     = 'webswing'
   Ensure   = 'Present'
   Version  = '2.5.10'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'webswing':
  provider => 'chocolatey',
  ensure   => '2.5.10',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install webswing version="2.5.10" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator mkevenaar on 16 Mar 2019.


For many years Swing has been the framework of choice for many companies and individuals for creating rich applications. They all invested a lot of money and effort into developing these applications. But nowadays, the Swing framework is becoming the limiting factor for them, because they are not able to use these applications in modern web browsers. And with the Applet technology support being discontinued, it leaves these companies with very few options.

This is where Webswing comes to the rescue. With virtually no extra work, the Swing application or Applet can instantly be used in a browser just like the native application. All it takes is a simple configuration using the built-in admin web interface.

Webswing offers a unique and instant solution for:

  • Swing Applications
  • Java Applets
  • Netbeans Platform Applications
  • JavaFx Applications (beta)

All this with:

  • No browser plugin required - only HTML5
  • No code modification or conversion
  • Works with every framework

And as a bonus you get:

  • monitoring
  • live control of user sessions
  • recording and playback of sessions
  • memory, CPU usage statistics
  • logs viewer
  • advanced access control

$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = "${env:ProgramFiles(x86)}\Webswing"
  url           = $url
  softwareName  = 'Webswing*'
  checksum      = 'F32ABBBE36AFAD2D92879E5812DC55A5515BEFF5920BA620BA98C7268E3C5E4D'
  checksumType  = 'sha256'
  silentArgs   = ''

Install-ChocolateyZipPackage @packageArgs
$ErrorActionPreference = 'Stop'; # stop on all errors

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'ChocoWebswing*'  #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
  ZipFileName   = ''

$uninstalled = $false

function Uninstall-ChocolateyZipPackageFix {
    [parameter(Mandatory=$true, Position=0)][string] $packageName,
    [parameter(Mandatory=$true, Position=1)][string] $zipFileName,
    [parameter(ValueFromRemainingArguments = $true)][Object[]] $ignoredArguments

  Write-FunctionCallLogMessage -Invocation $MyInvocation -Parameters $PSBoundParameters

  $zipContentFile=(join-path $packagelibPath $zipFileName) + "Install.txt"

  # The Zip Content File may have previously existed under a different
  # name.  If *Install.txt doesn't exist, check for the old name
  if(-Not (Test-Path -Path $zipContentFile)) {
    $zipContentFile=(Join-Path $packagelibPath -ChildPath $zipFileName) + ".txt"

  if ((Test-Path -path $zipContentFile)) {
    $zipContents=get-content $zipContentFile
    foreach ($fileInZip in $zipContents) {
      if ($fileInZip -ne $null -and $fileInZip.Trim() -ne '') {
        Remove-Item -Path "$fileInZip" -ErrorAction SilentlyContinue -Recurse -Force


Uninstall-ChocolateyZipPackageFix @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

This package has no dependencies.

Discussion for the Webswing (Install) Package

Ground Rules:

  • This discussion is only about Webswing (Install) and the Webswing (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Webswing (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus