[jira] [Updated] (OFBIZ-7316) Product Demand Report is not working

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7316:
-
Attachment: ProductDemandReport.patch

This report is not working for single record, hence corrected the condition.

> Product Demand Report is not working
> 
>
> Key: OFBIZ-7316
> URL: https://issues.apache.org/jira/browse/OFBIZ-7316
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
> Attachments: ProductDemandReport.patch
>
>
> Product Demand Report is not working 
> Screen : 
> https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
> Section : Product Demand Report



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

[jira] [Updated] (OFBIZ-7315) Order Discount Code Report is not working

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7315:
-
Attachment: OrderDiscountCodeReport.patch

In this report import statement is missing.

> Order Discount Code Report is not working
> -
>
> Key: OFBIZ-7315
> URL: https://issues.apache.org/jira/browse/OFBIZ-7315
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
> Attachments: OrderDiscountCodeReport.patch
>
>
> Order Discount Code Report is not working
> Screen : 
> https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
> Section : Order Discount Code Report



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

[jira] [Updated] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine

[Vishal Chhabria (JIRA)]

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

Vishal Chhabria updated OFBIZ-7008:
---
Attachment: OFBIZ-7008.patch

Updated productPromoId.

> Support to add condition for Geo Location in Promo Engine
> -
>
> Key: OFBIZ-7008
> URL: https://issues.apache.org/jira/browse/OFBIZ-7008
> Project: OFBiz
>  Issue Type: New Feature
>Affects Versions: Trunk
>Reporter: Vishal Chhabria
>Assignee: Mridul Pathak
>Priority: Trivial
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7008.patch, OFBIZ-7008.patch, OFBIZ-7008.patch, 
> OFBIZ-7008.patch, SampleData.xml
>
>




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

[jira] [Updated] (OFBIZ-7314) Last 3 Months Sales Report is not working

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7314:
-
Attachment: Last3MonthsSalesReport.patch

Found following issues.
1. In this report we used findByPrimaryKey which has been moved in 
GenericHelper Class.
2. Report is not working for single record.
3. LinkList class is used by name LinkedkList 

> Last 3 Months Sales Report is not working 
> --
>
> Key: OFBIZ-7314
> URL: https://issues.apache.org/jira/browse/OFBIZ-7314
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
> Attachments: Last3MonthsSalesReport.patch
>
>
> Last 3 Months Sales Report is not working 
> Screen : 
> https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
> Section : Last 3 Months Sales Report



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

[jira] [Updated] (OFBIZ-7313) Coupon Sales Report is not working

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7313:
-
Attachment: CouponSalesReport.patch

Issue is like this report is not working for single record and LinkedList class 
is being used by name LinkedkList.

> Coupon Sales Report is not working
> --
>
> Key: OFBIZ-7313
> URL: https://issues.apache.org/jira/browse/OFBIZ-7313
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
> Attachments: CouponSalesReport.patch
>
>
> Coupon Sales Report is not working (Data is not getting populated)
> Screen : 
> https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
> Section : Coupon Sales Report



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

[jira] [Updated] (OFBIZ-7312) Order BIRT report is not working properly

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7312:
-
Description: 
Order BIRT reports are not working it is either broken or not populating data 
correctly(specially in case of a single order).

1. Coupon Sales Report
2. Last 3Months Sales Report
3. Order Discount Code Report
4. Product Demand Report
5. Sales Report
6. Net Before Overhead Report
7. Sale Orders By Channel
8. Order By Referrer

  was:
Order BIRT reports are not working it is either broken or not populating data 
correctly(specially in case of a single order).

1. Coupon Sales Report
2. Last 3Months Sales Report
3. Order Discount Code Report
4. Product Demand Report
5. Sales Report
6. Net Before Overhead Report
7. Product Demand Report
8. Sale Orders By Channel
9. Order By Referrer


> Order BIRT report is not working properly
> -
>
> Key: OFBIZ-7312
> URL: https://issues.apache.org/jira/browse/OFBIZ-7312
> Project: OFBiz
>  Issue Type: Bug
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
>
> Order BIRT reports are not working it is either broken or not populating data 
> correctly(specially in case of a single order).
> 1. Coupon Sales Report
> 2. Last 3Months Sales Report
> 3. Order Discount Code Report
> 4. Product Demand Report
> 5. Sales Report
> 6. Net Before Overhead Report
> 7. Sale Orders By Channel
> 8. Order By Referrer



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

Re: buildbot failure in on ofbiz-trunk

[Deepak Dixit]

yes may be, not sure :)

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Jun 12, 2016 at 2:10 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Ah, maybe fixed with r1747963?
>
> Jacques
>
>
>
> Le 12/06/2016 à 10:39, Jacques Le Roux a écrit :
>
>> We don't have history on HTML test results. So it's hard to tell now ,
>> because you have successfully committed since (would need to browse
>> https://ci.apache.org/builders/ofbiz-trunk/builds/826/steps/compile_1/logs/stdio
>> ).
>> Anyway it works now so just forget it ;)
>>
>> Jacques
>>
>> Le 12/06/2016 à 09:38, Deepak Dixit a écrit :
>>
>>> I don't know why buildbot send failure notification for r#1747956, In
>>> this
>>> commit changes only done for  PartyServices.java and all the party
>>> related
>>> test passed successfully.
>>>
>>> {quote}
>>>
>>>   [java] 2016-06-12 07:12:56,826 |main
>>> |GenericDelegator  |I| Rolling back 42 entity operations
>>>   [java] 2016-06-12 07:12:57,359 |main
>>> |TestRunContainer  |I| [JUNIT] Results for test suite:
>>> partytests
>>>   [java] 2016-06-12 07:12:57,359 |main
>>> |TestRunContainer  |I| [JUNIT] Pass: true | # Tests: 16 |
>>> # Failed: 0 # Errors: 0
>>>
>>> {quote}
>>>
>>> Thanks & Regards
>>> --
>>> Deepak Dixit
>>> www.hotwaxsystems.com
>>>
>>> On Sun, Jun 12, 2016 at 12:44 PM,  wrote:
>>>
>>> The Buildbot has detected a new failure on builder ofbiz-trunk while
 building . Full details are available at:
  https://ci.apache.org/builders/ofbiz-trunk/builds/826

 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] 1747956
 Blamelist: deepak

 BUILD FAILED: failed compile_1

 Sincerely,
   -The Buildbot





>>
>

[jira] [Created] (OFBIZ-7316) Product Demand Report is not working

[Rohit Koushal (JIRA)]

Rohit Koushal created OFBIZ-7316:


 Summary: Product Demand Report is not working
 Key: OFBIZ-7316
 URL: https://issues.apache.org/jira/browse/OFBIZ-7316
 Project: OFBiz
  Issue Type: Sub-task
  Components: order, specialpurpose/birt
Reporter: Rohit Koushal
Assignee: Rohit Koushal


Product Demand Report is not working 
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Product Demand Report




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

[jira] [Commented] (OFBIZ-7266) Auto-complete on lookup field should be able to support filter by date.

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7266:
-

Hi [~kongrath],

You can attach patch using same name, jira automatically handle version. You 
can use .patch for patch name

> Auto-complete on lookup field should be able to support filter by date.
> ---
>
> Key: OFBIZ-7266
> URL: https://issues.apache.org/jira/browse/OFBIZ-7266
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Priority: Minor
> Attachments: auto-complete-fix-v2.patch, auto-complete-fix.patch
>
>
> Hi,
> For the general reason, if the lookup popup (like as performFind service 
> work) able to filter the result from date. so, in the auto complete for 
> lookup filed should be also able too.
> Simple :
> add this tag in action tag before call LookupDecorator
> and filter on field "fromDate", "thruDate" as default.
> {code:xml}
> 
> {code}
> Advance :
> you can customize "fromDate" and "thruDate" field names by do follow below
> {code:xml}
> 
> 
> 
> {code}
> Best Regards,
> Kongrath



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

