[jira] [Updated] (OFBIZ-7093) Remaining quantity should be ZERO for completed order items

[Akash Jain (JIRA)]

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

Akash Jain updated OFBIZ-7093:
--
Attachment: Remaining.png

> Remaining quantity should be ZERO for completed order items
> ---
>
> Key: OFBIZ-7093
> URL: https://issues.apache.org/jira/browse/OFBIZ-7093
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 14.12, Trunk
>Reporter: Akash Jain
>Priority: Minor
> Fix For: Release Branch 14.12, Trunk
>
> Attachments: Remaining.png
>
>
> There are the steps:
> -- Initiate sales order.
> -- Add service product (ex. sv-1000) in the cart
> -- Place order and mark approved.
> -- Order item of service product will be completed but Remaining quantity 
> still ONE (attaching screen-shot).
> Expected Result:
> -- Order item of service product should be completed (working)
> -- Remaining quantity should be ZERO (need to fix)



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

[jira] [Updated] (OFBIZ-7092) Backordered flag should not be shown for service product

[Akash Jain (JIRA)]

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

Akash Jain updated OFBIZ-7092:
--
Component/s: order

> Backordered flag should not be shown for service product
> 
>
> Key: OFBIZ-7092
> URL: https://issues.apache.org/jira/browse/OFBIZ-7092
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk
>Reporter: Akash Jain
>Priority: Minor
> Fix For: Trunk
>
> Attachments: Backordered.png
>
>
> These are the steps:
> -- Initiate sales order.
> -- Add service product (ex. sv-1000) in the cart
> Backordered flag (attached screen-shot) should not be shown for service 
> product.



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

[jira] [Created] (OFBIZ-7094) While creating inventory item of type "SERIALIZED_INV_ITEM" in "INV_ON_HOLD" status it gets created in "INV_AVAILABLE" status

[Aditi Patidar (JIRA)]

Aditi Patidar created OFBIZ-7094:


 Summary: While creating inventory item of type 
"SERIALIZED_INV_ITEM" in "INV_ON_HOLD" status it gets created in 
"INV_AVAILABLE" status
 Key: OFBIZ-7094
 URL: https://issues.apache.org/jira/browse/OFBIZ-7094
 Project: OFBiz
  Issue Type: Bug
  Components: product
Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12
Reporter: Aditi Patidar
Assignee: Aditi Patidar


Use Case:  When we create a serialized inventory item and the serial number is 
not provided, it should be created in "INV_ON_HOLD" status to exclude this item 
from being count in ATP.

As per the current implementation in service receiveInventoryProduct if status 
provided is "INV_ON_HOLD" for inventory item of type "SERIALIZED_INV_ITEM" it 
should not update to "INV_AVAILABLE" but it's not working expectedly. Here is 
the logic to check for the same:

{code}
























 





{code}



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

[jira] [Assigned] (OFBIZ-6364) Viewing party content should open in a new window

[Deepak Dixit (JIRA)]

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

Deepak Dixit reassigned OFBIZ-6364:
---

Assignee: Deepak Dixit

> Viewing party content should open in a new window
> -
>
> Key: OFBIZ-6364
> URL: https://issues.apache.org/jira/browse/OFBIZ-6364
> Project: OFBiz
>  Issue Type: Improvement
>  Components: party
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Deepak Dixit
> Attachments: OFBIZ-6364.patch
>
>
> Currently, when the user clicks on the 'view' button to view the content in a 
> party profile the item is shown in the same screen. However, for a better ux 
> this should open in a new window.



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

[jira] [Created] (OFBIZ-7093) Remaining quantity should be ZERO for completed order items

[Akash Jain (JIRA)]

Akash Jain created OFBIZ-7093:
-

 Summary: Remaining quantity should be ZERO for completed order 
items
 Key: OFBIZ-7093
 URL: https://issues.apache.org/jira/browse/OFBIZ-7093
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk, Release Branch 14.12
Reporter: Akash Jain
Priority: Minor
 Fix For: Trunk, Release Branch 14.12


There are the steps:
-- Initiate sales order.
-- Add service product (ex. sv-1000) in the cart
-- Place order and mark approved.
-- Order item of service product will be completed but Remaining quantity still 
ONE (attaching screen-shot).

Expected Result:
-- Order item of service product should be completed (working)
-- Remaining quantity should be ZERO (need to fix)



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

[jira] [Updated] (OFBIZ-7092) Backordered flag should not be shown for service product

[Akash Jain (JIRA)]

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

Akash Jain updated OFBIZ-7092:
--
Description: 
These are the steps:
-- Initiate sales order.
-- Add service product (ex. sv-1000) in the cart

Backordered flag (attached screen-shot) should not be shown for service product.



  was:
These are the steps:
-- Initiate sales order.
-- Add service product (ex. sv-1000) in the cart

Backordered flag should not be shown for service product.




> Backordered flag should not be shown for service product
> 
>
> Key: OFBIZ-7092
> URL: https://issues.apache.org/jira/browse/OFBIZ-7092
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Akash Jain
>Priority: Minor
> Fix For: Trunk
>
> Attachments: Backordered.png
>
>
> These are the steps:
> -- Initiate sales order.
> -- Add service product (ex. sv-1000) in the cart
> Backordered flag (attached screen-shot) should not be shown for service 
> product.



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

[jira] [Updated] (OFBIZ-7092) Backordered flag should not be shown for service product

[Akash Jain (JIRA)]

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

Akash Jain updated OFBIZ-7092:
--
Attachment: Backordered.png

> Backordered flag should not be shown for service product
> 
>
> Key: OFBIZ-7092
> URL: https://issues.apache.org/jira/browse/OFBIZ-7092
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Akash Jain
>Priority: Minor
> Fix For: Trunk
>
> Attachments: Backordered.png
>
>
> These are the steps:
> -- Initiate sales order.
> -- Add service product (ex. sv-1000) in the cart
> Backordered flag should not be shown for service product.



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

[jira] [Updated] (OFBIZ-7085) WorkEffort Reviews list does not show any record

[Pranay Pandey (JIRA)]

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

Pranay Pandey updated OFBIZ-7085:
-
Summary: WorkEffort Reviews list does not show any record  (was: WorkEffort 
Reviews list does not show any record.)

> WorkEffort Reviews list does not show any record
> 
>
> Key: OFBIZ-7085
> URL: https://issues.apache.org/jira/browse/OFBIZ-7085
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Pranay Pandey
> Attachments: OFBIZ-7085.patch
>
>
> Steps to regenerate the issue:
> 1. Go to WorkEffort's Review page- 
> https://localhost:8443/workeffort/control/EditWorkEffortReviews?workEffortId=9002
> 2. Add one review, still review list does not show any review.



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

[jira] [Created] (OFBIZ-7092) Backordered flag should not be shown for service product

[Akash Jain (JIRA)]

Akash Jain created OFBIZ-7092:
-

 Summary: Backordered flag should not be shown for service product
 Key: OFBIZ-7092
 URL: https://issues.apache.org/jira/browse/OFBIZ-7092
 Project: OFBiz
  Issue Type: Improvement
Affects Versions: Trunk
Reporter: Akash Jain
Priority: Minor
 Fix For: Trunk


These are the steps:
-- Initiate sales order.
-- Add service product (ex. sv-1000) in the cart

Backordered flag should not be shown for service product.





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

[jira] [Updated] (OFBIZ-7091) Two empty options are shown in shipping method select box on Edit promo screen

[Swapnil M Mane (JIRA)]

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

Swapnil M Mane updated OFBIZ-7091:
--
Description: 
On Edit promo screen, in existing condition section's select box two empty 
options are shown.
Please find the screenshot for more detail.

Reason and Solution:
As per the code in EditProductPromoRules.ftl,

{code}
${carrierParty!}${description}
{code}

And the carrierParty is calculated above, if it is not available the first 
option will show automatically as empty option

{code}
${carrierParty!}${description}
{code}

So, we don't need the second empty option field and can remove it.
{code}

{code}

  was:
On Edit promo screen, in existing condition section's select box two empty 
options are shown.
Please find the screenshot for more detail.

Reason and Solution:
As per the code in EditProductPromoRules.ftl,

{code}
${carrierParty!}${description}
{code}

And the carrierParty is calculated above, if it is not available the first 
option will show automatically as empty option

{code}
${carrierParty!}${description}
{code}

So, we don't need the section option empty option field and can remove it.
{code}

{code}


> Two empty options are shown in shipping method select box on Edit promo screen
> --
>
> Key: OFBIZ-7091
> URL: https://issues.apache.org/jira/browse/OFBIZ-7091
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Affects Versions: Trunk
>Reporter: Swapnil M Mane
>Assignee: Pranay Pandey
>Priority: Trivial
> Attachments: EditProductPromoRules.png, OFBIZ-7091.patch
>
>
> On Edit promo screen, in existing condition section's select box two empty 
> options are shown.
> Please find the screenshot for more detail.
> Reason and Solution:
> As per the code in EditProductPromoRules.ftl,
> {code}
>  "${carrierShippingMethod!}">${carrierParty!}${description} 
> {code}
> And the carrierParty is calculated above, if it is not available the first 
> option will show automatically as empty option
> {code}
>  "${carrierShippingMethod!}">${carrierParty!}${description}
> {code}
> So, we don't need the second empty option field and can remove it.
> {code}
> 
> {code}



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

[jira] [Updated] (OFBIZ-7091) Two empty options are shown in shipping method select box on Edit promo screen

[Swapnil M Mane (JIRA)]

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

Swapnil M Mane updated OFBIZ-7091:
--
Attachment: OFBIZ-7091.patch

> Two empty options are shown in shipping method select box on Edit promo screen
> --
>
> Key: OFBIZ-7091
> URL: https://issues.apache.org/jira/browse/OFBIZ-7091
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Affects Versions: Trunk
>Reporter: Swapnil M Mane
>Assignee: Pranay Pandey
>Priority: Trivial
> Attachments: EditProductPromoRules.png, OFBIZ-7091.patch
>
>
> On Edit promo screen, in existing condition section's select box two empty 
> options are shown.
> Please find the screenshot for more detail.
> Reason and Solution:
> As per the code in EditProductPromoRules.ftl,
> {code}
>  "${carrierShippingMethod!}">${carrierParty!}${description} 
> {code}
> And the carrierParty is calculated above, if it is not available the first 
> option will show automatically as empty option
> {code}
>  "${carrierShippingMethod!}">${carrierParty!}${description}
> {code}
> So, we don't need the section option empty option field and can remove it.
> {code}
> 
> {code}



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

[jira] [Updated] (OFBIZ-7090) Return Pdf is throwing exception

[Avnindra Sharma (JIRA)]

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

Avnindra Sharma updated OFBIZ-7090:
---
Attachment: screenshot-1.png

> Return Pdf is throwing exception
> 
>
> Key: OFBIZ-7090
> URL: https://issues.apache.org/jira/browse/OFBIZ-7090
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Priority: Blocker
> Attachments: screenshot-1.png
>
>




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

[jira] [Updated] (OFBIZ-7091) Two empty options are shown in shipping method select box on Edit promo screen

[Swapnil M Mane (JIRA)]

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

Swapnil M Mane updated OFBIZ-7091:
--
Attachment: EditProductPromoRules.png

> Two empty options are shown in shipping method select box on Edit promo screen
> --
>
> Key: OFBIZ-7091
> URL: https://issues.apache.org/jira/browse/OFBIZ-7091
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Affects Versions: Trunk
>Reporter: Swapnil M Mane
>Assignee: Pranay Pandey
>Priority: Trivial
> Attachments: EditProductPromoRules.png
>
>
> On Edit promo screen, in existing condition section's select box two empty 
> options are shown.
> Please find the screenshot for more detail.
> Reason and Solution:
> As per the code in EditProductPromoRules.ftl,
> {code}
>  "${carrierShippingMethod!}">${carrierParty!}${description} 
> {code}
> And the carrierParty is calculated above, if it is not available the first 
> option will show automatically as empty option
> {code}
>  "${carrierShippingMethod!}">${carrierParty!}${description}
> {code}
> So, we don't need the section option empty option field and can remove it.
> {code}
> 
> {code}



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

[jira] [Created] (OFBIZ-7091) Two empty options are shown in shipping method select box on Edit promo screen

[Swapnil M Mane (JIRA)]

Swapnil M Mane created OFBIZ-7091:
-

 Summary: Two empty options are shown in shipping method select box 
on Edit promo screen
 Key: OFBIZ-7091
 URL: https://issues.apache.org/jira/browse/OFBIZ-7091
 Project: OFBiz
  Issue Type: Improvement
  Components: product
