[jira] [Assigned] (OFBIZ-6652) Errors in ProductSummary.groovy

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux reassigned OFBIZ-6652:
--

Assignee: Jacques Le Roux

> Errors in ProductSummary.groovy
> ---
>
> Key: OFBIZ-6652
> URL: https://issues.apache.org/jira/browse/OFBIZ-6652
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 12.04, Release Branch 13.07, Release 
> Branch 14.12, Trunk
>Reporter: Oleg Andreyev
>Assignee: Jacques Le Roux
> Attachments: prod_summary_12.diff, prod_summary_13.diff, 
> prod_summary_trunk_14.diff
>
>
> There are a couple of errors in this file. They are not related each to other.
> 1. 12 & 13 use EntityQuery class that is not available in these releases. 
> This cause error in Quick Add screen creating a purchase order.
> 2. In all releases the code in that file try to collect prices for variants. 
> Doing so it use NumberFormat.format() to transform base price into string 
> that is part of an embed JS snippet. In case purchase order this price is 
> rather empty. Using null with formatting method cause error.
> You may see this error in the trunk if you starts PO and and try Browser 
> Categories->Widgets->Small Widgets. This price should appear if you select  
> Select Units of Measure for WG- but currently this does not work.
> I'm not sure these prices make sense for purchase orders but my goal was just 
> fix ugly error message. Solution display N/A if price is not available. 



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

[jira] [Commented] (OFBIZ-6652) Errors in ProductSummary.groovy

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6652:


Thanks Oleg,

For R12 and R13 it was my bad. I just reverted r1639921 and r1639922

I will review the older error later

> Errors in ProductSummary.groovy
> ---
>
> Key: OFBIZ-6652
> URL: https://issues.apache.org/jira/browse/OFBIZ-6652
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 12.04, Release Branch 13.07, Release 
> Branch 14.12, Trunk
>Reporter: Oleg Andreyev
> Attachments: prod_summary_12.diff, prod_summary_13.diff, 
> prod_summary_trunk_14.diff
>
>
> There are a couple of errors in this file. They are not related each to other.
> 1. 12 & 13 use EntityQuery class that is not available in these releases. 
> This cause error in Quick Add screen creating a purchase order.
> 2. In all releases the code in that file try to collect prices for variants. 
> Doing so it use NumberFormat.format() to transform base price into string 
> that is part of an embed JS snippet. In case purchase order this price is 
> rather empty. Using null with formatting method cause error.
> You may see this error in the trunk if you starts PO and and try Browser 
> Categories->Widgets->Small Widgets. This price should appear if you select  
> Select Units of Measure for WG- but currently this does not work.
> I'm not sure these prices make sense for purchase orders but my goal was just 
> fix ugly error message. Solution display N/A if price is not available. 



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

[jira] [Updated] (OFBIZ-6652) Errors in ProductSummary.groovy

2015-09-23 Thread Oleg Andreyev (JIRA) 

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

Oleg Andreyev updated OFBIZ-6652:
-
Attachment: prod_summary_trunk_14.diff
prod_summary_12.diff
prod_summary_13.diff

> Errors in ProductSummary.groovy
> ---
>
> Key: OFBIZ-6652
> URL: https://issues.apache.org/jira/browse/OFBIZ-6652
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 12.04, Release Branch 13.07, Release 
> Branch 14.12, Trunk
>Reporter: Oleg Andreyev
> Attachments: prod_summary_12.diff, prod_summary_13.diff, 
> prod_summary_trunk_14.diff
>
>
> There are a couple of errors in this file. They are not related each to other.
> 1. 12 & 13 use EntityQuery class that is not available in these releases. 
> This cause error in Quick Add screen creating a purchase order.
> 2. In all releases the code in that file try to collect prices for variants. 
> Doing so it use NumberFormat.format() to transform base price into string 
> that is part of an embed JS snippet. In case purchase order this price is 
> rather empty. Using null with formatting method cause error.
> You may see this error in the trunk if you starts PO and and try Browser 
> Categories->Widgets->Small Widgets. This price should appear if you select  
> Select Units of Measure for WG- but currently this does not work.
> I'm not sure these prices make sense for purchase orders but my goal was just 
> fix ugly error message. Solution display N/A if price is not available. 



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

[jira] [Created] (OFBIZ-6652) Errors in ProductSummary.groovy

2015-09-23 Thread Oleg Andreyev (JIRA) 
Oleg Andreyev created OFBIZ-6652:


 Summary: Errors in ProductSummary.groovy
 Key: OFBIZ-6652
 URL: https://issues.apache.org/jira/browse/OFBIZ-6652
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk, Release Branch 14.12, Release Branch 13.07, 
Release Branch 12.04
Reporter: Oleg Andreyev


There are a couple of errors in this file. They are not related each to other.

1. 12 & 13 use EntityQuery class that is not available in these releases. This 
cause error in Quick Add screen creating a purchase order.

2. In all releases the code in that file try to collect prices for variants. 
Doing so it use NumberFormat.format() to transform base price into string that 
is part of an embed JS snippet. In case purchase order this price is rather 
empty. Using null with formatting method cause error.

You may see this error in the trunk if you starts PO and and try Browser 
Categories->Widgets->Small Widgets. This price should appear if you select  
Select Units of Measure for WG- but currently this does not work.

I'm not sure these prices make sense for purchase orders but my goal was just 
fix ugly error message. Solution display N/A if price is not available. 



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

Webinar: This new assessment can improve your application

2015-09-23 Thread Ron Wheeler 


This might provide some interesting ideas for visualization and reporting.

I suspect that it will demonstrate the ideas with Jaspersoft but the 
concepts should be applicable to other technologies.



Ron

 Forwarded Message 

Jaspersoft 


Dear Ron

Chances are your application provides reports or visualizations for end 
users. But, are they good enough? And if you want them to be better, 
what are your choices? This 10-min assessment can help you prepare 
whether to build or buy software that can improve how data is visualized 
and interacted with in your application.


The assessment was developed by Wayne Eckerson (expert BI analyst) using 
responses from over 2,000 software industry professionals. Each 
completed assessment provides a custom set of recommendations that can 
be used to enhance the value of your application and its data. 	






Button2.jpg 




TIBCO Jaspersoft | 350 Rhode Island Street, Suite 250 |
San Francisco, CA 94103
Copyright © 2000-2015 TIBCO Software Inc. All rights reserved
Legal Notices  | 
Policies 




