[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-5522:
---
Comment: was deleted

(was: 

Online Cake Delivery @ http://www.cakengift.in/ , 
Cake Delivery in Delhi @ 
http://www.cakengift.in/by-city/cake-delivery-in-delhi-333.html
Cake Delivery in Noida @ 
http://www.cakengift.in/by-city/cake-delivery-in-noida-335.html
Cake Delivery in Gurgaon @ 
http://www.cakengift.in/by-city/cake-delivery-in-gurgaon-334.html
Cake Delivery in Ghaziabad @ 
http://www.cakengift.in/by-city/cake-delivery-in-ghaziabad-336.html
Cake Delivery in Faridabad @ 
http://www.cakengift.in/by-city/cake-delivery-in-faridabad-337.html
Online Birthday Cake @ 
http://www.cakengift.in/by-occasion/birthday-cakes-339.html

)

> Introduce websocket usage
> -
>
> Key: OFBIZ-5522
> URL: https://issues.apache.org/jira/browse/OFBIZ-5522
> Project: OFBiz
>  Issue Type: Task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> After a discussion with Ean, was suggested (draft here):
> You need a service that lets you "subscribe" a widget to an entity and
> then propagate change events to the widget as the entity is modified.
> A generic mechanism like that could eventually expand to be a general
> purpose "data bound widgets" system that mostly looks like the existing
> system but magically reflects updates.
> Could be used with/for
> * The entity cache and webforms to automatically update views when data 
> changes. 
> * Replaces the current system notes
> * Create a dashboard type pages  (to be discussed futher)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-5522:
---
Comment: was deleted

(was: Order Cake in Delhi @ 
http://www.cakengift.in/by-city/cake-delivery-in-delhi-333.html, 
Order Cake in Noida @ 
http://www.cakengift.in/by-city/cake-delivery-in-noida-335.html, 
Order Cake in Gurgaon @ 
http://www.cakengift.in/by-city/cake-delivery-in-gurgaon-334.html , 
Order Cake in Ghaziabad @ 
http://www.cakengift.in/by-city/cake-delivery-in-ghaziabad-336.html, 
Order Cake in Faridabad @ 
http://www.cakengift.in/by-city/cake-delivery-in-faridabad-337.html
)

> Introduce websocket usage
> -
>
> Key: OFBIZ-5522
> URL: https://issues.apache.org/jira/browse/OFBIZ-5522
> Project: OFBiz
>  Issue Type: Task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> After a discussion with Ean, was suggested (draft here):
> You need a service that lets you "subscribe" a widget to an entity and
> then propagate change events to the widget as the entity is modified.
> A generic mechanism like that could eventually expand to be a general
> purpose "data bound widgets" system that mostly looks like the existing
> system but magically reflects updates.
> Could be used with/for
> * The entity cache and webforms to automatically update views when data 
> changes. 
> * Replaces the current system notes
> * Create a dashboard type pages  (to be discussed futher)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5522) Introduce websocket usage

[Delivery Cake (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188831#comment-15188831
 ] 

Delivery Cake commented on OFBIZ-5522:
--



Online Cake Delivery @ http://www.cakengift.in/ , 
Cake Delivery in Delhi @ 
http://www.cakengift.in/by-city/cake-delivery-in-delhi-333.html
Cake Delivery in Noida @ 
http://www.cakengift.in/by-city/cake-delivery-in-noida-335.html
Cake Delivery in Gurgaon @ 
http://www.cakengift.in/by-city/cake-delivery-in-gurgaon-334.html
Cake Delivery in Ghaziabad @ 
http://www.cakengift.in/by-city/cake-delivery-in-ghaziabad-336.html
Cake Delivery in Faridabad @ 
http://www.cakengift.in/by-city/cake-delivery-in-faridabad-337.html
Online Birthday Cake @ 
http://www.cakengift.in/by-occasion/birthday-cakes-339.html



> Introduce websocket usage
> -
>
> Key: OFBIZ-5522
> URL: https://issues.apache.org/jira/browse/OFBIZ-5522
> Project: OFBiz
>  Issue Type: Task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> After a discussion with Ean, was suggested (draft here):
> You need a service that lets you "subscribe" a widget to an entity and
> then propagate change events to the widget as the entity is modified.
> A generic mechanism like that could eventually expand to be a general
> purpose "data bound widgets" system that mostly looks like the existing
> system but magically reflects updates.
> Could be used with/for
> * The entity cache and webforms to automatically update views when data 
> changes. 
> * Replaces the current system notes
> * Create a dashboard type pages  (to be discussed futher)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5522) Introduce websocket usage

[Delivery Cake (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188832#comment-15188832
 ] 

Delivery Cake commented on OFBIZ-5522:
--

Order Cake in Delhi @ 
http://www.cakengift.in/by-city/cake-delivery-in-delhi-333.html, 
Order Cake in Noida @ 
http://www.cakengift.in/by-city/cake-delivery-in-noida-335.html, 
Order Cake in Gurgaon @ 
http://www.cakengift.in/by-city/cake-delivery-in-gurgaon-334.html , 
Order Cake in Ghaziabad @ 
http://www.cakengift.in/by-city/cake-delivery-in-ghaziabad-336.html, 
Order Cake in Faridabad @ 
http://www.cakengift.in/by-city/cake-delivery-in-faridabad-337.html


> Introduce websocket usage
> -
>
> Key: OFBIZ-5522
> URL: https://issues.apache.org/jira/browse/OFBIZ-5522
> Project: OFBiz
>  Issue Type: Task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> After a discussion with Ean, was suggested (draft here):
> You need a service that lets you "subscribe" a widget to an entity and
> then propagate change events to the widget as the entity is modified.
> A generic mechanism like that could eventually expand to be a general
> purpose "data bound widgets" system that mostly looks like the existing
> system but magically reflects updates.
> Could be used with/for
> * The entity cache and webforms to automatically update views when data 
> changes. 
> * Replaces the current system notes
> * Create a dashboard type pages  (to be discussed futher)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6924) comments on ordering products should be store driven

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188203#comment-15188203
 ] 

