Migration Notes - Revision history

Diego.ruiz: Replaced content with "Category:Features Category:Migration M Category:Development‏‎ Category:Developer documentation‏‎ Category:Updated2022..."

2026-09-25T11:31:52Z

Replaced content with "Category:Features Category:Migration M Category:Development‏‎ Category:Developer documentation‏‎ Category:Updated2022..."

Show changes

CarlosRuiz: /* Version iDempiere 14 (to be released, known as master) */ IDEMPIERE-7084

2026-08-25T10:48:54Z

Version iDempiere 14 (to be released, known as master): IDEMPIERE-7084

CarlosRuiz: /* Technical Notes from 13 */

2026-06-02T13:39:19Z

Technical Notes from 13

Diego.ruiz at 09:14, 21 May 2026

2026-05-21T09:14:29Z

CarlosRuiz: /* SOAP Web Services Extracted from Core */

2026-04-23T08:04:47Z

SOAP Web Services Extracted from Core

CarlosRuiz: change to link to docs

2026-04-23T07:51:26Z

change to link to docs

Diego.ruiz: MIgration notes for IDEMPIERE66-47 and 6955

2026-04-22T11:26:28Z

MIgration notes for IDEMPIERE66-47 and 6955

CarlosRuiz: websocket and atmosphere

2026-04-21T10:15:10Z

websocket and atmosphere

CarlosRuiz: /* WebSocket as default Server Push in zkwebui */

2026-04-13T14:56:09Z

WebSocket as default Server Push in zkwebui

CarlosRuiz: typo

2026-04-04T19:43:04Z

typo

@@ Line 17: / Line 17: @@
 Websocket improves performance and reduces overhead in standard environments.
-However, WebSocket connectivity may fail in certain infrastructure configurations. Three known scenarios are affected.
+However, in case WebSocket fails or is not fit for your environment you can switch to atmosphere.
 '''To use Atmosphere:'''