[jira] [Updated] (OFBIZ-7313) Coupon Sales Report is not working

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7313:
-
Description: 
Coupon Sales Report is not working (Data is not getting populated)
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Coupon Sales Report

  was:
Coupon Sales Report is not working 
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Coupon Sales Report


> Coupon Sales Report is not working
> --
>
> Key: OFBIZ-7313
> URL: https://issues.apache.org/jira/browse/OFBIZ-7313
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
>
> Coupon Sales Report is not working (Data is not getting populated)
> Screen : 
> https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
> Section : Coupon Sales Report



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

[jira] [Updated] (OFBIZ-7315) Order Discount Code Report is not working

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7315:
-
Description: 
Order Discount Code Report is not working
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Order Discount Code Report

  was:
Order Discount Code Report si not working
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Order Discount Code Report


> Order Discount Code Report is not working
> -
>
> Key: OFBIZ-7315
> URL: https://issues.apache.org/jira/browse/OFBIZ-7315
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
>
> Order Discount Code Report is not working
> Screen : 
> https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
> Section : Order Discount Code Report



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

[jira] [Updated] (OFBIZ-7315) Order Discount Code Report is not working

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7315:
-
Description: 
Order Discount Code Report si not working
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Order Discount Code Report

  was:
Order Discount Code Report
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Order Discount Code Report


> Order Discount Code Report is not working
> -
>
> Key: OFBIZ-7315
> URL: https://issues.apache.org/jira/browse/OFBIZ-7315
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
>
> Order Discount Code Report si not working
> Screen : 
> https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
> Section : Order Discount Code Report



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

[jira] [Updated] (OFBIZ-7314) Last 3 Months Sales Report is not working

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7314:
-
Description: 
Last 3 Months Sales Report is not working 
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Last 3 Months Sales Report

  was:
Coupon Sales Report is not working 
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Last 3 Months Sales Report


> Last 3 Months Sales Report is not working 
> --
>
> Key: OFBIZ-7314
> URL: https://issues.apache.org/jira/browse/OFBIZ-7314
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
>
> Last 3 Months Sales Report is not working 
> Screen : 
> https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
> Section : Last 3 Months Sales Report



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

[jira] [Created] (OFBIZ-7315) Order Discount Code Report is not working

[Rohit Koushal (JIRA)]

Rohit Koushal created OFBIZ-7315:


 Summary: Order Discount Code Report is not working
 Key: OFBIZ-7315
 URL: https://issues.apache.org/jira/browse/OFBIZ-7315
 Project: OFBiz
  Issue Type: Sub-task
  Components: order, specialpurpose/birt
Reporter: Rohit Koushal
Assignee: Rohit Koushal


Order Discount Code Report
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Order Discount Code Report



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

[jira] [Created] (OFBIZ-7314) Last 3 Months Sales Report is not working

[Rohit Koushal (JIRA)]

Rohit Koushal created OFBIZ-7314:


 Summary: Last 3 Months Sales Report is not working 
 Key: OFBIZ-7314
 URL: https://issues.apache.org/jira/browse/OFBIZ-7314
 Project: OFBiz
  Issue Type: Sub-task
  Components: order, specialpurpose/birt
Reporter: Rohit Koushal
Assignee: Rohit Koushal


Coupon Sales Report is not working 
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Last 3 Months Sales Report



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

[jira] [Created] (OFBIZ-7313) Coupon Sales Report is not working

[Rohit Koushal (JIRA)]

Rohit Koushal created OFBIZ-7313:


 Summary: Coupon Sales Report is not working
 Key: OFBIZ-7313
 URL: https://issues.apache.org/jira/browse/OFBIZ-7313
 Project: OFBiz
  Issue Type: Sub-task
  Components: order, specialpurpose/birt
Reporter: Rohit Koushal
Assignee: Rohit Koushal


Coupon Sales Report is not working 
Screen : 
https://ofbiz-vm.apache.org:8443/ordermgr/control/OrderPurchaseReportOptions
Section : Coupon Sales Report



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

[jira] [Assigned] (OFBIZ-7312) Order BIRT report is not working properly

[Rohit Koushal (JIRA)]

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

Rohit Koushal reassigned OFBIZ-7312:


Assignee: Rohit Koushal

> Order BIRT report is not working properly
> -
>
> Key: OFBIZ-7312
> URL: https://issues.apache.org/jira/browse/OFBIZ-7312
> Project: OFBiz
>  Issue Type: Bug
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>Assignee: Rohit Koushal
>
> Order BIRT reports are not working it is either broken or not populating data 
> correctly(specially in case of a single order).
> 1. Coupon Sales Report
> 2. Last 3Months Sales Report
> 3. Order Discount Code Report
> 4. Product Demand Report
> 5. Sales Report
> 6. Net Before Overhead Report
> 7. Product Demand Report
> 8. Sale Orders By Channel
> 9. Order By Referrer



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

[jira] [Updated] (OFBIZ-7312) Order BIRT report is not working properly

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7312:
-
Description: 
Order BIRT reports are not working it is either broken or not populating data 
correctly(specially in case of a single order).

1. Coupon Sales Report
2. Last 3Months Sales Report
3. Order Discount Code Report
4. Product Demand Report
5. Sales Report
6. Net Before Overhead Report
7. Product Demand Report
8. Sale Orders By Channel
9. Order By Referrer

  was:
Order BIRT reports are not working it is either broken or not populating data 
correctly(specially in case of a single order).

1. Coupon Sales Report
2. Last 3Months Sales Report
3. Order Discount Code Report
4. Product Demand Report
5. Sales Report
6. Net Before Overhead Report
7. Product Demand Report
8. Sale Orders By Channel


> Order BIRT report is not working properly
> -
>
> Key: OFBIZ-7312
> URL: https://issues.apache.org/jira/browse/OFBIZ-7312
> Project: OFBiz
>  Issue Type: Bug
>  Components: order, specialpurpose/birt
>Reporter: Rohit Koushal
>
> Order BIRT reports are not working it is either broken or not populating data 
> correctly(specially in case of a single order).
> 1. Coupon Sales Report
> 2. Last 3Months Sales Report
> 3. Order Discount Code Report
> 4. Product Demand Report
> 5. Sales Report
> 6. Net Before Overhead Report
> 7. Product Demand Report
> 8. Sale Orders By Channel
> 9. Order By Referrer



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

[jira] [Created] (OFBIZ-7312) Order BIRT report is not working properly

[Rohit Koushal (JIRA)]

Rohit Koushal created OFBIZ-7312:


 Summary: Order BIRT report is not working properly
 Key: OFBIZ-7312
 URL: https://issues.apache.org/jira/browse/OFBIZ-7312
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/birt
Reporter: Rohit Koushal


Order BIRT reports are not working it is either broken or not populating data 
correctly(specially in case of a single order).

1. Coupon Sales Report
2. Last 3Months Sales Report
3. Order Discount Code Report
4. Product Demand Report
5. Sales Report
6. Net Before Overhead Report
7. Product Demand Report
8. Sale Orders By Channel



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

[jira] [Updated] (OFBIZ-7311) Formatting in the CSS files

[Swapnil M Mane (JIRA)]

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

Swapnil M Mane updated OFBIZ-7311:
--
Description: 
This is a placeholder task to capture all tasks regarding the formatting of CSS 
code and renaming of files for the various themes. 

In CSS files, we are having various inconsistency in the formatting of the code 
for e.g. we have following types of code formatting

// No space
{code}
ul#preferences-menu a:hover {
text-decoration: none;
}
{code}

// Space of 2
{code}
div.autocomplete ul {
  list-style-type:none;
  margin:0;
  padding:0;
}
{code}

// Space of 4
{code}
.control-area a {
font-size: 1.1em;
color: #5CA3D7;
}
{code}