Jacques Le Roux commented on OFBIZ-6924:


I agree

> comments on ordering products should be store driven
> 
>
> Key: OFBIZ-6924
> URL: https://issues.apache.org/jira/browse/OFBIZ-6924
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Pierre Smits
>
> Currently, in ecommerce/tiny-gismo-GZ-1000-p a comment field is shown.
> This is a result of the following code in productdetail.ftl
> {code}
> <#assign commentEnable = 
> Static["org.ofbiz.entity.util.EntityUtilProperties"].getPropertyValue("order",
>  "order.item.comment.enable", delegator)>
> <#if commentEnable.equals("Y")>
> <#assign orderItemAttr = 
> Static["org.ofbiz.entity.util.EntityUtilProperties"].getPropertyValue("order",
>  "order.item.attr.prefix", delegator)>
> ${uiLabelMap.CommonComment} name="${orderItemAttr}comment"/>
> 
> {code}
> Based on the code excerpt this is set by a property value in the order 
> component. However this should be based on a configuration setting in the 
> store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

buildbot success in on ofbiz-trunk

[buildbot]

The Buildbot has detected a restored build on builder ofbiz-trunk while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk/builds/452

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: forced: by IRC user  (privmsg): forces manual build 
after svn up failed
Build Source Stamp: HEAD
Blamelist: 

Build succeeded!

Sincerely,
 -The Buildbot

buildbot success in on ofbiz-branch12

[buildbot]

The Buildbot has detected a restored build on builder ofbiz-branch12 while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch12/builds/87

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: forced: by IRC user  (privmsg): forces manual build 
after tests failed but work locally
Build Source Stamp: HEAD
Blamelist: 

Build succeeded!

Sincerely,
 -The Buildbot

BuildBot works again

[Jacques Le Roux]

FYI: https://issues.apache.org/jira/browse/INFRA-11094

Jacques

[jira] [Commented] (OFBIZ-6920) Credit card details cannot be updated

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187568#comment-15187568
 ] 

Jacques Le Roux commented on OFBIZ-6920:


OK I had a look. The problem is we are calling createCreditCard map proc from 
updateCreditCard service after calling updateCreditCard map proc. And when we 
update the data we don't see the real card number but something like 
""

Since we don't want to change createCreditCard map proc and I see no simple way 
to detect if we should or not use isAnyCard call in createCreditCard map proc 
depending on where it's called (creating or updating) I will simply copy the 
needed check from createCreditCard map proc into updateCreditCard map proc but 
not the isAnyCard call of course.  Then it will work but if the user changes 
also the card number. If she does it will need to be right because it will not 
be checked! I can't see any other ways because we can't use a hidden field with 
the real card number in, it would be insecure. We could thouhg introduce a 
specific encryption/decryption but it seems a bit too much.

If somebody has a better idea please tell, before I commit the change I 
propose...

> Credit card details cannot be updated
> -
>
> Key: OFBIZ-6920
> URL: https://issues.apache.org/jira/browse/OFBIZ-6920
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Reporter: Vyom Jain
>Assignee: Jacques Le Roux
>
> It seems after OFBIZ-3956, credit card details can no longer be updated, for 
> example, if one wishes to update the expiry date of a credit card 
> results in following "The Following Errors Occurred: Card Number is 
> erroneous".
> This issue can be replicated here - 
> https://demo-trunk-ofbiz.apache.org/partymgr/control/editcreditcard?paymentMethodId=9015=DemoCustomer



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

buildbot failure in on ofbiz-branch12

[buildbot]

The Buildbot has detected a new failure on builder ofbiz-branch12 while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch12/builds/86

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz12-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release12.04] 1734273
Blamelist: jleroux

BUILD FAILED: failed compile_1

Sincerely,
 -The Buildbot

buildbot exception in on ofbiz-trunk

[buildbot]

The Buildbot has detected a build exception on builder ofbiz-trunk while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk/builds/451

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/trunk] 1734276
Blamelist: jleroux

BUILD FAILED: exception upload_2

Sincerely,
 -The Buildbot

[jira] [Closed] (OFBIZ-6926) Replace the contrast Java agent by the notsoserial Java agent

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-6926.
--
Resolution: Fixed

> Replace the contrast Java agent by the notsoserial Java agent
> -
>
> Key: OFBIZ-6926
> URL: https://issues.apache.org/jira/browse/OFBIZ-6926
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: tools/security
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, Upcoming Branch
>
>
> The goal is to replace the contrast Java agent by the notsoserial Java agent 
> which can be used to protect OFBiz instances from possible Java serialize 
> vulnerabilities. 
> For that we need to modifie the *-secure targets (start-secure, 
> start-batch-secure, start-pos-secure, start-both-secure) to use the 
> notsoserial Java agent with its most secure setting. 
> See 
> https://cwiki.apache.org/confluence/display/OFBIZ/The+infamous+Java+serialize+vulnerability
>  for more information 
> The notsoserial Java agent is placed in the tools/security/notsoserial folder 
> and a dependency-check folder created under the tools/security folder to move 
> there the dependency-check files from the tools/security folder.
> The trunk demo will be using the notsoserial Java agent ASAP. The older ones 
> will keep the contrast Java agent which should be enough as soon as we will 
> comment out the RMI stuff in OFBiz. 
> Users need to care anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6926) Replace the contrast Java agent by the notsoserial Java agent

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187319#comment-15187319
 ] 

Jacques Le Roux commented on OFBIZ-6926:


Done at (a bit of mess sorry :/)
trunk r1730735, 1730736, 1730747, 1730758, 1733063
R15.12 r1730738, 1732865, 1732866, 1732876, 1732881, 1732885
R14.12 r1732878, 1732886

