search

jlabbe-processia / mxupdate

Automatically exported from code.google.com/p/mxupdate
1 stars 1 forks source link

type, policies, ... could not be updated if MxUpdate installed the first time within a MX enironment #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. MxUpdate must be installed the first time
2. update a type, relationship or policy (admin object which are using the 
JPOCaller class)

What is the expected output? What do you see instead?
The update failed if the error that the JPO caller instance is not defined for 
the instance. 

Please use labels and text to provide additional information.

Original issue reported on code.google.com by tim.mox...@googlemail.com on 1 May 2009 at 1:41

GoogleCodeExporter commented 8 years ago 
Before the update runs, the administration object instance is defined within 
the JPOCaller class. Inside the update within TCL the JPO caller class is 
called.

In the case that MxUpdate is installed the first time it seems that the 
JPOCaller class is not compiled when called within TCL. While tracking, the 
name of the class of the JPO 
was e.g. if the case the admin instance was defined 
JPOCaller_mxJPOzm0_oAAAAAEAAAOo but if called from TCL the class name of the 
JPO is JPOCaller_mxJPOzm0_oAAAAAEAAAOp.

So the original class name of the JPO must be stored and reused for this cases 
so that the administration object could by updated.

Interesting: After the first possible run of e.g. type update in class name of 
the JPOCaller JPO was identically for the case of definition and the case of 
called within TCL.

Original comment by tim.mox...@googlemail.com on 1 May 2009 at 1:51

GoogleCodeExporter commented 8 years ago 
issue is fixed with r296

Original comment by tim.mox...@googlemail.com on 1 May 2009 at 2:14

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
new release V0.2.1 r304 includes the fix for this issue

Original comment by tim.mox...@googlemail.com on 1 May 2009 at 4:30

GoogleCodeExporter commented 8 years ago 
define correct version label

Original comment by tim.mox...@googlemail.com on 30 May 2009 at 2:25

GoogleCodeExporter commented 8 years ago 
define version where the issues were deployed (and fixed)

Original comment by tim.mox...@googlemail.com on 30 May 2009 at 2:26

GoogleCodeExporter commented 8 years ago 
wrong version label 0.3.0 removed

Original comment by tim.mox...@googlemail.com on 30 May 2009 at 2:26

GoogleCodeExporter commented 8 years ago 
wrong component label was assigned

Original comment by tim.mox...@googlemail.com on 31 May 2009 at 10:39

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@googlemail.com on 18 Jul 2009 at 6:50

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 7 Feb 2014 at 8:27

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 7 Feb 2014 at 8:28