For better readability we should format the existing files with space of 4.

Also for some theme, we named CSS files as *maincss.css* and for some, we named 
it as *style.css*. We can rename these file as per best practices for 
consistency.

  was:
This is a placeholder task to capture all tasks regarding the formatting of CSS 
code and renaming of files for the various themes. 

In CSS files, we are having various inconsistency in the formatting of the code 
for e.g. we have following types of code formatting

// No space
{code}
ul#preferences-menu a:hover {
text-decoration: none;
}
{code}

// Space of 2
{code}
div.autocomplete ul {
  list-style-type:none;
  margin:0;
  padding:0;
}
{code}

// Space of 4
{code}
.control-area a {
font-size: 1.1em;
color: #5CA3D7;
}
{code}

For better readability we should format the existing files with space of 4.

Also for some theme, we named CSS files as *maincss.css* and for some we named 
it as *style.css*. We can rename these file as per best practices for 
consistency.


> Formatting in the CSS files
> ---
>
> Key: OFBIZ-7311
> URL: https://issues.apache.org/jira/browse/OFBIZ-7311
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Swapnil M Mane
>Assignee: Swapnil M Mane
>Priority: Minor
>
> This is a placeholder task to capture all tasks regarding the formatting of 
> CSS code and renaming of files for the various themes. 
> In CSS files, we are having various inconsistency in the formatting of the 
> code for e.g. we have following types of code formatting
> // No space
> {code}
> ul#preferences-menu a:hover {
> text-decoration: none;
> }
> {code}
> // Space of 2
> {code}
> div.autocomplete ul {
>   list-style-type:none;
>   margin:0;
>   padding:0;
> }
> {code}
> // Space of 4
> {code}
> .control-area a {
> font-size: 1.1em;
> color: #5CA3D7;
> }
> {code}
> For better readability we should format the existing files with space of 4.
> Also for some theme, we named CSS files as *maincss.css* and for some, we 
> named it as *style.css*. We can rename these file as per best practices for 
> consistency.



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

[jira] [Updated] (OFBIZ-7311) Formatting and renaming of the CSS files as per best practices

[Swapnil M Mane (JIRA)]

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

Swapnil M Mane updated OFBIZ-7311:
--
Summary: Formatting and renaming of the CSS files as per best practices  
(was: Formatting in the CSS files)

> Formatting and renaming of the CSS files as per best practices
> --
>
> Key: OFBIZ-7311
> URL: https://issues.apache.org/jira/browse/OFBIZ-7311
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Swapnil M Mane
>Assignee: Swapnil M Mane
>Priority: Minor
>
> This is a placeholder task to capture all tasks regarding the formatting of 
> CSS code and renaming of files for the various themes. 
> In CSS files, we are having various inconsistency in the formatting of the 
> code for e.g. we have following types of code formatting
> // No space
> {code}
> ul#preferences-menu a:hover {
> text-decoration: none;
> }
> {code}
> // Space of 2
> {code}
> div.autocomplete ul {
>   list-style-type:none;
>   margin:0;
>   padding:0;
> }
> {code}
> // Space of 4
> {code}
> .control-area a {
> font-size: 1.1em;
> color: #5CA3D7;
> }
> {code}
> For better readability we should format the existing files with space of 4.
> Also for some theme, we named CSS files as *maincss.css* and for some, we 
> named it as *style.css*. We can rename these file as per best practices for 
> consistency.



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

[jira] [Updated] (OFBIZ-7311) Formatting in the CSS files

[Swapnil M Mane (JIRA)]

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

Swapnil M Mane updated OFBIZ-7311:
--
Description: 
This is a placeholder task to capture all tasks regarding the formatting of CSS 
code and renaming of files for the various themes. 

In CSS files, we are having various inconsistency in the formatting of the code 
for e.g. we have following types of code formatting

// No space
{code}
ul#preferences-menu a:hover {
text-decoration: none;
}
{code}

// Space of 2
{code}
div.autocomplete ul {
  list-style-type:none;
  margin:0;
  padding:0;
}
{code}

// Space of 4
{code}
.control-area a {
font-size: 1.1em;
color: #5CA3D7;
}
{code}

For better readability we should format the existing files with space of 4.

Also for some theme, we named CSS files as *maincss.css* and for some we named 
it as *style.css*. We can rename these file as per best practices for 
consistency.

  was:
In CSS files, we are having various inconsistency in the formatting of the code 
for e.g. we have following types of code formatting

// No space
{code}
ul#preferences-menu a:hover {
text-decoration: none;
}
{code}

// Space of 2
{code}
div.autocomplete ul {
  list-style-type:none;
  margin:0;
  padding:0;
}
{code}

// Space of 4
{code}
.control-area a {
font-size: 1.1em;
color: #5CA3D7;
}
{code}

For better readability we should format the existing files with space of 4.


> Formatting in the CSS files
> ---
>
> Key: OFBIZ-7311
> URL: https://issues.apache.org/jira/browse/OFBIZ-7311
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Swapnil M Mane
>Assignee: Swapnil M Mane
>Priority: Minor
>
> This is a placeholder task to capture all tasks regarding the formatting of 
> CSS code and renaming of files for the various themes. 
> In CSS files, we are having various inconsistency in the formatting of the 
> code for e.g. we have following types of code formatting
> // No space
> {code}
> ul#preferences-menu a:hover {
> text-decoration: none;
> }
> {code}
> // Space of 2
> {code}
> div.autocomplete ul {
>   list-style-type:none;
>   margin:0;
>   padding:0;
> }
> {code}
> // Space of 4
> {code}
> .control-area a {
> font-size: 1.1em;
> color: #5CA3D7;
> }
> {code}
> For better readability we should format the existing files with space of 4.
> Also for some theme, we named CSS files as *maincss.css* and for some we 
> named it as *style.css*. We can rename these file as per best practices for 
> consistency.



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

Re: Proposal to modify the testing framework for OFBiz

[Pranay Pandey]

+1

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Fri, Jun 10, 2016 at 7:46 PM, Taher Alkhateeb  wrote:

> Hello Everyone,
>
> I was able to get a few tests running and this is very doable. But I faced
> a big problem in designing the testing framework because of ANT.
>
> The problem
> 
> The way the build scripts are designed in OFBiz are very complex. A master
> file calls other files which call other files. And in the middle you have
> external libraries (ant-contrib) and macros, and variables, and class path
> declarations, and and and 
>
> I cannot declare the tests programmatically (with JUnit test suites)
> because this means lower level components would depend on higher level
> components. So I have to do it in ANT, by navigating this maze of build
> scripts, and it was a headache for me just to read them, let alone modify
> them to create a testing framework.
>
> Suggested Solution
> 
> I suggest to implement the testing framework in Gradle, and simply call it
> from within ant. This is a middle solution that sustains ant for now, but
> can allow us to switch out later.
>
> This means I will just add one more file called build.gradle in the top
> level directory, and figure out the business logic for calling the test
> suites from that file
>
> I look forward to your feedback.
>
> Regards,
>
> Taher Alkhateeb
>
> On Wed, Jun 8, 2016 at 6:00 PM, Taher Alkhateeb <
> slidingfilame...@gmail.com>
> wrote:
>
> > Hi Everyone,
> >
> > Thank you all for your support, JIRA created in
> > https://issues.apache.org/jira/browse/OFBIZ-7254
> >
> > I will start working on it and try to implement ASAP to get my focus back
> > on refactoring.
> >
> > Cheers!
> >
> > Taher Alkhateeb
> >
> > On Wed, Jun 8, 2016 at 4:58 PM, Deepak Dixit <
> > deepak.di...@hotwaxsystems.com> wrote:
> >
> >> +1
> >>
> >> Thanks & Regards
> >> --
> >> Deepak Dixit
> >> www.hotwaxsystems.com
> >>
> >> On Wed, Jun 8, 2016 at 7:12 PM, Mridul Pathak <
> >> mridul.pat...@hotwaxsystems.com> wrote:
> >>
> >> > +1
> >> >
> >> > Makes perfect sense.
> >> >
> >> > --
> >> > Thanks & Regards,
> >> > Mridul Pathak
> >> > Senior Manager
> >> > HotWax Systems
> >> > http://www.hotwaxsystems.com
> >> >
> >> > > On Jun 8, 2016, at 2:41 PM, Taher Alkhateeb <
> >> slidingfilame...@gmail.com>
> >> > wrote:
> >> > >
> >> > > Hello Everyone,
> >> > >
> >> > > After refactoring the start component and while starting on the base
> >> > > component I realized that the testing framework for OFBiz is not
> good.
> >> > You
> >> > > cannot do real test driven development or red-green-refactor with
> the
> >> > > current setup, hence my proposal to change it. I explain below:
> >> > >
> >> > > Problem with current design
> >> > > 
> >> > > - What we have right now is not unit tests, it's really integration
> >> > tests.
> >> > > You have to start the framework, the database, the service engine,
> the
> >> > > entity engine and pretty much everything.
> >> > > - Testing is very slow, because it's an integration test as I
> >> mentioned
> >> > > above. 10 minutes on a good computer!
> >> > > - There is zero mocking! We actually have to --load-data for things
> to
> >> > > work. Again, these are integration tests.
> >> > > - Too complex: Integration tests by their nature are grabbing too
> >> much.
> >> > > Mind you, I am not objecting to integration tests (I actually like
> >> them)
> >> > > but I am objecting to not having real unit-tests. Unit tests should
> >> all
> >> > run
> >> > > in a few seconds.
> >> > >
> >> > > Proposed solution
> >> > > --
> >> > > - We keep what is considered real integration tests the way they are
> >> > right
> >> > > now and keep using them
> >> > > - We move what should be unit tests into simple JUnit classes, and
> we
> >> do
> >> > > not run them using java -jar ofbiz.jar --test, but instead run them
> >> > > directly from the build.xml script, so these files are not
> identified
> >> in
> >> > > any XML document, but are simply called immediately from the build
> >> > scripts.
> >> > > - We clearly mark the difference between integration tests and unit
> >> tests
> >> > > (inside the source files or in the suite declarations).
> >> > > - We change the run-tests target in build.xml to run both unit tests
> >> and
> >> > > integration tests.
> >> > >
> >> > > I intend to heavily refactor the framework and I would feel better
> >> about
> >> > > introducing this change while refactoring. What do you guys think?
> >> Ideas?
> >> > > Suggestions? Approvals and thumbs up?
> >> > >
> >> > > Regards,
> >> > >
> >> > > Taher Alkhateeb
> >> >
> >> >
> >>
> >
> >
>

[jira] [Created] (OFBIZ-7311) Formatting in the CSS files

[Swapnil M Mane (JIRA)]

Swapnil M Mane created OFBIZ-7311:
-

 Summary: Formatting in the CSS files
 Key: OFBIZ-7311
 URL: https://issues.apache.org/jira/browse/OFBIZ-7311
 Project: OFBiz
  Issue Type: Improvement
Reporter: Swapnil M Mane
Assignee: Swapnil M Mane
Priority: Minor


In CSS files, we are having various inconsistency in the formatting of the code 
for e.g. we have following types of code formatting

// No space
{code}
ul#preferences-menu a:hover {
text-decoration: none;
}
{code}

// Space of 2
{code}
div.autocomplete ul {
  list-style-type:none;
  margin:0;
  padding:0;
}
{code}

// Space of 4
{code}
.control-area a {
font-size: 1.1em;
color: #5CA3D7;
}
{code}

For better readability we should format the existing files with space of 4.



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

[jira] [Updated] (OFBIZ-7266) Auto-complete on lookup field should be able to support filter by date.

[Kongrath Suankaewmanee (JIRA)]

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

Kongrath Suankaewmanee updated OFBIZ-7266:
--
Attachment: auto-complete-fix-v2.patch

> Auto-complete on lookup field should be able to support filter by date.
> ---
>
> Key: OFBIZ-7266
> URL: https://issues.apache.org/jira/browse/OFBIZ-7266
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Priority: Minor
> Attachments: auto-complete-fix-v2.patch, auto-complete-fix.patch
>
>
> Hi,
> For the general reason, if the lookup popup (like as performFind service 
> work) able to filter the result from date. so, in the auto complete for 
> lookup filed should be also able too.
> Simple :
> add this tag in action tag before call LookupDecorator
> and filter on field "fromDate", "thruDate" as default.
> {code:xml}
> 
> {code}
> Advance :
> you can customize "fromDate" and "thruDate" field names by do follow below
> {code:xml}
> 
> 
> 
> {code}
> Best Regards,
> Kongrath



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

[jira] [Updated] (OFBIZ-7266) Auto-complete on lookup field should be able to support filter by date.

[Kongrath Suankaewmanee (JIRA)]

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

Kongrath Suankaewmanee updated OFBIZ-7266:
--
Description: 
Hi,

For the general reason, if the lookup popup (like as performFind service work) 
able to filter the result from date. so, in the auto complete for lookup filed 
should be also able too.

Simple :

add this tag in action tag before call LookupDecorator
and filter on field "fromDate", "thruDate" as default.

{code:xml}

{code}

Advance :

you can customize "fromDate" and "thruDate" field names by do follow below

{code:xml}



{code}

Best Regards,
Kongrath


  was:
Hi,

For the general reason, if the lookup popup (like as performFind service work) 
able to filter the result from date. so, in the auto complete for lookup filed 
should be also able too.

Simple :

add this tag in action tag before call LookupDecorator
and filter on field "fromDate", "thruDate" as default.

{code:xml}

{code}

Advance :

you can customize "fromDate" and "thruDate" field names by do follow below

{code:xml}



{code}

Best Regards,
Kongrath



> Auto-complete on lookup field should be able to support filter by date.
> ---
>
> Key: OFBIZ-7266
> URL: https://issues.apache.org/jira/browse/OFBIZ-7266
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Priority: Minor
> Attachments: auto-complete-fix.patch
>
>
> Hi,
> For the general reason, if the lookup popup (like as performFind service 
> work) able to filter the result from date. so, in the auto complete for 
> lookup filed should be also able too.
> Simple :
> add this tag in action tag before call LookupDecorator
> and filter on field "fromDate", "thruDate" as default.
> {code:xml}
> 
> {code}
> Advance :
> you can customize "fromDate" and "thruDate" field names by do follow below
> {code:xml}
> 
> 
> 
> {code}
> Best Regards,
> Kongrath



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

[jira] [Updated] (OFBIZ-7112) EntityUtilProperties

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-7112:
---
Attachment: OFBIZ-7112.patch

Hi Wai,

Here find attached a slightly modifed version of your patch. I simply used 
UtilValidate.isEmpty() when possible and formatted the EntityQuery.use() calls 
as we normally do (easier reading, one was alredy too much indented, not 
yours). So there a no functional changes in this new attached patch.

Before that I tested your patch and all tests dont' pass. There are 5 which 
fails. Please have a look, thanks!


> EntityUtilProperties
> 
>
> Key: OFBIZ-7112
> URL: https://issues.apache.org/jira/browse/OFBIZ-7112
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7112.patch, OFBIZ-7112.patch, OFBIZ-7112.patch
>
>
> Ofbiz reads properties from either a properties file or the 
> entity:SystemProperty. The way it works previously is that ofbiz reads from 
> the entity:SystemProperty first and if there is no value associated with the 
> target propertyname, it would then locate the value from the relevant 
> properties file.
> In other words, if there is a database entry for a property, the database 
> entry should override the associated properties file.
> The issue is that if a database entry exist but the value is empty, it would 
> look for a value from the properties file.  It should not do so.  If a 
> database entry exists for the propertyname of interest, the value should be 
> taken from the database even if it holds an empty value.



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