> Replace the contrast Java agent by the notsoserial Java agent
> -
>
> Key: OFBIZ-6926
> URL: https://issues.apache.org/jira/browse/OFBIZ-6926
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: tools/security
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, Upcoming Branch
>
>
> The goal is to replace the contrast Java agent by the notsoserial Java agent 
> which can be used to protect OFBiz instances from possible Java serialize 
> vulnerabilities. 
> For that we need to modifie the *-secure targets (start-secure, 
> start-batch-secure, start-pos-secure, start-both-secure) to use the 
> notsoserial Java agent with its most secure setting. 
> See 
> https://cwiki.apache.org/confluence/display/OFBIZ/The+infamous+Java+serialize+vulnerability
>  for more information 
> The notsoserial Java agent is placed in the tools/security/notsoserial folder 
> and a dependency-check folder created under the tools/security folder to move 
> there the dependency-check files from the tools/security folder.
> The trunk demo will be using the notsoserial Java agent ASAP. The older ones 
> will keep the contrast Java agent which should be enough as soon as we will 
> comment out the RMI stuff in OFBiz. 
> Users need to care anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6926) Replace the contrast Java agent by the notsoserial Java agent

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-6926:
---
Issue Type: Sub-task  (was: Improvement)
Parent: OFBIZ-1525

> Replace the contrast Java agent by the notsoserial Java agent
> -
>
> Key: OFBIZ-6926
> URL: https://issues.apache.org/jira/browse/OFBIZ-6926
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: tools/security
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, Upcoming Branch
>
>
> The goal is to replace the contrast Java agent by the notsoserial Java agent 
> which can be used to protect OFBiz instances from possible Java serialize 
> vulnerabilities. 
> For that we need to modifie the *-secure targets (start-secure, 
> start-batch-secure, start-pos-secure, start-both-secure) to use the 
> notsoserial Java agent with its most secure setting. 
> See 
> https://cwiki.apache.org/confluence/display/OFBIZ/The+infamous+Java+serialize+vulnerability
>  for more information 
> The notsoserial Java agent is placed in the tools/security/notsoserial folder 
> and a dependency-check folder created under the tools/security folder to move 
> there the dependency-check files from the tools/security folder.
> The trunk demo will be using the notsoserial Java agent ASAP. The older ones 
> will keep the contrast Java agent which should be enough as soon as we will 
> comment out the RMI stuff in OFBiz. 
> Users need to care anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6926) Replace the contrast Java agent by the notsoserial Java agent

[Jacques Le Roux (JIRA)]

Jacques Le Roux created OFBIZ-6926:
--

 Summary: Replace the contrast Java agent by the notsoserial Java 
agent
 Key: OFBIZ-6926
 URL: https://issues.apache.org/jira/browse/OFBIZ-6926
 Project: OFBiz
  Issue Type: Improvement
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
 Fix For: 14.12.01, Upcoming Branch


The goal is to replace the contrast Java agent by the notsoserial Java agent 
which can be used to protect OFBiz instances from possible Java serialize 
vulnerabilities. 

For that we need to modifie the *-secure targets (start-secure, 
start-batch-secure, start-pos-secure, start-both-secure) to use the notsoserial 
Java agent with its most secure setting. 
See 
https://cwiki.apache.org/confluence/display/OFBIZ/The+infamous+Java+serialize+vulnerability
 for more information 

The notsoserial Java agent is placed in the tools/security/notsoserial folder 
and a dependency-check folder created under the tools/security folder to move 
there the dependency-check files from the tools/security folder.

The trunk demo will be using the notsoserial Java agent ASAP. The older ones 
will keep the contrast Java agent which should be enough as soon as we will 
comment out the RMI stuff in OFBiz. 

Users need to care anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6926) Replace the contrast Java agent by the notsoserial Java agent

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-6926:
---
Component/s: tools/security

> Replace the contrast Java agent by the notsoserial Java agent
> -
>
> Key: OFBIZ-6926
> URL: https://issues.apache.org/jira/browse/OFBIZ-6926
> Project: OFBiz
>  Issue Type: Improvement
>  Components: tools/security
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, Upcoming Branch
>
>
> The goal is to replace the contrast Java agent by the notsoserial Java agent 
> which can be used to protect OFBiz instances from possible Java serialize 
> vulnerabilities. 
> For that we need to modifie the *-secure targets (start-secure, 
> start-batch-secure, start-pos-secure, start-both-secure) to use the 
> notsoserial Java agent with its most secure setting. 
> See 
> https://cwiki.apache.org/confluence/display/OFBIZ/The+infamous+Java+serialize+vulnerability
>  for more information 
> The notsoserial Java agent is placed in the tools/security/notsoserial folder 
> and a dependency-check folder created under the tools/security folder to move 
> there the dependency-check files from the tools/security folder.
> The trunk demo will be using the notsoserial Java agent ASAP. The older ones 
> will keep the contrast Java agent which should be enough as soon as we will 
> comment out the RMI stuff in OFBiz. 
> Users need to care anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5461) include ivy clearcache in build

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187279#comment-15187279
 ] 

Jacques Le Roux commented on OFBIZ-5461:


Done in
trunk r1734276
R15.12 r1734277
R14.12 r1734278



> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Christian Geisert
> Fix For: 14.12.01, Upcoming Branch
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5461) include ivy clearcache in build

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-5461.
--
   Resolution: Fixed
Fix Version/s: Upcoming Branch

> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Christian Geisert
> Fix For: 14.12.01, Upcoming Branch
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5461) include ivy clearcache in build

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187274#comment-15187274
 ] 

Jacques Le Roux commented on OFBIZ-5461:


Ha sorry, I should have looked at it. I thought  was only 
harcoded there. Now that I look at it I should not indeed not have let that 
passed. At least an  should have been used there.

OK, Christian while a it I remove it, thanks for spotting that!


> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Christian Geisert
> Fix For: 14.12.01
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6218) Unit tests throw exception in DBCP

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-6218.
--
   Resolution: Pending Closed
Fix Version/s: Upcoming Branch
   13.07.03
   12.04.06
   14.12.01

> Unit tests throw exception in DBCP
> --
>
> Key: OFBIZ-6218
> URL: https://issues.apache.org/jira/browse/OFBIZ-6218
> Project: OFBiz
>  Issue Type: Bug
>Reporter: Adrian Crum
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
>
> Attachments: OFBIZ-6218.patch
>
>
> Details in comments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6218) Unit tests throw exception in DBCP

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187265#comment-15187265
 ] 