Affects Versions: Trunk
Reporter: Swapnil M Mane
Assignee: Pranay Pandey
Priority: Trivial


On Edit promo screen, in existing condition section's select box two empty 
options are shown.
Please find the screenshot for more detail.

Reason and Solution:
As per the code in EditProductPromoRules.ftl,

{code}
${carrierParty!}${description}
{code}

And the carrierParty is calculated above, if it is not available the first 
option will show automatically as empty option

{code}
${carrierParty!}${description}
{code}

So, we don't need the section option empty option field and can remove it.
{code}

{code}



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

[jira] [Closed] (OFBIZ-7086) Employee position's responsibility update gives error

[Pranay Pandey (JIRA)]

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

Pranay Pandey closed OFBIZ-7086.

   Resolution: Fixed
Fix Version/s: 13.07.04
   15.12.01
   Upcoming Branch
   14.12.01

> Employee position's responsibility update gives error
> -
>
> Key: OFBIZ-7086
> URL: https://issues.apache.org/jira/browse/OFBIZ-7086
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Pranay Pandey
> Fix For: 14.12.01, Upcoming Branch, 15.12.01, 13.07.04
>
> Attachments: OFBIZ-7086-Releases.patch, OFBIZ-7086-Screenshot.png, 
> OFBIZ-7086-trunk.patch
>
>
> Steps to regenerate:
> 1. Go to 
> https://localhost:8443/humanres/control/EditEmplPositionResponsibilities?emplPositionId=DEMO100
> 2. Add one responsibility.
> 3. On update the responsibility, getting error.
> Please find attached screenshot of error.



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

[jira] [Commented] (OFBIZ-7086) Employee position's responsibility update gives error

[Pranay Pandey (JIRA)]

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

Pranay Pandey commented on OFBIZ-7086:
--

Done in Trunk at r1744829, R15.12 at r1744830, R14.12 at r1744831 and R13.07 at 
r1744832.

Thanks Amardeep Singh Jhajj for reporting the issue and providing the patch.

> Employee position's responsibility update gives error
> -
>
> Key: OFBIZ-7086
> URL: https://issues.apache.org/jira/browse/OFBIZ-7086
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Pranay Pandey
> Attachments: OFBIZ-7086-Releases.patch, OFBIZ-7086-Screenshot.png, 
> OFBIZ-7086-trunk.patch
>
>
> Steps to regenerate:
> 1. Go to 
> https://localhost:8443/humanres/control/EditEmplPositionResponsibilities?emplPositionId=DEMO100
> 2. Add one responsibility.
> 3. On update the responsibility, getting error.
> Please find attached screenshot of error.



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

[jira] [Updated] (OFBIZ-7090) Return Pdf is throwing exception

[Nameet Jain (JIRA)]

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

Nameet Jain updated OFBIZ-7090:
---
Summary: Return Pdf is throwing exception  (was: Return Pdf is throwing 
exception.)

> Return Pdf is throwing exception
> 
>
> Key: OFBIZ-7090
> URL: https://issues.apache.org/jira/browse/OFBIZ-7090
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Priority: Blocker
>




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

[jira] [Commented] (OFBIZ-7078) Extend OrderAdjustment entity and add isManual field

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7078:
-

This an improvement but I think we can backport these changes to 15.12, 14.12 
and 13.07 as well.

> Extend OrderAdjustment entity and add isManual field
> 
>
> Key: OFBIZ-7078
> URL: https://issues.apache.org/jira/browse/OFBIZ-7078
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7078.patch
>
>
> Extend OrderAdjustment entity and add isManual field to recognize manually 
> added order adjustment.   
> As per current implementation code using orderAdjustment.comments field to 
> recognize manually added comment using string "Added manually by"
> {code}
> if ( adjustment.get("comments") != null
> && 
> ((String)adjustment.get("comments")).startsWith("Added manually by")) {
> cart.addAdjustment(adjustment);
> }
> {code}



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

[jira] [Created] (OFBIZ-7090) Return Pdf is throwing exception.

[Nameet Jain (JIRA)]

Nameet Jain created OFBIZ-7090:
--

 Summary: Return Pdf is throwing exception.
 Key: OFBIZ-7090
 URL: https://issues.apache.org/jira/browse/OFBIZ-7090
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Nameet Jain
Priority: Blocker






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

[jira] [Updated] (OFBIZ-7088) Balance Sheet Screen is broken

[Nameet Jain (JIRA)]

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

Nameet Jain updated OFBIZ-7088:
---
Summary: Balance Sheet Screen is broken  (was: Balance Sheet Screen is 
broken.)

> Balance Sheet Screen is broken
> --
>
> Key: OFBIZ-7088
> URL: https://issues.apache.org/jira/browse/OFBIZ-7088
> Project: OFBiz
>  Issue Type: Bug
>  Components: accounting
>Reporter: Nameet Jain
>Priority: Critical
>
> Console Logs
>  [java] 2016-05-21 09:24:44,989 |http-nio-8443-exec-7 |EntityExpr 
>|W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr 
> =-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value 
> passed in [java.sql.Date] is not compatible with the Java type of the field 
> [java.sql.Timestamp]



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

[jira] [Updated] (OFBIZ-6364) Viewing party content should open in a new window

[Renuka Srishti (JIRA)]

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

Renuka Srishti updated OFBIZ-6364:
--
Attachment: OFBIZ-6364.patch

Here is the patch for this issue.

> Viewing party content should open in a new window
> -
>
> Key: OFBIZ-6364
> URL: https://issues.apache.org/jira/browse/OFBIZ-6364
> Project: OFBiz
>  Issue Type: Improvement
>  Components: party
>Affects Versions: Trunk
>Reporter: Pierre Smits
> Attachments: OFBIZ-6364.patch
>
>
> Currently, when the user clicks on the 'view' button to view the content in a 
> party profile the item is shown in the same screen. However, for a better ux 
> this should open in a new window.



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

Re: OFBiz Committers Survey

[Ashish Vijaywargiya]

Done, Thanks Sharan!

On Thu, May 19, 2016 at 6:54 PM, Sharan-F  wrote:

> Hi Everyone
>
> I've sent out the survey today so all our committers (including emeritus
> and
> inactive) should get an email with a link to it.
> I'll plan to keep the survey open for 7 days (less if I get all the
> responses back beforehand!) to give people enough time to complete it.
>
> Thanks in advance for your feedback.
>
> Thanks
> Sharan
>
>
>
>
> --
> View this message in context:
> http://ofbiz.135035.n4.nabble.com/OFBiz-Committers-Survey-tp4680727p4680804.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>

[jira] [Assigned] (OFBIZ-7088) Balance Sheet Screen is broken

[Deepak Dixit (JIRA)]

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

Deepak Dixit reassigned OFBIZ-7088:
---

Assignee: Deepak Dixit

> Balance Sheet Screen is broken
> --
>
> Key: OFBIZ-7088
> URL: https://issues.apache.org/jira/browse/OFBIZ-7088
> Project: OFBiz
>  Issue Type: Bug
>  Components: accounting
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
>Priority: Critical
>
> Console Logs
>  [java] 2016-05-21 09:24:44,989 |http-nio-8443-exec-7 |EntityExpr 
>|W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr 
> =-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value 
> passed in [java.sql.Date] is not compatible with the Java type of the field 
> [java.sql.Timestamp]



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

[jira] [Assigned] (OFBIZ-7002) Images are not rendered in content

[Mohammed Rehan Khan (JIRA)]

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

Mohammed Rehan Khan reassigned OFBIZ-7002:
--

Assignee: Mohammed Rehan Khan

> Images are not rendered in content
> --
>
> Key: OFBIZ-7002
> URL: https://issues.apache.org/jira/browse/OFBIZ-7002
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 12.04, Release Branch 13.07, Release 
> Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Jacques Le Roux
>Assignee: Mohammed Rehan Khan
>
> When you get to content/control/WebSiteCms?webSiteId=CmsSite and add a new 
> image in the tree, it's no rendered. Same at 
> {code}
> content/control/EditLayout?drDataResourceId=NOCONTENTFOUND=NOCONTENTFOUND
> {code}



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

[jira] [Assigned] (OFBIZ-7000) You cannot edit an image in content

[Mohammed Rehan Khan (JIRA)]

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

Mohammed Rehan Khan reassigned OFBIZ-7000:
--

Assignee: Mohammed Rehan Khan

> You cannot edit an image in content
> ---
>
> Key: OFBIZ-7000
> URL: https://issues.apache.org/jira/browse/OFBIZ-7000
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 12.04, Release Branch 13.07, Release 
> Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Jacques Le Roux
>Assignee: Mohammed Rehan Khan
>Priority: Minor
>
> If you get to 
> {code}
> content/control/EditLayout?drDataResourceId=NOCONTENTFOUND=NOCONTENTFOUND
> {code}
> When trying to editing you get an error
> {code}
> 2016-04-11 10:48:42,932 |http-bio-8443-exec-9 |ScreenFactory 
> |I| Got 9 screens in 0.004s from: 
> file:/C:/projectASF-Mars/ofbiz/applications/content/widget/layout/LayoutScreens.xml
> 2016-04-11 10:48:43,051 |http-bio-8443-exec-9 |ScriptUtil
> |W| Error running script at location 
> [component://content/webapp/content/WEB-INF/actions/layout/EditSubContent.groovy]:
>  org.ofbiz.b
> ase.util.GeneralException: The desired mime-type is not a text type, cannot 
> render as text: image/png
> org.ofbiz.base.util.GeneralException: The desired mime-type is not a text 
> type, cannot render as text: image/png
> at 
> org.ofbiz.content.data.DataResourceWorker.renderDataResourceAsText(DataResourceWorker.java:624)
>  ~[ofbiz-content.jar:?]
> at 
> org.ofbiz.content.data.DataResourceWorker.renderDataResourceAsText(DataResourceWorker.java:603)
>  ~[ofbiz-content.jar:?]
> at 
> org.ofbiz.content.data.DataResourceWorker$renderDataResourceAsText.call(Unknown
>  Source) ~[?:?]
> at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
>  ~[groovy-all-2.4.5.jar:2.4.5]
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
>  ~[groovy-all-2.4.5.jar:2.4.5]
> at EditSubContent.run(EditSubContent.groovy:50) ~[?:?]
> {code}



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

[jira] [Updated] (OFBIZ-7086) Employee position's responsibility update gives error

[Pranay Pandey (JIRA)]

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

Pranay Pandey updated OFBIZ-7086:
-
Affects Version/s: Release Branch 13.07
   Release Branch 14.12
   Release Branch 15.12

> Employee position's responsibility update gives error
> -
>
> Key: OFBIZ-7086
> URL: https://issues.apache.org/jira/browse/OFBIZ-7086
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Pranay Pandey
> Attachments: OFBIZ-7086-Releases.patch, OFBIZ-7086-Screenshot.png, 
> OFBIZ-7086-trunk.patch
>
>
> Steps to regenerate:
> 1. Go to 
> https://localhost:8443/humanres/control/EditEmplPositionResponsibilities?emplPositionId=DEMO100
> 2. Add one responsibility.
> 3. On update the responsibility, getting error.
> Please find attached screenshot of error.



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

Re: JIRA Ticket for Documentation Effort

[Ashish Vijaywargiya]

+1

Thanks,
Ashish

On Sat, May 21, 2016 at 10:29 AM, Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

> Hi Community,
>
> What do you think of this option, should we create a Ticket in JIRA for any
> of the documentation effort?
>
> I am going to start work on OFBiz Beginners Tutorial overhaul(Will create a
> new one and open it for review to the community for feedback) and was
> thinking to map the effort with a JIRA Ticket. Please let me know your
> thoughts.
>
>
>
> Best regards,
>
> Pranay Pandey
> HotWax Systems
> http://www.hotwaxsystems.com/
>

JIRA Ticket for Documentation Effort

[Pranay Pandey]

Hi Community,

What do you think of this option, should we create a Ticket in JIRA for any
of the documentation effort?

I am going to start work on OFBiz Beginners Tutorial overhaul(Will create a
new one and open it for review to the community for feedback) and was
thinking to map the effort with a JIRA Ticket. Please let me know your
thoughts.



Best regards,

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

[jira] [Updated] (OFBIZ-7087) Material/Component requirement is not available for 'Confirmed' Production Runs

[Swapnil Shah (JIRA)]

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

Swapnil Shah updated OFBIZ-7087:

Attachment: Unconfirmed_PR_1.png
Confirmed_PR_1.png

> Material/Component requirement is not available for 'Confirmed' Production 
> Runs
> ---
>
> Key: OFBIZ-7087
> URL: https://issues.apache.org/jira/browse/OFBIZ-7087
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Reporter: Swapnil Shah
> Attachments: Confirmed_PR_1.png, Unconfirmed_PR_1.png
>
>
> All the material/component requirements are rightly visible as soon as any 
> production run gets created but once its Confirmed then there is no way to 
> see the specific material/components that are required for any task from any 
> tab/screen against the given production run (even its not listed on Actual 
> Material screen)
> To begin with, let's add back the same 'Material' section (as visible for any 
> Created/Scheduled production runs) just below the production run task section 
> listing task-wise component requirement along with respective quantity



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