[jira] [Assigned] (OFBIZ-7112) EntityUtilProperties

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux reassigned OFBIZ-7112:
--

Assignee: Jacques Le Roux

> EntityUtilProperties
> 
>
> Key: OFBIZ-7112
> URL: https://issues.apache.org/jira/browse/OFBIZ-7112
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7112.patch, OFBIZ-7112.patch
>
>
> Ofbiz reads properties from either a properties file or the 
> entity:SystemProperty. The way it works previously is that ofbiz reads from 
> the entity:SystemProperty first and if there is no value associated with the 
> target propertyname, it would then locate the value from the relevant 
> properties file.
> In other words, if there is a database entry for a property, the database 
> entry should override the associated properties file.
> The issue is that if a database entry exist but the value is empty, it would 
> look for a value from the properties file.  It should not do so.  If a 
> database entry exists for the propertyname of interest, the value should be 
> taken from the database even if it holds an empty value.



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

Re: Taher Alkhateeb joins the OFBiz PMC

[Michael Brohl]

Good news, congratulations, Taher!

Michael

Am 10.06.16 um 09:32 schrieb Taher Alkhateeb:

Thank you Jacopo and everyone.

It's an honor to be part of such a wonderful group of people. I look
forward to helping the project however I can.

Cheers

Taher Alkhateeb

On Fri, Jun 10, 2016 at 9:48 AM, Nicolas Malin 
wrote:


Le 10/06/2016 08:05, Jacopo Cappellato a écrit :


Welcome, Taher! Keep up the great work.

Jacopo

Congrats and welcome :) !

Nicolas






smime.p7s
Description: S/MIME Cryptographic Signature

[jira] [Reopened] (OFBIZ-7061) Autocompletion for Compound Widget

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux reopened OFBIZ-7061:


> Autocompletion for Compound Widget
> --
>
> Key: OFBIZ-7061
> URL: https://issues.apache.org/jira/browse/OFBIZ-7061
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: james yong
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7061.patch, OFBIZ-7061.patch, OFBIZ-7061.patch
>
>
> I am trying to enable auto-completion when coding compound widget.
> My plan as follows:
> 1. The following xsd will be modified to use namespace
> site-conf.xsd
> widget-form.xsd
> widget-screen.xsd
> widget-menu.xsd
> simple-methods.xsd
> For example, in site-conf.xsd, we add the following document level attribute
> {code}
> xmlns="http://ofbiz.apache.org/sc; 
> targetNamespace="http://ofbiz.apache.org/sc;
> {code}
> 2. Import the above schema into compound-widgets.xsd so that compound widgets 
> use only one consolidated schema. 
> 3. Update ExampleCompoundWidgets.xml to use the new compound-widgets.xsd. For 
> example
> {code}
> http://www.w3.org/2001/XMLSchema-instance; 
> xmlns:sc="http://ofbiz.apache.org/sc;
> xmlns:m="http://ofbiz.apache.org/m;
> xmlns:s="http://ofbiz.apache.org/s;
> xmlns:f="http://ofbiz.apache.org/f;
> xmlns:sm="http://ofbiz.apache.org/sm;
> 
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/compound-widgets.xsd;>
> 
> 
> 
>  path="component://example/widget/example/ExampleCompoundWidgets.xml"/>
> 
> 
>  auth="true"/> value="CompoundWidgets2"/>
> 
>  page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets1"/>
>  page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets2"/>
> 
> .. the rest
> {code}
> 4. Change java code to support reading xml with namespace (i.e. xml for 
> compound widgets)
> 5. Update the attributes at document level for rest of the controllers, 
> menus, forms, simple methods and screens. Current setting will not work for 
> schema with a namespace. For example, in controller.xml, we will change 
> {code}
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/site-conf.xsd”
> {code} 
> to 
> {code}
> xmlns="http://ofbiz.apache.org/sc” 
> xsi:schemaLocation="http://ofbiz.apache.org/dtds/site-conf-ns.xsd”>
> {code}



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

[jira] [Created] (OFBIZ-7310) Use UtilValidate.isEmpty() instead of length() <= 0

[Jacques Le Roux (JIRA)]

Jacques Le Roux created OFBIZ-7310:
--

 Summary: Use UtilValidate.isEmpty()  instead of length() <= 0
 Key: OFBIZ-7310
 URL: https://issues.apache.org/jira/browse/OFBIZ-7310
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Trivial
 Fix For: Upcoming Branch


While reviewing Wai's patch for OFBIZ-7112 I noticed that he (re)used this 
pattern introduced earlier:
{code}
  (resource == null || resource.length() <= 0)
{code}
>From Java spec. a String, Collection, Map or CharSequence can't have a 
>negative length, so the pattern above can be reduced to
{code}
  (resource == null || resource.length() == 0)
{code}
which can be replaced using
{code}
  UtilValidate.isEmpty()
{code}
I checked, there are several other occurrences of this pattern (some very old, 
I guess most were routinely copied from an initial occurrence). I decided to 
replace all of them.

I did that already long ago for the
{code}
  (resource == null || resource.length() == 0)
{code}
pattern. It remains 4 of them. Three are justified (because of the dependency 
on base component or because using isEmpty() on Object is disputable for 
performance reasons). I'll took care of the remaining one right away!




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

[jira] [Commented] (OFBIZ-7300) partial received orders are getting cancelled using cancel option over order header

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-7300:


I'd not say it would resolve the issue. Just thinking about it, what about 
serialised products, does it make sense in POs? If yes then we would need to 
differentiate by item.

> partial received orders are getting cancelled using cancel option over order 
> header 
> 
>
> Key: OFBIZ-7300
> URL: https://issues.apache.org/jira/browse/OFBIZ-7300
> Project: OFBiz
>  Issue Type: Bug
>Reporter: Ankush Upadhyay
>
> Steps to reproduce:
> 1. Place purchase order with some quantities.
> 2. Receive few quantities.
> 3. Now cancel the order.
> Actual Behaviour:
> Order gets cancelled, status in OrderHeader change to ORDER_CANCELLED and in 
> OrderItem change to ITEM_CANCELLED.
> Expected result:
> Order should mark to ORDER_COMPLETED and item should mark to ITEM_COMPLETED,
> Remaining quantity (unreceived) should be set in OrderItem.cancelQuantity.



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

[jira] [Issue Comment Deleted] (OFBIZ-7299) Partial shipped orders are getting cancelled using cancel option over order header

[Jacques Le Roux (JIRA)]

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

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

(was: Yep..it was a typo :) ...i have corrected it now)

> Partial shipped orders are getting cancelled using cancel option over order 
> header 
> ---
>
> Key: OFBIZ-7299
> URL: https://issues.apache.org/jira/browse/OFBIZ-7299
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Ankush Upadhyay
>
> Steps to reproduce:
> 1. Place sales order with quantities more than 1.
> 2. Ship few quantities from facility manager.
> 3. Now cancel the order.
> Actual Behaviour:
> - Order gets cancelled, status in OrderHeader change to ORDER_CANCELLED and 
> in OrderItem change to ITEM_CANCELLED.
> Expected result:
> - Order should mark to ORDER_COMPLETED and item should mark to 
> ITEM_COMPLETED, 
> - Remaining quantity (unshipped) should be set in OrderItem.cancelQuantity. 



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

[jira] [Issue Comment Deleted] (OFBIZ-7299) Partial shipped orders are getting cancelled using cancel option over order header

[Jacques Le Roux (JIRA)]

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

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

(was: CABC-7300 is certainly an external (to ASF) reference ;) 
I guess you meant OFBIZ-7300 :))

