JADE  Environment Development Ideas

Complete JCF Command File Support

As part of recent work, we needed to decommission an old application, with its initialize/finalize methods in particular referring to redundant code.

Previously, we'd have just deleted the initialize/finalize methods via a JCF command, but there's now been some validation introduced which prevents doing that when they're referenced by an application.

Okay, so we'll delete the application as well then (that's good, we don't like clutter anyways).  As all our changes are deployed incrementally, we'd do something like this in a JCF command file.

Delete Application <schema>::<application>


However, this JCF command is not supported like others may also have assumed upfront.

The JCF command file support needs to be updated to cover all scenarios where an entity can be deleted or renamed via the IDE.  This is particularly relevant in the context of improving source control, for which there needs to be a way of deploying deletes & renames incrementally in a consistent manner.

So far, I've identified the following entities which aren't covered like you might expect by the documented JCF commands:

  • Applications
  • Libraries
  • Exported Package Entities (while a package can be deleted, we can't remove a specific entity from the package via JCF).
  • External Component Libraries (ActiveX & .NET)
  • Exposures (C# & web services)
  • Dynamic Property Clusters
  • Relational Views (ODBC & RPS) (while we can exclude tables/columns, we can't delete/rename RPS mappings via JCF).
  • External Databases
  • HTML Documents
  • Ad Hoc Indexes

Once completed, it'd be ideal if functionality gaps of this nature were regarded as a fault before/after new schema entities are introduced to ensure complete JCF support is kept up-to-date.

  • Kevin Saul
  • Sep 9 2019
  • Investigating
  • Attach files
  • Admin
    Ashley Bass commented
    10 Oct 22:19

    We're going investigate this and have some questions about priority across our customer base, please respond to the team's questions with your feedback.

  • Thaban Segaran commented
    11 Oct 19:41

    The RPS ability to rename/add/delete fields is a must for us.