← Older revision		Revision as of 13:39, 2 June 2026
Line 108:		Line 108:

	This script can also fail on versions 11 and 12, and as explained above the solution is to install the pgcrypto extension.		This script can also fail on versions 11 and 12, and as explained above the solution is to install the pgcrypto extension.
		+
		+	=== Problem with some PostgreSQL queries because of the UUID changes ===
		+
		+	For the solution of [https://idempiere.atlassian.net/browse/IDEMPIERE-6650 IDEMPIERE-6650] the JDBC URL now has the <code>stringtype=unspecified</code> to allow the postgresql backend determine the data type of the parameters.
		+
		+	However, there are certain SQL constructions that can be problematic for postgres, some of those are commonly used in jasper.
		+
		+	For example a jasper with the following where clause:
		+	<syntaxhighlight lang=sql>
		+	SELECT Name FROM C_BPartner bp WHERE ( ? IS NULL OR bp.Value=? )
		+	</syntaxhighlight>
		+	throws error <code>org.postgresql.util.PSQLException: ERROR: could not determine data type of parameter $1</code>
		+
		+	The solution is simple, the SQL must be changed to cast the binding variable (?) to the desired data type. In postgresql that can be done using <code>::varchar</code>, but this is not compatible with oracle, so it's more recommended to use the CAST function, or in case of a string you can concatenate with an empty string, like:
		+	<syntaxhighlight lang=sql>
		+	SELECT Name FROM C_BPartner bp WHERE ( ?\|\|'' IS NULL OR bp.Value=? )
		+	</syntaxhighlight>
		+
		+	For more information read [https://idempiere.atlassian.net/browse/IDEMPIERE-6650?focusedCommentId=72214 the comment here].

	=== Deprecated PO getters on X_ classes ===		=== Deprecated PO getters on X_ classes ===

← Older revision		Revision as of 09:14, 21 May 2026
Line 58:		Line 58:

	== Technical Notes from 13 ==		== Technical Notes from 13 ==
		+
		+	=== Changes in Inventory Imports via CSV ===
		+
		+	With [https://idempiere.atlassian.net/browse/IDEMPIERE-7010 IDEMPIERE-7010], the UOM and Qty Entered fields in the Physical Inventory and Inventory Increase/Decrease windows were introduced. However, existing CSV Import Formats for "Inventory Decrease/Increase" and "Physical Inventory" will fail and require updates because the old Qty fields are now read-only:
		+
		+	* In Inventory Decrease/Increase, `QtyInternalUse` must be changed to `QtyEntered`.
		+	* In Physical Inventory, `QtyCount` must be changed to `QtyEntered`.

	=== Changes in default Server Push in zkwebui ===		=== Changes in default Server Push in zkwebui ===

← Older revision		Revision as of 08:04, 23 April 2026
Line 46:		Line 46:

	This change reduces the core footprint by removing the Apache CXF framework and related WSDL libraries from base installations.		This change reduces the core footprint by removing the Apache CXF framework and related WSDL libraries from base installations.
		+
		+	See https://docs.idempiere.org/docs/new-features/v14/soap-web-services-plugin

	=== Accounting Implementation Classes Moved to org.idempiere.acct ===		=== Accounting Implementation Classes Moved to org.idempiere.acct ===

@@ Line 51: / Line 51: @@
 The accounting implementation classes (document posting logic, <code>Doc_*</code> classes, accounting schema handling) have been extracted from iDempiere core into a dedicated bundle: <code>org.idempiere.acct</code>.
-This change lays the groundwork for running iDempiere without the accounting engine. However, this is '''not yet fully supported''' in this release, some UI elements such as the '''Post button''' are still visible when the accounting bundle is absent, but clicking them will not perform any action.
+Please check for details and impact at https://docs.idempiere.org/docs/new-features/v14/accounting-plugin
 = Version iDempiere 13 =

← Older revision		Revision as of 11:26, 22 April 2026
Line 28:		Line 28:

	To use Websocket you can use <code>-Dorg.idempiere.ui.zk.serverpush=websocket</code>, or simply don't set it at all as is the default.		To use Websocket you can use <code>-Dorg.idempiere.ui.zk.serverpush=websocket</code>, or simply don't set it at all as is the default.
		+
		+	=== SOAP Web Services Extracted from Core ===
		+
		+	The SOAP Web Services bundle (<code>org.idempiere.webservice</code>) has been removed from iDempiere core and is now distributed as a separate optional plugin hosted at [https://github.com/idempiere/idempiere-soap-webservices idempiere-soap-webservices].
		+
		+	'''Required action for implementations using SOAP Web Services:'''
		+
		+	After upgrading to this release, the SOAP endpoints (<code>ModelADService</code>, <code>CompositeService</code>) will '''no longer be available''' until the plugin is explicitly installed via the Extension Manager.
		+
		+	To restore SOAP Web Services functionality:
		+	# Open the '''Extension Manager''' in iDempiere.
		+	# Install the '''iDempiere SOAP Web Services (ADInterface)''' extensions
		+
		+	'''No action is required''' for implementations that use only the REST API.
		+
		+	'''For plugin developers:''' If your custom plugin depends on SOAP web service classes (e.g. inside <code>org.idempiere.webservice.*</code>), you must update your plugin's dependency declaration in <code>MANIFEST.MF</code> to reference the new standalone bundle instead of core. Failure to do so will result in compilation errors when building against this release.
		+
		+	This change reduces the core footprint by removing the Apache CXF framework and related WSDL libraries from base installations.
		+
		+	=== Accounting Implementation Classes Moved to org.idempiere.acct ===
		+
		+	The accounting implementation classes (document posting logic, <code>Doc_*</code> classes, accounting schema handling) have been extracted from iDempiere core into a dedicated bundle: <code>org.idempiere.acct</code>.
		+
		+	This change lays the groundwork for running iDempiere without the accounting engine. However, this is '''not yet fully supported''' in this release, some UI elements such as the '''Post button''' are still visible when the accounting bundle is absent, but clicking them will not perform any action.
		+
		+	'''For standard implementations:''' No action is required. The <code>org.idempiere.acct</code> bundle is included and active by default, and behavior is identical to previous releases.
		+
		+	'''For plugin developers:''' If your custom plugin references any accounting implementation classes (e.g., <code>org.compiere.acct.</code>, <code>Doc_</code> classes, or posting-related logic), you must declare an explicit dependency on the new bundle in your <code>MANIFEST.MF</code>:
		+
		+	Require-Bundle: org.idempiere.acct
		+
		+	Plugins that do not declare this dependency '''will fail to compile''' or throw a <code>ClassNotFoundException</code> at runtime. Plugins that only reference model classes such as <code>MAcctSchema</code> or <code>MGLJournal</code> and do not invoke posting logic directly are '''not affected'''.

	= Version iDempiere 13 =		= Version iDempiere 13 =

@@ Line 7: / Line 7: @@
 [[Category:Reference]]
-= Version iDempiere 13 =
+= Version iDempiere 14 (to be released, known as master) =
-== Technical Notes from 13 ==
+== Technical Notes from 14 ==
 === WebSocket as default Server Push in zkwebui ===
-In [[ChangeLog_Release_13#2026-04-13|Release-13-2026-04-13]] this has been rolled back and the default is again atmosphere, leaving the instructions here in case somebody wants to use Websocket with release-13:
+The default server push mechanism in r14 has been set to WebSocket.
 Websocket improves performance and reduces overhead in standard environments.
@@ Line 25: / Line 23: @@
 * Connecting using a ssh tunnel for port 8443 doesn't work
-'''To use Websocket:'''
+'''To use Atmosphere:'''
 When running iDempiere setup add the following to the "Java Options": <code>-Dorg.idempiere.ui.zk.serverpush=websocket</code>
 === MAttachment.setTitle driven by list ===

@@ Line 13: / Line 13: @@
 === WebSocket as default Server Push in zkwebui ===
-The default server push mechanism for zkwebui has been migrated by default from Atmosphere to WebSocket.  This change improves performance and reduces overhead in standard environments.
+In [[ChangeLog_Release_13#2026-04-13|Release-13-2026-04-13]] this has been rolled back and the default is again atmosphere, leaving the instructions here in case somebody wants to use Websocket with release-13:
-However, WebSocket connectivity may fail in certain infrastructure configurations. Two known scenarios are affected.
+The default server push mechanism was set initially to WebSocket and reverted back to Atmosphere.
 * LXC containers: WebSocket connections may not work correctly depending on the host kernel and network configuration of the LXC environment
 * Port redirection via iptables: Redirecting port 8443 to 443 using iptables rules can break WebSocket handshake negotiation
-'''Workaround:'''
+When running iDempiere setup add the following to the "Java Options": <code>-Dorg.idempiere.ui.zk.serverpush=websocket</code>
-No functional changes are introduced by this workaround. Reverting to Atmosphere restores previous behavior without affecting iDempiere's business logic or data.
+To use Atmosphere you can use <code>-Dorg.idempiere.ui.zk.serverpush=atmosphere</code>, or simply don't set it at all.
 === MAttachment.setTitle driven by list ===

@@ Line 115: / Line 115: @@
 * <code>public static boolean showCustomize(int WindowNo, int AD_Tab_ID, Map &lt;Integer, String&gt; columnsWidth, ArrayList &lt;Integer&gt; gridFieldIds, GridView gridPanel, QuickGridView quickGridView, boolean isQuickForm)</code>
-'''Dailog'''
+'''Dialog'''
 * <code>public static boolean ask(int windowNo, String adMessage)</code>
 * <code>public static boolean ask(int windowNo, String adMessage, String additionalMessage)</code>