[jira] [Updated] (OFBIZ-7085) WorkEffort Reviews list does not show any record.

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7085:

Assignee: Pranay Pandey  (was: Amardeep Singh Jhajj)

> WorkEffort Reviews list does not show any record.
> -
>
> Key: OFBIZ-7085
> URL: https://issues.apache.org/jira/browse/OFBIZ-7085
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Pranay Pandey
> Attachments: OFBIZ-7085.patch
>
>
> Steps to regenerate the issue:
> 1. Go to WorkEffort's Review page- 
> https://localhost:8443/workeffort/control/EditWorkEffortReviews?workEffortId=9002
> 2. Add one review, still review list does not show any review.



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

[jira] [Updated] (OFBIZ-7086) Employee position's responsibility update gives error

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7086:

Assignee: Pranay Pandey  (was: Amardeep Singh Jhajj)

> Employee position's responsibility update gives error
> -
>
> Key: OFBIZ-7086
> URL: https://issues.apache.org/jira/browse/OFBIZ-7086
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Amardeep Singh Jhajj
>Assignee: Pranay Pandey
> Attachments: OFBIZ-7086-Releases.patch, OFBIZ-7086-Screenshot.png, 
> OFBIZ-7086-trunk.patch
>
>
> Steps to regenerate:
> 1. Go to 
> https://localhost:8443/humanres/control/EditEmplPositionResponsibilities?emplPositionId=DEMO100
> 2. Add one responsibility.
> 3. On update the responsibility, getting error.
> Please find attached screenshot of error.



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

[jira] [Commented] (OFBIZ-7086) Employee position's responsibility update gives error

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj commented on OFBIZ-7086:
-

Please find attached patch for Release 13.07, 14.12, 15.12 and trunk. Thanks.

> Employee position's responsibility update gives error
> -
>
> Key: OFBIZ-7086
> URL: https://issues.apache.org/jira/browse/OFBIZ-7086
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7086-Releases.patch, OFBIZ-7086-Screenshot.png, 
> OFBIZ-7086-trunk.patch
>
>
> Steps to regenerate:
> 1. Go to 
> https://localhost:8443/humanres/control/EditEmplPositionResponsibilities?emplPositionId=DEMO100
> 2. Add one responsibility.
> 3. On update the responsibility, getting error.
> Please find attached screenshot of error.



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

[jira] [Updated] (OFBIZ-7086) Employee position's responsibility update gives error

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7086:

Attachment: OFBIZ-7086-Releases.patch
OFBIZ-7086-trunk.patch

> Employee position's responsibility update gives error
> -
>
> Key: OFBIZ-7086
> URL: https://issues.apache.org/jira/browse/OFBIZ-7086
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7086-Releases.patch, OFBIZ-7086-Screenshot.png, 
> OFBIZ-7086-trunk.patch
>
>
> Steps to regenerate:
> 1. Go to 
> https://localhost:8443/humanres/control/EditEmplPositionResponsibilities?emplPositionId=DEMO100
> 2. Add one responsibility.
> 3. On update the responsibility, getting error.
> Please find attached screenshot of error.



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

[jira] [Commented] (OFBIZ-7081) Error on Edit Credit Card page

[Ashish Vijaywargiya (JIRA)]

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

Ashish Vijaywargiya commented on OFBIZ-7081:


Thanks Jacques for taking care of this issue.

> Error on Edit Credit Card page
> --
>
> Key: OFBIZ-7081
> URL: https://issues.apache.org/jira/browse/OFBIZ-7081
> Project: OFBiz
>  Issue Type: Bug
>  Components: order, party
>Affects Versions: Release Branch 13.07
>Reporter: Ravi Lodhi
>Assignee: Jacques Le Roux
> Fix For: 13.07.04
>
>
> Step to regenerate (create a new order):
> 1) Start placing a new order from 
> http://demo-stable-ofbiz.apache.org/ordermgr/control/orderentry
> 2) Add products and click on "Finalize Order" button and continue till the 
> Order Entry Payment Settings screen.
> 3) From the listed method go to edit credit card (e.g. CC: CCT_VISA) by 
> clicking update button.
> 4) See the Card Type drop down having only one option and see the FreeMarker 
> template error.
> Root Cause:
> CcTypes.groovy file is missing.



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

[jira] [Created] (OFBIZ-7089) Cash Flow Statement report is broken

[Nameet Jain (JIRA)]

Nameet Jain created OFBIZ-7089:
--

 Summary: Cash Flow Statement report is broken
 Key: OFBIZ-7089
 URL: https://issues.apache.org/jira/browse/OFBIZ-7089
 Project: OFBiz
  Issue Type: Bug
  Components: accounting
Affects Versions: Trunk
Reporter: Nameet Jain


Console Logs:

 [java] 2016-05-21 09:52:55,079 |http-nio-8443-exec-5 |EntityExpr   
 |W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr 
=-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value 
passed in [java.sql.Date] is not compatible with the Java type of the field 
[java.sql.Timestamp]
 [java] java.lang.Exception: Location of database type warning



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

[jira] [Commented] (OFBIZ-7072) DataResource.dataResourceName field should be at least 255 Chars

[Ashish Vijaywargiya (JIRA)]

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

Ashish Vijaywargiya commented on OFBIZ-7072:


I will back port this changes to all the recent branches.

> DataResource.dataResourceName field should be at least 255 Chars
> 
>
> Key: OFBIZ-7072
> URL: https://issues.apache.org/jira/browse/OFBIZ-7072
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Release 
> Branch 15.12
>Reporter: Forrest Rae
>Assignee: Ashish Vijaywargiya
> Attachments: OFBIZ-7072.patch
>
>
> Most major operating systems limit the length of a file name to 255 chars.  
> When sending an email with file attachments, the attachments get saved as 
> DataResources associated with a CommunicationEvent, with the filename being 
> saved in the DataResource.dataResourceName field.  Currently, this field is 
> set to name, which is limited to 100 chars.  These two limitations don't add 
> up, and the field should be increased to 255 chars.



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

[jira] [Created] (OFBIZ-7088) Balance Sheet Screen is broken.

[Nameet Jain (JIRA)]

Nameet Jain created OFBIZ-7088:
--

 Summary: Balance Sheet Screen is broken.
 Key: OFBIZ-7088
 URL: https://issues.apache.org/jira/browse/OFBIZ-7088
 Project: OFBiz
  Issue Type: Bug
  Components: accounting
Reporter: Nameet Jain
Priority: Critical


Console Logs

 [java] 2016-05-21 09:24:44,989 |http-nio-8443-exec-7 |EntityExpr   
 |W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr 
=-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value 
passed in [java.sql.Date] is not compatible with the Java type of the field 
[java.sql.Timestamp]



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

[jira] [Created] (OFBIZ-7087) Material/Component requirement is not available for 'Confirmed' Production Runs

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7087:
---

 Summary: Material/Component requirement is not available for 
'Confirmed' Production Runs
 Key: OFBIZ-7087
 URL: https://issues.apache.org/jira/browse/OFBIZ-7087
 Project: OFBiz
  Issue Type: Improvement
  Components: manufacturing
Reporter: Swapnil Shah


All the material/component requirements are rightly visible as soon as any 
production run gets created but once its Confirmed then there is no way to see 
the specific material/components that are required for any task from any 
tab/screen against the given production run (even its not listed on Actual 
Material screen)

To begin with, let's add back the same 'Material' section (as visible for any 
Created/Scheduled production runs) just below the production run task section 
listing task-wise component requirement along with respective quantity



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

[jira] [Updated] (OFBIZ-7086) Employee position's responsibility update gives error

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7086:

Attachment: OFBIZ-7086-Screenshot.png

> Employee position's responsibility update gives error
> -
>
> Key: OFBIZ-7086
> URL: https://issues.apache.org/jira/browse/OFBIZ-7086
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7086-Screenshot.png
>
>
> Steps to regenerate:
> 1. Go to 
> https://localhost:8443/humanres/control/EditEmplPositionResponsibilities?emplPositionId=DEMO100
> 2. Add one responsibility.
> 3. On update the responsibility, getting error.
> Please find attached screenshot of error.



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

[jira] [Created] (OFBIZ-7086) Employee position's responsibility update gives error

[Amardeep Singh Jhajj (JIRA)]

Amardeep Singh Jhajj created OFBIZ-7086:
---

 Summary: Employee position's responsibility update gives error
 Key: OFBIZ-7086
 URL: https://issues.apache.org/jira/browse/OFBIZ-7086
 Project: OFBiz
  Issue Type: Bug
Affects Versions: Trunk
Reporter: Amardeep Singh Jhajj
Assignee: Amardeep Singh Jhajj


Steps to regenerate:

1. Go to 
https://localhost:8443/humanres/control/EditEmplPositionResponsibilities?emplPositionId=DEMO100

2. Add one responsibility.

3. On update the responsibility, getting error.

Please find attached screenshot of error.



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

[jira] [Commented] (OFBIZ-7085) WorkEffort Reviews list does not show any record.

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj commented on OFBIZ-7085:
-

Please find attached patch for Release 13.07, 14.12, 15.12 and trunk. Thanks.

> WorkEffort Reviews list does not show any record.
> -
>
> Key: OFBIZ-7085
> URL: https://issues.apache.org/jira/browse/OFBIZ-7085
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7085.patch
>
>
> Steps to regenerate the issue:
> 1. Go to WorkEffort's Review page- 
> https://localhost:8443/workeffort/control/EditWorkEffortReviews?workEffortId=9002
> 2. Add one review, still review list does not show any review.



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

[jira] [Updated] (OFBIZ-7085) WorkEffort Reviews list does not show any record.

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7085:

Attachment: OFBIZ-7085.patch

> WorkEffort Reviews list does not show any record.
> -
>
> Key: OFBIZ-7085
> URL: https://issues.apache.org/jira/browse/OFBIZ-7085
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7085.patch
>
>
> Steps to regenerate the issue:
> 1. Go to WorkEffort's Review page- 
> https://localhost:8443/workeffort/control/EditWorkEffortReviews?workEffortId=9002
> 2. Add one review, still review list does not show any review.



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

[jira] [Created] (OFBIZ-7085) WorkEffort Reviews list does not show any record.

[Amardeep Singh Jhajj (JIRA)]

Amardeep Singh Jhajj created OFBIZ-7085:
---

 Summary: WorkEffort Reviews list does not show any record.
 Key: OFBIZ-7085
 URL: https://issues.apache.org/jira/browse/OFBIZ-7085
 Project: OFBiz
  Issue Type: Bug
  Components: workeffort
Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12, 
Release Branch 13.07
Reporter: Amardeep Singh Jhajj
Assignee: Amardeep Singh Jhajj


Steps to regenerate the issue:

1. Go to WorkEffort's Review page- 
https://localhost:8443/workeffort/control/EditWorkEffortReviews?workEffortId=9002

2. Add one review, still review list does not show any review.



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

[jira] [Updated] (OFBIZ-6783) Refactor the start component

[Taher Alkhateeb (JIRA)]

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

Taher Alkhateeb updated OFBIZ-6783:
---
Attachment: OFBIZ-6783.patch

This is a new big patch, and all tests run from my side. I made big changes and 
appreciate your feedback. What I've done is the following:

- separate the AdminPortThread into a new class
- delete CommonsDaemonStart
- refactor everything so that all dependencies between classes are explicit 
through function calls (no hidden state or declarations)
- move all the server processing logic (status, shutdown, start ...) to a new 
class called StartupControlPanel. All methods in this class are static with 
side effects only limited to the arguments passed to them.
- add a few missing apache copyright headers
- refactoring some names to make them clearer

I know this is a big scary patch. But it makes reasoning about the code easier, 
and the next step is to fully refactor StartupControlPanel.start(...) to make 
it clean and efficient. But the main benefit of this patch is tangling all the 
dependency mess that used to exist.