Jacques Le Roux commented on OFBIZ-6218:


I have committed the fix for OFBIZ-6888 in all supported places. I close here, 
we will reopen or create a new Jira issue when we will have more detailled 
information

> Unit tests throw exception in DBCP
> --
>
> Key: OFBIZ-6218
> URL: https://issues.apache.org/jira/browse/OFBIZ-6218
> Project: OFBiz
>  Issue Type: Bug
>Reporter: Adrian Crum
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-6218.patch
>
>
> Details in comments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6888) GroovyEngine.serviceInvoker masks Groovy script exceptions in some cases

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-6888.
--
   Resolution: Fixed
Fix Version/s: Upcoming Branch
   13.07.03
   12.04.06
   14.12.01

Thanks Forrest,

Your patch is in
trunk r1734269
R15.12 r1734270
R14.12 r1734271
R13.07 r1734272
R12.04 r1734273




> GroovyEngine.serviceInvoker masks Groovy script exceptions in some cases
> 
>
> Key: OFBIZ-6888
> URL: https://issues.apache.org/jira/browse/OFBIZ-6888
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Forrest Rae
>Assignee: Jacques Le Roux
>  Labels: errorhandling
> Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
>
> Attachments: OFBIZ-6888.patch
>
>
> If GroovyEngine.serviceInvoker catches an exception in a Groovy script, it 
> would mask the exception in some cases.  An exception's detailMessage can be 
> null.  If it is null, the exception won't be properly returned and logged, 
> and that will make spotting problems very difficult.  This was the case for 
> me while trying to track down a problem with a 
> java.util.ConcurrentModificationException error in a Groovy script.  I 
> suspect that this choice to mask exceptions and only return the message has 
> cause bugs to not be spotted.
> Disabling this for now in favor of returning a proper exception.  
> GroovyEngine.serviceInvoker() should throw GenericServiceException if error, 
> rather than returning ServiceUtil.returnError(e.getMessage())



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5461) include ivy clearcache in build

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187229#comment-15187229
 ] 

Pierre Smits commented on OFBIZ-5461:
-

Beware that  is called within the 'clean-all' 
target and the 'clean-downloads' target.

And the clean-downloads target is also called in the clean-all target.

[~jacques.le.roux] The target 'clean-ivy' already exists.

> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Christian Geisert
> Fix For: 14.12.01
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5672) UOM conversion for supplier and sale order

[Julien NICOLAS (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187189#comment-15187189
 ] 

Julien NICOLAS commented on OFBIZ-5672:
---

I think it was initially developed for 13.07. I'll really be surprised if it 
works on trunk but not on 13.07.
I'm busy by now but next week, I hope to have time to take a look on that.

> UOM conversion for supplier and sale order
> --
>
> Key: OFBIZ-5672
> URL: https://issues.apache.org/jira/browse/OFBIZ-5672
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Release Branch 13.07, Trunk
> Environment: OOTB
>Reporter: Julien NICOLAS
>Assignee: Jacques Le Roux
>Priority: Minor
>  Labels: features
> Attachments: OFBIZ-5672-UOM-conversion-supplier-and-sale-order.13.07
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> It's possible to define different UomQuantity in measures tab, supplier tab 
> or price tab of a product but OFBiz don't manage it in stock.
> The improvement must manage it using UomConversion table for standard 
> conversions.
> When a new order (supplier or sale) is created, the user can choose the 
> UomQuantity if more than one UomQuantity is available.
> By default if only one conversion is defined in UomConversion table, OFBiz 
> will use it for both conversion way.
> However, it's possible to define different rules for each ways.
> Add new concept in UomConversion rules : rouding method and number of digit 
> after decimal point.
> To be more flexible, add new fields in price and supplier product tab.
>   - Uom conversion factor
>   - Rounding method
>   - Number of digit after decimal point
> If those fields are empty, OFBiz will use the standard UomConversion table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Proposal for the "Tweets" and "News" sections of the main web page of the OFBiz site

[Jacopo Cappellato]

yes, the width will be the same of the main section.

Jacopo


On Wed, Mar 9, 2016 at 11:32 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Agreed, so we increase the width of the "Tweets" section, right? Same
> height I guess.
>
> Jacques
>
>
> Le 09/03/2016 11:08, Julien NICOLAS a écrit :
>
>> +1
>>
>> There is a lot of tweet with @apacheOfibz and it could be interesting to
>> have it as main news.
>>
>> Le 09/03/2016 10:45, Jacopo Cappellato a écrit :
>>
>>> Proposal:
>>> in the main page of the ofbiz web site, move the "Tweets" section from
>>> the
>>> right bar to the main section of the page, before the "News" section;
>>> then
>>> rename the "News" section into "Announcements" or similar.
>>>
>>> Goal:
>>> give more visibility to our tweets because it is a more dynamic section
>>> while the "News" section is update less frequently only when some
>>> announcements or milestone is reached.
>>>
>>> What do you think?
>>>
>>> Jacopo
>>>
>>>
>>
>>

[jira] [Commented] (OFBIZ-5672) UOM conversion for supplier and sale order

[Sharan Foga (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187180#comment-15187180
 ] 

Sharan Foga commented on OFBIZ-5672:


No - I didnt but I will do. I would need it backported anyway

> UOM conversion for supplier and sale order
> --
>
> Key: OFBIZ-5672
> URL: https://issues.apache.org/jira/browse/OFBIZ-5672
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Release Branch 13.07, Trunk
> Environment: OOTB
>Reporter: Julien NICOLAS
>Assignee: Jacques Le Roux
>Priority: Minor
>  Labels: features
> Attachments: OFBIZ-5672-UOM-conversion-supplier-and-sale-order.13.07
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> It's possible to define different UomQuantity in measures tab, supplier tab 
> or price tab of a product but OFBiz don't manage it in stock.
> The improvement must manage it using UomConversion table for standard 
> conversions.
> When a new order (supplier or sale) is created, the user can choose the 
> UomQuantity if more than one UomQuantity is available.
> By default if only one conversion is defined in UomConversion table, OFBiz 
> will use it for both conversion way.
> However, it's possible to define different rules for each ways.
> Add new concept in UomConversion rules : rouding method and number of digit 
> after decimal point.
> To be more flexible, add new fields in price and supplier product tab.
>   - Uom conversion factor
>   - Rounding method
>   - Number of digit after decimal point
> If those fields are empty, OFBiz will use the standard UomConversion table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6925) Incorrect content length in response from HTTP service engine

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-6925.
--
   Resolution: Fixed
Fix Version/s: Upcoming Branch
   12.04.06
   14.12.01

Thanks Oleg,

Your patch is in
trunk r1734246
R15.12 r1734247
R14.12 r1734248
R13.07 r1734249
R12.04 r1734250




> Incorrect content length in response from HTTP service engine
> -
>
> Key: OFBIZ-6925
> URL: https://issues.apache.org/jira/browse/OFBIZ-6925
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: 13.07.02
> Environment: OSX
>Reporter: Oleg Andreyev
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 12.04.06, Upcoming Branch, 13.07.02
>
> Attachments: contentLength.diff
>
>
> Obvious error that cause deserialization errors on receiving side under some 
> conditions because data extracted from response shorter than it really was 
> sent. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-6925) Incorrect content length in response from HTTP service engine

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux reassigned OFBIZ-6925:
--

