X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.22.2a (ClamAV engine v0.102.2) X-Junk-Score: 0 [] X-KAS-Score: 0 [] Return-Path: Received: from wout1-smtp.messagingengine.com ([64.147.123.24] verified) by post.selbstdenker.com (CommuniGate Pro SMTP 6.3.7) with ESMTPS id 27028423 for webobjects-dev@wocommunity.org; Tue, 28 Dec 2021 07:29:41 +0100 Received-SPF: none receiver=post.selbstdenker.com; client-ip=64.147.123.24; envelope-from=paulh@logicsquad.net Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 654F43201C2D for ; Tue, 28 Dec 2021 01:29:19 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 28 Dec 2021 01:29:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=sJQ+9N ajRFvasaLo2PbYGy15GbmbH7HlsaVbKxTTFyo=; b=bPiR4cxNa/0JwRZF8u+wYI XA6t28CAxEOQ+TicJewoUsTZZW08WlpNmO7+04JqF7Yce/azYz4oylmre5dmm079 xNpw4LGHGmvNb2DNDiUJgNhuX9G72YrUN1FEMIWZ5yBM2PDKZ4DLBC/NcFEoQ6dx xd8+TAoHEixJe7S4yO5kpKSlJ/8ll7/QI4BzFhcwrxBjF+GGgdO+i7YBYdhJBJhw ZpBcEm9J0ajxpBVE5Tc4ij/3gG0hq8DHeccscTmsYu7GMgOh1W/TUTv4HNRkppS2 Z7zle2hHEEyGJuXMW4zb8fpAs3d73mT/lklsgk4NauFnoYXwyFRRbOSQ3TtGNhRg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddruddukedgiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtggfuffhfvfgjkffosegrtdhmrehhtddvnecuhfhrohhmpefrrghulhcu jfhorggulhgvhicuoehprghulhhhsehlohhgihgtshhquhgrugdrnhgvtheqnecuggftrf grthhtvghrnhepjeelleejfefgkeelhfdvudffgfevkeeitdeiteeihfeiudekueekgedv geetieeunecuffhomhgrihhnpehgihhthhhusgdrtghomhdplhhoghhitghsqhhurggurd hnvghtpdhlihhnkhgvughinhdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpehprghulhhhsehlohhgihgtshhquhgrugdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 28 Dec 2021 01:29:17 -0500 (EST) From: Paul Hoadley Content-Type: multipart/alternative; boundary="Apple-Mail=_6EDFE434-39F3-4833-9AA1-70FC677E6E90" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Re: [WO-DEV] Installation on osx Monterey - deployment Date: Tue, 28 Dec 2021 16:59:15 +1030 References: To: WebObjects & WOnder Development In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3608.120.23.2.7) --Apple-Mail=_6EDFE434-39F3-4833-9AA1-70FC677E6E90 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Stavros, On 28 Dec 2021, at 3:04 pm, Stavros Panidis = wrote: > Old applications run with no problems but when I deploy the new one, = built in Java 17, application does not start, even after I add: >=20 > --add-exports=3Djava.base/sun.security.action=3DALL-UNNAMED >=20 > in JavaMonitor (Additional arguments). I ran into this issue a few months ago, and discussed it in #java on = Slack. The problem is that the application launch script inside the WOA = bundle does some magic on all the arguments to get them into the right = place on the eventual command line invocation. There are two issues: (a) = --add-exports needs to appear before the Java class name on the command = line; but (b) the launch script pre-dates the existence of any arguments = that look like that, and hence doesn't move it. So it's appearing on the = command line after the class name, and has no effect. There's an easy fix, but you need to be using Maven to build: = wolifecycle-maven-plugin 2.5 will add options like this to the = *ClassPath.txt files, where they will be honoured on launch. You can = specify them in build.properties. https://github.com/wocommunity/wolifecycle-maven-plugin/pull/15 = --=20 Paul Hoadley https://logicsquad.net/ https://www.linkedin.com/company/logic-squad/ --Apple-Mail=_6EDFE434-39F3-4833-9AA1-70FC677E6E90 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Stavros,

On 28 Dec 2021, at = 3:04 pm, Stavros Panidis <stavros.panidis@gmail.com> wrote:

Old applications run with no problems but when I deploy the = new one, built in Java 17, application does not start, even after I = add:

--add-exports=3Djava.base/sun.security.action=3DALL-UNNAMED

in = JavaMonitor (Additional = arguments).
=
I ran into this issue a few months ago, and = discussed it in #java on Slack. The problem is that the application = launch script inside the WOA bundle does some magic on all the arguments = to get them into the right place on the eventual command line = invocation. There are two issues: (a) --add-exports needs to appear = before the Java class name on the command line; but (b) the launch = script pre-dates the existence of any arguments that look like that, and = hence doesn't move it. So it's appearing on the command line after the = class name, and has no effect.

There's= an easy fix, but you need to be using Maven to = build: wolifecycle-maven-plugin 2.5 will add options like this to = the *ClassPath.txt files, where they will be honoured on launch. You can = specify them in build.properties.



-- 
Paul Hoadley
https://logicsquad.net/https://www.linkedin.com/company/logic-squad/

= --Apple-Mail=_6EDFE434-39F3-4833-9AA1-70FC677E6E90--