I look forward to hearing from you on this.

> Refactor the start component
> 
>
> Key: OFBIZ-6783
> URL: https://issues.apache.org/jira/browse/OFBIZ-6783
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>  Labels: framework, main, refactoring, start
> Attachments: OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, 
> OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, 
> OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, StartCommandUtil.java
>
>
> Looking at the main method and design of Start.java and the start component 
> overall looks ugly. The things I would like to fix so far are:
> - the files are too long
> - some variables are not even needed (loaderArgs?)
> - the level of abstraction is wrong
> - main throws an exception!
> - the arguments processing logic is terrible, need to move it to commons-cli
> It's just so messy and ugly to look at. So for me refactoring starts at 
> Start! Given that this is an important component, I will provide a patch to 
> be reviewed by the community before committing just to be on the safe side.



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

Changing the core API design

[Taher Alkhateeb]

Hey everyone,

So I’ve been digging into the code for kickstarting ofbiz and I think it
has design flaws. For example the whole logic around StartupLoader.java
seems to introduce too many levels of indirection just to serve one thing
which is the POS component.

There are unnecessary locks, highly indirect code, and java classes that
should not even exist in base. I think a simple process was made overly
complicated (and as a side effect also slow).

I would like to bounce off a few ideas with anyone experienced in this area
on some design changes. This would be things like:
- eliminating or substantially changing the StartupLoader
- changing the implementation of the AdminPortThread
- better utilization of java.util.concurrent for some areas
- doing something about the POS component, perhaps even removing it, I mean
it depends on XUI, omg! A web solution might be a much better fit

Is anyone interested in working on this? already working on this? or think
I'm going in the right direction? I'd love to hear some thoughts or even
chat up on IRC or something.

I appreciate hearing your thoughts.

Taher Alkhateeb

[jira] [Commented] (OFBIZ-7072) DataResource.dataResourceName field should be at least 255 Chars

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-7072:


"most of the field definitions" is not a comprehensible definition :p or at 
least it's not actionnable, see?

> DataResource.dataResourceName field should be at least 255 Chars
> 
>
> Key: OFBIZ-7072
> URL: https://issues.apache.org/jira/browse/OFBIZ-7072
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Release 
> Branch 15.12
>Reporter: Forrest Rae
>Assignee: Ashish Vijaywargiya
> Attachments: OFBIZ-7072.patch
>
>
> Most major operating systems limit the length of a file name to 255 chars.  
> When sending an email with file attachments, the attachments get saved as 
> DataResources associated with a CommunicationEvent, with the filename being 
> saved in the DataResource.dataResourceName field.  Currently, this field is 
> set to name, which is limited to 100 chars.  These two limitations don't add 
> up, and the field should be increased to 255 chars.



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

[jira] [Commented] (OFBIZ-7072) DataResource.dataResourceName field should be at least 255 Chars

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-7072:


Good point Pierre!

> DataResource.dataResourceName field should be at least 255 Chars
> 
>
> Key: OFBIZ-7072
> URL: https://issues.apache.org/jira/browse/OFBIZ-7072
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Release 
> Branch 15.12
>Reporter: Forrest Rae
>Assignee: Ashish Vijaywargiya
> Attachments: OFBIZ-7072.patch
>
>
> Most major operating systems limit the length of a file name to 255 chars.  
> When sending an email with file attachments, the attachments get saved as 
> DataResources associated with a CommunicationEvent, with the filename being 
> saved in the DataResource.dataResourceName field.  Currently, this field is 
> set to name, which is limited to 100 chars.  These two limitations don't add 
> up, and the field should be increased to 255 chars.



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

[jira] [Commented] (OFBIZ-7072) DataResource.dataResourceName field should be at least 255 Chars

[Pierre Smits (JIRA)]

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

Pierre Smits commented on OFBIZ-7072:
-

If this is a bug, then I suggest to include the error thrown in this issue. 

> DataResource.dataResourceName field should be at least 255 Chars
> 
>
> Key: OFBIZ-7072
> URL: https://issues.apache.org/jira/browse/OFBIZ-7072
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Release 
> Branch 15.12
>Reporter: Forrest Rae
>Assignee: Ashish Vijaywargiya
> Attachments: OFBIZ-7072.patch
>
>
> Most major operating systems limit the length of a file name to 255 chars.  
> When sending an email with file attachments, the attachments get saved as 
> DataResources associated with a CommunicationEvent, with the filename being 
> saved in the DataResource.dataResourceName field.  Currently, this field is 
> set to name, which is limited to 100 chars.  These two limitations don't add 
> up, and the field should be increased to 255 chars.



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

[jira] [Commented] (OFBIZ-7072) DataResource.dataResourceName field should be at least 255 Chars

[Forrest Rae (JIRA)]

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

Forrest Rae commented on OFBIZ-7072:


I think it's a bug.  Though, I think most of the field definitions are way too 
short.  :P

> DataResource.dataResourceName field should be at least 255 Chars
> 
>
> Key: OFBIZ-7072
> URL: https://issues.apache.org/jira/browse/OFBIZ-7072
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Release 
> Branch 15.12
>Reporter: Forrest Rae
>Assignee: Ashish Vijaywargiya
> Attachments: OFBIZ-7072.patch
>
>
> Most major operating systems limit the length of a file name to 255 chars.  
> When sending an email with file attachments, the attachments get saved as 
> DataResources associated with a CommunicationEvent, with the filename being 
> saved in the DataResource.dataResourceName field.  Currently, this field is 
> set to name, which is limited to 100 chars.  These two limitations don't add 
> up, and the field should be increased to 255 chars.



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

[jira] [Updated] (OFBIZ-7078) Extend OrderAdjustment entity and add isManual field

[Deepak Dixit (JIRA)]

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

Deepak Dixit updated OFBIZ-7078:

Fix Version/s: Upcoming Branch

> Extend OrderAdjustment entity and add isManual field
> 
>
> Key: OFBIZ-7078
> URL: https://issues.apache.org/jira/browse/OFBIZ-7078
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7078.patch
>
>
> Extend OrderAdjustment entity and add isManual field to recognize manually 
> added order adjustment.   
> As per current implementation code using orderAdjustment.comments field to 
> recognize manually added comment using string "Added manually by"
> {code}
> if ( adjustment.get("comments") != null
> && 
> ((String)adjustment.get("comments")).startsWith("Added manually by")) {
> cart.addAdjustment(adjustment);
> }
> {code}



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

[jira] [Closed] (OFBIZ-7078) Extend OrderAdjustment entity and add isManual field

[Deepak Dixit (JIRA)]

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

Deepak Dixit closed OFBIZ-7078.
---
Resolution: Fixed

> Extend OrderAdjustment entity and add isManual field
> 
>
> Key: OFBIZ-7078
> URL: https://issues.apache.org/jira/browse/OFBIZ-7078
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-7078.patch
>
>
> Extend OrderAdjustment entity and add isManual field to recognize manually 
> added order adjustment.   
> As per current implementation code using orderAdjustment.comments field to 
> recognize manually added comment using string "Added manually by"
> {code}
> if ( adjustment.get("comments") != null
> && 
> ((String)adjustment.get("comments")).startsWith("Added manually by")) {
> cart.addAdjustment(adjustment);
> }
> {code}



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

[jira] [Commented] (OFBIZ-7078) Extend OrderAdjustment entity and add isManual field

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7078:
-

Thanks Rohit for your contribution.
This has been committed at trunk at r#1744781

> Extend OrderAdjustment entity and add isManual field
> 
>
> Key: OFBIZ-7078
> URL: https://issues.apache.org/jira/browse/OFBIZ-7078
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-7078.patch
>
>
> Extend OrderAdjustment entity and add isManual field to recognize manually 
> added order adjustment.   
> As per current implementation code using orderAdjustment.comments field to 
> recognize manually added comment using string "Added manually by"
> {code}
> if ( adjustment.get("comments") != null
> && 
> ((String)adjustment.get("comments")).startsWith("Added manually by")) {
> cart.addAdjustment(adjustment);
> }
> {code}



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

Re: [DISCUSSION] AXIS replacement by CXF

[Jacques Le Roux]

I'd first look at different somehow related threads: 
http://ofbiz.markmail.org/search/?q=cxf

Jacques


Le 20/05/2016 à 14:15, Pierre Smits a écrit :

Hi all,

Currently axis2 (Apache Axis)functionality is in place in the OFBiz code
base to provide SOAP services.

I wonder whether replacing that by cxf (Apache CXF) to enable more web
services functionalties (SOAP, REST, RESTful HTTP, and more) in OFBiz would
help adoption. It seems to me it would then be easier to have OFBiz work
not only as a producer, but enhance consumer capabilities as well.

What are your thought and/or concerns on this subject?

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

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

[jira] [Commented] (OFBIZ-7072) DataResource.dataResourceName field should be at least 255 Chars

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-7072:


Commited in trunk at r1744710
I wonder if this should be really considered a bug (I also tend to think so). 
If yes it should be backported

> DataResource.dataResourceName field should be at least 255 Chars
> 
>
> Key: OFBIZ-7072
> URL: https://issues.apache.org/jira/browse/OFBIZ-7072
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Release 
> Branch 15.12
>Reporter: Forrest Rae
>Assignee: Ashish Vijaywargiya
> Attachments: OFBIZ-7072.patch
>
>
> Most major operating systems limit the length of a file name to 255 chars.  
> When sending an email with file attachments, the attachments get saved as 
> DataResources associated with a CommunicationEvent, with the filename being 
> saved in the DataResource.dataResourceName field.  Currently, this field is 
> set to name, which is limited to 100 chars.  These two limitations don't add 
> up, and the field should be increased to 255 chars.



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

[jira] [Closed] (OFBIZ-7083) Unable to add new note to Fixed Asset's maintenance

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux closed OFBIZ-7083.
--
   Resolution: Fixed
Fix Version/s: 15.12.01
   14.12.01

Thanks Amardeep,

Not sure what happened before, anyway it actually works well and edit as well

Your patch is in 
trunk r1744773  
R15.12 r1744774
R14.12 r1744775
R13.07 not concerned



> Unable to add new note to Fixed Asset's maintenance
> ---
>
> Key: OFBIZ-7083
> URL: https://issues.apache.org/jira/browse/OFBIZ-7083
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIZ-7083-Screenshot.png, OFBIZ-7083.patch
>
>
> Getting error when tried to add note to fixed asset maintenance. Please find 
> attached screenshot.
> Steps to regenerate:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/EditFixedAssetMaint?fixedAssetId=1=2
> 2. Now click on notes.
> 3. Now screen will have option to update notes instead of add notes.
> 4. Fill note field and click on update. We will get error.



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

[jira] [Comment Edited] (OFBIZ-7083) Unable to add new note to Fixed Asset's maintenance

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux edited comment on OFBIZ-7083 at 5/20/16 5:20 PM:
-

