Opentaps 1.4 to 1.5 Technical Upgrade Notes - Revision history

Sichen: /* Entity Engine Change */

2011-06-01T16:40:35Z

‎Entity Engine Change

Sichen: /* Entity Engine Change */

2010-12-22T00:35:21Z

‎Entity Engine Change

Sichen: /* Controller */

2010-12-22T00:35:01Z

‎Controller

Sichen: /* Application Changes */

2010-12-22T00:34:42Z

‎Application Changes

Sichen: /* Application Changes */

2010-12-22T00:34:25Z

‎Application Changes

Sichen: /* Web Tier Changes */

2010-12-21T23:39:39Z

‎Web Tier Changes

Sichen at 23:38, 21 December 2010

2010-12-21T23:38:00Z

Sichen: /* Controller */

2010-12-21T23:37:48Z

‎Controller

Sichen: Protected "Opentaps 1.4 to 1.5 Technical Upgrade Notes": Sysop page [edit=sysop:move=sysop]

2010-12-21T23:37:34Z

Protected "Opentaps 1.4 to 1.5 Technical Upgrade Notes": Sysop page [edit=sysop:move=sysop]

Sichen: New page: This page describes technical differences between opentaps 1.4 and 1.5. You should read it if you are upgrading or migrating code developed for opentaps 1.4 to opentaps 1.5 ===Entity Eng...

2010-12-21T23:37:33Z

New page: This page describes technical differences between opentaps 1.4 and 1.5. You should read it if you are upgrading or migrating code developed for opentaps 1.4 to opentaps 1.5 ===Entity Eng...

New page

This page describes technical differences between opentaps 1.4 and 1.5. You should read it if you are upgrading or migrating code developed for opentaps 1.4 to opentaps 1.5

===Entity Engine Change===

opentaps 1.5 now offers the multi-tenancy features of ofbiz 10.04. This means that you need to configure your database differently in `entityengine.xml`. Your delegator must now have a main and a tenant datasource:
<delegator name="default" entity-model-reader="main" entity-group-reader="main" entity-eca-reader="main" distributed-cache-clear-enabled="false">
<group-map group-name="org.ofbiz" datasource-name="localmysql"/>
<group-map group-name="org.ofbiz.olap" datasource-name="localderbyolap"/>
<group-map group-name="org.ofbiz.tenant" datasource-name="localmysql_tenant"/>
<group-map group-name="org.opentaps.analytics" datasource-name="analytics"/>
<group-map group-name="org.opentaps.testing" datasource-name="testing"/>
</delegator>

You will then need to define the datasource more than once, even if they both use the same database:
<datasource name="localmysql_tenant"
helper-class="org.ofbiz.entity.datasource.GenericHelperDAO"
field-type-name="mysql"
check-on-start="true"
add-missing-on-start="true"
check-pks-on-start="false"
use-foreign-keys="true"
join-style="ansi-no-parenthesis"
alias-view-columns="false"
drop-fk-use-foreign-key-keyword="true"
table-type="InnoDB"
character-set="latin1"
collate="latin1_general_cs">
<read-data reader-name="seed"/>
<read-data reader-name="seed-initial"/>
<read-data reader-name="demo"/>
<read-data reader-name="ext"/>
<inline-jdbc
jdbc-driver="com.mysql.jdbc.Driver"
jdbc-uri="jdbc:mysql://127.0.0.1/opentaps_1_5?autoReconnect=true&useOldAliasMetadataBehavior=true"
jdbc-username="opentaps"
jdbc-password="opentaps"
isolation-level="ReadCommitted"
pool-minsize="2"
pool-maxsize="250"
time-between-eviction-runs-millis="600000"/>

</datasource>

as well as:

<datasource name="localmysql"
helper-class="org.ofbiz.entity.datasource.GenericHelperDAO"
field-type-name="mysql"
check-on-start="true"
add-missing-on-start="true"
check-pks-on-start="false"
use-foreign-keys="true"
join-style="ansi-no-parenthesis"
alias-view-columns="false"
drop-fk-use-foreign-key-keyword="true"
table-type="InnoDB"
character-set="latin1"
collate="latin1_general_cs">
<read-data reader-name="seed"/>
<read-data reader-name="seed-initial"/>
<read-data reader-name="demo"/>
<read-data reader-name="ext"/>
<inline-jdbc
jdbc-driver="com.mysql.jdbc.Driver"
jdbc-uri="jdbc:mysql://127.0.0.1/opentaps_1_5?autoReconnect=true&useOldAliasMetadataBehavior=true"
jdbc-username="opentaps"
jdbc-password="opentaps"
isolation-level="ReadCommitted"
pool-minsize="2"
pool-maxsize="250"
time-between-eviction-runs-millis="600000"/>

