manage-strategies

<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->

---

name: manage-strategies description: General development strategies and preferences for OFBiz. Use when deciding between multiple implementation options (e.g., XML vs Groovy services).

Skill: manage-strategies

Goal

Provide clear guidance on preferred implementation patterns and architecture decisions when multiple options exist in OFBiz.

Triggers

ALWAYS read this skill when:

• Designing a new service, screen, or logic component.
• Choosing between XML, Groovy, or Java for implementation.
• Reviewing code for architectural alignment.

Core Preferences

1. Services: XML vs. Java/Groovy

• XML (MiniLang/Simple Method): DEPRECATED. Do not use for new logic.
• Java: Preferred for complex, performance-critical, or core domain logic.
• Groovy: Preferred for orchestration, business rules, and script-based services.
• Preference Order: Groovy > Java > XML (Legacy only).

2. Logic Placement

• Prefer Groovy/Java: For service implementation.
• Avoid XML Actions: While controller.xml or screens allow some XML actions, keep these to a minimum. Move logic to Groovy scripts.

Dos and Don'ts

Area	DO	DON'T
Services	Implement in Groovy or Java.	Implement in MiniLang (XML).
Logic	Keep logic in .groovy or .java files.	Embed complex logic in <actions> tags of XML files.
UI	Use Freemarker (FTL) for custom layout logic.	Use complex inline Java in FTL files.
Data	Use EntityQuery for all data retrieval.	Use delegator.findByAnd or legacy low-level methods.
Extensions	Use <extend-entity> and plugin overrides.	Modify core framework files directly.

Guardrails

• Modern First: Always choose the modern (Java/Groovy/FTL) approach over the legacy XML-heavy approach.
• Service Engine: Use engine="groovy" or engine="java" in your service definitions.

Examples

Example: Preferred Service Definition

<!-- Proper service definition using Groovy engine -->
<service name="myCustomService" engine="groovy" 
         location="component://myplugin/src/main/groovy/org/apache/ofbiz/myplugin/MyServices.groovy" invoke="myServiceLogic">
    <description>My preferred modern service implementation</description>
    <attribute name="id" mode="IN" type="String"/>
</service>