Not sure about you, but after applying the patch I get this error (I see the 
"Add" button)
{code}
2016-05-20 18:41:50,385 |ttp-nio-8443-exec-10 |ControlServlet
|T| [[[EditWorkEffortNotes(Domain:https://localhost)] Request Done- 
total:0.428,since last([EditWorkEffortNo...):0.428]]
2016-05-20 18:41:54,883 |http-nio-8443-exec-3 |ControlServlet
|T| [[[createWorkEffortNote(Domain:https://localhost)] Request Begun, 
encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceEcaRule
|I| For Service ECA [workEffortGenericPermission] on [return] got false for 
condition: [hasPermission][equals][false][true][Boolean
]
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceDispatcher 
|T| Sync service [assetmaint/workEffortGenericPermission] finished in [48] 
milliseconds
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceDispatcher 
|E| Incoming context (in runSync : createWorkEffortNote) does not match 
expected requirements
org.ofbiz.service.ServiceValidationException: Le paramÞtre requis suivant 
manque : [createWorkEffortNote.workEffortId]
at org.ofbiz.service.ModelService.validate(ModelService.java:557) 
~[ofbiz-service.jar:?]
at 
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376) 
[ofbiz-service.jar:?]
{code}


was (Author: jacques.le.roux):
Not sure about you, but after applying the patch I guess this error (I see the 
"Add" button)
{code}
2016-05-20 18:41:50,385 |ttp-nio-8443-exec-10 |ControlServlet
|T| [[[EditWorkEffortNotes(Domain:https://localhost)] Request Done- 
total:0.428,since last([EditWorkEffortNo...):0.428]]
2016-05-20 18:41:54,883 |http-nio-8443-exec-3 |ControlServlet
|T| [[[createWorkEffortNote(Domain:https://localhost)] Request Begun, 
encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceEcaRule
|I| For Service ECA [workEffortGenericPermission] on [return] got false for 
condition: [hasPermission][equals][false][true][Boolean
]
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceDispatcher 
|T| Sync service [assetmaint/workEffortGenericPermission] finished in [48] 
milliseconds
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceDispatcher 
|E| Incoming context (in runSync : createWorkEffortNote) does not match 
expected requirements
org.ofbiz.service.ServiceValidationException: Le paramÞtre requis suivant 
manque : [createWorkEffortNote.workEffortId]
at org.ofbiz.service.ModelService.validate(ModelService.java:557) 
~[ofbiz-service.jar:?]
at 
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376) 
[ofbiz-service.jar:?]
{code}

> Unable to add new note to Fixed Asset's maintenance
> ---
>
> Key: OFBIZ-7083
> URL: https://issues.apache.org/jira/browse/OFBIZ-7083
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7083-Screenshot.png, OFBIZ-7083.patch
>
>
> Getting error when tried to add note to fixed asset maintenance. Please find 
> attached screenshot.
> Steps to regenerate:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/EditFixedAssetMaint?fixedAssetId=1=2
> 2. Now click on notes.
> 3. Now screen will have option to update notes instead of add notes.
> 4. Fill note field and click on update. We will get error.



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

[jira] [Closed] (OFBIZ-7084) Fixed asset maintenance pdf has missing UI Labels

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux closed OFBIZ-7084.
--
   Resolution: Fixed
Fix Version/s: 15.12.01
   14.12.01

Thanks Amardeep,

Your patch is in
trunk r1744768  
R15.12 r1744769
R14.12 r1744770
R13.07 not concerned

There are still some labels missing, it's a 1st step...

> Fixed asset maintenance pdf has missing UI Labels
> -
>
> Key: OFBIZ-7084
> URL: https://issues.apache.org/jira/browse/OFBIZ-7084
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIZ-7084.patch, Screen Shot 2016-05-19 at 11.57.35 
> PM.png
>
>
> Please find attached screenshot of PDF.
> Steps to get fixed asset maintenance pdf:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/findFixedAssetMaints
> 2. Create maintenance for Fixed asset by clicking create maintenance button.
> 3. On edit fixed asset maintenance page, click on print(PDF).
> https://localhost:8443/assetmaint/control/printFixedAssetMaint.pdf?fixedAssetId=1=1



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

[jira] [Commented] (OFBIZ-7083) Unable to add new note to Fixed Asset's maintenance

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-7083:


Not sure about you, but after applying the patch I guess this error (I see the 
"Add" button)
{code}
2016-05-20 18:41:50,385 |ttp-nio-8443-exec-10 |ControlServlet
|T| [[[EditWorkEffortNotes(Domain:https://localhost)] Request Done- 
total:0.428,since last([EditWorkEffortNo...):0.428]]
2016-05-20 18:41:54,883 |http-nio-8443-exec-3 |ControlServlet
|T| [[[createWorkEffortNote(Domain:https://localhost)] Request Begun, 
encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceEcaRule
|I| For Service ECA [workEffortGenericPermission] on [return] got false for 
condition: [hasPermission][equals][false][true][Boolean
]
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceDispatcher 
|T| Sync service [assetmaint/workEffortGenericPermission] finished in [48] 
milliseconds
2016-05-20 18:41:54,936 |http-nio-8443-exec-3 |ServiceDispatcher 
|E| Incoming context (in runSync : createWorkEffortNote) does not match 
expected requirements
org.ofbiz.service.ServiceValidationException: Le paramÞtre requis suivant 
manque : [createWorkEffortNote.workEffortId]
at org.ofbiz.service.ModelService.validate(ModelService.java:557) 
~[ofbiz-service.jar:?]
at 
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376) 
[ofbiz-service.jar:?]
{code}

> Unable to add new note to Fixed Asset's maintenance
> ---
>
> Key: OFBIZ-7083
> URL: https://issues.apache.org/jira/browse/OFBIZ-7083
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7083-Screenshot.png, OFBIZ-7083.patch
>
>
> Getting error when tried to add note to fixed asset maintenance. Please find 
> attached screenshot.
> Steps to regenerate:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/EditFixedAssetMaint?fixedAssetId=1=2
> 2. Now click on notes.
> 3. Now screen will have option to update notes instead of add notes.
> 4. Fill note field and click on update. We will get error.



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

[jira] [Assigned] (OFBIZ-7083) Unable to add new note to Fixed Asset's maintenance

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux reassigned OFBIZ-7083:
--

Assignee: Jacques Le Roux  (was: Amardeep Singh Jhajj)

> Unable to add new note to Fixed Asset's maintenance
> ---
>
> Key: OFBIZ-7083
> URL: https://issues.apache.org/jira/browse/OFBIZ-7083
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7083-Screenshot.png, OFBIZ-7083.patch
>
>
> Getting error when tried to add note to fixed asset maintenance. Please find 
> attached screenshot.
> Steps to regenerate:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/EditFixedAssetMaint?fixedAssetId=1=2
> 2. Now click on notes.
> 3. Now screen will have option to update notes instead of add notes.
> 4. Fill note field and click on update. We will get error.



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

[jira] [Assigned] (OFBIZ-7084) Fixed asset maintenance pdf has missing UI Labels

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux reassigned OFBIZ-7084:
--

Assignee: Jacques Le Roux  (was: Amardeep Singh Jhajj)

> Fixed asset maintenance pdf has missing UI Labels
> -
>
> Key: OFBIZ-7084
> URL: https://issues.apache.org/jira/browse/OFBIZ-7084
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-7084.patch, Screen Shot 2016-05-19 at 11.57.35 
> PM.png
>
>
> Please find attached screenshot of PDF.
> Steps to get fixed asset maintenance pdf:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/findFixedAssetMaints
> 2. Create maintenance for Fixed asset by clicking create maintenance button.
> 3. On edit fixed asset maintenance page, click on print(PDF).
> https://localhost:8443/assetmaint/control/printFixedAssetMaint.pdf?fixedAssetId=1=1



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

[jira] [Commented] (OFBIZ-7084) Fixed asset maintenance pdf has missing UI Labels

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj commented on OFBIZ-7084:
-

Please find attached patch for Release 14.12, 15.12 and trunk. Thanks.

> Fixed asset maintenance pdf has missing UI Labels
> -
>
> Key: OFBIZ-7084
> URL: https://issues.apache.org/jira/browse/OFBIZ-7084
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
>Priority: Minor
> Attachments: OFBIZ-7084.patch, Screen Shot 2016-05-19 at 11.57.35 
> PM.png
>
>
> Please find attached screenshot of PDF.
> Steps to get fixed asset maintenance pdf:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/findFixedAssetMaints
> 2. Create maintenance for Fixed asset by clicking create maintenance button.
> 3. On edit fixed asset maintenance page, click on print(PDF).
> https://localhost:8443/assetmaint/control/printFixedAssetMaint.pdf?fixedAssetId=1=1



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

[jira] [Updated] (OFBIZ-7084) Fixed asset maintenance pdf has missing UI Labels

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7084:

Attachment: OFBIZ-7084.patch

> Fixed asset maintenance pdf has missing UI Labels
> -
>
> Key: OFBIZ-7084
> URL: https://issues.apache.org/jira/browse/OFBIZ-7084
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
>Priority: Minor
> Attachments: OFBIZ-7084.patch, Screen Shot 2016-05-19 at 11.57.35 
> PM.png
>
>
> Please find attached screenshot of PDF.
> Steps to get fixed asset maintenance pdf:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/findFixedAssetMaints
> 2. Create maintenance for Fixed asset by clicking create maintenance button.
> 3. On edit fixed asset maintenance page, click on print(PDF).
> https://localhost:8443/assetmaint/control/printFixedAssetMaint.pdf?fixedAssetId=1=1



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

Re: svn commit: r1738904 - in /ofbiz/branches/release15.12: ./ framework/base/lib/j2eespecs/ framework/catalina/ framework/catalina/lib/ framework/catalina/src/org/ofbiz/catalina/container/ framework/

[Jacopo Cappellato]

:-)

Thank you Jacques.

Jacopo

On Fri, May 20, 2016 at 3:18 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> With 3 positive committers I decided to go, done for R14.12 r1744733
>
> R13.07 will need more work...
>
>
>
> Le 20/05/2016 à 14:12, Jacopo Cappellato a écrit :
>
>> It sounds like a good idea to me too. And I agree with Jacques that we
>> should strive to maintain the same version in all the active release
>> branches 13.07, 14.12, 15.12.
>>
>> Jacopo
>>
>> On Fri, May 20, 2016 at 1:17 PM, Deepak Dixit <
>> deepak.di...@hotwaxsystems.com> wrote:
>>
>> No Jacques there is not specific reason for this, I generally prefer to
>>> backport changes to most recent/active branches. Just to avoid conflicts
>>> I
>>> skip 13.07 most of the time :)
>>>
>>> Thanks & Regards
>>> --
>>> Deepak Dixit
>>> www.hotwaxsystems.com
>>>
>>> On Fri, May 20, 2016 at 4:34 PM, Jacques Le Roux <
>>> jacques.le.r...@les7arts.com> wrote:
>>>
>>> That sounds like a good idea to me Deepak, and then why not R13.07?

 I though noticed that Pierre Smits suggested to not backport in earlier
 releases branches than R15.12. Pierre is there a special reason with

>>> that?
>>>
 BTW I noticed that you guys at HW are not backporting much in R13.07, is
 there a special reason with that?

 Thanks!

 Jacques



 Le 20/05/2016 à 12:24, Deepak Dixit a écrit :

 Hi Jacques,
>
> I think it would be useful to backport this to 14.12 releases.In this
>
 way
>>>
 we will have less tomcat revisions to keep an eye on for vulnerability
> fixes, and we will specialize in one version only so that our upgrade
> effort will be smaller.
>
>
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Wed, Apr 13, 2016 at 1:13 PM,  wrote:
>
> Author: jleroux
>
>> Date: Wed Apr 13 07:43:07 2016
>> New Revision: 1738904
>>
>> URL: http://svn.apache.org/viewvc?rev=1738904=rev
>> Log:
>> "Applied fix from trunk for revision: 1738902"
>>
>>
>>> 
>>>
 r1738902 | jleroux | 2016-04-13 09:40:25 +0200 (mer. 13 avr. 2016) | 4
>> lignes
>>
>> A slightly modified patch from Chatree Srichart for "Upgrade Tomcat to
>> 8.0.32" https://issues.apache.org/jira/browse/OFBIZ-6915
>>
>> jleroux: I simply changed the doc link in catalina ofbiz-component.xml
>>
>>
>>
>>> 
>>>

>> Added:
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-3.0.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/base/lib/j2eespecs/el-api-3.0.jar
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.3.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/base/lib/j2eespecs/jsp-api-2.3.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.1.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/base/lib/j2eespecs/servlet-api-3.1.jar
>>   ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.5.jar
>> - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/ecj-4.5.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-jasper.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-jasper.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
>>
>>
>>
>>
>>> 

[jira] [Updated] (OFBIZ-7084) Fixed asset maintenance pdf has missing UI Labels

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7084:

Attachment: Screen Shot 2016-05-19 at 11.57.35 PM.png

> Fixed asset maintenance pdf has missing UI Labels
> -
>
> Key: OFBIZ-7084
> URL: https://issues.apache.org/jira/browse/OFBIZ-7084
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
>Priority: Minor
> Attachments: Screen Shot 2016-05-19 at 11.57.35 PM.png
>
>
> Please find attached screenshot of PDF.
> Steps to get fixed asset maintenance pdf:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/findFixedAssetMaints
> 2. Create maintenance for Fixed asset by clicking create maintenance button.
> 3. On edit fixed asset maintenance page, click on print(PDF).
> https://localhost:8443/assetmaint/control/printFixedAssetMaint.pdf?fixedAssetId=1=1



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

[jira] [Created] (OFBIZ-7084) Fixed asset maintenance pdf has missing UI Labels

[Amardeep Singh Jhajj (JIRA)]

Amardeep Singh Jhajj created OFBIZ-7084:
---

 Summary: Fixed asset maintenance pdf has missing UI Labels
 Key: OFBIZ-7084
 URL: https://issues.apache.org/jira/browse/OFBIZ-7084
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/assetmaint
Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12
Reporter: Amardeep Singh Jhajj
Assignee: Amardeep Singh Jhajj
Priority: Minor


Please find attached screenshot of PDF.

Steps to get fixed asset maintenance pdf:

1. Go to Asset Maintenance : 
https://localhost:8443/assetmaint/control/findFixedAssetMaints

2. Create maintenance for Fixed asset by clicking create maintenance button.

3. On edit fixed asset maintenance page, click on print(PDF).

https://localhost:8443/assetmaint/control/printFixedAssetMaint.pdf?fixedAssetId=1=1



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

[jira] [Updated] (OFBIZ-7082) FileNotFoundException while editing contact information

[Deepak Dixit (JIRA)]

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

Deepak Dixit updated OFBIZ-7082:

Priority: Minor  (was: Major)

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Harsh Vijaywargiya
>Assignee: Deepak Dixit
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



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

[jira] [Issue Comment Deleted] (OFBIZ-7082) FileNotFoundException while editing contact information

[Deepak Dixit (JIRA)]

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

Deepak Dixit updated OFBIZ-7082:

Comment: was deleted

(was: Thanks Harsh for reporting this issue. )

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Harsh Vijaywargiya
>Assignee: Deepak Dixit
> Fix For: Upcoming Branch
>
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



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

[jira] [Commented] (OFBIZ-7082) FileNotFoundException while editing contact information

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7082:
-

Thanks Harsh for reporting this issue.
This has been Fixed at r#1744745

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Harsh Vijaywargiya
>Assignee: Deepak Dixit
> Fix For: Upcoming Branch
>
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



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

[jira] [Closed] (OFBIZ-7082) FileNotFoundException while editing contact information

[Deepak Dixit (JIRA)]

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

Deepak Dixit closed OFBIZ-7082.
---
   Resolution: Fixed
Fix Version/s: Upcoming Branch

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Harsh Vijaywargiya
>Assignee: Deepak Dixit
> Fix For: Upcoming Branch
>
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



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

[jira] [Commented] (OFBIZ-7082) FileNotFoundException while editing contact information

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7082:
-

Thanks Harsh for reporting this issue. 

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Harsh Vijaywargiya
>Assignee: Deepak Dixit
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



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

[jira] [Commented] (OFBIZ-7083) Unable to add new note to Fixed Asset's maintenance

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj commented on OFBIZ-7083:
-

Please find attached patch for Release 14.12, 15.12 and trunk. Thanks.

> Unable to add new note to Fixed Asset's maintenance
> ---
>
> Key: OFBIZ-7083
> URL: https://issues.apache.org/jira/browse/OFBIZ-7083
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7083-Screenshot.png, OFBIZ-7083.patch
>
>
> Getting error when tried to add note to fixed asset maintenance. Please find 
> attached screenshot.
> Steps to regenerate:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/EditFixedAssetMaint?fixedAssetId=1=2
> 2. Now click on notes.
> 3. Now screen will have option to update notes instead of add notes.
> 4. Fill note field and click on update. We will get error.



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

[jira] [Updated] (OFBIZ-7083) Unable to add new note to Fixed Asset's maintenance

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7083:

Attachment: OFBIZ-7083.patch
OFBIZ-7083-Screenshot.png

> Unable to add new note to Fixed Asset's maintenance
> ---
>
> Key: OFBIZ-7083
> URL: https://issues.apache.org/jira/browse/OFBIZ-7083
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7083-Screenshot.png, OFBIZ-7083.patch
>
>
> Getting error when tried to add note to fixed asset maintenance. Please find 
> attached screenshot.
> Steps to regenerate:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/EditFixedAssetMaint?fixedAssetId=1=2
> 2. Now click on notes.
> 3. Now screen will have option to update notes instead of add notes.
> 4. Fill note field and click on update. We will get error.



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

[jira] [Created] (OFBIZ-7083) Unable to add new note to Fixed Asset's maintenance.

[Amardeep Singh Jhajj (JIRA)]

Amardeep Singh Jhajj created OFBIZ-7083:
---

 Summary: Unable to add new note to Fixed Asset's maintenance.
 Key: OFBIZ-7083
 URL: https://issues.apache.org/jira/browse/OFBIZ-7083
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/assetmaint
Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12
Reporter: Amardeep Singh Jhajj
Assignee: Amardeep Singh Jhajj


Getting error when tried to add note to fixed asset maintenance. Please find 
attached screenshot.

Steps to regenerate:

1. Go to Asset Maintenance : 
https://localhost:8443/assetmaint/control/EditFixedAssetMaint?fixedAssetId=1=2

2. Now click on notes.

3. Now screen will have option to update notes instead of add notes.

4. Fill note field and click on update. We will get error.



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

[jira] [Updated] (OFBIZ-7083) Unable to add new note to Fixed Asset's maintenance

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7083:

Summary: Unable to add new note to Fixed Asset's maintenance  (was: Unable 
to add new note to Fixed Asset's maintenance.)

> Unable to add new note to Fixed Asset's maintenance
> ---
>
> Key: OFBIZ-7083
> URL: https://issues.apache.org/jira/browse/OFBIZ-7083
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/assetmaint
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
>
> Getting error when tried to add note to fixed asset maintenance. Please find 
> attached screenshot.
> Steps to regenerate:
> 1. Go to Asset Maintenance : 
> https://localhost:8443/assetmaint/control/EditFixedAssetMaint?fixedAssetId=1=2
> 2. Now click on notes.
> 3. Now screen will have option to update notes instead of add notes.
> 4. Fill note field and click on update. We will get error.



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

[jira] [Assigned] (OFBIZ-7082) FileNotFoundException while editing contact information

[Deepak Dixit (JIRA)]

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

Deepak Dixit reassigned OFBIZ-7082:
---

Assignee: Deepak Dixit  (was: Amardeep Singh Jhajj)

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Harsh Vijaywargiya
>Assignee: Deepak Dixit
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



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

[jira] [Commented] (OFBIZ-7082) FileNotFoundException while editing contact information

[Harsh Vijaywargiya (JIRA)]

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

Harsh Vijaywargiya commented on OFBIZ-7082:
---

To resolve this please rename EditcontaCtmech.ftl in party component to 
EditContactMech.ftl

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Harsh Vijaywargiya
>Assignee: Amardeep Singh Jhajj
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



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

Re: svn commit: r1738904 - in /ofbiz/branches/release15.12: ./ framework/base/lib/j2eespecs/ framework/catalina/ framework/catalina/lib/ framework/catalina/src/org/ofbiz/catalina/container/ framework/

[Deepak Dixit]

Thanks Jacques

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

On Fri, May 20, 2016 at 6:48 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> With 3 positive committers I decided to go, done for R14.12 r1744733
>
> R13.07 will need more work...
>
>
>
> Le 20/05/2016 à 14:12, Jacopo Cappellato a écrit :
>
>> It sounds like a good idea to me too. And I agree with Jacques that we
>> should strive to maintain the same version in all the active release
>> branches 13.07, 14.12, 15.12.
>>
>> Jacopo
>>
>> On Fri, May 20, 2016 at 1:17 PM, Deepak Dixit <
>> deepak.di...@hotwaxsystems.com> wrote:
>>
>> No Jacques there is not specific reason for this, I generally prefer to
>>> backport changes to most recent/active branches. Just to avoid conflicts
>>> I
>>> skip 13.07 most of the time :)
>>>
>>> Thanks & Regards
>>> --
>>> Deepak Dixit
>>> www.hotwaxsystems.com
>>>
>>> On Fri, May 20, 2016 at 4:34 PM, Jacques Le Roux <
>>> jacques.le.r...@les7arts.com> wrote:
>>>
>>> That sounds like a good idea to me Deepak, and then why not R13.07?

 I though noticed that Pierre Smits suggested to not backport in earlier
 releases branches than R15.12. Pierre is there a special reason with

>>> that?
>>>
 BTW I noticed that you guys at HW are not backporting much in R13.07, is
 there a special reason with that?

 Thanks!

 Jacques



 Le 20/05/2016 à 12:24, Deepak Dixit a écrit :

 Hi Jacques,
>
> I think it would be useful to backport this to 14.12 releases.In this
>
 way
>>>
 we will have less tomcat revisions to keep an eye on for vulnerability
> fixes, and we will specialize in one version only so that our upgrade
> effort will be smaller.
>
>
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Wed, Apr 13, 2016 at 1:13 PM,  wrote:
>
> Author: jleroux
>
>> Date: Wed Apr 13 07:43:07 2016
>> New Revision: 1738904
>>
>> URL: http://svn.apache.org/viewvc?rev=1738904=rev
>> Log:
>> "Applied fix from trunk for revision: 1738902"
>>
>>
>>> 
>>>
 r1738902 | jleroux | 2016-04-13 09:40:25 +0200 (mer. 13 avr. 2016) | 4
>> lignes
>>
>> A slightly modified patch from Chatree Srichart for "Upgrade Tomcat to
>> 8.0.32" https://issues.apache.org/jira/browse/OFBIZ-6915
>>
>> jleroux: I simply changed the doc link in catalina ofbiz-component.xml
>>
>>
>>
>>> 
>>>

>> Added:
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-3.0.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/base/lib/j2eespecs/el-api-3.0.jar
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.3.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/base/lib/j2eespecs/jsp-api-2.3.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.1.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/base/lib/j2eespecs/servlet-api-3.1.jar
>>   ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.5.jar
>> - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/ecj-4.5.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-jasper.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-jasper.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
>>
>>
>>
>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
>>>
 - copied unchanged from r1738902,
>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
>>
>>
>>
>>
>>> 

[jira] [Commented] (OFBIZ-6915) Upgrade Tomcat to 8.0.33

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-6915:


Backported in R14.12 at r1744733

> Upgrade Tomcat to 8.0.33
> 
>
> Key: OFBIZ-6915
> URL: https://issues.apache.org/jira/browse/OFBIZ-6915
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
> Environment: Ubuntu 14.04 
>Reporter: Chatree Srichart
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 15.12.01
>
> Attachments: tomcat-8.0.32-libs.zip, tomcat-8.0.33-libs.zip, 
> upgrade_tomcat_to_8.0.32.patch, upgrade_tomcat_to_8.0.33.patch, 
> upgrade_tomcat_to_8.0.33.status
>
>
> I am working on a library which requires Tomcat 8 but it cannot work on the 
> current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat 
> to version 8? I also provides a patch and libraries for Tomcat 8.0.32.
> Migrating from 7.0.x to 8.0.x
> https://tomcat.apache.org/migration-8.html
> Tomcat 8 Security
> https://tomcat.apache.org/security-8.html
> Tomcat 8 Changelog
> http://tomcat.apache.org/tomcat-8.0-doc/changelog.html



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

[jira] [Updated] (OFBIZ-6915) Upgrade Tomcat to 8.0.33

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-6915:
---
Fix Version/s: 14.12.01

> Upgrade Tomcat to 8.0.33
> 
>
> Key: OFBIZ-6915
> URL: https://issues.apache.org/jira/browse/OFBIZ-6915
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
> Environment: Ubuntu 14.04 
>Reporter: Chatree Srichart
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 15.12.01
>
> Attachments: tomcat-8.0.32-libs.zip, tomcat-8.0.33-libs.zip, 
> upgrade_tomcat_to_8.0.32.patch, upgrade_tomcat_to_8.0.33.patch, 
> upgrade_tomcat_to_8.0.33.status
>
>
> I am working on a library which requires Tomcat 8 but it cannot work on the 
> current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat 
> to version 8? I also provides a patch and libraries for Tomcat 8.0.32.
> Migrating from 7.0.x to 8.0.x
> https://tomcat.apache.org/migration-8.html
> Tomcat 8 Security
> https://tomcat.apache.org/security-8.html
> Tomcat 8 Changelog
> http://tomcat.apache.org/tomcat-8.0-doc/changelog.html



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

Re: svn commit: r1738904 - in /ofbiz/branches/release15.12: ./ framework/base/lib/j2eespecs/ framework/catalina/ framework/catalina/lib/ framework/catalina/src/org/ofbiz/catalina/container/ framework/

[Jacques Le Roux]

With 3 positive committers I decided to go, done for R14.12 r1744733

R13.07 will need more work...


Le 20/05/2016 à 14:12, Jacopo Cappellato a écrit :

It sounds like a good idea to me too. And I agree with Jacques that we
should strive to maintain the same version in all the active release
branches 13.07, 14.12, 15.12.

Jacopo

On Fri, May 20, 2016 at 1:17 PM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:


No Jacques there is not specific reason for this, I generally prefer to
backport changes to most recent/active branches. Just to avoid conflicts I
skip 13.07 most of the time :)

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

On Fri, May 20, 2016 at 4:34 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


That sounds like a good idea to me Deepak, and then why not R13.07?

I though noticed that Pierre Smits suggested to not backport in earlier
releases branches than R15.12. Pierre is there a special reason with

that?

BTW I noticed that you guys at HW are not backporting much in R13.07, is
there a special reason with that?

Thanks!

Jacques



Le 20/05/2016 à 12:24, Deepak Dixit a écrit :


Hi Jacques,

I think it would be useful to backport this to 14.12 releases.In this

way

we will have less tomcat revisions to keep an eye on for vulnerability
fixes, and we will specialize in one version only so that our upgrade
effort will be smaller.



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

On Wed, Apr 13, 2016 at 1:13 PM,  wrote:

Author: jleroux

Date: Wed Apr 13 07:43:07 2016
New Revision: 1738904

URL: http://svn.apache.org/viewvc?rev=1738904=rev
Log:
"Applied fix from trunk for revision: 1738902"




r1738902 | jleroux | 2016-04-13 09:40:25 +0200 (mer. 13 avr. 2016) | 4
lignes

A slightly modified patch from Chatree Srichart for "Upgrade Tomcat to
8.0.32" https://issues.apache.org/jira/browse/OFBIZ-6915

jleroux: I simply changed the doc link in catalina ofbiz-component.xml






Added:



ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-3.0.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/base/lib/j2eespecs/el-api-3.0.jar



ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.3.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/base/lib/j2eespecs/jsp-api-2.3.jar




ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.1.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/base/lib/j2eespecs/servlet-api-3.1.jar
  ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.5.jar
- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/ecj-4.5.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-jasper.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-jasper.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli-adapters.jar

- copied unchanged from r1738902,



ofbiz/trunk/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli-adapters.jar




ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli.jar

- copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli.jar

[jira] [Closed] (OFBIZ-7081) Error on Edit Credit Card page

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux closed OFBIZ-7081.
--
   Resolution: Fixed
Fix Version/s: 13.07.04

Thanks Ravi for the report,

When I backported OFBIZ-1524 "Improve the way CreditCard.cardType field is 
managed" in R13.07 I did not notice that Ashish "forgot to commit a file in one 
of [his] recent commit r1626425" and then Pierre at "CcTypes.groovy misses 
licence" - OFBIZ-6684 completed the file. At r1744730 I did both

> Error on Edit Credit Card page
> --
>
> Key: OFBIZ-7081
> URL: https://issues.apache.org/jira/browse/OFBIZ-7081
> Project: OFBiz
>  Issue Type: Bug
>  Components: order, party
>Affects Versions: Release Branch 13.07
>Reporter: Ravi Lodhi
>Assignee: Jacques Le Roux
> Fix For: 13.07.04
>
>
> Step to regenerate (create a new order):
> 1) Start placing a new order from 
> http://demo-stable-ofbiz.apache.org/ordermgr/control/orderentry
> 2) Add products and click on "Finalize Order" button and continue till the 
> Order Entry Payment Settings screen.
> 3) From the listed method go to edit credit card (e.g. CC: CCT_VISA) by 
> clicking update button.
> 4) See the Card Type drop down having only one option and see the FreeMarker 
> template error.
> Root Cause:
> CcTypes.groovy file is missing.



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

[jira] [Updated] (OFBIZ-7082) FileNotFoundException while editing contact information

[Amardeep Singh Jhajj (JIRA)]

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

Amardeep Singh Jhajj updated OFBIZ-7082:

Assignee: Amardeep Singh Jhajj

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Harsh Vijaywargiya
>Assignee: Amardeep Singh Jhajj
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



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

[jira] [Assigned] (OFBIZ-7081) Error on Edit Credit Card page

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux reassigned OFBIZ-7081:
--

Assignee: Jacques Le Roux

> Error on Edit Credit Card page
> --
>
> Key: OFBIZ-7081
> URL: https://issues.apache.org/jira/browse/OFBIZ-7081
> Project: OFBiz
>  Issue Type: Bug
>  Components: order, party
>Affects Versions: Release Branch 13.07
>Reporter: Ravi Lodhi
>Assignee: Jacques Le Roux
>
> Step to regenerate (create a new order):
> 1) Start placing a new order from 
> http://demo-stable-ofbiz.apache.org/ordermgr/control/orderentry
> 2) Add products and click on "Finalize Order" button and continue till the 
> Order Entry Payment Settings screen.
> 3) From the listed method go to edit credit card (e.g. CC: CCT_VISA) by 
> clicking update button.
> 4) See the Card Type drop down having only one option and see the FreeMarker 
> template error.
> Root Cause:
> CcTypes.groovy file is missing.



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

[jira] [Created] (OFBIZ-7082) FileNotFoundException while editing contact information

[Harsh Vijaywargiya (JIRA)]

Harsh Vijaywargiya created OFBIZ-7082:
-

 Summary: FileNotFoundException while editing contact information
 Key: OFBIZ-7082
 URL: https://issues.apache.org/jira/browse/OFBIZ-7082
 Project: OFBiz
  Issue Type: Bug
  Components: party
Affects Versions: Trunk
Reporter: Harsh Vijaywargiya


Getting following error while trying to update any contact information

Error rendering included template at location 
[component://party/template/party/EditContactMech.ftl]: 
java.io.FileNotFoundException: /home/common/ofbiz-



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

[jira] [Created] (OFBIZ-7081) Error on Edit Credit Card page

[Ravi Lodhi (JIRA)]

Ravi Lodhi created OFBIZ-7081:
-

 Summary: Error on Edit Credit Card page
 Key: OFBIZ-7081
 URL: https://issues.apache.org/jira/browse/OFBIZ-7081
 Project: OFBiz
  Issue Type: Bug
  Components: order, party
Affects Versions: Release Branch 13.07
Reporter: Ravi Lodhi


Step to regenerate (create a new order):
1) Start placing a new order from 
http://demo-stable-ofbiz.apache.org/ordermgr/control/orderentry
2) Add products and click on "Finalize Order" button and continue till the 
Order Entry Payment Settings screen.
3) From the listed method go to edit credit card (e.g. CC: CCT_VISA) by 
clicking update button.
4) See the Card Type drop down having only one option and see the FreeMarker 
template error.


Root Cause:
CcTypes.groovy file is missing.



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

[DISCUSSION] AXIS replacement by CXF

[Pierre Smits]

Hi all,

Currently axis2 (Apache Axis)functionality is in place in the OFBiz code
base to provide SOAP services.

I wonder whether replacing that by cxf (Apache CXF) to enable more web
services functionalties (SOAP, REST, RESTful HTTP, and more) in OFBiz would
help adoption. It seems to me it would then be easier to have OFBiz work
not only as a producer, but enhance consumer capabilities as well.

What are your thought and/or concerns on this subject?

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

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

Re: svn commit: r1738904 - in /ofbiz/branches/release15.12: ./ framework/base/lib/j2eespecs/ framework/catalina/ framework/catalina/lib/ framework/catalina/src/org/ofbiz/catalina/container/ framework/

[Jacopo Cappellato]

It sounds like a good idea to me too. And I agree with Jacques that we
should strive to maintain the same version in all the active release
branches 13.07, 14.12, 15.12.

Jacopo

On Fri, May 20, 2016 at 1:17 PM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:

> No Jacques there is not specific reason for this, I generally prefer to
> backport changes to most recent/active branches. Just to avoid conflicts I
> skip 13.07 most of the time :)
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Fri, May 20, 2016 at 4:34 PM, Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
> > That sounds like a good idea to me Deepak, and then why not R13.07?
> >
> > I though noticed that Pierre Smits suggested to not backport in earlier
> > releases branches than R15.12. Pierre is there a special reason with
> that?
> >
> > BTW I noticed that you guys at HW are not backporting much in R13.07, is
> > there a special reason with that?
> >
> > Thanks!
> >
> > Jacques
> >
> >
> >
> > Le 20/05/2016 à 12:24, Deepak Dixit a écrit :
> >
> >> Hi Jacques,
> >>
> >> I think it would be useful to backport this to 14.12 releases.In this
> way
> >> we will have less tomcat revisions to keep an eye on for vulnerability
> >> fixes, and we will specialize in one version only so that our upgrade
> >> effort will be smaller.
> >>
> >>
> >>
> >> Thanks & Regards
> >> --
> >> Deepak Dixit
> >> www.hotwaxsystems.com
> >>
> >> On Wed, Apr 13, 2016 at 1:13 PM,  wrote:
> >>
> >> Author: jleroux
> >>> Date: Wed Apr 13 07:43:07 2016
> >>> New Revision: 1738904
> >>>
> >>> URL: http://svn.apache.org/viewvc?rev=1738904=rev
> >>> Log:
> >>> "Applied fix from trunk for revision: 1738902"
> >>>
> 
> >>> r1738902 | jleroux | 2016-04-13 09:40:25 +0200 (mer. 13 avr. 2016) | 4
> >>> lignes
> >>>
> >>> A slightly modified patch from Chatree Srichart for "Upgrade Tomcat to
> >>> 8.0.32" https://issues.apache.org/jira/browse/OFBIZ-6915
> >>>
> >>> jleroux: I simply changed the doc link in catalina ofbiz-component.xml
> >>>
> >>>
> 
> >>>
> >>>
> >>> Added:
> >>>
> >>>
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-3.0.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/base/lib/j2eespecs/el-api-3.0.jar
> >>>
> >>>
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.3.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/base/lib/j2eespecs/jsp-api-2.3.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.1.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/base/lib/j2eespecs/servlet-api-3.1.jar
> >>>  ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.5.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/ecj-4.5.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-jasper.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-jasper.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar
> >>>
> >>>
> >>>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar
> >>>- copied unchanged from r1738902,
> >>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar
> >>>
> >>>
> 

[jira] [Commented] (OFBIZ-7079) Extend Product entity and add serialized field

[Pierre Smits (JIRA)]

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

Pierre Smits commented on OFBIZ-7079:
-

This is complicating the matter a bit more, as there might be inconsistencies 
when an adopter has multiple facilities in place. 

How do we handle that? 

Related issues might be: 
* OFBIZ-6939
* OFBIZ-6964

I would say that the setting in the product would always override the setting 
in the facility.


> Extend Product entity and add serialized field
> --
>
> Key: OFBIZ-7079
> URL: https://issues.apache.org/jira/browse/OFBIZ-7079
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
>
> Extend Product entity and add serialized field to recognize product behavior. 
> Will use product.serialized at the time of receiving to identified inventory 
> item behavior.
> This will be setup time configuration, At the time of Product creation will 
> set this flag. 



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

[jira] [Updated] (OFBIZ-7078) Extend OrderAdjustment entity and add isManual field

[Rohit Koushal (JIRA)]

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

Rohit Koushal updated OFBIZ-7078:
-
Attachment: OFBIZ-7078.patch

Hi [~deepakdixit],
I have attached the patch regarding the binding our logic to pattern in 
comment. Please review and let me know if you have any concern.

> Extend OrderAdjustment entity and add isManual field
> 
>
> Key: OFBIZ-7078
> URL: https://issues.apache.org/jira/browse/OFBIZ-7078
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-7078.patch
>
>
> Extend OrderAdjustment entity and add isManual field to recognize manually 
> added order adjustment.   
> As per current implementation code using orderAdjustment.comments field to 
> recognize manually added comment using string "Added manually by"
> {code}
> if ( adjustment.get("comments") != null
> && 
> ((String)adjustment.get("comments")).startsWith("Added manually by")) {
> cart.addAdjustment(adjustment);
> }
> {code}



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

Re: svn commit: r1738904 - in /ofbiz/branches/release15.12: ./ framework/base/lib/j2eespecs/ framework/catalina/ framework/catalina/lib/ framework/catalina/src/org/ofbiz/catalina/container/ framework/

[Deepak Dixit]

No Jacques there is not specific reason for this, I generally prefer to
backport changes to most recent/active branches. Just to avoid conflicts I
skip 13.07 most of the time :)

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

On Fri, May 20, 2016 at 4:34 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> That sounds like a good idea to me Deepak, and then why not R13.07?
>
> I though noticed that Pierre Smits suggested to not backport in earlier
> releases branches than R15.12. Pierre is there a special reason with that?
>
> BTW I noticed that you guys at HW are not backporting much in R13.07, is
> there a special reason with that?
>
> Thanks!
>
> Jacques
>
>
>
> Le 20/05/2016 à 12:24, Deepak Dixit a écrit :
>
>> Hi Jacques,
>>
>> I think it would be useful to backport this to 14.12 releases.In this way
>> we will have less tomcat revisions to keep an eye on for vulnerability
>> fixes, and we will specialize in one version only so that our upgrade
>> effort will be smaller.
>>
>>
>>
>> Thanks & Regards
>> --
>> Deepak Dixit
>> www.hotwaxsystems.com
>>
>> On Wed, Apr 13, 2016 at 1:13 PM,  wrote:
>>
>> Author: jleroux
>>> Date: Wed Apr 13 07:43:07 2016
>>> New Revision: 1738904
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1738904=rev
>>> Log:
>>> "Applied fix from trunk for revision: 1738902"
>>> 
>>> r1738902 | jleroux | 2016-04-13 09:40:25 +0200 (mer. 13 avr. 2016) | 4
>>> lignes
>>>
>>> A slightly modified patch from Chatree Srichart for "Upgrade Tomcat to
>>> 8.0.32" https://issues.apache.org/jira/browse/OFBIZ-6915
>>>
>>> jleroux: I simply changed the doc link in catalina ofbiz-component.xml
>>>
>>> 
>>>
>>>
>>> Added:
>>>
>>>  ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-3.0.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/base/lib/j2eespecs/el-api-3.0.jar
>>>
>>> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.3.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/base/lib/j2eespecs/jsp-api-2.3.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.1.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/base/lib/j2eespecs/servlet-api-3.1.jar
>>>  ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.5.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/ecj-4.5.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-jasper.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-jasper.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli-adapters.jar
>>>- copied unchanged from r1738902,
>>>
>>> ofbiz/trunk/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli-adapters.jar
>>>
>>>
>>> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli.jar
>>>- copied unchanged from r1738902,
>>> ofbiz/trunk/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli.jar
>>> Removed:
>>>
>>>  ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-2.2.jar

[jira] [Commented] (OFBIZ-7079) Extend Product entity and add serialized field

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7079:
-

Yup, thanks for the example ;)