Facebook  		Linkedin 
 		Twitter 
 		YouTube 






This email was sent to rwhee...@artifact-software.com. If you no longer 
wish to receive these emails you may unsubscribe 
 at any time.

[jira] [Commented] (OFBIZ-6495) The tag in view entity PartyExport does not work

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6495:


It's clearer after formatting the SQL requests But then is it only about adding 
the 2 dates fields? Then it would be OK with me :) I'll though then check the 
changes in ModelViewEntity.java are necessary (I guess so ;))

> The tag  in view entity PartyExport does not work
> 
>
> Key: OFBIZ-6495
> URL: https://issues.apache.org/jira/browse/OFBIZ-6495
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Wei Zhang
>Assignee: Jacques Le Roux
> Attachments: patches-6495.zip
>
>
> The tag  in view entity PartyExport in 
> applications\party\entitydef\entitymodel.xml does not work.



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

[jira] [Comment Edited] (OFBIZ-6495) The tag in view entity PartyExport does not work

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux edited comment on OFBIZ-6495 at 9/23/15 1:10 PM:
-

Thanks for your explanation Wei. I tried your suggestion and got

{code}
EntityName: PartyExport SQL:
SELECT PRT.PARTY_ID,
   PRT.STATUS_ID,
   PRT.PREFERRED_CURRE NCY_UOM_ID,
   GRP.GROUP_NAME,
   PER.FIRST_NAME,
   PER.MIDDLE_NAME,
   PER.LAST_NAME,
   PR.PARTY_ID_FROM,
   CGRP.GROUP_NAME,
   PRL.ROLE_TYPE_ID,
   CM.CONTACT_MECH_TYPE_ID,
   PCP.CONTACT_MECH_PURPOSE_TYPE_ID,
   CM.INFO_STRING,
   TN.C OUNTRY_CODE,
   TN.AREA_CODE,
   TN.CONTACT_NUMBER,
   PA.ADDRESS1,
   PA.ADDRESS2,
   PA.CITY,
   PA.STATE_PROVINCE_GEO_ID,
   PA.POSTAL_CODE,
   PA.COUNTRY_GEO_ID
FROM (OFBIZ.PARTY PRT
  LEFT OUTER JOIN OFBIZ.PARTY_GROUP GRP ON PRT.PARTY_ID = 
GRP.PARTY_ID)
 LEFT OUTER JOIN OFBIZ.PERSON PER ON PRT.PARTY_ID = PER.PARTY_ID)
LEFT OUTER JOIN OFBIZ.PARTY_RELATIONSHIP PR ON PRT.PARTY_ID = 
PR.PARTY_ID_TO
AND (PR.ROLE_TYPE_ID_FROM = 'ACCOUNT' AND 
PR.PARTY_RELATIONSHIP_TYPE_ID = 'EMPLOYMENT'))
   LEFT OUTER JOIN OFBIZ.PARTY_GROUP CGRP ON PR.PARTY_ID_FROM = 
CGRP.PARTY_ID)
  LEFT OUTER JOIN OFBIZ.PARTY_ROLE PRL ON PRT.PARTY_ID = PRL.PARTY_ID)
  LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH PCM ON PRT.PARTY_ID = 
PCM.PARTY_ID)
LEFT OUTER JOIN OFBIZ.POSTAL_ADDRESS PA ON PCM.CONTACT_MECH_ID = 
PA.CONTACT_MECH_ID)
   LEFT OUTER JOIN OFBIZ.CONTACT_MECH CM ON PCM.CONTACT_ MECH_ID = 
CM.CONTACT_MECH_ID)
  LEFT OUTER JOIN OFBIZ.TELECOM_NUMBER TN ON PCM.CONTACT_MECH_ID = 
TN.CONTACT_MECH_ID)
LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH_PURPOSE PCP ON PCM.CONTACT_MECH_ID = 
PCP.CONTACT_MEC H_ID
AND PCM.PARTY_ID = PCP.PARTY_ID
WHERE (((PRL.ROLE_TYPE_ID = ?
 OR PRL.ROLE_TYPE_ID = ?
 OR PRL.ROLE_TYPE_ID = ?)
AND (PRT.STATUS_ID <> ?
 OR PRT.STATUS_ID IS NULL)
AND PRT.PARTY_ID = ?))
ORDER BY PRT.PARTY_ ID ASC
WHERE clause:[PRL_ROLE_TYPE_ID=CUSTOMER, PRL_ROLE_TYPE_ID=SUPPLIER, 
PRL_ROLE_TYPE_ID=EMPLOYEE, PRT_STATUS_ID=PARTY_DISABLED, PRT_PARTY_ID=admin]
{code}
before applying your patches and
{code}
EntityName: PartyExport SQL:
SELECT PRT.PARTY_ID,
   PRT.STATUS_ID,
   PRT.PREFERRED_CURRE NCY_UOM_ID,
   GRP.GROUP_NAME,
   PER.FIRST_NAME,
   PER.MIDDLE_NAME,
   PER.LAST_NAME,
   PR.PARTY_ID_FROM,
   CGRP.GROUP_NAME,
   PRL.ROLE_TYPE_ID,
   CM.CONTACT_MECH_TYPE_ID,
   PCP.CONTACT_MECH_PURPOSE_TYPE_ID,
   CM.INFO_STRING,
   TN.C OUNTRY_CODE,
   TN.AREA_CODE,
   TN.CONTACT_NUMBER,
   PA.ADDRESS1,
   PA.ADDRESS2,
   PA.CITY,
   PA.STATE_PROVINCE_GEO_ID,
   PA.POSTAL_CODE,
   PA.COUNTRY_GEO_ID,
   PCM.FROM_DATE,
   PCM.THRU_DATE
FROM (OFBIZ.PARTY PRT
  LEFT OUTER JOIN OFBIZ.PARTY_GROUP GRP ON PRT.PARTY_ID = 
GRP.PARTY_ID)
 LEFT OUTER JOIN OFBIZ.PERSON PER ON PRT.PARTY_ID = PER.PARTY_ID)
LEFT OUTER JOIN OFBIZ.PARTY_RELATIONSHIP PR ON PRT.PARTY_ID = 
PR.PARTY_ID_TO
AND ((PR.ROLE_TYPE_ID_FROM = 'ACCOUNT' AND 
PR.PARTY_RELATIONSHIP_TYPE_ID = 'EMPLOYMENT')))
   LEFT OUTER JOIN OFBIZ.PARTY_GROUP CGRP ON PR.PARTY_ID_FROM = 