Assignee: Jacques Le Roux

> Incorrect content length in response from HTTP service engine
> -
>
> Key: OFBIZ-6925
> URL: https://issues.apache.org/jira/browse/OFBIZ-6925
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: 13.07.02
> Environment: OSX
>Reporter: Oleg Andreyev
>Assignee: Jacques Le Roux
> Fix For: 13.07.02
>
> Attachments: contentLength.diff
>
>
> Obvious error that cause deserialization errors on receiving side under some 
> conditions because data extracted from response shorter than it really was 
> sent. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5672) UOM conversion for supplier and sale order

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187166#comment-15187166
 ] 

Jacques Le Roux commented on OFBIZ-5672:


Did you try on trunk?

> UOM conversion for supplier and sale order
> --
>
> Key: OFBIZ-5672
> URL: https://issues.apache.org/jira/browse/OFBIZ-5672
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Release Branch 13.07, Trunk
> Environment: OOTB
>Reporter: Julien NICOLAS
>Assignee: Jacques Le Roux
>Priority: Minor
>  Labels: features
> Attachments: OFBIZ-5672-UOM-conversion-supplier-and-sale-order.13.07
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> It's possible to define different UomQuantity in measures tab, supplier tab 
> or price tab of a product but OFBiz don't manage it in stock.
> The improvement must manage it using UomConversion table for standard 
> conversions.
> When a new order (supplier or sale) is created, the user can choose the 
> UomQuantity if more than one UomQuantity is available.
> By default if only one conversion is defined in UomConversion table, OFBiz 
> will use it for both conversion way.
> However, it's possible to define different rules for each ways.
> Add new concept in UomConversion rules : rouding method and number of digit 
> after decimal point.
> To be more flexible, add new fields in price and supplier product tab.
>   - Uom conversion factor
>   - Rounding method
>   - Number of digit after decimal point
> If those fields are empty, OFBiz will use the standard UomConversion table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5461) include ivy clearcache in build

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187163#comment-15187163
 ] 

Jacques Le Roux commented on OFBIZ-5461:


Will you not provide an "ant clean-ivy" target? ;)

> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Christian Geisert
> Fix For: 14.12.01
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

buildbot success in on ofbiz-trunk

[buildbot]

The Buildbot has detected a restored build on builder ofbiz-trunk while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk/builds/448

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/trunk] 1734241
Blamelist: jleroux

Build succeeded!

Sincerely,
 -The Buildbot

[jira] [Commented] (OFBIZ-6925) Incorrect content length in response from HTTP service engine

[Oleg Andreyev (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187126#comment-15187126
 ] 

Oleg Andreyev commented on OFBIZ-6925:
--

Tested on 13.07 but patch is good from all versions (trunk, 14,13,12).

> Incorrect content length in response from HTTP service engine
> -
>
> Key: OFBIZ-6925
> URL: https://issues.apache.org/jira/browse/OFBIZ-6925
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: 13.07.02
> Environment: OSX
>Reporter: Oleg Andreyev
> Fix For: 13.07.02
>
> Attachments: contentLength.diff
>
>
> Obvious error that cause deserialization errors on receiving side under some 
> conditions because data extracted from response shorter than it really was 
> sent. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6925) Incorrect content length in response from HTTP service engine

[Oleg Andreyev (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Andreyev updated OFBIZ-6925:
-
Attachment: contentLength.diff

> Incorrect content length in response from HTTP service engine
> -
>
> Key: OFBIZ-6925
> URL: https://issues.apache.org/jira/browse/OFBIZ-6925
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: 13.07.02
> Environment: OSX
>Reporter: Oleg Andreyev
> Fix For: 13.07.02
>
> Attachments: contentLength.diff
>
>
> Obvious error that cause deserialization errors on receiving side under some 
> conditions because data extracted from response shorter than it really was 
> sent. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6925) Incorrect content length in response from HTTP service engine

[Oleg Andreyev (JIRA)]

Oleg Andreyev created OFBIZ-6925:


 Summary: Incorrect content length in response from HTTP service 
engine
 Key: OFBIZ-6925
 URL: https://issues.apache.org/jira/browse/OFBIZ-6925
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: 13.07.02
 Environment: OSX
Reporter: Oleg Andreyev
 Fix For: 13.07.02


Obvious error that cause deserialization errors on receiving side under some 
conditions because data extracted from response shorter than it really was 
sent. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-6921) Four of the remote SOAP test services don't work

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux reassigned OFBIZ-6921:
--

Assignee: (was: Jacques Le Roux)

> Four of the remote SOAP test services don't work
> 
>
> Key: OFBIZ-6921
> URL: https://issues.apache.org/jira/browse/OFBIZ-6921
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> For 5 years now the testRemoteSoap1 to testRemoteSoap4 test services don't 
> work. I added then when replacing testRemoteSoap at r1072378 but forgot then 
> to open a Jira issue, here it is!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6922) Currently the testRemoteSoap test service does not work.

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-6922.
--
   Resolution: Fixed