I think as we have Facility.defaultInventoryItemTypeId, so we can add this flag 
as ProductFacility level as well, in this way different facilities may have 
different handling.

So handling should be like:
* if the flag at ProductFacility is set then it is used
* otherwise the flag at Product level is used

Does this sounds good?

> Extend Product entity and add serialized field
> --
>
> Key: OFBIZ-7079
> URL: https://issues.apache.org/jira/browse/OFBIZ-7079
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
>
> Extend Product entity and add serialized field to recognize product behavior. 
> Will use product.serialized at the time of receiving to identified inventory 
> item behavior.
> This will be setup time configuration, At the time of Product creation will 
> set this flag. 



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

Re: svn commit: r1738904 - in /ofbiz/branches/release15.12: ./ framework/base/lib/j2eespecs/ framework/catalina/ framework/catalina/lib/ framework/catalina/src/org/ofbiz/catalina/container/ framework/

[Jacques Le Roux]

That sounds like a good idea to me Deepak, and then why not R13.07?

I though noticed that Pierre Smits suggested to not backport in earlier 
releases branches than R15.12. Pierre is there a special reason with that?

BTW I noticed that you guys at HW are not backporting much in R13.07, is there 
a special reason with that?

Thanks!

Jacques


Le 20/05/2016 à 12:24, Deepak Dixit a écrit :