CGRP.PARTY_ID)
  LEFT OUTER JOIN OFBIZ.PARTY_ROLE PRL ON PRT. PARTY_ID = PRL.PARTY_ID)
 LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH PCM ON PRT.PARTY_ID = 
PCM.PARTY_ID
 AND (((PCM.THRU_DATE IS NULL
OR PCM.THRU_DATE > '2015-09-23 14:27:04.919')
   AND (PCM.FROM_DATE IS NULL
OR PC M.FROM_DATE <= '2015-09-23 14:27:04.919'
LEFT OUTER JOIN OFBIZ.POSTAL_ADDRESS PA ON PCM.CONTACT_MECH_ID = 
PA.CONTACT_MECH_ID)
   LEFT OUTER JOIN OFBIZ.CONTACT_MECH CM ON PCM.CONTACT_MECH_ID = 
CM.CONTACT_MECH _ID)
  LEFT OUTER JOIN OFBIZ.TELECOM_NUMBER TN ON PCM.CONTACT_MECH_ID = 
TN.CONTACT_MECH_ID)
LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH_PURPOSE PCP ON PCM.CONTACT_MECH_ID = 
PCP.CONTACT_MECH_ID
AND PCM.PARTY_ID = P CP.PARTY_ID
AND (((PCM.THRU_DATE IS NULL
   OR PCM.THRU_DATE > '2015-09-23 14:27:04.919')
  AND (PCM.FROM_DATE IS NULL
   OR PCM.FROM_DATE <= '2015-09-23 14:27:04.919')))
WHERE (((PRL.ROLE_TYPE_ID = ?
 OR PRL.ROLE_TYP E_ID = ?
 OR PRL.ROLE_TYPE_ID = ?)
AND (PRT.STATUS_ID <> ?
 OR PRT.STATUS_ID IS NULL)
AND PRT.PARTY_ID = ?))
ORDER BY PRT.PARTY_ID ASC
WHERE clause:[PRL_ROLE_TYPE_ID=CUSTOMER, PRL_ROLE_TYPE_ID=SUPPLIER, 
PRL_ROLE_TYPE_ID=EMPLOYEE, PRT_STATUS_ID=PARTY_DISABLED, PRT_PARTY_ID=admin]
{code}
after. So yes there is a difference, but it's not obvious to spot whatn and 
especially why "The tag  in view entity PartyEx

[jira] [Comment Edited] (OFBIZ-6495) The tag in view entity PartyExport does not work

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux edited comment on OFBIZ-6495 at 9/23/15 1:04 PM:
-

Thanks for your explanation Wei. I tried your suggestion and got

{code}
EntityName: PartyExport SQL:
SELECT PRT.PARTY_ID,
   PRT.STATUS_ID,
   PRT.PREFERRED_CURRE NCY_UOM_ID,
   GRP.GROUP_NAME,
   PER.FIRST_NAME,
   PER.MIDDLE_NAME,
   PER.LAST_NAME,
   PR.PARTY_ID_FROM,
   CGRP.GROUP_NAME,
   PRL.ROLE_TYPE_ID,
   CM.CONTACT_MECH_TYPE_ID,
   PCP.CONTACT_MECH_PURPOSE_TYPE_ID,
   CM.INFO_STRING,
   TN.C OUNTRY_CODE,
   TN.AREA_CODE,
   TN.CONTACT_NUMBER,
   PA.ADDRESS1,
   PA.ADDRESS2,
   PA.CITY,
   PA.STATE_PROVINCE_GEO_ID,
   PA.POSTAL_CODE,
   PA.COUNTRY_GEO_ID
FROM (OFBIZ.PARTY PRT
  LEFT OUTER JOIN OFBIZ.PARTY_GROUP GRP ON PRT.PARTY_ID = 
GRP.PARTY_ID)
 LEFT OUTER JOIN OFBIZ.PERSON PER ON PRT.PARTY_ID = PER.PARTY_ID)
LEFT OUTER JOIN OFBIZ.PARTY_RELATIONSHIP PR ON PRT.PARTY_ID = 
PR.PARTY_ID_TO
AND (PR.ROLE_TYPE_ID_FROM = 'ACCO
UNT'
 AND PR.PARTY_RELATIONSHIP_TYPE_ID = 'EMPLOYMENT'))
   LEFT OUTER JOIN OFBIZ.PARTY_GROUP CGRP ON PR.PARTY_ID_FROM = 
CGRP.PARTY_ID)
  LEFT OUTER JOIN OFBIZ.PARTY_ROLE PRL ON PRT.PARTY_ID = PRL.PARTY_ID) 
LEFT OU TER
 JOIN OFBIZ.PARTY_CONTACT_MECH PCM ON PRT.PARTY_ID = PCM.PARTY_ID)
LEFT OUTER JOIN OFBIZ.POSTAL_ADDRESS PA ON PCM.CONTACT_MECH_ID = 
PA.CONTACT_MECH_ID)
   LEFT OUTER JOIN OFBIZ.CONTACT_MECH CM ON PCM.CONTACT_ MECH_ID = 
CM.CONTACT_MECH_ID)
  LEFT OUTER JOIN OFBIZ.TELECOM_NUMBER TN ON PCM.CONTACT_MECH_ID = 
