| Author |
Message
|
| udayakumarisampalli |
 Posted: Tue Nov 28, 2006 10:39 pm Post subject: Problem with Broker Schema in MB 6 which is not there inMB5 |
 |
|
Novice
Joined: 20 Jul 2006
Posts: 19
Location: India
|
i am facing the problem with Broker Schema in one my flows in MB 6. i have some code in MB5 i have migrated it to MB 6. that perticular flow is using the some mehtods which are defined in the another ESQL file in the same project.
IN MB 5: in the ESQL file having procedures was defined with top line as "BROKER SHCEMA AAA" (say AAA is a project name. and in the message flow ESQL file which is calling these procedures is agani defined with broker shcema as "BROKER SCHEMA AAA" in the first line. so when it is calling any procedure in the esql code it directly calling with procedure name( ex if procedure is "bbb" it is calling as "call bbb ") there was no problem in MB 5.
But in MB 6: the same ESQL code giving error while deploying the bar file to execution group as" Undefined procedure bbb". so i have done modification in the code as "CALL AAA.bbb" then it is identifying the procedure. what might be the problem . i think we are not required to prefix with Broker schema Variable before the procedure call.
does this required to be done like this. or did i missed any thing while migration or do i need to specify any property in any of the node to identify this. please require any kind of inputs |
|
| Back to top |
|
 |
| kspranava |
| Posted: Wed Nov 29, 2006 1:12 am Post subject: |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi udayakumarisampalli,
Tyr cleaning up the project (Project --> Clean...); sometimes it works!
-kspranava. |
|
| Back to top |
|
|
| udayakumarisampalli |
| Posted: Wed Nov 29, 2006 2:36 am Post subject: |
|
|
Novice
Joined: 20 Jul 2006
Posts: 19
Location: India
|
hi pranava,
i did that too. i cleaned, recreated i tried many options. but still in same position. does in MB 6 requires method calling happens to be in this manner?
thank you
regards
Uday |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 29, 2006 2:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Broker schemas are like namespaces.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Wed Nov 29, 2006 3:37 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
schemas r like packages in java, if u call a method in a different schema name u have to add tht schema in tht esql file using the PATH statement (similar to import decl in java)
Anoop |
|
| Back to top |
|
|
| udayakumarisampalli |
| Posted: Wed Nov 29, 2006 3:57 am Post subject: |
|
|
Novice
Joined: 20 Jul 2006
Posts: 19
Location: India
|
| but if you see my problem i am calling the procedure from the ESQL file which present in the same Project not from differnt project. it working fine with out prefix in MB 5 it is giving error in MB 6. what might be the problem |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 29, 2006 4:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It doesn't matter whether the ESQL file is in the same project or not - the only thing you have to do if it's in a different project is explictly mark the dependancy on the project preferences.
jbanoop has given you a very reasonable thing to try, add a PATH to your ESQL.
Unless you just want to spend more time complaining that it worked just fine in v5.
It's possible you've found a bug - it's also possible you've found a bug that has already been fixed. But you also haven't told us what version of the Toolkit you're using.
Thirdly, they have changed the way ESQL files get included when building CMF files. It used to be that any use of any method in a broker namespace would cause the entire namespace to get loaded. So you might be seeing a consequence of that - that it worked in v5 because you properly pathed a procedure in a different file (but the same namespace) as your other procedure.
Fourthly, you've got a working fix.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