Hi Jacques,

I think it would be useful to backport this to 14.12 releases.In this way
we will have less tomcat revisions to keep an eye on for vulnerability
fixes, and we will specialize in one version only so that our upgrade
effort will be smaller.



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

On Wed, Apr 13, 2016 at 1:13 PM,  wrote:


Author: jleroux
Date: Wed Apr 13 07:43:07 2016
New Revision: 1738904

URL: http://svn.apache.org/viewvc?rev=1738904=rev
Log:
"Applied fix from trunk for revision: 1738902"

r1738902 | jleroux | 2016-04-13 09:40:25 +0200 (mer. 13 avr. 2016) | 4
lignes

A slightly modified patch from Chatree Srichart for "Upgrade Tomcat to
8.0.32" https://issues.apache.org/jira/browse/OFBIZ-6915

jleroux: I simply changed the doc link in catalina ofbiz-component.xml




Added:
 ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-3.0.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/base/lib/j2eespecs/el-api-3.0.jar

ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.3.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/base/lib/j2eespecs/jsp-api-2.3.jar

ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.1.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/base/lib/j2eespecs/servlet-api-3.1.jar
 ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.5.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/ecj-4.5.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-jasper.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-jasper.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli-adapters.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli-adapters.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli.jar
   - copied unchanged from r1738902,