TN.CONTACT_MECH_ID)
LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH_PURPOSE PCP ON PCM.CONTACT_MECH_ID = 
PCP.CONTACT_MEC H_ID
AND PCM.PARTY_ID = PCP.PARTY_ID
WHERE (((PRL.ROLE_TYPE_ID = ?
 OR PRL.ROLE_TYPE_ID = ?
 OR PRL.ROLE_TYPE_ID = ?)
AND (PRT.STATUS_ID <> ?
 OR PRT.STATUS_ID IS NULL)
AND PRT.PARTY_ID = ?))
ORDER BY PRT.PARTY_ ID ASC
WHERE clause:[PRL_ROLE_TYPE_ID=CUSTOMER, PRL_ROLE_TYPE_ID=SUPPLIER, 
PRL_ROLE_TYPE_ID=EMPLOYEE, PRT_STATUS_ID=PARTY_DISABLED, PRT_PARTY_ID=admin]
{code}
before applying your patches and
{code}
EntityName: PartyExport SQL:
SELECT PRT.PARTY_ID,
   PRT.STATUS_ID,
   PRT.PREFERRED_CURRE NCY_UOM_ID,
   GRP.GROUP_NAME,
   PER.FIRST_NAME,
   PER.MIDDLE_NAME,
   PER.LAST_NAME,
   PR.PARTY_ID_FROM,
   CGRP.GROUP_NAME,
   PRL.ROLE_TYPE_ID,
   CM.CONTACT_MECH_TYPE_ID,
   PCP.CONTACT_MECH_PURPOSE_TYPE_ID,
   CM.INFO_STRING,
   TN.C OUNTRY_CODE,
   TN.AREA_CODE,
   TN.CONTACT_NUMBER,
   PA.ADDRESS1,
   PA.ADDRESS2,
   PA.CITY,
   PA.STATE_PROVINCE_GEO_ID,
   PA.POSTAL_CODE,
   PA.COUNTRY_GEO_ID,
   PCM.FROM_DATE,
   PCM.THRU_DATE
FROM (OFBIZ.PARTY PRT LEFT OUTER
  JOIN OFBIZ.PARTY_GROUP GRP ON PRT.PARTY_ID = GRP.PARTY_ID)
 LEFT OUTER JOIN OFBIZ.PERSON PER ON PRT.PARTY_ID = PER.PARTY_ID)
LEFT OUTER JOIN OFBIZ.PARTY_RELATIONSHIP PR ON PRT.PARTY_ID = 
PR.PARTY_ID_TO
AND ((PR.ROLE_TYPE_ID_FROM = 'ACCOUNT'
  AND PR.PARTY_RELATIONSHIP_TYPE_ID = 'EMPLOYMENT')))
   LEFT OUTER JOIN OFBIZ.PARTY_GROUP CGRP ON PR.PARTY_ID_FROM = 
CGRP.PARTY_ID)
  LEFT OUTER JOIN OFBIZ.PARTY_ROLE PRL ON PRT. PARTY_ID = PRL.PARTY_ID)
 LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH PCM ON PRT.PARTY_ID = 
PCM.PARTY_ID
 AND (((PCM.THRU_DATE IS NULL
OR PCM.THRU_DATE > '2015-09-23 14:27:04.919')
   AND (PCM.FROM_DATE IS NULL
OR PC M.FROM_DATE <= '2015-09-23 14:27:04.919'
LEFT OUTER JOIN OFBIZ.POSTAL_ADDRESS PA ON PCM.CONTACT_MECH_ID = 
PA.CONTACT_MECH_ID)
   LEFT OUTER JOIN OFBIZ.CONTACT_MECH CM ON PCM.CONTACT_MECH_ID = 
CM.CONTACT_MECH _ID)
  LEFT OUTER JOIN OFBIZ.TELECOM_NUMBER TN ON PCM.CONTACT_MECH_ID = 
TN.CONTACT_MECH_ID)
LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH_PURPOSE PCP ON PCM.CONTACT_MECH_ID = 
PCP.CONTACT_MECH_ID
AND PCM.PARTY_ID = P CP.PARTY_ID
AND (((PCM.THRU_DATE IS NULL
   OR PCM.THRU_DATE > '2015-09-23 14:27:04.919')
  AND (PCM.FROM_DATE IS NULL
   OR PCM.FROM_DATE <= '2015-09-23 14:27:04.919')))
WHERE (((PRL.ROLE_TYPE_ID = ?
 OR PRL.ROLE_TYP E_ID = ?
 OR PRL.ROLE_TYPE_ID = ?)
AND (PRT.STATUS_ID <> ?
 OR PRT.STATUS_ID IS NULL)
AND PRT.PARTY_ID = ?))
ORDER BY PRT.PARTY_ID ASC
WHERE clause:[PRL_ROLE_TYPE_ID=CUSTOMER, PRL_ROLE_TYPE_ID=SUPPLIER, PRL_ROL
E_TYPE_ID=EMPLOYEE, PRT_STATUS_ID=PARTY_DISABLED, PRT_PARTY_ID=admin]{code}
after. So yes there is a difference, but it's not obvious to spot whatn and 
especially why

[jira] [Commented] (OFBIZ-6495) The tag in view entity PartyExport does not work

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6495:


Thanks for your explanation Wei. I tried your suggestion and got

{code}
EntityName: PartyExport Sql: SELECT PRT.PARTY_ID, PRT.STATUS_ID, 
PRT.PREFERRED_CURRE
NCY_UOM_ID, GRP.GROUP_NAME, PER.FIRST_NAME, PER.MIDDLE_NAME, PER.LAST_NAME, 
PR.PARTY_ID_FROM, CGRP.GROUP_NAME, PRL.ROLE_TYPE_ID, CM.CONTACT_MECH_TYPE_ID, 
PCP.CONTACT_MECH_PURPOSE_TYPE_ID, CM.INFO_STRING, TN.C
OUNTRY_CODE, TN.AREA_CODE, TN.CONTACT_NUMBER, PA.ADDRESS1, PA.ADDRESS2, 
PA.CITY, PA.STATE_PROVINCE_GEO_ID, PA.POSTAL_CODE, PA.COUNTRY_GEO_ID FROM 
(OFBIZ.PARTY PRT LEFT OUTER JOIN OFBIZ.PARTY_GROUP GRP
 ON PRT.PARTY_ID = GRP.PARTY_ID) LEFT OUTER JOIN OFBIZ.PERSON PER ON 