Fix Version/s: Upcoming Branch
   13.07.03
   12.04.06
   14.12.01

Because http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService is the 
ultimate location for the testRemoteSoap I decided to not change it to 
http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService where it's 
redirected by the SSL ASF proxy)

Closing after r1734241. I simply put a comment in source to clarify that it can 
be used only against trunk demo. So in case the infra team moves things around, 
as long as the OFBiz VM domain will be ofbiz-vm.apache.org this test will work. 
Anyway it's minor:  this test, used for local loopback testing (OFBiz Client 
SOAP -> OFBiz Server SOAP)  is not run with all others tests because it depends 
on the trunk demo, hence an Internet connection. Can be used when necessary...

> Currently the testRemoteSoap test service does not work.
> 
>
> Key: OFBIZ-6922
> URL: https://issues.apache.org/jira/browse/OFBIZ-6922
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
>
>
> *At the moment* the testRemoteSoap which is based on 
> http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not 
> work. There are 2 points to consider here.
> # Because we share/use the ASF SSL certificate we pass by an ASF proxy to 
> redirect requests. So we should rather call
> http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService
> because when when we call this request, the proxy underneath redirects to
> http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService
> So the current SOAP service location should be changed and the port removed.
> # At the moment after recent infra changes none of the calls to 
> demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or 
> old.ofbiz.apache.org domains work.
> So I will temporarily replace the domain by ofbiz-vm.apache.org but will not 
> close this issue because I will soon contact the infra team to fix the issue 
> with the domains.
> Note this is the remote test SOAP service, so only the trunk is concerned. We 
> don't test againt the other domains. Also this test is not part of the global 
> test suite (all tests).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6922) Currently the testRemoteSoap test service does not work.

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-6922:
---
Description: 
*At the moment* the testRemoteSoap which is based on 
http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not 
work. There are 2 points to consider here.
# Because we share/use the ASF SSL certificate we pass by an ASF proxy to 
redirect requests. So we should rather call
http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService
because when when we call this request, the proxy underneath redirects to
http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService
So the current SOAP service location should be changed and the port removed.
# At the moment after recent infra changes none of the calls to 
demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or 
old.ofbiz.apache.org domains work.

So I will temporarily replace the domain by ofbiz-vm.apache.org but will not 
close this issue because I will soon contact the infra team to fix the issue 
with the domains.

Note this is the remote test SOAP service, so only the trunk is concerned. We 
don't test againt the other domains. Also this test is not part of the global 
test suite (all tests).

  was:
*At the moment* the testRemoteSoap which is based on 
http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not 
work. There are 2 points to consider here.
# Because we share/use the ASF SSL certificate we pass by an ASF proxy to 
redirect requests. So we should rather call
http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService
because when when we call this request, the proxy underneath redirects to
http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService
So the current SOAP service location should be changed and the port removed.
# At the moment after recent infra changes none of the calls to 
demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or 
old.ofbiz.apache.org domains work.

So I will temporarily replace the domain by ofbiz-vm.apache.org but will not 
close this issue because I will soon contact the infra team to fix the issue 
with the domains.

Note this is the remote test SOAP services, so only the trunk is concerned. We 
don't test againt the other domains. Also this test is not part of the global 
test suite (all tests).


> Currently the testRemoteSoap test service does not work.
> 
>
> Key: OFBIZ-6922
> URL: https://issues.apache.org/jira/browse/OFBIZ-6922
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>
> *At the moment* the testRemoteSoap which is based on 
> http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not 
> work. There are 2 points to consider here.
> # Because we share/use the ASF SSL certificate we pass by an ASF proxy to 
> redirect requests. So we should rather call
> http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService
> because when when we call this request, the proxy underneath redirects to
> http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService
> So the current SOAP service location should be changed and the port removed.
> # At the moment after recent infra changes none of the calls to 
> demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or 
> old.ofbiz.apache.org domains work.
> So I will temporarily replace the domain by ofbiz-vm.apache.org but will not 
> close this issue because I will soon contact the infra team to fix the issue 
> with the domains.
> Note this is the remote test SOAP service, so only the trunk is concerned. We 
> don't test againt the other domains. Also this test is not part of the global 
> test suite (all tests).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6922) Currently the testRemoteSoap test service does not work.

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187048#comment-15187048
 ] 

Jacques Le Roux commented on OFBIZ-6922:


Yes!

> Currently the testRemoteSoap test service does not work.
> 
>
> Key: OFBIZ-6922
> URL: https://issues.apache.org/jira/browse/OFBIZ-6922
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>
> *At the moment* the testRemoteSoap which is based on 
> http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not 
> work. There are 2 points to consider here.
> # Because we share/use the ASF SSL certificate we pass by an ASF proxy to 
> redirect requests. So we should rather call
> http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService
> because when when we call this request, the proxy underneath redirects to
> http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService
> So the current SOAP service location should be changed and the port removed.
> # At the moment after recent infra changes none of the calls to 
> demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or 
> old.ofbiz.apache.org domains work.
> So I will temporarily replace the domain by ofbiz-vm.apache.org but will not 
> close this issue because I will soon contact the infra team to fix the issue 
> with the domains.
> Note this is the remote test SOAP services, so only the trunk is concerned. 
> We don't test againt the other domains. Also this test is not part of the 
> global test suite (all tests).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6922) Currently the testRemoteSoap test service does not work.

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-6922:
---
Summary: Currently the testRemoteSoap test service does not work.  (was: 
Currently the testRemoteSoap test services does not work.)

