Julien Bigot schrieb:
I have an application with a composite A containing a composite B that
contains my 4 C++ components.
The problem is that when I use Scagen on the directory containing these files,
it generates a backtrace for the .composite file of A (xml at the end of the
mail) as it contains a component whose implementation is not of the type
implementation.cpp.
It does not crash though, but it would be good not to have this disturbing
backtrace.
I tried to look at the Scagen code and found that in the
ComponentDomNodeHandler class, it is assumed that the implementation of the
component is of implementation.cpp type with no further check. I don't know
what the right way to fix that is.
I'd like your help on that.
Thank you,
Julien
<?xml version="1.0" encoding="UTF-8"?>
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0" name="the_application">
<component name="application">
<implementation.composite name="main_assembly" />
</component>
</composite>
Use Scagen on your Composite B folder only. Composite A should be into a
different one. Only Composites using cpp implementations need to be
processed with the generator. That would get rid of the warning. But as
far as I know it's irrelevant anyway.
Best Regards
D. Rogowski
--
velian GmbH IT-Solutions, Software & Consulting
Daniel Rogowski - Leiter der Softwareentwicklung
- Chief Development Officer (CDO)
Rebenring 33, 38106 Braunschweig
Telefon: +49 531 3804 310
Telefax: +49 531 3804 152
Mobil: +49 163 4606 352
http://www.velian.de
Ust.-ID: DE 256368411
Amtsgericht Braunschweig, HRB 200992 | Geschäftsführer: Michael Körber