PRT.PARTY_ID = PER.PARTY_ID) LEFT OUTER JOIN OFBIZ.PARTY_RELATIONSHIP PR ON 
PRT.PARTY_ID = PR.PARTY_ID_TO AND (PR.ROLE_TYPE_ID_FROM = 'ACCO
UNT' AND PR.PARTY_RELATIONSHIP_TYPE_ID = 'EMPLOYMENT')) LEFT OUTER JOIN 
OFBIZ.PARTY_GROUP CGRP ON PR.PARTY_ID_FROM = CGRP.PARTY_ID) LEFT OUTER JOIN 
OFBIZ.PARTY_ROLE PRL ON PRT.PARTY_ID = PRL.PARTY_ID) LEFT OU
TER JOIN OFBIZ.PARTY_CONTACT_MECH PCM ON PRT.PARTY_ID = PCM.PARTY_ID) LEFT 
OUTER JOIN OFBIZ.POSTAL_ADDRESS PA ON PCM.CONTACT_MECH_ID = PA.CONTACT_MECH_ID) 
LEFT OUTER JOIN OFBIZ.CONTACT_MECH CM ON PCM.CONTACT_
MECH_ID = CM.CONTACT_MECH_ID) LEFT OUTER JOIN OFBIZ.TELECOM_NUMBER TN ON 
PCM.CONTACT_MECH_ID = TN.CONTACT_MECH_ID) LEFT OUTER JOIN 
OFBIZ.PARTY_CONTACT_MECH_PURPOSE PCP ON PCM.CONTACT_MECH_ID = PCP.CONTACT_MEC
H_ID AND PCM.PARTY_ID = PCP.PARTY_ID WHERE (((PRL.ROLE_TYPE_ID = ? OR 
PRL.ROLE_TYPE_ID = ? OR PRL.ROLE_TYPE_ID = ?) AND (PRT.STATUS_ID <> ? OR 
PRT.STATUS_ID IS NULL) AND PRT.PARTY_ID = ?)) ORDER BY PRT.PARTY_
ID ASC where clause:[PRL_ROLE_TYPE_ID=CUSTOMER, PRL_ROLE_TYPE_ID=SUPPLIER, 
PRL_ROLE_TYPE_ID=EMPLOYEE, PRT_STATUS_ID=PARTY_DISABLED, PRT_PARTY_ID=admin]
{code}
before applying your patches and
{code}
EntityName: PartyExport Sql: SELECT PRT.PARTY_ID, PRT.STATUS_ID, 
PRT.PREFERRED_CURRE
NCY_UOM_ID, GRP.GROUP_NAME, PER.FIRST_NAME, PER.MIDDLE_NAME, PER.LAST_NAME, 
PR.PARTY_ID_FROM, CGRP.GROUP_NAME, PRL.ROLE_TYPE_ID, CM.CONTACT_MECH_TYPE_ID, 
PCP.CONTACT_MECH_PURPOSE_TYPE_ID, CM.INFO_STRING, TN.C
OUNTRY_CODE, TN.AREA_CODE, TN.CONTACT_NUMBER, PA.ADDRESS1, PA.ADDRESS2, 
PA.CITY, PA.STATE_PROVINCE_GEO_ID, PA.POSTAL_CODE, PA.COUNTRY_GEO_ID, 
PCM.FROM_DATE, PCM.THRU_DATE FROM (OFBIZ.PARTY PRT LEFT OU
TER JOIN OFBIZ.PARTY_GROUP GRP ON PRT.PARTY_ID = GRP.PARTY_ID) LEFT OUTER JOIN 
OFBIZ.PERSON PER ON PRT.PARTY_ID = PER.PARTY_ID) LEFT OUTER JOIN 
OFBIZ.PARTY_RELATIONSHIP PR ON PRT.PARTY_ID = PR.PARTY_ID_TO AND
 ((PR.ROLE_TYPE_ID_FROM = 'ACCOUNT' AND PR.PARTY_RELATIONSHIP_TYPE_ID = 
'EMPLOYMENT'))) LEFT OUTER JOIN OFBIZ.PARTY_GROUP CGRP ON PR.PARTY_ID_FROM = 
CGRP.PARTY_ID) LEFT OUTER JOIN OFBIZ.PARTY_ROLE PRL ON PRT.
PARTY_ID = PRL.PARTY_ID) LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH PCM ON 
PRT.PARTY_ID = PCM.PARTY_ID AND (((PCM.THRU_DATE IS NULL OR PCM.THRU_DATE > 
'2015-09-23 14:27:04.919') AND (PCM.FROM_DATE IS NULL OR PC
M.FROM_DATE <= '2015-09-23 14:27:04.919' LEFT OUTER JOIN 
OFBIZ.POSTAL_ADDRESS PA ON PCM.CONTACT_MECH_ID = PA.CONTACT_MECH_ID) LEFT OUTER 
JOIN OFBIZ.CONTACT_MECH CM ON PCM.CONTACT_MECH_ID = CM.CONTACT_MECH
_ID) LEFT OUTER JOIN OFBIZ.TELECOM_NUMBER TN ON PCM.CONTACT_MECH_ID = 
TN.CONTACT_MECH_ID) LEFT OUTER JOIN OFBIZ.PARTY_CONTACT_MECH_PURPOSE PCP ON 
PCM.CONTACT_MECH_ID = PCP.CONTACT_MECH_ID AND PCM.PARTY_ID = P
CP.PARTY_ID AND (((PCM.THRU_DATE IS NULL OR PCM.THRU_DATE > '2015-09-23 
14:27:04.919') AND (PCM.FROM_DATE IS NULL OR PCM.FROM_DATE <= '2015-09-23 
14:27:04.919'))) WHERE (((PRL.ROLE_TYPE_ID = ? OR PRL.ROLE_TYP
E_ID = ? OR PRL.ROLE_TYPE_ID = ?) AND (PRT.STATUS_ID <> ? OR PRT.STATUS_ID IS 
NULL) AND PRT.PARTY_ID = ?)) ORDER BY PRT.PARTY_ID ASC where 
clause:[PRL_ROLE_TYPE_ID=CUSTOMER, PRL_ROLE_TYPE_ID=SUPPLIER, PRL_ROL
E_TYPE_ID=EMPLOYEE, PRT_STATUS_ID=PARTY_DISABLED, PRT_PARTY_ID=admin]
{code}
after. So yes there is a difference, but it's not obvious to spot whatn and 
especially why "The tag  in view entity PartyExport 
does not work". Because the result is the same in both cases (exportParty.csv):
{code}
partyId,"preferredCurrencyUomId","groupName","firstName","middleName","lastName","companyPartyId","companyName","roleTypeId","contactMechPurposeTypeId","contactMechTypeId","emailAddress","telCountryCode","telAreaCode","telContactNumber","address1","address2","city","stateProvinceGeoId","postalCode","countryGeoId",
{code}

Could you please give me some light about what you are doing and why? Thanks!

BTW I tried only the export, were you concerned by the import?

> The tag  in view entity PartyExport does not work
> 
>
> Key: OFBIZ-6495

Re: ModelEntity was null for related entity name Tenant

2015-09-23 Thread Jacques Le Roux 

Thanks Pierre,

