| Why is my custom element not listed in the Elements pane? |
| Categories: Audium OpenSDK |
| Article ID: | 92 |
| Last updated: | February 11, 2008 |
| User Opinions |
0%
100%
(1 vote)
|
|
Thank you for rating this answer.
|
SUMMARY
This article explains why a custom element would not show up in Audium Studio's Elements pane, and details the process Audium Studio goes through while loading elements and plugins.
SYMPTOMS
Developer has created a custom element, and would like to use it in Audium Studio. However, even though the class or JAR files are placed in the correct locations, the element does not show up in the Elements pane. Developer would like to better understand the process of how custom elements are loaded, so that he/she can debug the problem.
RESOLUTION
Audium Studio, upon startup, checks for custom elements and plugins. If one is found, it is loaded and instantiated. The whole classpath is checked for any additional classes required to instantiate the given element. It is a best practice to keep third party libraries that a custom element needs in the same location as the element itself.
Once the class is instantiated, Audium Studio calls the appropriate methods to get the element's name, display folder, and settings. Note that getElementName() and getExitStates(), as mentioned in the Audium Java API Javadocs, cannot return null.
Note that local elements will be loaded and instantiated every time the associated callflow is opened. Hence, you do not have to restart Audium Studio to refresh/add new elements.
If any of the methods required to create the element contains a runtime error, the element will fail to load and will not show in the Elements pane.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment