[cosmic-users] Re: [cosmic-dev] Incorrect method signature

Douglas C. Schmidt schmidt at dre.vanderbilt.edu
Wed Apr 26 09:47:20 CDT 2006


Hi Nick,

   Thanks for the bug report.  Jeff/Will/Jai, is this something you guys
could fix while Kitty's out of town?

Thanks,

        Doug

> CoSMIC VERSION: 0.4.5
>=20
>     HOST MACHINE and OPERATING SYSTEM:
>       i.e., which version of Windows are you using. Windows XP, CentOS 4.2
>=20
>     TOOL/AREA/CLASS/EXAMPLE AFFECTED:
> [Particularly, which tool in CoSMIC is affected? PICML or
> generate_component_mpc.pl
>=20
>     DOES THE PROBLEM AFFECT:
>         COMPILATION?
>         LINKING?
>         EXECUTION? Incorrect method signature
>         OTHER
>=20
>     SYNOPSIS:
>=20
> Note: I used =D2Building a Stock Quooter with CoSMIC and Dance Tutorial f=
or
> guidance.
>=20
> Modelling Side (Windows XP)
>=20
> 1. Create ProxyComponent.idl
>=20
> //ProxyComponent.idl,v 1.1 2006
> #include <Components.idl>
> module MyProxyComponent
> {
>=20
>   interface Dummy {
>       void DoNothing();
>   };
>   /**
>    * @class ProxyCOmponent
>    *
>    * @brief component
>    */
>   component ProxyComponent supports Dummy
>   {
>       attribute string theExecutable;
>       attribute string theArg0;
>       attribute string theArg1;
>       attribute string theArg2;
>       attribute string theArg3;
>       attribute string theArg4;
>       attribute string theArg5;
>       attribute string theArg6;
>       attribute string theArg7;
>       attribute string theArg8;
>       attribute string theArg9;
>       attribute string theEnvironmentFile;
>   };
>=20
>   /**
>    * @class ProxyComponentHome
>    *
>    * @brief home for ProxyComponent component
>    */
>   home ProxyComponentHome manages ProxyComponent
>   {
>   };
> };
>=20
> 2. Create ProxyComponnent.cidl
>=20
> #ifndef PROXYCOMPONENT_CIDL
> #define PROXYCOMPONENT_CIDL
> #include "ProxyComponent.idl"
> module MyProxyComponent
> {
>   composition session ProxyComponent_Impl
>   {
>     home executor ProxyComponentHome_Exec
>     {
>       implements ProxyComponentHome;
>       manages ProxyComponent_Exec;
>     };
>   };
> };
> #endif // !defined PROXYCOMPONENT_CIDL
>=20
> 3. Run C:\Program Files\Microsoft Visual Studio .NET
> 2003\Vc7\bin\VCVARS32.bat
>=20
> 4 Run idl_to_picml -x ProxyComponent ProxyComponent.idl
>=20
> 5. In GME, Create Project, PICML, D:\njg\env\ProxyComponent
>=20
> 6 In GME Run File->Import XML d:\njg\env\ProxyComponent.xme
>=20
> 7 In GME ComponentImplementations, Expand ProxyComponentImplementation,
> ProxyComponent_svnt,
>    entrypoin and note the value: createProxyComponentHome_Servant
>=20
>  8. Finish up the model details and Generate FlattendDeploymentPlan with
> name PC_Plan.
>=20
> Code Side  (LINUX CENTOS)
>=20
> 1. Put PC_Plan into descriptors folder, characterization file
> ProxyComponent.wlgChar into characterization folder. (Attached)
>=20
> 2. Write the code for ProxyComponent_exec.(cpp h)  (Attached)
>=20
> 3. Source the shell script to setup ACE/TAO/CIAO environment.
>=20
> 4. Create folder and put in ProxyComponent_exec.(cpp h), ProxyComponent.i=
dl
> and ProxyComponent.cidl.
>=20
> 5. Run $CIAO_ROOT/bin/cidlc  ProxyComponent.cidl.
>=20
> 6. Run $CIAO_ROOT/bin/generate_component_mpc.pl ProxyComponent.
>=20
> 7. Run $ACE_ROOT/bin/mwc.pl.
>=20
> 8. Run gmake and fix bugs until a closure is formed.
>=20
> 3. Run Node Manager and Execution Manager and Plan Launcher.
>=20
> 4. Dies trying to find createProxyComponentHome_Servant.
>=20
> (output):
>=20
> Node Manager
>=20
> Node Daemon Profile
> ------------------------------------
> Current Directory  :
> /proj/CHSIRAD/BUILD_0/DRM/AIF/ComponentizedWLG/ComponentWLG/characterizat=
ion
> NodeDaemon Name    : localhost
> NodeDaemon Port    : 10000
> -ORBEndpoint iiop://localhost:10000 -s
> /proj/CHSIRAD/BUILD_0/DRM/Middleware/ACE_wrappers/TAO/CIAO/DAnCE/NodeAppl=
ication/NodeApplicationCIAO_NodeManager
>  IOR:
> IOR:010000001900000049444c3a4349414f2f4e6f64654d616e616765723a312e3000000=
000010000000000000068000000010102000a0000006c6f63616c686f73740010271b000000=
14010f00525354ab234e447eab0e00000000000100000001000000000200000000000000080=
0000001000000004f4154010000001800000001000000010001000100000001000105090101=
0000000000
> CIAO_NodeManager is running...
> *** Starting NodeApplication
> Running NodeApplication...
> (5358|3086887776) EXCEPTION, Container_Impl::install
>=20
> user exception, ID 'IDL:Deployment/ImplEntryPointNotFound:1.0'
> (5358|3086887776) EXCEPTION, CIAO_NodeApplication::install error
>=20
> user exception, ID 'IDL:Deployment/ImplEntryPointNotFound:1.0'
>=20
> *************************************************************************=
******
> Execution Manager
>=20
> CIAO_ExecutionManager is running...
> (5351|3086882496) EXCEPTION, DomainApplicationManager_Impl::startLaunch
>=20
> user exception, ID 'IDL:Deployment/StartError:1.0'
>=20
> *************************************************************************=
******
>=20
> Plan Launcher
>=20
> (5356|3086874304) Initializing the Xerces runtime
> CIAO_PlanLauncher: start Launch application...
> EXCEPTION: StartError exception caught:
> SessionContainer::ciao_install_home, Entry point
> createProxyComponentHome_Servant invalid in dll ProxyComponent_svnt
> Deployment failed.  Plan_Launcher exiting.
>=20
> *************************************************************************=
******
>=20
> 5. Should be looking for create_MyProxyComponent_ProxyComponentHome_Serva=
nt
> .
>=20
> 6. Verify by running nm -o libProxyComponent_svnt.so | grep Home_Servant
> and noting it finds
>      create_MyProxyComponent_ProxyComponentHome_Servant but not
>      create_MyProxyComponent_ProxyComponentHome_Servant
>=20
> Modelling side
>=20
> 1. Change name in ArtifactContainer, redeploy.
>=20
> Code Side
>=20
> 1. Repeat test and it works.
>=20
> (See attached file: ProxyComponent_exec.h)(See attached file:
> ProxyComponent.cidl)(See attached file: ProxyComponent.idl)(See attached
> file: ProxyComponent.wlgChar)(See attached file: ProxyComponent_exec.cpp)
> (See attached file: PC_Plan.cdp)
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> cosmic-dev mailing list
> cosmic-dev at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/cosmic-dev


More information about the cosmic-users mailing list