Branch: refs/heads/master
Home:
https://github.com/idempiere/idempiere
Commit: f941c6d6cbc60808ca4cc2c9a3a22f41030eebb8
https://github.com/idempiere/idempiere/commit/f941c6d6cbc60808ca4cc2c9a3a22f41030eebb8
Author: Diego Ruiz <
1206532...@users.noreply.github.com>
Date: 2026-09-09 (Wed, 09 Sep 2026)
Changed paths:
M org.adempiere.server-feature/feature.xml
M org.adempiere.server-feature/server.product.functionaltest.launch
M org.adempiere.server-feature/server.product.launch
M org.idempiere.p2.profile/core/core.product.launch
M org.idempiere.p2.profile/extended/extended.product.launch
M org.idempiere.p2.profile/features/core/feature.xml
M org.idempiere.p2.targetplatform/base.target
M org.idempiere.p2.targetplatform/base.tpd
M org.idempiere.p2.targetplatform/maven.locations.target
M org.idempiere.p2.targetplatform/org.idempiere.p2.targetplatform.target
M org.idempiere.test/idempiere.unit.test.launch
M org.idempiere.test/idempiere.unit.test.parallel.launch
Log Message:
-----------
IDEMPIERE-6955 - Remove the SOAP web service runtime stack from core (#3333)
* IDEMPIERE-6955 - Remove the SOAP web service runtime stack from core
The SOAP module was extracted to an external extension, but its third
party runtime (Apache CXF, Spring, neethi, wsdl4j) only ever reached the
product through org.idempiere.webservices.feature. Dropping that feature
removed about twenty bundles from every product build while the launch
configurations kept listing them, so the extension still resolves in a
development launch but cannot be installed on a real installation.
Take the remaining pieces of that stack out of core as well, so the
extension can ship them itself through a library extension:
- Replace the only core usage of Spring, HtmlUtils.htmlUnescape in
CompareCtxHelpSuggestion, with StringEscapeUtils.unescapeHtml4 and drop
org.springframework.web.util from org.adempiere.ui.zk. commons-text was
already imported by that bundle.
- Remove org.apache.cxf.cxf-rt-databinding-xmlbeans, the last CXF entry,
from org.adempiere.server.feature and org.idempiere.core.feature. It
belongs to the SOAP module and is what pulled cxf-core and
xmlschema-core into the product.
- List the HK2 and Jersey bundles that the REST API extension needs
explicitly, instead of relying on them arriving transitively via CXF.
- Drop the CXF and Spring plugins that org.idempiere.core.feature had
inherited from the old web service feature list, keeping the JAX-WS
client bundles that org.idempiere.webservices.client.feature still uses.
- Remove the stale entries from the launch configurations. Spring stays in
the unit test launches because org.idempiere.test still uses it for
classpath scanning.
The product and the p2 repository now build without any CXF or Spring
bundle, and no remaining bundle has a mandatory requirement on them.
Co-Authored-By: Claude Opus 5 <
nor...@anthropic.com>
* IDEMPIERE-6955 - Spring back in core - hengsin peer review
---------
Co-authored-by: Claude Opus 5 <
nor...@anthropic.com>
To unsubscribe from these emails, change your notification settings at
https://github.com/idempiere/idempiere/settings/notifications