Express Re-generation
Hi all,
Currently, there are two developers working on the same application
using Forté Express, version 1.0.f.1. When one developer integrates, the
other developer updates. In some occasion's the developer that has
updated obtains this sort of message when running the application.
Error invoking a method on an object class (AFS012CoreBMServiceMgrProxy)
named
(instance/0502e43b-43b5-11d1-bf9d-7650f160aa77:0x299:0x16/afs012corebmse
rvices_cl0/ris001windows_cl0-asf012corebmservice0x299:0x1)
method (Ox80000009,26,6)
We are customising classes that are generated, including the above
AFS012CoreBMServiceMgr, as well as other class Managers.
Has anyone else experienced something like this, and further more, has
any knowledge on how these circumstances maybe caused.
Does anyone have any ideas ?
Rick Ross
Sealcorp Holdings Limited
email: rick.ross@sealcorp.com.au
[999 byte] By [
] at [2007-11-25 5:00:57]
--Original Message--
From:Inman, Kal
Sent:Tuesday, October 28, 1997 7:14 AM
To: 'Rick.Ross@sealcorp.com.au'
Subject:RE: Express Re-generation
We experience what I believe to be the same problem using Forté Express,
version 1.0.f. What we found, generating through fscript, is when a
developer checks out and modifies a business model or an application
model, the generation process will do a branch on the classes it needs
to modify. When the developer integrates, obviously branched classes
cannot be integrated.
When your second developer updates her/his workspace, they will not
receive all of the modifications required. We found a couple of ways to
work around this problem.
1) Have your developers do a check out all, regenerate, and then
integrate. This is the safest way.
2) The second developer who does the update of her/his workspace
can check out and regenerate the models.
However, this will leave their workspace in the same branched
state of the first developer. Unless they execute the first alternative
prior to integration, this cycle will repeat its self.
We have not had the opportunity to fully evaluate if this has been fixed
in Forte Express R2.
Hope this helps.
Kal Inman
Andersen Windows Corporation
--Original Message--
From:Rick.Ross@sealcorp.com.au
[SMTP:Rick.Ross@sealcorp.com.au]
Sent:Tuesday, October 28, 1997 3:24 AM
To: kamranamin@yahoo.com
Subject:Express Re-generation
Hi all,
Currently, there are two developers working on the same
application
using Forté Express, version 1.0.f.1. When one developer
integrates, the
other developer updates. In some occasion's the developer that
has
updated obtains this sort of message when running the
application.
Error invoking a method on an object class
(AFS012CoreBMServiceMgrProxy)
named
(instance/0502e43b-43b5-11d1-bf9d-7650f160aa77:0x299:0x16/afs012corebmse
rvices_cl0/ris001windows_cl0-asf012corebmservice0x299:0x1)
method (Ox80000009,26,6)
We are customising classes that are generated, including the
above
AFS012CoreBMServiceMgr, as well as other class Managers.
Has anyone else experienced something like this, and further
more, has
any knowledge on how these circumstances maybe caused.
Does anyone have any ideas ?
Rick Ross
Sealcorp Holdings Limited
email: rick.ross@sealcorp.com.au
at 2007-6-29 9:19:56 >
Morning....
We have had the same problem with our application. What happens is that
when somebody makes a change to anything in the Business Model and then
integrates their workspace, anybody else who has "included public" that
same business model in another workspace does not pick up all of the
changes. The business model picks up the changes but the services do not.
There are two solutions. Both are not very good. The first is to delete
the business model from your workspace but leave the business model
services then do the update. That way you will always pick up the changes.
The problem with this is that it is most likely a supplier plan to
something else so you temporarily have to take it off the supplier plan
list. This can then cause problems when you go to regen a different
business model.The second solution is that whenever somebody has made a
change to the business model, every other workspace using the same business
model must first update their workspace and then also do a "force complete
generation" under "File" in your business model. This is very time
consuming for large business models and a waste of time when you have the
same business model in many workspaces.
We have lost countless hours doing this but fortunately it solves the
runtime error. We have called the problem in to Forte's Help desk. Hope
this helps.
Rick.Ross@sealcorp.com.au on 10/28/97 04:24:26 AM
To:forte-users@Sagesoln.com
cc:(bcc: Sandra Power/University of Windsor)
Subject: Express Re-generation
Hi all,
Currently, there are two developers working on the same application
using Fort? Express, version 1.0.f.1. When one developer integrates, the
other developer updates. In some occasion's the developer that has
updated obtains this sort of message when running the application.
Error invoking a method on an object class (AFS012CoreBMServiceMgrProxy)
named
(instance/0502e43b-43b5-11d1-bf9d-7650f160aa77:0x299:0x16/afs012corebmse
rvices_cl0/ris001windows_cl0-asf012corebmservice0x299:0x1)
method (Ox80000009,26,6)
We are customising classes that are generated, including the above
AFS012CoreBMServiceMgr, as well as other class Managers.
Has anyone else experienced something like this, and further more, has
any knowledge on how these circumstances maybe caused.
Does anyone have any ideas ?
Rick Ross
Sealcorp Holdings Limited
email: rick.ross@sealcorp.com.au
Thanks.....
Sandy Power
University of Windsor
Programmer/Analyst
401 Sunset
Windsor, Ontario
N9B 3P4
(519) 253-4232 Ext. 2773
Fax: (519) 973-7083
at 2007-6-29 9:19:56 >