> Partial shipped orders are getting cancelled using cancel option over order 
> header 
> ---
>
> Key: OFBIZ-7299
> URL: https://issues.apache.org/jira/browse/OFBIZ-7299
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Ankush Upadhyay
>
> Steps to reproduce:
> 1. Place sales order with quantities more than 1.
> 2. Ship few quantities from facility manager.
> 3. Now cancel the order.
> Actual Behaviour:
> - Order gets cancelled, status in OrderHeader change to ORDER_CANCELLED and 
> in OrderItem change to ITEM_CANCELLED.
> Expected result:
> - Order should mark to ORDER_COMPLETED and item should mark to 
> ITEM_COMPLETED, 
> - Remaining quantity (unshipped) should be set in OrderItem.cancelQuantity. 



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

[jira] [Commented] (OFBIZ-7260) Show the newly added component to Production run task (apart from BoM components) over Production Run PDF

[Pierre Smits (JIRA)]

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

Pierre Smits commented on OFBIZ-7260:
-

What are the version(s) and the component(s) this issue relates to?

> Show the newly added component to Production run task (apart from BoM 
> components) over Production Run PDF
> -
>
> Key: OFBIZ-7260
> URL: https://issues.apache.org/jira/browse/OFBIZ-7260
> Project: OFBiz
>  Issue Type: New Feature
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
> Attachments: AM.png, PR PDF.png
>
>
> So far it seems production run PDF shows only components added via original 
> BoM associated with the finished good (possibly based on 
> WorkEffortGoodStandard), but not the ones that are directly added via Actual 
> Material screen in adhoc manner
> It should list all the components used to complete a production run. Please 
> refer to attached screenshot for reference.



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

[jira] [Commented] (OFBIZ-7110) The Actual Material Cost is not accounting for cost of returned items against the issued items for production run tasks

[Pierre Smits (JIRA)]

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

Pierre Smits commented on OFBIZ-7110:
-

What are the version(s) and the component(s) this issue relates to?

> The Actual Material Cost is not accounting for cost of returned items against 
> the issued items for production run tasks
> ---
>
> Key: OFBIZ-7110
> URL: https://issues.apache.org/jira/browse/OFBIZ-7110
> Project: OFBiz
>  Issue Type: New Feature
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
> Attachments: MatCost_1.png, Matcost_2.png
>
>
> As of now the 'Actual Material Cost' over Actual Cost tab for any production 
> run just shown as weighted sums up of the issued inventory's cost. 
> We could allow it to account for returned items as well by deducting weighted 
> sum of returned inventory's cost from the weighted sum of issued inventory's 
> cost.
> Please refer to attached screenshot for more details



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

[jira] [Commented] (OFBIZ-7108) Provide an option to specify the Facility Location while producing the inventory/stock once production run gets completed

[Pierre Smits (JIRA)]

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

Pierre Smits commented on OFBIZ-7108:
-

What are the version(s) and the component(s) this issue relates to?

> Provide an option to specify the Facility Location while producing the 
> inventory/stock once production run gets completed
> -
>
> Key: OFBIZ-7108
> URL: https://issues.apache.org/jira/browse/OFBIZ-7108
> Project: OFBiz
>  Issue Type: New Feature
>Reporter: Swapnil Shah
> Attachments: OFBIZ-7108.patch, ProduceStock.png
>
>
> Currently there is no option to specify where the produced inventory against 
> finished good would be stocked in the facility. 
> Let's try to add the option to select and specify the facility location under 
> 'Production Run Produce' or 'Production Run Declare and Produce' section. 
> Once user submit the quantity and location same should be set over produced 
> InventoryItem.locationSeqId
> Please refer the attached screenshot for reference



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

[jira] [Commented] (OFBIZ-7299) Partial shipped orders are getting cancelled using cancel option over order header

[Swapnil Shah (JIRA)]

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

Swapnil Shah commented on OFBIZ-7299:
-

Yep..it was a typo :) ...i have corrected it now

> Partial shipped orders are getting cancelled using cancel option over order 
> header 
> ---
>
> Key: OFBIZ-7299
> URL: https://issues.apache.org/jira/browse/OFBIZ-7299
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Ankush Upadhyay
>
> Steps to reproduce:
> 1. Place sales order with quantities more than 1.
> 2. Ship few quantities from facility manager.
> 3. Now cancel the order.
> Actual Behaviour:
> - Order gets cancelled, status in OrderHeader change to ORDER_CANCELLED and 
> in OrderItem change to ITEM_CANCELLED.
> Expected result:
> - Order should mark to ORDER_COMPLETED and item should mark to 
> ITEM_COMPLETED, 
> - Remaining quantity (unshipped) should be set in OrderItem.cancelQuantity. 



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

[jira] [Comment Edited] (OFBIZ-7299) Partial shipped orders are getting cancelled using cancel option over order header

[Swapnil Shah (JIRA)]

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

Swapnil Shah edited comment on OFBIZ-7299 at 6/12/16 9:00 AM:
--

The problem specified in this ticket looks similar to what is reported over 
OFBIZ-7300 (and possibly calls for similar expected behavior at order and line 
item level). Only context is changed from Sales Order(by honoring Shipped Qty) 
to Purchase Order (by honoring Received qty).


was (Author: swash78):
The problem specified in this ticket looks similar to what is reported over 
CABC-7300 (and possibly calls for similar expected behavior at order and line 
item level). Only context is changed from Sales Order(by honoring Shipped Qty) 
to Purchase Order (by honoring Received qty).

> Partial shipped orders are getting cancelled using cancel option over order 
> header 
> ---
>
> Key: OFBIZ-7299
> URL: https://issues.apache.org/jira/browse/OFBIZ-7299
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Ankush Upadhyay
>
> Steps to reproduce:
> 1. Place sales order with quantities more than 1.
> 2. Ship few quantities from facility manager.
> 3. Now cancel the order.
> Actual Behaviour:
> - Order gets cancelled, status in OrderHeader change to ORDER_CANCELLED and 
> in OrderItem change to ITEM_CANCELLED.
> Expected result:
> - Order should mark to ORDER_COMPLETED and item should mark to 
> ITEM_COMPLETED, 
> - Remaining quantity (unshipped) should be set in OrderItem.cancelQuantity. 



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

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Ah, maybe fixed with r1747963?

Jacques


Le 12/06/2016 à 10:39, Jacques Le Roux a écrit :
We don't have history on HTML test results. So it's hard to tell now , because you have successfully committed since (would need to browse 
https://ci.apache.org/builders/ofbiz-trunk/builds/826/steps/compile_1/logs/stdio).

Anyway it works now so just forget it ;)

Jacques

Le 12/06/2016 à 09:38, Deepak Dixit a écrit :

I don't know why buildbot send failure notification for r#1747956, In this
commit changes only done for  PartyServices.java and all the party related
test passed successfully.

{quote}

  [java] 2016-06-12 07:12:56,826 |main