ofbiz/trunk/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli.jar
Removed:
 ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-2.2.jar

ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.2.jar

ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.0.jar
 ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.4.2.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-catalina-ha.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-catalina-tribes.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-catalina.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-jasper.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-tomcat-api.jar

ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-tomcat-coyote.jar

[jira] [Commented] (OFBIZ-7079) Extend Product entity and add serialized field

[Pierre Smits (JIRA)]

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

Pierre Smits commented on OFBIZ-7079:
-

e.g:
{code}





{code}
in InventoryForms.xml

> Extend Product entity and add serialized field
> --
>
> Key: OFBIZ-7079
> URL: https://issues.apache.org/jira/browse/OFBIZ-7079
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
>
> Extend Product entity and add serialized field to recognize product behavior. 
> Will use product.serialized at the time of receiving to identified inventory 
> item behavior.
> This will be setup time configuration, At the time of Product creation will 
> set this flag. 



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

[jira] [Commented] (OFBIZ-7079) Extend Product entity and add serialized field

[Pierre Smits (JIRA)]

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

Pierre Smits commented on OFBIZ-7079:
-

Yes, that way adopters could easily reuse functions in form widgets (and/or in 
freemarker templates) in other areas in product forms.

> Extend Product entity and add serialized field
> --
>
> Key: OFBIZ-7079
> URL: https://issues.apache.org/jira/browse/OFBIZ-7079
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
>
> Extend Product entity and add serialized field to recognize product behavior. 
> Will use product.serialized at the time of receiving to identified inventory 
> item behavior.
> This will be setup time configuration, At the time of Product creation will 
> set this flag. 



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

Re: svn commit: r1738904 - in /ofbiz/branches/release15.12: ./ framework/base/lib/j2eespecs/ framework/catalina/ framework/catalina/lib/ framework/catalina/src/org/ofbiz/catalina/container/ framework/

[Deepak Dixit]

Hi Jacques,

I think it would be useful to backport this to 14.12 releases.In this way
we will have less tomcat revisions to keep an eye on for vulnerability
fixes, and we will specialize in one version only so that our upgrade
effort will be smaller.



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

On Wed, Apr 13, 2016 at 1:13 PM,  wrote:

> Author: jleroux
> Date: Wed Apr 13 07:43:07 2016
> New Revision: 1738904
>
> URL: http://svn.apache.org/viewvc?rev=1738904=rev
> Log:
> "Applied fix from trunk for revision: 1738902  "
> 
> r1738902 | jleroux | 2016-04-13 09:40:25 +0200 (mer. 13 avr. 2016) | 4
> lignes
>
> A slightly modified patch from Chatree Srichart for "Upgrade Tomcat to
> 8.0.32" https://issues.apache.org/jira/browse/OFBIZ-6915
>
> jleroux: I simply changed the doc link in catalina ofbiz-component.xml
>
> 
>
>
> Added:
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-3.0.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/base/lib/j2eespecs/el-api-3.0.jar
>
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.3.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/base/lib/j2eespecs/jsp-api-2.3.jar
>
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.1.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/base/lib/j2eespecs/servlet-api-3.1.jar
> ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.5.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/ecj-4.5.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-ha.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina-tribes.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-catalina.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-catalina.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-jasper.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-jasper.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-api.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-coyote.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-jni.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util-scan.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-8.0.33-tomcat-util.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli-adapters.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli-adapters.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli.jar
>   - copied unchanged from r1738902,
> ofbiz/trunk/framework/catalina/lib/tomcat-extras-8.0.33-tomcat-juli.jar
> Removed:
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/el-api-2.2.jar
>
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/jsp-api-2.2.jar
>
> ofbiz/branches/release15.12/framework/base/lib/j2eespecs/servlet-api-3.0.jar
> ofbiz/branches/release15.12/framework/catalina/lib/ecj-4.4.2.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-catalina-ha.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-catalina-tribes.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-catalina.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-jasper.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-tomcat-api.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-tomcat-coyote.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-7.0.68-tomcat-util.jar
>
> ofbiz/branches/release15.12/framework/catalina/lib/tomcat-extras-7.0.68-tomcat-juli-adapters.jar
>
> 

[jira] [Commented] (OFBIZ-7079) Extend Product entity and add serialized field

[Deepak Dixit (JIRA)]

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

Deepak Dixit commented on OFBIZ-7079:
-

Are you suggesting like we have Facility.defaultInventoryItemTypeId?

If yes I think its good idea to add Product.inventoryItemTypeId (as id field) 
instead of Product.serialized (as indicator)

> Extend Product entity and add serialized field
> --
>
> Key: OFBIZ-7079
> URL: https://issues.apache.org/jira/browse/OFBIZ-7079
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
>
> Extend Product entity and add serialized field to recognize product behavior. 
> Will use product.serialized at the time of receiving to identified inventory 
> item behavior.
> This will be setup time configuration, At the time of Product creation will 
> set this flag. 



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

[jira] [Commented] (OFBIZ-7079) Extend Product entity and add serialized field

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-7079:


Yes, in relation with the serialNumber field

> Extend Product entity and add serialized field
> --
>
> Key: OFBIZ-7079
> URL: https://issues.apache.org/jira/browse/OFBIZ-7079
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
>
> Extend Product entity and add serialized field to recognize product behavior. 
> Will use product.serialized at the time of receiving to identified inventory 
> item behavior.
> This will be setup time configuration, At the time of Product creation will 
> set this flag. 



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

[jira] [Commented] (OFBIZ-7079) Extend Product entity and add serialized field

[Pierre Smits (JIRA)]

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

Pierre Smits commented on OFBIZ-7079:
-

Ahh. I guess you meant to say how inventory management is done: serialized or 
not. That field is already defined in the entity model, but not for the product 
definition and it is called 'inventoryItemTypeId'.

And is used in several places. 

I suggest to reuse the name to achieve a sense of coherence.

> Extend Product entity and add serialized field
> --
>
> Key: OFBIZ-7079
> URL: https://issues.apache.org/jira/browse/OFBIZ-7079
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
>
> Extend Product entity and add serialized field to recognize product behavior. 
> Will use product.serialized at the time of receiving to identified inventory 
> item behavior.
> This will be setup time configuration, At the time of Product creation will 
> set this flag. 



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

[jira] [Commented] (OFBIZ-7080) ECommerce - UI Issue on Change Password Screen Title

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-7080:


Thanks Pranay,

Backported in R13.07 at r1744679

> ECommerce - UI Issue on Change Password Screen Title
> 
>
> Key: OFBIZ-7080
> URL: https://issues.apache.org/jira/browse/OFBIZ-7080
> Project: OFBiz
>  Issue Type: Bug
>Reporter: Chandan Khandelwal
>Assignee: Pranay Pandey
>Priority: Trivial
> Fix For: 14.12.01, 15.12.01, 13.07.04
>
> Attachments: OFBIZ-7080-1412.patch, OFBIZ-7080-1512 .patch, 
> OFBIZ-7080.patch
>
>
> Change password title is not showing properly on 
> http://demo-stable-ofbiz.apache.org/ecommerce/control/changepassword



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

[jira] [Updated] (OFBIZ-7080) ECommerce - UI Issue on Change Password Screen Title

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-7080:
---
Fix Version/s: (was: Upcoming Branch)
   13.07.04
   15.12.01
   14.12.01

> ECommerce - UI Issue on Change Password Screen Title
> 
>
> Key: OFBIZ-7080
> URL: https://issues.apache.org/jira/browse/OFBIZ-7080
> Project: OFBiz
>  Issue Type: Bug
>Reporter: Chandan Khandelwal
>Assignee: Pranay Pandey
>Priority: Trivial
> Fix For: 14.12.01, 15.12.01, 13.07.04
>
> Attachments: OFBIZ-7080-1412.patch, OFBIZ-7080-1512 .patch, 
> OFBIZ-7080.patch
>
>
> Change password title is not showing properly on 
> http://demo-stable-ofbiz.apache.org/ecommerce/control/changepassword



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