Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8F0EB200CC5 for ; Tue, 27 Jun 2017 07:32:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8DBD6160BDA; Tue, 27 Jun 2017 05:32:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D557E160BDE for ; Tue, 27 Jun 2017 07:32:06 +0200 (CEST) Received: (qmail 3789 invoked by uid 500); 27 Jun 2017 05:32:05 -0000 Mailing-List: contact notifications-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list notifications@ofbiz.apache.org Received: (qmail 3778 invoked by uid 99); 27 Jun 2017 05:32:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2017 05:32:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8D2021AA29C for ; Tue, 27 Jun 2017 05:32:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id L3aoQOTkQofI for ; Tue, 27 Jun 2017 05:32:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 835A85FCD7 for ; Tue, 27 Jun 2017 05:32:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D18ADE00A0 for ; Tue, 27 Jun 2017 05:32:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id DA5732410F for ; Tue, 27 Jun 2017 05:32:02 +0000 (UTC) Date: Tue, 27 Jun 2017 05:32:00 +0000 (UTC) From: "Devanshu Vyas (JIRA)" To: notifications@ofbiz.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OFBIZ-9434) Remove hard-coded instances of "IN" with ModelService.IN_PARAM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 27 Jun 2017 05:32:07 -0000 Devanshu Vyas created OFBIZ-9434: ------------------------------------ Summary: Remove hard-coded instances of "IN" with ModelService.IN_PARAM Key: OFBIZ-9434 URL: https://issues.apache.org/jira/browse/OFBIZ-9434 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Devanshu Vyas Priority: Minor I found many occurrences in OFBiz where "IN" is used directly instead of ModelService.IN_PARAM which is the intended meaning/usage. {code} Map addOrderItemShipGroupMap = dctx.makeValidContext("addOrderItemShipGroup", "IN", context); {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)