|GenericDelegator  |I| Rolling back 42 entity operations
  [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Results for test suite:
partytests
  [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Pass: true | # Tests: 16 |
# Failed: 0 # Errors: 0

{quote}

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Jun 12, 2016 at 12:44 PM,  wrote:


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

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] 1747956
Blamelist: deepak

BUILD FAILED: failed compile_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

We don't have history on HTML test results. So it's hard to tell now , because you have successfully committed since (would need to browse 
https://ci.apache.org/builders/ofbiz-trunk/builds/826/steps/compile_1/logs/stdio).

Anyway it works now so just forget it ;)

Jacques

Le 12/06/2016 à 09:38, Deepak Dixit a écrit :

I don't know why buildbot send failure notification for r#1747956, In this
commit changes only done for  PartyServices.java and all the party related
test passed successfully.

{quote}

  [java] 2016-06-12 07:12:56,826 |main
|GenericDelegator  |I| Rolling back 42 entity operations
  [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Results for test suite:
partytests
  [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Pass: true | # Tests: 16 |
# Failed: 0 # Errors: 0

{quote}

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Jun 12, 2016 at 12:44 PM,  wrote:


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

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] 1747956
Blamelist: deepak

BUILD FAILED: failed compile_1

Sincerely,
  -The Buildbot

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/827

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] 1747959
Blamelist: deepak

Build succeeded!

Sincerely,
 -The Buildbot

[jira] [Commented] (OFBIZ-7269) Error while importing party

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7269:
-

Fixed typo in middle name fixed at 

Trunk at r#1747963
15.12 at r#1747964
14.12 at r#1747965

> Error while importing party
> ---
>
> Key: OFBIZ-7269
> URL: https://issues.apache.org/jira/browse/OFBIZ-7269
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIZ-7269.patch
>
>
> The following errors occurred while importing  party from import/export screen
> https://localhost:8443/partymgr/control/ImportExport
> {quote}
> Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service 
> invocation error (Mapping for midleName not found, expected one of [partyId, 
> preferredCurrencyUomId, groupName, firstName, middleName, lastName, 
> companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId, 
> contactMechTypeId, emailAddress, telCountryCode, telAreaCode, 
> telContactNumber, address1, address2, city, stateProvinceGeoId, postalCode, 
> countryGeoId, ])
> {quote}



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

Re: buildbot failure in on ofbiz-trunk

[Deepak Dixit]

I don't know why buildbot send failure notification for r#1747956, In this
commit changes only done for  PartyServices.java and all the party related
test passed successfully.

{quote}

 [java] 2016-06-12 07:12:56,826 |main
|GenericDelegator  |I| Rolling back 42 entity operations
 [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Results for test suite:
partytests
 [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Pass: true | # Tests: 16 |
# Failed: 0 # Errors: 0

{quote}

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Jun 12, 2016 at 12:44 PM,  wrote:

> The Buildbot has detected a new failure on builder ofbiz-trunk while
> building . Full details are available at:
> https://ci.apache.org/builders/ofbiz-trunk/builds/826
>
> 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] 1747956
> Blamelist: deepak
>
> BUILD FAILED: failed compile_1
>
> Sincerely,
>  -The Buildbot
>
>
>
>

[jira] [Closed] (OFBIZ-7199) Incorrect "Required for SO" when adding same product with different desired delivery date

[Deepak Dixit (JIRA)]

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

Deepak Dixit closed OFBIZ-7199.
---
Resolution: Not A Problem

> Incorrect "Required for SO" when adding same product with different desired 
> delivery date
> -
>
> Key: OFBIZ-7199
> URL: https://issues.apache.org/jira/browse/OFBIZ-7199
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
>
> Steps to regenerate:
> 1) Add a product, quantity 1 and (say Rainbow Gizmo) with some delivery date.
> 2) Add again the same product with 2 quantity with the different delivery 
> date.
> 3) Place the order. Items will be added as separate line item
> When we look "Required for SO" field for the line items, they shows 3. 
> Actually, it should show 1 and 2 respectively.



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

[jira] [Commented] (OFBIZ-7199) Incorrect "Required for SO" when adding same product with different desired delivery date

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7199:
-

IMO we can discard this issue as "Required for SO" showing total outstanding 
quantity for SO. So this is correct behavior.

> Incorrect "Required for SO" when adding same product with different desired 
> delivery date
> -
>
> Key: OFBIZ-7199
> URL: https://issues.apache.org/jira/browse/OFBIZ-7199
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
>
> Steps to regenerate:
> 1) Add a product, quantity 1 and (say Rainbow Gizmo) with some delivery date.
> 2) Add again the same product with 2 quantity with the different delivery 
> date.
> 3) Place the order. Items will be added as separate line item
> When we look "Required for SO" field for the line items, they shows 3. 
> Actually, it should show 1 and 2 respectively.



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

[jira] [Closed] (OFBIZ-7213) Override allow-html attribute do not work in service implementing any interface

[Deepak Dixit (JIRA)]

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

Deepak Dixit closed OFBIZ-7213.
---
   Resolution: Fixed
Fix Version/s: 13.07.04
   15.12.01
   14.12.01

> Override allow-html attribute do not work in service implementing any 
> interface
> ---
>
> Key: OFBIZ-7213
> URL: https://issues.apache.org/jira/browse/OFBIZ-7213
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
>Priority: Critical
> Fix For: 14.12.01, 15.12.01, 13.07.04
>
> Attachments: OFBIZ-7213.patch
>
>
> To test I used an interface say "testInterface". Try as shown below
> =Add test interface and service =
> {code}
> 
> 
> 
>  location="org.ofbiz.order.order.OrderServices" 
> invoke="checkAllowHtmlForOverride">
> 
> 
> 
> {code}
> ===
> Add service definition for the service "checkAllowHtmlForOverride"  in 
> "org.ofbiz.order.order.OrderServices". 
> {code}
> public static Map checkAllowHtmlForOverride(DispatchContext 
> dctx, Map context) {
> String testData = (String) context.get("testData");
> Debug.log("==" + testData);
> return ServiceUtil.returnSuccess();
> }
> {code}
> Run service "checkAllowHtmlForOverride" from service engine. 
> {code}
> *Exception :* 
>  [java] 2016-06-07 19:07:38,429 |http-nio-8443-exec-9 |ServiceDispatcher  
>|E| Incoming context (in runSync : checkAllowHtmlForOverride) does 
> not match expected requirements
>  [java] org.ofbiz.service.ServiceValidationException: In field [testData] 
> less-than (<) and greater-than (>) symbols are not allowed.
>  [java]   at 
> org.ofbiz.service.ModelService.validate(ModelService.java:597) 
> ~[ofbiz-service.jar:?]
>  [java]   at 
> org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376) 
> [ofbiz-service.jar:?]
> {code}



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

[jira] [Commented] (OFBIZ-7213) Override allow-html attribute do not work in service implementing any interface

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7213:
-

This has been done at

Trunk at r#1747959
15.12 at r#1747960
14.12 at r#1747961
13.07 at r#1747962

Thanks Nameet for you contribution.

> Override allow-html attribute do not work in service implementing any 
> interface
> ---
>
> Key: OFBIZ-7213
> URL: https://issues.apache.org/jira/browse/OFBIZ-7213
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
>Priority: Critical
> Attachments: OFBIZ-7213.patch
>
>
> To test I used an interface say "testInterface". Try as shown below
> =Add test interface and service =
> {code}
> 
> 
> 
>  location="org.ofbiz.order.order.OrderServices" 
> invoke="checkAllowHtmlForOverride">
> 
> 
> 
> {code}
> ===
> Add service definition for the service "checkAllowHtmlForOverride"  in 
> "org.ofbiz.order.order.OrderServices". 
> {code}
> public static Map checkAllowHtmlForOverride(DispatchContext 
> dctx, Map context) {
> String testData = (String) context.get("testData");
> Debug.log("==" + testData);
> return ServiceUtil.returnSuccess();
> }
> {code}
> Run service "checkAllowHtmlForOverride" from service engine. 
> {code}
> *Exception :* 
>  [java] 2016-06-07 19:07:38,429 |http-nio-8443-exec-9 |ServiceDispatcher  
>|E| Incoming context (in runSync : checkAllowHtmlForOverride) does 
> not match expected requirements
>  [java] org.ofbiz.service.ServiceValidationException: In field [testData] 
> less-than (<) and greater-than (>) symbols are not allowed.
>  [java]   at 
> org.ofbiz.service.ModelService.validate(ModelService.java:597) 
> ~[ofbiz-service.jar:?]
>  [java]   at 
> org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376) 
> [ofbiz-service.jar:?]
> {code}



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

buildbot failure in on ofbiz-trunk

[buildbot]

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

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] 1747956
Blamelist: deepak

BUILD FAILED: failed compile_1

Sincerely,
 -The Buildbot

[jira] [Commented] (OFBIZ-7269) Error while importing party

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7269:
-

This has been committed at 

Trunk at r#1747956
15.12 at r#1747957
14.12 at r#1747958
13.07 (feature does not exists)

