manage-minilang

Modify and debug OFBiz MiniLang XML service workflows.

175|216|Updated Mar 5, 2017
One-click install
npx skills add https://github.com/apache/ofbiz-plugins --skill manage-minilang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-minilang
Source: https://github.com/apache/ofbiz-plugins/tree/main/ai-agent-skills/manage-minilang
Command: npx skills add https://github.com/apache/ofbiz-plugins --skill manage-minilang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps manage and maintain legacy business logic written in OFBiz MiniLang (XML), providing guidance for modification and troubleshooting.

Core Features & Use Cases

  • Legacy Code Maintenance: Modify existing MiniLang service workflows defined in XML.
  • Troubleshooting: Debug issues within existing MiniLang codebases.
  • Migration Path: Facilitates the process of migrating MiniLang logic to Groovy.

Quick Start

Locate the <simple-method> in a script/.../*.xml file and define logic using standard tags like <entity-one>, <set>, or <call-service>.

Frequently Asked Questions about manage-minilang

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I modify existing OFBiz MiniLang XML service workflows?

To modify OFBiz MiniLang XML service workflows, locate the <simple-method> in a script/*.xml file and adjust logic using standard tags like <entity-one>, <set>, or <call-service> within the servicedef/services.xml structure.

What is the best way to debug simple engine services in OFBiz MiniLang?

Debugging simple engine services in OFBiz MiniLang requires understanding XML tags and OFBiz service definitions. You troubleshoot by inspecting the legacy business logic directly within the XML codebase to identify execution issues.

How do I migrate legacy MiniLang XML logic to Groovy?

Migrating MiniLang XML logic to Groovy involves planning the transition of legacy business logic from simple-method XML files. This Skill facilitates mapping existing XML service workflows to Groovy equivalents.

What do I need to know to maintain legacy MiniLang code?

Maintaining legacy MiniLang code requires a solid understanding of MiniLang tags and OFBiz service definitions, specifically how logic is structured within servicedef/services.xml and script XML files.

When should I not use MiniLang XML for OFBiz service definitions?

You should avoid using MiniLang XML for new OFBiz service definitions when modern alternatives like Groovy are available, as MiniLang is a legacy format primarily maintained for troubleshooting and migration purposes.