The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
"Setting Extension Dependencies"
Dear all,
I am trying to build a RapidMiner extension that relies on classes from another extension (the Linked Open Data extension). I followed the instructions for adding extension dependencies given in "How to Extend RapidMiner 5" and also this related thread: http://rapid-i.com/rapidforum/index.php/topic,6500.0.html. Basically, these are the changes I did inside the build.xml:
However, after running RapidMiner, the new extension is not present in the Operators view, even though there are no errors or exceptions in the log (says that the new extension was successfully registered). And also, the operators from the LOD extension are doubled (each LOD operator appears twice).
I have tested the extension without adding dependency to the LOD extension (and of course without the operators that rely on classes from the LOD extension) and everything works just fine.
I will be grateful for any help you can provide!
Best,
Petar
I am trying to build a RapidMiner extension that relies on classes from another extension (the Linked Open Data extension). I followed the instructions for adding extension dependencies given in "How to Extend RapidMiner 5" and also this related thread: http://rapid-i.com/rapidforum/index.php/topic,6500.0.html. Basically, these are the changes I did inside the build.xml:
and:
<fileset id="build.dependentExtensions" dir="..">
<include name="RapidMiner_Extension_LOD/build.xml" />
</fileset>
<property name="extension.dependencies" value="rmx_lod[1.0]" />Also, the whole LOD extension project is added as a dependency to my current project, not as a jar.
However, after running RapidMiner, the new extension is not present in the Operators view, even though there are no errors or exceptions in the log (says that the new extension was successfully registered). And also, the operators from the LOD extension are doubled (each LOD operator appears twice).
I have tested the extension without adding dependency to the LOD extension (and of course without the operators that rely on classes from the LOD extension) and everything works just fine.
I will be grateful for any help you can provide!
Best,
Petar
Tagged:
0
Answers
usually such errors occur because you are loading extension classes twice. Can you check the following folders for your extensions:
1) USER_HOME/.RapidMiner5/managed (remove from the .xml file as well)
2) IDE_WORKSPACE/RapidMiner/lib/plugins
if you have duplicates, remove all of them except for one version of each extension in the 2) folder. Make sure that the versioning of the LOD extension matches your required extension. If that does not help, please post the full startup log of RapidMiner Studio.
Regards,
Marco
Thanks for your reply!
I already took care of the duplicates, exactly as you described, before posting here.
Here is the startup log of RapidMiner Studio (the name of the new extension is RMDI): And here is the output when building the extension: And here is the manifest of RMDI.jar: Probably the duplicate LOD operators are loaded from the new RMDI.jar which has registered the LOD.jar as a dependency. But, I don't understand why the RMDI operators are not present in RapidMiner Studio.
Thanks for your help!
Cheers,
Petar
this looks rather sensible, I cannot spot an obvious problem. Have you downloaded the web and text mining extension sources and closely compared the web extension to your own extension? Both depend on another extension while providing their own set of operators.
Regards,
Marco
The problem is simpler than it appears. The Operator[Template].xml file in both extension had the same name, therefore the operators of the LOD extension were doubled, and no operators of the new extension were registered.
Thanks for the pointers!
Regards,
Petar
good job finding that! These errors are annoyingly hard to spot ;D
Regards,
Marco