> Error while importing party
> ---
>
> Key: OFBIZ-7269
> URL: https://issues.apache.org/jira/browse/OFBIZ-7269
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIZ-7269.patch
>
>
> The following errors occurred while importing  party from import/export screen
> https://localhost:8443/partymgr/control/ImportExport
> {quote}
> Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service 
> invocation error (Mapping for midleName not found, expected one of [partyId, 
> preferredCurrencyUomId, groupName, firstName, middleName, lastName, 
> companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId, 
> contactMechTypeId, emailAddress, telCountryCode, telAreaCode, 
> telContactNumber, address1, address2, city, stateProvinceGeoId, postalCode, 
> countryGeoId, ])
> {quote}



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

[jira] [Closed] (OFBIZ-7269) Error while importing party

[Deepak Dixit (JIRA)]

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

Deepak Dixit closed OFBIZ-7269.
---
   Resolution: Fixed
Fix Version/s: 15.12.01
   14.12.01

> Error while importing party
> ---
>
> Key: OFBIZ-7269
> URL: https://issues.apache.org/jira/browse/OFBIZ-7269
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIZ-7269.patch
>
>
> The following errors occurred while importing  party from import/export screen
> https://localhost:8443/partymgr/control/ImportExport
> {quote}
> Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service 
> invocation error (Mapping for midleName not found, expected one of [partyId, 
> preferredCurrencyUomId, groupName, firstName, middleName, lastName, 
> companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId, 
> contactMechTypeId, emailAddress, telCountryCode, telAreaCode, 
> telContactNumber, address1, address2, city, stateProvinceGeoId, postalCode, 
> countryGeoId, ])
> {quote}



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

[jira] [Comment Edited] (OFBIZ-7269) Error while importing party

[Deepak Dixit (JIRA)]

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

Deepak Dixit edited comment on OFBIZ-7269 at 6/12/16 7:11 AM:
--

This has been committed at 

Trunk at r#1747956
15.12 at r#1747957
14.12 at r#1747958
13.07 (feature does not exists)

Thanks Nameet Jain for your contribution.


was (Author: deepak.dixit):
This has been committed at 

Trunk at r#1747956
15.12 at r#1747957
14.12 at r#1747958
13.07 (feature does not exists)

> Error while importing party
> ---
>
> Key: OFBIZ-7269
> URL: https://issues.apache.org/jira/browse/OFBIZ-7269
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIZ-7269.patch
>
>
> The following errors occurred while importing  party from import/export screen
> https://localhost:8443/partymgr/control/ImportExport
> {quote}
> Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service 
> invocation error (Mapping for midleName not found, expected one of [partyId, 
> preferredCurrencyUomId, groupName, firstName, middleName, lastName, 
> companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId, 
> contactMechTypeId, emailAddress, telCountryCode, telAreaCode, 
> telContactNumber, address1, address2, city, stateProvinceGeoId, postalCode, 
> countryGeoId, ])
> {quote}



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

[jira] [Assigned] (OFBIZ-7269) Error while importing party

[Deepak Dixit (JIRA)]

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

Deepak Dixit reassigned OFBIZ-7269:
---

Assignee: Deepak Dixit

> Error while importing party
> ---
>
> Key: OFBIZ-7269
> URL: https://issues.apache.org/jira/browse/OFBIZ-7269
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
> Attachments: OFBIZ-7269.patch
>
>
> The following errors occurred while importing  party from import/export screen
> https://localhost:8443/partymgr/control/ImportExport
> {quote}
> Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service 
> invocation error (Mapping for midleName not found, expected one of [partyId, 
> preferredCurrencyUomId, groupName, firstName, middleName, lastName, 
> companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId, 
> contactMechTypeId, emailAddress, telCountryCode, telAreaCode, 
> telContactNumber, address1, address2, city, stateProvinceGeoId, postalCode, 
> countryGeoId, ])
> {quote}



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

[jira] [Commented] (OFBIZ-7299) Partial shipped orders are getting cancelled using cancel option over order header

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7299:
-

I think we can rename cancel button text in case of partially shipped/received 
orders, we can use "Cancel Remaining Items" instead or "Cancel Order". I think 
its an utility to cancel remaining items.

> Partial shipped orders are getting cancelled using cancel option over order 
> header 
> ---
>
> Key: OFBIZ-7299
> URL: https://issues.apache.org/jira/browse/OFBIZ-7299
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Ankush Upadhyay
>
> Steps to reproduce:
> 1. Place sales order with quantities more than 1.
> 2. Ship few quantities from facility manager.
> 3. Now cancel the order.
> Actual Behaviour:
> - Order gets cancelled, status in OrderHeader change to ORDER_CANCELLED and 
> in OrderItem change to ITEM_CANCELLED.
> Expected result:
> - Order should mark to ORDER_COMPLETED and item should mark to 
> ITEM_COMPLETED, 
> - Remaining quantity (unshipped) should be set in OrderItem.cancelQuantity. 



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

[jira] [Commented] (OFBIZ-7061) Autocompletion for Compound Widget

[james yong (JIRA)]

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

james yong commented on OFBIZ-7061:
---

To make the change at step 5 easier, we can make the namespace schemas be 
accessible from a public URL. 

Examples:
http://ofbiz.apache.org/dtds/simple-methods-ns.xsd
http://ofbiz.apache.org/dtds/site-conf-ns.xsd
http://ofbiz.apache.org/dtds/widget-form-ns.xsd
http://ofbiz.apache.org/dtds/widget-menu-ns.xsd
http://ofbiz.apache.org/dtds/widget-screen-ns.xsd
http://ofbiz.apache.org/dtds/widget-tree-ns.xsd







> Autocompletion for Compound Widget
> --
>
> Key: OFBIZ-7061
> URL: https://issues.apache.org/jira/browse/OFBIZ-7061
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: james yong
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7061.patch, OFBIZ-7061.patch, OFBIZ-7061.patch
>
>
> I am trying to enable auto-completion when coding compound widget.
> My plan as follows:
> 1. The following xsd will be modified to use namespace
> site-conf.xsd
> widget-form.xsd
> widget-screen.xsd
> widget-menu.xsd
> simple-methods.xsd
> For example, in site-conf.xsd, we add the following document level attribute
> {code}
> xmlns="http://ofbiz.apache.org/sc; 
> targetNamespace="http://ofbiz.apache.org/sc;
> {code}
> 2. Import the above schema into compound-widgets.xsd so that compound widgets 
> use only one consolidated schema. 
> 3. Update ExampleCompoundWidgets.xml to use the new compound-widgets.xsd. For 
> example
> {code}
> http://www.w3.org/2001/XMLSchema-instance; 
> xmlns:sc="http://ofbiz.apache.org/sc;
> xmlns:m="http://ofbiz.apache.org/m;
> xmlns:s="http://ofbiz.apache.org/s;
> xmlns:f="http://ofbiz.apache.org/f;
> xmlns:sm="http://ofbiz.apache.org/sm;
> 
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/compound-widgets.xsd;>
> 
> 
> 
>  path="component://example/widget/example/ExampleCompoundWidgets.xml"/>
> 
> 
>  auth="true"/> value="CompoundWidgets2"/>
> 
>  page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets1"/>
>  page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets2"/>
> 
> .. the rest
> {code}
> 4. Change java code to support reading xml with namespace (i.e. xml for 
> compound widgets)
> 5. Update the attributes at document level for rest of the controllers, 
> menus, forms, simple methods and screens. Current setting will not work for 
> schema with a namespace. For example, in controller.xml, we will change 
> {code}
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/site-conf.xsd”
> {code} 
> to 
> {code}
> xmlns="http://ofbiz.apache.org/sc” 
> xsi:schemaLocation="http://ofbiz.apache.org/dtds/site-conf-ns.xsd”>
> {code}



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