Feedback
Did this article resolve your question/issue?

   

Article

Custom extensions no longer recognized after upgrade to Corticon Studio 5.7

« Go Back

Information

 
TitleCustom extensions no longer recognized after upgrade to Corticon Studio 5.7
URL Namecustom-extensions-no-longer-recognized-after-upgrade-to-corticon-studio-5-7
Article Number000122577
EnvironmentProduct: Corticon Studio
Version: 5.6.x and above
OS: Windows
Database: N/A
Browser: N/A
Application Server: N/A
Question/Problem Description
When attempting to upgrade Corticcon Rule Projects to version 5.7, Corticon Studio is not recognizing the custom Java extensions.
How can Corticon Studio be configured to recognize custom Java extensions?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Corticon Studio 5.7 is not properly configured to recognize the custom extensions.
Resolution
Reference the following for ways to make Custom Extensions recognizable to Corticon Studio 5.7.x and above:
  • In Corticon Studio's 5.7.x and above Project Explorer, add the Custom Extension JAR to the Corticon Rule Project by right mouse clicking the Rule Project and selecting Properties > Corticon Extensions > Add and navigating to the custom Extension JAR file and then clicking Open
  • If using a custom extension plug-in from Corticon Studio version 5.5.x which is compatible with version 5.7.x and above, the following can also be done for Custom Extension recognition:
1) Edit the name of the plugin to include a version higher than the Corticon Studio version installed.
    If Corticon Studio 5.7.2 is installed, then typically a file such as the following will be installed:
        C:\Program Files\Progress\Corticon 5.7\Studio\eclipse\plugins\com.corticon.eclipse.studio.operations.extended.core_5.7.2_20190805_0725.jar. (This file can also be removed and saved in another location.)
    Therefore, name the Custom Extension plug-in something similar to:
        com.corticon.eclipse.studio.operations.extended.core_6.7.2_20190805_0725.jar

2) Copy the newly named extension plug-in JAR file to the Corticon 5.7 eclipse plugin directory:
    C:\Program Files\Progress\Corticon
5.7\Studio\eclipse\plugins\com.corticon.eclipse.studio.operations.extended.core_6.7.2_20190805_0725.jar


3) Make sure Corticon Studio 5.7 is being run with the -clean option. to force the system to rebuild the bundle cache and ensure the proper loading of the plugin.
    Progress Article 000091554, Starting Corticon Studio with the -clean option

4) Make sure that when launching Corticon Studio for the first time after adding the new plug-in, that it is launched with administrator privileges (right-click Corticon Studio from the Start menu, and then choose Run as administrator) so that the plug-in gets properly installed and registered. Do this whenever the plugin is updated.
 
 
Workaround
Notes
References to Other Documentation:
Progress Article(s):
000085122, Creating Custom Extended Operators in Corticon 5.6.x and above
 
Last Modified Date12/3/2019 3:59 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.