</datasource>

== Web Tier Changes ==

=== Controller ===

If you use minilang event servlets, you must now specify the path explicitly with the `component://` notation. Thus,

<event type="simple" path="org/ofbiz/accounting/payment/PaymentMethodEvents.xml" invoke="deletePaymentMethod"/>

must be changed to

<event type="simple" path="component://accounting/script/org/ofbiz/accounting/payment/PaymentMethodEvents.xml" invoke="deletePaymentMethod"/>

@@ Line 83: / Line 83: @@
 ==== Controller ====
-If you use minilang event servlets, you must now specify the path explicitly with the `component://` notation.  Thus,
+If you use minilang event servlets, you must now specify the path explicitly with the <tt>component://</tt> notation.  Thus,
   <event type="simple" path="org/ofbiz/accounting/payment/PaymentMethodEvents.xml" invoke="deletePaymentMethod"/>

← Older revision		Revision as of 00:34, 22 December 2010
Line 92:		Line 92:
	== Application Changes ==		== Application Changes ==

−	All opentaps applications have been moved from <td>hot-deploy</td> to <td>opentaps</td>.	+	All opentaps applications have been moved from <tt>hot-deploy</tt> to <tt>opentaps</tt>.

← Older revision		Revision as of 00:34, 22 December 2010
Line 92:		Line 92:
	== Application Changes ==		== Application Changes ==

−	All opentaps applications have been moved from `hot-deploy` to `opentaps`.	+	All opentaps applications have been moved from <td>hot-deploy</td> to <td>opentaps</td>.

← Older revision		Revision as of 23:38, 21 December 2010
Line 1:		Line 1:
	This page describes technical differences between opentaps 1.4 and 1.5. You should read it if you are upgrading or migrating code developed for opentaps 1.4 to opentaps 1.5		This page describes technical differences between opentaps 1.4 and 1.5. You should read it if you are upgrading or migrating code developed for opentaps 1.4 to opentaps 1.5
		+
		+	__TOC__

	===Entity Engine Change===		===Entity Engine Change===

@@ Line 34: / Line 34: @@
          <inline-jdbc
                  jdbc-driver="com.mysql.jdbc.Driver"
-                 jdbc-uri="jdbc:mysql://127.0.0.1/opentaps_1_5?autoReconnect=true&amp;useOldAliasMetadataBehavior=true"
+                 jdbc-uri="jdbc:mysql://127.0.0.1/opentaps_1_5?autoReconnect=true&amp;amp;useOldAliasMetadataBehavior=true"
                  jdbc-username="opentaps"
                  jdbc-password="opentaps"

@@ Line 5: / Line 5: @@
 ===Entity Engine Change===
-opentaps 1.5 now offers the multi-tenancy features of ofbiz 10.04.  This means that you need to configure your database differently in `entityengine.xml`.  Your delegator must now have a main and a tenant datasource:
+opentaps 1.5 now offers the multi-tenancy features of ofbiz 10.04.  This means that you need to configure your database differently in <tt>entityengine.xml</tt>.  Your delegator must now have a main and a tenant datasource:
      <delegator name="default" entity-model-reader="main" entity-group-reader="main" entity-eca-reader="main" distributed-cache-clear-enabled="false">
          <group-map group-name="org.ofbiz" datasource-name="localmysql"/>

@@ Line 79: / Line 79: @@
      </datasource>
-== Web Tier Changes ==
+=== Web Tier Changes ===
-=== Controller ===
+==== Controller ====
 If you use minilang event servlets, you must now specify the path explicitly with the `component://` notation.  Thus,
@@ Line 89: / Line 89: @@
 must be changed to
   <event type="simple" path="component://accounting/script/org/ofbiz/accounting/payment/PaymentMethodEvents.xml" invoke="deletePaymentMethod"/>

← Older revision	Revision as of 23:37, 21 December 2010
(No difference)