[jira] [Updated] (OFBIZ-10512) Change order of parameters in runSyncIgnore
[
https://issues.apache.org/jira/browse/OFBIZ-10512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Fallik updated OFBIZ-10512:
--
Description:
It is confusing that the order of the arguments passed to
{{LocalDispatcher.runSyncIgnore()}} is not the same in all overloaded methods.
cf.
{{void runSyncIgnore(String serviceName, Map context,
int transactionTimeout, boolean requireNewTransaction) throws
ServiceAuthException, ServiceValidationException, GenericServiceException;
void runSyncIgnore(String serviceName, int transactionTimeout, boolean
requireNewTransaction, Object... context) throws ServiceAuthException,
ServiceValidationException, GenericServiceException;
(ll. 101 + 102 in LocalDispatcher.java)}}
The {{context}} parameter could be passed as second or as fourth argument, no
matter if it is a Map or an Object.
was:
It is confusing that the order of the arguments passed to
`LocalDispatcher.runSyncIgnore()` is not the same in all overloaded methods.
cf.
```
void runSyncIgnore(String serviceName, Map context,
int transactionTimeout, boolean requireNewTransaction) throws
ServiceAuthException, ServiceValidationException, GenericServiceException;
void runSyncIgnore(String serviceName, int transactionTimeout, boolean
requireNewTransaction, Object... context) throws ServiceAuthException,
ServiceValidationException, GenericServiceException;```
(ll. 101 + 102 in LocalDispatcher.java)
The `context` parameter could be passed as second or as fourth argument, no
matter if it is a Map or an Object.
> Change order of parameters in runSyncIgnore
> ---
>
> Key: OFBIZ-10512
> URL: https://issues.apache.org/jira/browse/OFBIZ-10512
> Project: OFBiz
> Issue Type: Wish
>Reporter: Niklas Fallik
>Priority: Major
>
> It is confusing that the order of the arguments passed to
> {{LocalDispatcher.runSyncIgnore()}} is not the same in all overloaded methods.
> cf.
> {{void runSyncIgnore(String serviceName, Map
> context, int transactionTimeout, boolean requireNewTransaction) throws
> ServiceAuthException, ServiceValidationException, GenericServiceException;
> void runSyncIgnore(String serviceName, int transactionTimeout, boolean
> requireNewTransaction, Object... context) throws ServiceAuthException,
> ServiceValidationException, GenericServiceException;
> (ll. 101 + 102 in LocalDispatcher.java)}}
> The {{context}} parameter could be passed as second or as fourth argument, no
> matter if it is a Map or an Object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10512) Change order of parameters in runSyncIgnore
[
https://issues.apache.org/jira/browse/OFBIZ-10512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Fallik updated OFBIZ-10512:
--
Description:
It is confusing that the order of the arguments passed to
LocalDispatcher.runSyncIgnore() is not the same in all overloaded methods.
cf.
void runSyncIgnore(String serviceName, Map context,
int transactionTimeout, boolean requireNewTransaction) throws
ServiceAuthException, ServiceValidationException, GenericServiceException;
void runSyncIgnore(String serviceName, int transactionTimeout, boolean
requireNewTransaction, Object... context) throws ServiceAuthException,
ServiceValidationException, GenericServiceException;
(ll. 101 + 102 in LocalDispatcher.java)
The context parameter could be passed as second or as fourth argument, no
matter if it is a Map or an Object.
was:
It is confusing that the order of the arguments passed to
{{LocalDispatcher.runSyncIgnore()}} is not the same in all overloaded methods.
cf.
{{void runSyncIgnore(String serviceName, Map context,
int transactionTimeout, boolean requireNewTransaction) throws
ServiceAuthException, ServiceValidationException, GenericServiceException;
void runSyncIgnore(String serviceName, int transactionTimeout, boolean
requireNewTransaction, Object... context) throws ServiceAuthException,
ServiceValidationException, GenericServiceException;
(ll. 101 + 102 in LocalDispatcher.java)}}
The {{context}} parameter could be passed as second or as fourth argument, no
matter if it is a Map or an Object.
> Change order of parameters in runSyncIgnore
> ---
>
> Key: OFBIZ-10512
> URL: https://issues.apache.org/jira/browse/OFBIZ-10512
> Project: OFBiz
> Issue Type: Wish
>Reporter: Niklas Fallik
>Priority: Major
>
> It is confusing that the order of the arguments passed to
> LocalDispatcher.runSyncIgnore() is not the same in all overloaded methods.
> cf.
> void runSyncIgnore(String serviceName, Map context,
> int transactionTimeout, boolean requireNewTransaction) throws
> ServiceAuthException, ServiceValidationException, GenericServiceException;
> void runSyncIgnore(String serviceName, int transactionTimeout, boolean
> requireNewTransaction, Object... context) throws ServiceAuthException,
> ServiceValidationException, GenericServiceException;
> (ll. 101 + 102 in LocalDispatcher.java)
> The context parameter could be passed as second or as fourth argument, no
> matter if it is a Map or an Object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OFBIZ-10512) Change order of parameters in runSyncIgnore
Niklas Fallik created OFBIZ-10512: - Summary: Change order of parameters in runSyncIgnore Key: OFBIZ-10512 URL: https://issues.apache.org/jira/browse/OFBIZ-10512 Project: OFBiz Issue Type: Wish Reporter: Niklas Fallik It is confusing that the order of the arguments passed to `LocalDispatcher.runSyncIgnore()` is not the same in all overloaded methods. cf. ``` void runSyncIgnore(String serviceName, Map context, int transactionTimeout, boolean requireNewTransaction) throws ServiceAuthException, ServiceValidationException, GenericServiceException; void runSyncIgnore(String serviceName, int transactionTimeout, boolean requireNewTransaction, Object... context) throws ServiceAuthException, ServiceValidationException, GenericServiceException;``` (ll. 101 + 102 in LocalDispatcher.java) The `context` parameter could be passed as second or as fourth argument, no matter if it is a Map or an Object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10512) Change order of parameters in runSyncIgnore
[
https://issues.apache.org/jira/browse/OFBIZ-10512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Fallik updated OFBIZ-10512:
--
Description:
It is confusing that the order of the arguments passed to
LocalDispatcher.runSyncIgnore() is not the same in all overloaded methods.
{{cf.}}
{{ void runSyncIgnore(String serviceName, Map
context, int transactionTimeout, boolean requireNewTransaction) throws
ServiceAuthException, ServiceValidationException, GenericServiceException;}}
{{ void runSyncIgnore(String serviceName, int transactionTimeout, boolean
requireNewTransaction, Object... context) throws ServiceAuthException,
ServiceValidationException, GenericServiceException;}}
{{ (ll. 101 + 102 in LocalDispatcher.java)}}
The context parameter could be passed as second or as fourth argument, no
matter if it is a Map or an Object.
was:
It is confusing that the order of the arguments passed to
LocalDispatcher.runSyncIgnore() is not the same in all overloaded methods.
cf.
void runSyncIgnore(String serviceName, Map context,
int transactionTimeout, boolean requireNewTransaction) throws
ServiceAuthException, ServiceValidationException, GenericServiceException;
void runSyncIgnore(String serviceName, int transactionTimeout, boolean
requireNewTransaction, Object... context) throws ServiceAuthException,
ServiceValidationException, GenericServiceException;
(ll. 101 + 102 in LocalDispatcher.java)
The context parameter could be passed as second or as fourth argument, no
matter if it is a Map or an Object.
> Change order of parameters in runSyncIgnore
> ---
>
> Key: OFBIZ-10512
> URL: https://issues.apache.org/jira/browse/OFBIZ-10512
> Project: OFBiz
> Issue Type: Wish
>Reporter: Niklas Fallik
>Priority: Major
>
> It is confusing that the order of the arguments passed to
> LocalDispatcher.runSyncIgnore() is not the same in all overloaded methods.
> {{cf.}}
> {{ void runSyncIgnore(String serviceName, Map
> context, int transactionTimeout, boolean requireNewTransaction) throws
> ServiceAuthException, ServiceValidationException, GenericServiceException;}}
> {{ void runSyncIgnore(String serviceName, int transactionTimeout, boolean
> requireNewTransaction, Object... context) throws ServiceAuthException,
> ServiceValidationException, GenericServiceException;}}
> {{ (ll. 101 + 102 in LocalDispatcher.java)}}
> The context parameter could be passed as second or as fourth argument, no
> matter if it is a Map or an Object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10512) Change order of parameters in runSyncIgnore
[
https://issues.apache.org/jira/browse/OFBIZ-10512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Fallik updated OFBIZ-10512:
--
Priority: Minor (was: Major)
> Change order of parameters in runSyncIgnore
> ---
>
> Key: OFBIZ-10512
> URL: https://issues.apache.org/jira/browse/OFBIZ-10512
> Project: OFBiz
> Issue Type: Wish
>Reporter: Niklas Fallik
>Priority: Minor
>
> It is confusing that the order of the arguments passed to
> LocalDispatcher.runSyncIgnore() is not the same in all overloaded methods.
> {{cf.}}
> {{ void runSyncIgnore(String serviceName, Map
> context, int transactionTimeout, boolean requireNewTransaction) throws
> ServiceAuthException, ServiceValidationException, GenericServiceException;}}
> {{ void runSyncIgnore(String serviceName, int transactionTimeout, boolean
> requireNewTransaction, Object... context) throws ServiceAuthException,
> ServiceValidationException, GenericServiceException;}}
> {{ (ll. 101 + 102 in LocalDispatcher.java)}}
> The context parameter could be passed as second or as fourth argument, no
> matter if it is a Map or an Object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OFBIZ-10587) _WARNING_MESSAGE_
Niklas Fallik created OFBIZ-10587: - Summary: _WARNING_MESSAGE_ Key: OFBIZ-10587 URL: https://issues.apache.org/jira/browse/OFBIZ-10587 Project: OFBiz Issue Type: Wish Components: ALL COMPONENTS Affects Versions: 16.11.04 Reporter: Niklas Fallik Hi there, I am looking for a way to display warning messages. We are using EVENT_MESSAGE and ERROR_MESSAGE which we can pass to the frontend to display to the user, but it turned out that it would be nice to have a type for warnings like WARNING_MESSAGE. I figured out that the java classes ServiceEventHandler and ScriptEventHandler deal with those message types. I really would appreciate if anyone already had a solution for this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
