| How to view changes to custom elements without restarting Audium Studio |
| Categories: Audium Studio (3.4.x) |
| Article ID: | 25 |
| Last updated: | January 08, 2007 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
When developing custom elements, a developer may compile the Java class encapsulating the element many times. This article describes how to compile it and then be able to see the changes in Audium Studio without having to restart Audium Studio.
SYMPTOMS
Developer has updated a custom element's code and would like to use it immediately, without having to close and reopen Audium Studio.
RESOLUTION
When developing a custom element, deploy its class file in the java/application folder of a particular Audium application, even if the intention is to deploy it in the common directory when development is complete. When a new version of the element is compiled, in Audium Studio open up the workspace of another application, then open up the workspace of the application in which the custom element is deployed.
You will now see the most recent element and can drag it to the workspace. In addition, any elements already created of that type will also be updated (such as new settings, etc). The reason this is the case is that whenever an application's workspace is opened in Audium Studio, it looks through the java/application folder for any custom elements and if it finds them will load them into memory.
This is not the case with Java code deployed in the common folder. Anything in that folder is expected to be shared across all applications so Audium Studio loads it once when it starts up. Making changes to custom elements deployed in the common folder would require a restart of Audium Studio in order to see the changes.
Once the custom element development is complete, one can move the custom element classes or JAR files to whatever location is desired.
|
| 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