> Currently the testRemoteSoap test service does not work.
> 
>
> Key: OFBIZ-6922
> URL: https://issues.apache.org/jira/browse/OFBIZ-6922
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>
> *At the moment* the testRemoteSoap which is based on 
> http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not 
> work. There are 2 points to consider here.
> # Because we share/use the ASF SSL certificate we pass by an ASF proxy to 
> redirect requests. So we should rather call
> http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService
> because when when we call this request, the proxy underneath redirects to
> http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService
> So the current SOAP service location should be changed and the port removed.
> # At the moment after recent infra changes none of the calls to 
> demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or 
> old.ofbiz.apache.org domains work.
> So I will temporarily replace the domain by ofbiz-vm.apache.org but will not 
> close this issue because I will soon contact the infra team to fix the issue 
> with the domains.
> Note this is the remote test SOAP services, so only the trunk is concerned. 
> We don't test againt the other domains. Also this test is not part of the 
> global test suite (all tests).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5461) include ivy clearcache in build

[Christian Geisert (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187037#comment-15187037
 ] 

Christian Geisert commented on OFBIZ-5461:
--

Ok, I'll commit the change (removing  from )


> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Christian Geisert
> Fix For: 14.12.01
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-5461) include ivy clearcache in build

[Christian Geisert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Geisert reassigned OFBIZ-5461:


Assignee: Christian Geisert  (was: Jacques Le Roux)

> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Christian Geisert
> Fix For: 14.12.01
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5672) UOM conversion for supplier and sale order

[Sharan Foga (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187026#comment-15187026
 ] 

Sharan Foga commented on OFBIZ-5672:


Hi I'm looking at this type of UOM requirement and have tried this patch on 
13.07 but am getting errors. Does this patch need updating or am I doing 
something wrong?


> UOM conversion for supplier and sale order
> --
>
> Key: OFBIZ-5672
> URL: https://issues.apache.org/jira/browse/OFBIZ-5672
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Release Branch 13.07, Trunk
> Environment: OOTB
>Reporter: Julien NICOLAS
>Assignee: Jacques Le Roux
>Priority: Minor
>  Labels: features
> Attachments: OFBIZ-5672-UOM-conversion-supplier-and-sale-order.13.07
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> It's possible to define different UomQuantity in measures tab, supplier tab 
> or price tab of a product but OFBiz don't manage it in stock.
> The improvement must manage it using UomConversion table for standard 
> conversions.
> When a new order (supplier or sale) is created, the user can choose the 
> UomQuantity if more than one UomQuantity is available.
> By default if only one conversion is defined in UomConversion table, OFBiz 
> will use it for both conversion way.
> However, it's possible to define different rules for each ways.
> Add new concept in UomConversion rules : rouding method and number of digit 
> after decimal point.
> To be more flexible, add new fields in price and supplier product tab.
>   - Uom conversion factor
>   - Rounding method
>   - Number of digit after decimal point
> If those fields are empty, OFBiz will use the standard UomConversion table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5461) include ivy clearcache in build

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187014#comment-15187014
 ] 

Jacques Le Roux commented on OFBIZ-5461:


Good idea Christian, will you submit something?

> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
> Fix For: 14.12.01
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Proposal for the "Tweets" and "News" sections of the main web page of the OFBiz site

[Ashish Vijaywargiya]

+1

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997

On Wed, Mar 9, 2016 at 3:15 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> Proposal:
> in the main page of the ofbiz web site, move the "Tweets" section from the
> right bar to the main section of the page, before the "News" section; then
> rename the "News" section into "Announcements" or similar.
>
> Goal:
> give more visibility to our tweets because it is a more dynamic section
> while the "News" section is update less frequently only when some
> announcements or milestone is reached.
>
> What do you think?
>
> Jacopo
>

Re: Proposal for the "Tweets" and "News" sections of the main web page of the OFBiz site

[Taher Alkhateeb]

+1
On Mar 9, 2016 1:38 PM, "Sharan-F"  wrote:

> Hi Jacopo
>
> +1
>
> Yes it's a good idea. Our News section is a bit outdated now so keeping
> everything current is good. (BTW we have around 250 twitter followers now).
>
> Also I do have a work in progress regarding a re-design of the website that
> I'm working on and will share what I've done so far with everyone soon.
>
> Thanks
> Sharan
>
>
>
> --
> View this message in context:
> http://ofbiz.135035.n4.nabble.com/Proposal-for-the-Tweets-and-News-sections-of-the-main-web-page-of-the-OFBiz-site-tp4677665p4677670.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>

Re: Welcome to our new committer Gregory Draperi

[Arun Patidar]

Congratulations Gregory. Welcome aboard!


Thanks & Regards
---
Arun Patidar
Manager,Enterprise Software Development
HotWax Systems
www.hotwaxsystems.com

On Tuesday 08 March 2016 09:57 PM, Jacopo Cappellato wrote:

Gregory is a software security expert that has been "silently" helping the
OFBiz project for years by testing and assessing the security aspects of
our system and submitting valuable and precise reports and helping the PMC
to resolve them.

On behalf of the PMC, welcome onboard Gregory.

[jira] [Reopened] (OFBIZ-5461) include ivy clearcache in build

