Configuration

java.awt.headless

—

Required. Must be set to false. SwingBridge needs a real (non-headless) AWT toolkit to render Swing components into images on the server.

applibs.dir

applibs/ next to the application JAR (or the project root in dev)

Override the directory SwingBridge scans for application JARs. See Using the applibs Directory.

swingbridge.jarlist.baseDir

JVM working directory (user.dir)

Base directory used to resolve relative paths in swing-app-jar-list.conf. See Using swing-app-jar-list.conf.

swingbridge.rcp.cluster.dir

—

NetBeans RCP only. Absolute path to a pre-built NetBeans Platform distribution directory; the highest-priority discovery source for NetBeansRcpBridge. See NetBeans RCP → Cluster Discovery.

swingbridge.errorReporting.enabled

true

When set to false, the launch-failure error view shows only the failure header — the exception type, message, and stack trace are suppressed and the report-submission form is hidden. See Launch Failure Error View below.

swingbridge.screenSize

per-user

The screen size reported to the Swing application: derived from each session’s own browser, or a fixed <width>x<height>.

swingbridge.hidpi

off

Renders the back buffer at the browser’s device pixel ratio, for crisp text on Retina and 4K displays. auto, or a fixed decimal scale.

swingbridge.hidpiMaxScale

2.0

Upper bound on the HiDPI multiplier, between 1.0 and 4.0.

swingbridge.hidpiMaxBufferPixels

8000000

Upper bound on a single window’s back buffer, in device pixels.

swingbridge.backBufferType

adaptive

Pixel format of each window’s back buffer: adaptive, argb, or 565.

swingbridge.autoFocusOnAttach

true

The canvas adopts browser focus when it appears, so keystrokes reach the Swing application without the user clicking it first. It only takes focus when nobody else is using it — an unfocused page, another surface of the same bridge, or the navigation control that brought the user to the view; fields and buttons keep their focus, and popup, combo-popup and tooltip canvases never adopt focus at all. Set to false to disable it. An unparseable value falls back to enabled.

swingbridge.wheel.pixelsPerLine

40

How many pixels of browser wheel delta count as one Swing line-scroll step, for browsers that report pixel deltas. The fractional remainder is carried per window so high-resolution wheels and trackpads scroll smoothly. A blank, non-numeric or non-positive value falls back to the default. Read once at startup.

swingbridge.frameUpdateInterval

100 (milliseconds, minimum 71)

How often SwingBridge polls each Swing window for changes and pushes the dirty regions to the browser. Lower values feel more responsive at the cost of CPU; higher values save CPU at the cost of perceived latency.

swingbridge.consoleLogPrefix

false

When set to true, every console line written by an embedded Swing application is prefixed with that instance’s run ID ([swing:<runId>]), so concurrent users' output can be told apart in the server console.

swingbridge.consoleLogMirrorFile

—

Path to a file that receives a copy of the prefixed console output, for when the server console itself is not retained.

swingbridge.includeUserInLogs

false

When set to true, the logged-in user’s name is added to every attributed log line across all channels: the console prefix becomes [swing:<runId>|<user>] and the %swingUser / %X{swingUser} pattern tokens render the name. Off by default because a user’s name is personal data; without it, the name appears only in the per-instance correlation line. Requires an identity to have been published. See Showing the Name on Every Line.

swingbridge.log.user

None

Not set by the operator: an embedded Swing application sets this property at runtime, after its own login, to publish the authenticated user’s name for log attribution. The value is routed per session, so concurrent users can’t overwrite each other. See Adding the User’s Name to the Logs.