Does this means that it only happens when you set multitenant=Y in general.properties? I guess not because it's not my case, what else? Or did I 
misunderstood?


Jacques

Le 23/09/2015 10:50, Pierre Smits a écrit :

Hi Jacques,

This happens when the tenant* entities are accessed while the use has
logged  in at  tenant  level (delegator has a tenantId). The tenant*
entities are only accessible when delegator="default". When a user is
logged in at tenant level the delegator has an extension
(delegator="default#".

Best regards,

Pierre Smits

*OFBiz Extensions Marketplace*
http://oem.ofbizci.net

On Wed, Sep 23, 2015 at 10:36 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi,

Nobody has an idea about this error message?

 DatabaseUtil  |E| Error adding foreign key:
ModelEntity was null for related entity name Tenant

Jacques

[jira] [Comment Edited] (OFBIZ-6651) Remove deprecated methods from GenericValue and EntityUtil classes

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux edited comment on OFBIZ-6651 at 9/23/15 10:28 AM:
--

I guess so, nobody's perfect ;)


was (Author: jacques.le.roux):
I guess so ;)

> Remove deprecated methods from  GenericValue and EntityUtil classes
> ---
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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

[jira] [Commented] (OFBIZ-6651) Remove deprecated methods from GenericValue and EntityUtil classes

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6651:


I guess so ;)

> Remove deprecated methods from  GenericValue and EntityUtil classes
> ---
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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

[jira] [Commented] (OFBIZ-6651) Remove deprecated methods from GenericValue and EntityUtil classes

2015-09-23 Thread Martin Becker (JIRA) 

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

Martin Becker commented on OFBIZ-6651:
--

Oh yes, I see, sorry. Maybe I should have used the full text search by my own 
when I build the fix for OFBIZ-6276 a few month ago...

> Remove deprecated methods from  GenericValue and EntityUtil classes
> ---
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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

[jira] [Commented] (OFBIZ-293) data import - nulling fields impossible

2015-09-23 Thread Martin Becker (JIRA) 

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

Martin Becker commented on OFBIZ-293:
-

The use of the xsi:nil attribute is basically correct but is no solution for 
the problem we have to represent NULL values in XML element attributes, used 
for entity attributes. As I see, the xsi:nil attribute is only for defining a 
XML element as NULL, in our use case the entity itself.

My thought was to improve the current logic without compromising current legacy 
data and usage. For now, empty string attribute values are ignored when loading 
XML entity data, that is just not correct. If we treat them as empty string, 
what would be the most correct solution, we not really gain a functional 
benefit but need to fix existing entity data files with for example 
...parentTypeId=""... in it.

For a full update while syncing data over the entity xml mechanism, the current 
solution with an additional specified action like "REPLACE" meets the 
requirements and the "XML Standard" by interpreting missing entity field (xml 
attributes) as NULL values. 

The gap I want to fill is the default action for loading entity XML data, where 
only explicitly defined fields are part of an update and there should be the 
possibility to "clear" single field values. There should only be very rare 
cases where someone would want to define and insert empty strings instead of 
NULL. Not even the current logic support this.

> data import - nulling fields impossible
> ---
>
> Key: OFBIZ-293
> URL: https://issues.apache.org/jira/browse/OFBIZ-293
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Marco Risaliti
>Priority: Minor
> Attachments: OFBIZ-293_set-empty-strings-as-null.patch, 
> ofbiz-293-patch.txt, ofbiz-462-patch.txt
>
>
> It's a copy of the old-jira issue 
> http://jira.undersunconsulting.com/browse/OFBIZ-462 Tarlika Elisabeth Schmitz
> =
> I am on rev 5274. 
> data import from .xml file: empty attributes (e.g. description="") are 
> ignored and the field retains its former value. 
> Comment by Chris Juettner [04/Oct/05 01:51 PM]
> This patch comments out the check for null or empty values in the data XML 
> file found by the EntitySaxReader. I also added an additional warning message 
> in case you do not want to persist empty values to the database but still 
> would like to know what happened. 
> Comment by Si Chen [04/Oct/05 01:59 PM]
> Chris- 
> Just a comment: it's very important that a field in the entity engine is set 
> to null ONLY when the XML file specifically has an empty attribute (ie, 
> description=""). Otherwise, there's a lot of seed data that is in separate 
> XML files, and they could overwrite each other. 
> Comment by Chris Juettner [10/Oct/05 11:56 AM] [ Permlink ] 
> Si, 
> I'm not sure I understand your comment about seed data in seperate XML files 
> overwriting each other. Shouldn't seed data XML files be entity specific? Why 
> would one seed data XML file overwrite another? 
> Do you have any comment on what a better solution is for seed data values 
> that could be empty? 
> Thanks 
> Chris 



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

Re: ModelEntity was null for related entity name Tenant

2015-09-23 Thread Pierre Smits 
Hi Jacques,