[Christian Geisert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Geisert reopened OFBIZ-5461:
--

This change causes unnecessary long build time when using Ivy (and cleans the 
global Ivy cache, not just the OFBiz related stuff). I think 'clean' should 
just delete the build artefacts.
When you need to clear the Ivy cache just use the 'clean-ivy'' target.

> include ivy clearcache in build
> ---
>
> Key: OFBIZ-5461
> URL: https://issues.apache.org/jira/browse/OFBIZ-5461
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
> Fix For: 14.12.01
>
> Attachments: OFBIZ-5462-BUILD-ivy-v2.patch
>
>
> in a CI setup the cache of ivy needs to be cleared occasionaly in order to 
> retrieve correct files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Proposal for the "Tweets" and "News" sections of the main web page of the OFBiz site

[Sharan-F]

Hi Jacopo

+1

Yes it's a good idea. Our News section is a bit outdated now so keeping
everything current is good. (BTW we have around 250 twitter followers now).

Also I do have a work in progress regarding a re-design of the website that
I'm working on and will share what I've done so far with everyone soon.

Thanks
Sharan



--
View this message in context: 
http://ofbiz.135035.n4.nabble.com/Proposal-for-the-Tweets-and-News-sections-of-the-main-web-page-of-the-OFBiz-site-tp4677665p4677670.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: Proposal for the "Tweets" and "News" sections of the main web page of the OFBiz site

[Pierre Smits]

+1

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Mar 9, 2016 at 11:32 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Agreed, so we increase the width of the "Tweets" section, right? Same
> height I guess.
>
> Jacques
>
>
> Le 09/03/2016 11:08, Julien NICOLAS a écrit :
>
>> +1
>>
>> There is a lot of tweet with @apacheOfibz and it could be interesting to
>> have it as main news.
>>
>> Le 09/03/2016 10:45, Jacopo Cappellato a écrit :
>>
>>> Proposal:
>>> in the main page of the ofbiz web site, move the "Tweets" section from
>>> the
>>> right bar to the main section of the page, before the "News" section;
>>> then
>>> rename the "News" section into "Announcements" or similar.
>>>
>>> Goal:
>>> give more visibility to our tweets because it is a more dynamic section
>>> while the "News" section is update less frequently only when some
>>> announcements or milestone is reached.
>>>
>>> What do you think?
>>>
>>> Jacopo
>>>
>>>
>>
>>

Re: Proposal for the "Tweets" and "News" sections of the main web page of the OFBiz site

[Jacques Le Roux]

Agreed, so we increase the width of the "Tweets" section, right? Same height I 
guess.

Jacques

Le 09/03/2016 11:08, Julien NICOLAS a écrit :

+1

There is a lot of tweet with @apacheOfibz and it could be interesting to have 
it as main news.

Le 09/03/2016 10:45, Jacopo Cappellato a écrit :

Proposal:
in the main page of the ofbiz web site, move the "Tweets" section from the
right bar to the main section of the page, before the "News" section; then
rename the "News" section into "Announcements" or similar.

Goal:
give more visibility to our tweets because it is a more dynamic section
while the "News" section is update less frequently only when some
announcements or milestone is reached.

What do you think?

Jacopo

Re: Welcome to our new committer Gregory Draperi

[Shi Jinghai]

Gregory, welcome!

Kind Regards,

Shi Jinghai

-邮件原件-
发件人: gregory draperi [mailto:gregory.drap...@gmail.com] 
发送时间: 2016年3月9日 16:41
收件人: dev@ofbiz.apache.org
主题: Re: Welcome to our new committer Gregory Draperi

Hi all,

Thanks for all your nice words.

I hope I will be able to provide some good help regarding application
security.

Best wishes,

Gregory

2016-03-09 8:59 GMT+01:00 Julien NICOLAS :

> Congratulations & welcome aboard Gregory :)
>
> Julien.
>
>
> Le 08/03/2016 17:27, Jacopo Cappellato a écrit :
>
>> Gregory is a software security expert that has been "silently" helping the
>> OFBiz project for years by testing and assessing the security aspects of
>> our system and submitting valuable and precise reports and helping the PMC
>> to resolve them.
>>
>> On behalf of the PMC, welcome onboard Gregory.
>>
>>
>


-- 
Grégory Draperi

Re: Proposal for the "Tweets" and "News" sections of the main web page of the OFBiz site

[Julien NICOLAS]

+1

There is a lot of tweet with @apacheOfibz and it could be interesting to 
have it as main news.


Le 09/03/2016 10:45, Jacopo Cappellato a écrit :

Proposal:
in the main page of the ofbiz web site, move the "Tweets" section from the
right bar to the main section of the page, before the "News" section; then
rename the "News" section into "Announcements" or similar.

Goal:
give more visibility to our tweets because it is a more dynamic section
while the "News" section is update less frequently only when some
announcements or milestone is reached.

What do you think?

Jacopo

Proposal for the "Tweets" and "News" sections of the main web page of the OFBiz site

[Jacopo Cappellato]

Proposal:
in the main page of the ofbiz web site, move the "Tweets" section from the
right bar to the main section of the page, before the "News" section; then
rename the "News" section into "Announcements" or similar.

Goal:
give more visibility to our tweets because it is a more dynamic section
while the "News" section is update less frequently only when some
announcements or milestone is reached.

What do you think?

Jacopo

Re: Welcome to our new committer Gregory Draperi

[Jacques Le Roux]

I'm sure you will, welcome Gregory :)

Jacques

Le 09/03/2016 09:41, gregory draperi a écrit :

Hi all,

Thanks for all your nice words.

I hope I will be able to provide some good help regarding application
security.

Best wishes,

Gregory

2016-03-09 8:59 GMT+01:00 Julien NICOLAS :


Congratulations & welcome aboard Gregory :)

Julien.


Le 08/03/2016 17:27, Jacopo Cappellato a écrit :


Gregory is a software security expert that has been "silently" helping the
OFBiz project for years by testing and assessing the security aspects of
our system and submitting valuable and precise reports and helping the PMC
to resolve them.

On behalf of the PMC, welcome onboard Gregory.

Re: Welcome to our new committer Gregory Draperi

[gregory draperi]

Hi all,

Thanks for all your nice words.

I hope I will be able to provide some good help regarding application
security.

Best wishes,

Gregory

2016-03-09 8:59 GMT+01:00 Julien NICOLAS :

> Congratulations & welcome aboard Gregory :)
>
> Julien.
>
>
> Le 08/03/2016 17:27, Jacopo Cappellato a écrit :
>
>> Gregory is a software security expert that has been "silently" helping the
>> OFBiz project for years by testing and assessing the security aspects of
>> our system and submitting valuable and precise reports and helping the PMC
>> to resolve them.
>>
>> On behalf of the PMC, welcome onboard Gregory.
>>
>>
>


-- 
Grégory Draperi

Re: Welcome to our new committer Gregory Draperi

[Julien NICOLAS]

Congratulations & welcome aboard Gregory :)

Julien.

Le 08/03/2016 17:27, Jacopo Cappellato a écrit :

Gregory is a software security expert that has been "silently" helping the
OFBiz project for years by testing and assessing the security aspects of
our system and submitting valuable and precise reports and helping the PMC
to resolve them.

On behalf of the PMC, welcome onboard Gregory.