Hi Taher,
yes you are in the right place: the proposal is to remove, from the
ServiceDispatcher.runAsync method, the code following the two comments:
// pre-auth ECA
and
// pre-validate ECA
Jacopo
On Tue, Feb 23, 2016 at 7:10 AM, Taher Alkhateeb wrote:
> Hi
Hi Jacopo,
I'm trying to find where the logic described above is happening, am I in
the right place at ServiceDispatcher on the runAsync method right next to
the checking of pre-auth ECA rules?
Taher Alkhateeb
On Mon, Feb 22, 2016 at 5:45 PM, Jacopo Cappellato <
[
https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-6760:
I reopen just to check if we can improve data loading independency as we did
with current
[
https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157218#comment-15157218
]
Jacques Le Roux commented on OFBIZ-6760:
Though tinking more about it, does it make sense in any
[
https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157184#comment-15157184
]
Jacques Le Roux commented on OFBIZ-6760:
Mmm, as I suspected if you comment out the party
On 22/02/2016 15:45, Jacopo Cappellato wrote:
[...]
Proposed fix: we could simply remove the execution of "auth" and
"in-validate" secas when the async service is invoked, and defer their
execution at the time the service is actually executed (i.e. picked from
the queue and run).
Any
[
https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157172#comment-15157172
]
Jacques Le Roux commented on OFBIZ-6760:
All is done here now :)
> Move all entity definitions
[
https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157175#comment-15157175
]
Jacques Le Roux commented on OFBIZ-6760:
At least at long as only the Manufacturing and Marketing
[
https://issues.apache.org/jira/browse/OFBIZ-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-6757.
--
Resolution: Done
Fix Version/s: Upcoming Branch
Thanks Pierre, Deepak, Amit,
Amit your
[
https://issues.apache.org/jira/browse/OFBIZ-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-6758.
--
Resolution: Not A Problem
Assignee: Jacques Le Roux
Fix Version/s: Upcoming
Jacques Le Roux created OFBIZ-6913:
--
Summary: Update Tomcat to 7.0.68
Key: OFBIZ-6913
URL: https://issues.apache.org/jira/browse/OFBIZ-6913
Project: OFBiz
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/OFBIZ-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-1525:
---
Description:
The goal of this virtual issue is only to group together all OFBiz security
Hi all,
I am sharing here the result of an analysis that Nameet Jain and I did to
figure out why, under some circumstances the same seca service was executed
twice.
The problem is that, when a service is executed as "async" the secas
attached to the "auth" and "in-validate" events are executed
Ok Taher and Julien,
I will follow your advice to create services for specific deletions.
That 's a better idea.
Thanks for your advice,
Eric
Olagos bvba
Heidi Dehaes
Kerkstraat 34
2570 Duffel
Belgium
Tel. : 015/31 53 04
GSM :0485/22 35 80
E-mail : info.ola...@gmail.com
[
https://issues.apache.org/jira/browse/OFBIZ-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156792#comment-15156792
]
Jacques Le Roux commented on OFBIZ-6808:
Even if I wonder why this was not done in 1st place, I
I agree with Taher, It could be very dangerous and difficult to
understand 'what's happens' after a product deletion...
Julien.
Le 22/02/2016 11:38, Taher Alkhateeb a écrit :
Also, generally speaking, most modern systems that I know of avoid delete
altogether, and instead just disable or make
Hi Eric,
In addition to what Jacques put neatly below, I would add that the OFBiz
data model is complex and highly interconnected. And something central like
a product is pretty much connected to everything, so a delete might cascade
(more or less) the entire database.
I would also highly
[
https://issues.apache.org/jira/browse/OFBIZ-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156735#comment-15156735
]
Jacopo Cappellato commented on OFBIZ-6808:
--
The behavior reported in this ticket by
This is what I was up to so far
https://cwiki.apache.org/confluence/display/OFBENDUSER/How+to+delete+tuples+added+to+test+a+setup
It's manual and concerns only order, so you would need to do the same research
for product
There is no automation OOTB for that. It's even disputable as Scott's
Pierre Smits created OFBIZ-6912:
---
Summary: Be able to set additional attributes per product store
Key: OFBIZ-6912
URL: https://issues.apache.org/jira/browse/OFBIZ-6912
Project: OFBiz
Issue
20 matches
Mail list logo