This happens when the tenant* entities are accessed while the use has
logged  in at  tenant  level (delegator has a tenantId). The tenant*
entities are only accessible when delegator="default". When a user is
logged in at tenant level the delegator has an extension
(delegator="default#".

Best regards,

Pierre Smits

*OFBiz Extensions Marketplace*
http://oem.ofbizci.net

On Wed, Sep 23, 2015 at 10:36 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi,
>
> Nobody has an idea about this error message?
>
> DatabaseUtil  |E| Error adding foreign key:
> ModelEntity was null for related entity name Tenant
>
> Jacques
>

[jira] [Commented] (OFBIZ-6636) Certain temporal expressions are not evaluated correctly

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6636:


I put a "relate to" link

> Certain temporal expressions are not evaluated correctly
> 
>
> Key: OFBIZ-6636
> URL: https://issues.apache.org/jira/browse/OFBIZ-6636
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Vyom Jain
>
> Related to User ML post 
> http://mail-archives.apache.org/mod_mbox/ofbiz-user/201509.mbox/%3CCAKuEJqY2Qyv6-7rb_cQ7OnGqoaDsSXdde4E3F1DDt=dcz93...@mail.gmail.com%3E.
> There are couple of bugs in temporal expressions (see OFBIZ-6632) and after 
> various tests my conclusion is that at least HOUR_RANGE is not evaluated 
> properly.
> For example, if there's a requirement to schedule recurring job from Monday 
> to Friday and during certain hours then that no longer works as expected 
> (this used to work with TIME_OF_DAY_RANGE which was removed in subsequent 
> code refactoring). Even DAILY_GRIND in demo data doesn't schedule new jobs.



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

ModelEntity was null for related entity name Tenant

2015-09-23 Thread Jacques Le Roux 

Hi,

Nobody has an idea about this error message?

DatabaseUtil  |E| Error adding foreign key: ModelEntity was 
null for related entity name Tenant

Jacques

[jira] [Commented] (OFBIZ-6636) Certain temporal expressions are not evaluated correctly

2015-09-23 Thread Gil Portenseigne (JIRA) 

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

Gil Portenseigne commented on OFBIZ-6636:
-

Yeah same subject, in fact this bug lead to discover an infinite loop error, 
causing OFBIZ-6637 creation

> Certain temporal expressions are not evaluated correctly
> 
>
> Key: OFBIZ-6636
> URL: https://issues.apache.org/jira/browse/OFBIZ-6636
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Vyom Jain
>
> Related to User ML post 
> http://mail-archives.apache.org/mod_mbox/ofbiz-user/201509.mbox/%3CCAKuEJqY2Qyv6-7rb_cQ7OnGqoaDsSXdde4E3F1DDt=dcz93...@mail.gmail.com%3E.
> There are couple of bugs in temporal expressions (see OFBIZ-6632) and after 
> various tests my conclusion is that at least HOUR_RANGE is not evaluated 
> properly.
> For example, if there's a requirement to schedule recurring job from Monday 
> to Friday and during certain hours then that no longer works as expected 
> (this used to work with TIME_OF_DAY_RANGE which was removed in subsequent 
> code refactoring). Even DAILY_GRIND in demo data doesn't schedule new jobs.



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

[jira] [Issue Comment Deleted] (OFBIZ-5579) Error when add product to an order.

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

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

(was: I have already casted my vote. I will not do more.)

> Error when add product to an order.
> ---
>
> Key: OFBIZ-5579
> URL: https://issues.apache.org/jira/browse/OFBIZ-5579
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: nguyenthang
>Assignee: Divesh Dutta
>
> Flow:
> 1. Create Sales Order with default option (store - OFBiz - Ecommerce store; 
> No channel; user login ID: admin)
> 2. Continue with default option of Currency, Agreements, and Ship Dates.
> 3. Select product for this order (Ex: Forklift - Propane)
> 4. Click add to order
> --> Error:
> Forklift - Propane Powered.
> FORKLIFT_PROPANE
> Your Price: $0.00
> {code}
> Maximum Expression product.reservMaxPersons is undefined on line 364, column 
> 190 in component://order/webapp/ordermgr/entry/catalog/productdetail.ftl. The 
> problematic instruction: -- ==> ${product.reservMaxPersons} [on line 
> 364, column 188 in 
> component://order/webapp/ordermgr/entry/catalog/productdetail.ftl] -- 
> Java backtrace for programmers: -- 
> freemarker.core.InvalidReferenceException: Expression 
> product.reservMaxPersons is undefined on line 364, column 190 in 
> component://order/webapp/ordermgr/entry/catalog/productdetail.ftl. at 
> freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:125) at 
> freemarker.core.Expression.getStringValue(Expression.java:118) at 
> freemarker.core.Expression.getStringValue(Expression.java:93) at 
> freemarker.core.DollarVariable.accept(DollarVariable.java:76) at 
> freemarker.core.Environment.visit(Environment.java:221) at 
> freemarker.core.MixedContent.accept(MixedContent.java:92) at 
> freemarker.core.Environment.visit(Environment.java:221) at 
> freemarker.core.ConditionalBlock.accept(ConditionalBlock.java:79) at 
> freemarker.core.Environment.visit(Environment.java:221) at 
> freemarker.core.MixedContent.accept(MixedContent.java:92) at 
> freemarker.core.Environment.visit(Environment.java:221) at 
> freemarker.core.ConditionalBlock.accept(ConditionalBlock.java:79) at 
> freemarker.core.Environment.visit(Environment.java:221) at 
> freemarker.core.MixedContent.accept(MixedContent.java:92) at 
> freemarker.core.Environment.visit(Environment.java:221) at 
> freemarker.core.Environment.process(Environment.java:199) at 
> org.ofbiz.base.util.template.FreeMarkerWorker.renderTemplate(FreeMarkerWorker.java:251)
>  at 
> org.ofbiz.widget.screen.HtmlWidget.renderHtmlTemplate(HtmlWidget.java:224) at 
> org.ofbiz.widget.screen.HtmlWidget$HtmlTemplate.renderWidgetString(HtmlWidget.java:269)
>  at 
> org.ofbiz.widget.screen.HtmlWidget.renderWidgetString(HtmlWidget.java:129) at 
> org.ofbiz.widget.screen.ModelScreenWidget$PlatformSpecific.renderWidgetString(ModelScreenWidget.java:988)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:102)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:189)
>  at 
> org.ofbiz.widget.screen.ModelScreen.renderScreenString(ModelScreen.java:396) 
> at 
> org.ofbiz.widget.screen.ScreenFactory.renderReferencedScreen(ScreenFactory.java:216)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$IncludeScreen.renderWidgetString(ModelScreenWidget.java:596)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:102)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:189)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:102)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$DecoratorSection.renderWidgetString(ModelScreenWidget.java:696)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$SectionsRenderer.render(ModelScreenWidget.java:127)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$DecoratorSectionInclude.renderWidgetString(ModelScreenWidget.java:729)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:102)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$Container.renderWidgetString(ModelScreenWidget.java:331)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:102)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$Container.renderWidgetString(ModelScreenWidget.java:331)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:102)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:189)
>  at 
> org.ofbiz.widget.screen.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:102)
>  at 
> org.o

[jira] [Updated] (OFBIZ-6651) Remove deprecated methods from GenericValue and EntityUtil classes

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux updated OFBIZ-6651:
---
Issue Type: Sub-task  (was: Task)
Parent: OFBIZ-6275

> Remove deprecated methods from  GenericValue and EntityUtil classes
> ---
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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

[jira] [Comment Edited] (OFBIZ-6636) Certain temporal expressions are not evaluated correctly

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux edited comment on OFBIZ-6636 at 9/23/15 8:24 AM:
-

Does this not relate with OFBIZ-6637 ? Maybe even a duplicate (kinda)


was (Author: jacques.le.roux):
Does this not relate with OFBIZ-6637 ?

> Certain temporal expressions are not evaluated correctly
> 
>
> Key: OFBIZ-6636
> URL: https://issues.apache.org/jira/browse/OFBIZ-6636
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Vyom Jain
>
> Related to User ML post 
> http://mail-archives.apache.org/mod_mbox/ofbiz-user/201509.mbox/%3CCAKuEJqY2Qyv6-7rb_cQ7OnGqoaDsSXdde4E3F1DDt=dcz93...@mail.gmail.com%3E.
> There are couple of bugs in temporal expressions (see OFBIZ-6632) and after 
> various tests my conclusion is that at least HOUR_RANGE is not evaluated 
> properly.
> For example, if there's a requirement to schedule recurring job from Monday 
> to Friday and during certain hours then that no longer works as expected 
> (this used to work with TIME_OF_DAY_RANGE which was removed in subsequent 
> code refactoring). Even DAILY_GRIND in demo data doesn't schedule new jobs.



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

[jira] [Commented] (OFBIZ-6636) Certain temporal expressions are not evaluated correctly

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6636:


Does this not relate with OFBIZ-6637 ?

> Certain temporal expressions are not evaluated correctly
> 
>
> Key: OFBIZ-6636
> URL: https://issues.apache.org/jira/browse/OFBIZ-6636
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Vyom Jain
>
> Related to User ML post 
> http://mail-archives.apache.org/mod_mbox/ofbiz-user/201509.mbox/%3CCAKuEJqY2Qyv6-7rb_cQ7OnGqoaDsSXdde4E3F1DDt=dcz93...@mail.gmail.com%3E.
> There are couple of bugs in temporal expressions (see OFBIZ-6632) and after 
> various tests my conclusion is that at least HOUR_RANGE is not evaluated 
> properly.
> For example, if there's a requirement to schedule recurring job from Monday 
> to Friday and during certain hours then that no longer works as expected 
> (this used to work with TIME_OF_DAY_RANGE which was removed in subsequent 
> code refactoring). Even DAILY_GRIND in demo data doesn't schedule new jobs.



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

[jira] [Commented] (OFBIZ-6627) multiple select dropdown listbox shows only one entry

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6627:


Yes that would be better indeed...

> multiple select dropdown listbox shows only one entry
> -
>
> Key: OFBIZ-6627
> URL: https://issues.apache.org/jira/browse/OFBIZ-6627
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
>
> Attachments: OFBIZ-6627.patch
>
>
> Use this link https://localhost:8443/ordermgr/control/FindRequest
> Notice the customer request type id, status id, etc



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

[jira] [Updated] (OFBIZ-6651) Remove deprecated methods from GenericValue and EntityUtil classes

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux updated OFBIZ-6651:
---
Summary: Remove deprecated methods from  GenericValue and EntityUtil 
classes  (was: Remove deprecated methods from GenericValue class)

> Remove deprecated methods from  GenericValue and EntityUtil classes
> ---
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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

[jira] [Commented] (OFBIZ-6651) Remove deprecated methods from GenericValue class

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6651:


Hi Martin,

Did not see your comments (Jira should push updates when you have the issue 
opened), but that's actually what I did at r1704769. It's more complicated for 
getRelated (980 occurences) and getRelatedOne (726 occurences). I did it by 
hand yesterday after OFBIZ-6276, that gave me some thoughts...

> Remove deprecated methods from GenericValue class
> -
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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

[jira] [Assigned] (OFBIZ-6651) Remove deprecated methods from GenericValue class

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux reassigned OFBIZ-6651:
--

Assignee: Jacques Le Roux

> Remove deprecated methods from GenericValue class
> -
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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

[jira] [Commented] (OFBIZ-6651) Remove deprecated methods from GenericValue class

2015-09-23 Thread Martin Becker (JIRA) 

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

Martin Becker commented on OFBIZ-6651:
--

Why not just using the full text search for finding occurrences in templates, 
screen-definitions and scripts?

> Remove deprecated methods from GenericValue class
> -
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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

[jira] [Commented] (OFBIZ-6627) multiple select dropdown listbox shows only one entry

2015-09-23 Thread Gil Portenseigne (JIRA) 

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

Gil Portenseigne commented on OFBIZ-6627:
-

Thanks, i was just wondering if it could be a good improvement to get asm 
multiple dropdown replacing the current multiple implementation, instead of 
using ftl ?

> multiple select dropdown listbox shows only one entry
> -
>
> Key: OFBIZ-6627
> URL: https://issues.apache.org/jira/browse/OFBIZ-6627
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
>
> Attachments: OFBIZ-6627.patch
>
>
> Use this link https://localhost:8443/ordermgr/control/FindRequest
> Notice the customer request type id, status id, etc



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

[jira] [Commented] (OFBIZ-6637) Work Effort Month Calendar View Is Broken

2015-09-23 Thread Gil Portenseigne (JIRA) 

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

Gil Portenseigne commented on OFBIZ-6637:
-

My pleasure ! ;)

> Work Effort Month Calendar View Is Broken
> -
>
> Key: OFBIZ-6637
> URL: https://issues.apache.org/jira/browse/OFBIZ-6637
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: Upcoming Branch
>Reporter: Adrian Crum
>Assignee: Gil Portenseigne
> Attachments: OFBIZ-6637.patch
>
>
> The Work Effort Month calendar view does not work. The screen does not 
> display:
> https://localhost:8443/workeffort/control/calendar?period=month
> and CPU utilization remains high. It appears to be in an endless loop.



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

[jira] [Commented] (OFBIZ-6651) Remove deprecated methods from GenericValue class

2015-09-23 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6651:


OK good news point 1 is done: there are no deprecated methods from GenericValue 
class used in OFBiz OOTB Java code. I will do point 2 right away

> Remove deprecated methods from GenericValue class
> -
>
> Key: OFBIZ-6651
> URL: https://issues.apache.org/jira/browse/OFBIZ-6651
> Project: OFBiz
>  Issue Type: Task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Strategy:
> # Using an IDE replace the deprecated methods in Java code (but not in 
> GenericValue class)
> # Before removing the deprecated methods from GenericValue class, place 
> {code}
> Debug.logWarning("deprecated 'methodName', please replace them, see 
> OFBIZ-6651", new Exception()); 
> {code}
> in them. On the long run, this will allow to spot where these methods are 
> used in templates and scripts and replace them



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