[jira] [Updated] (OFBIZ-8119) Character encoding issue found in file build.gradle
[ https://issues.apache.org/jira/browse/OFBIZ-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fumiyoshi.to updated OFBIZ-8119: Attachment: OFBIZ-8119_CharacterEncodingInBuildFile.patch > Character encoding issue found in file build.gradle > --- > > Key: OFBIZ-8119 > URL: https://issues.apache.org/jira/browse/OFBIZ-8119 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: Trunk > Environment: Window10 > java version "1.8.0_101" >Reporter: fumiyoshi.to >Priority: Minor > Attachments: OFBIZ-8119_CharacterEncodingInBuildFile.patch, > build-error.png > > > I cann't build ofbiz when I run gradlew. > I found utf-8 should be the default character encoding used by the comipiling > work. > eg. > def defaultEncoding = 'UTF-8' > tasks.withType(AbstractCompile)*.options*.encoding = defaultEncoding > tasks.withType(GroovyCompile)*.groovyOptions*.encoding = defaultEncoding -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8119) Character encoding issue found in file build.gradle
[ https://issues.apache.org/jira/browse/OFBIZ-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fumiyoshi.to updated OFBIZ-8119: Attachment: build-error.png > Character encoding issue found in file build.gradle > --- > > Key: OFBIZ-8119 > URL: https://issues.apache.org/jira/browse/OFBIZ-8119 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: Trunk > Environment: Window10 > java version "1.8.0_101" >Reporter: fumiyoshi.to >Priority: Minor > Attachments: build-error.png > > > I cann't build ofbiz when I run gradlew. > I found utf-8 should be the default character encoding used by the comipiling > work. > eg. > def defaultEncoding = 'UTF-8' > tasks.withType(AbstractCompile)*.options*.encoding = defaultEncoding > tasks.withType(GroovyCompile)*.groovyOptions*.encoding = defaultEncoding -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8119) Character encoding issue found in file build.gradle
fumiyoshi.to created OFBIZ-8119: --- Summary: Character encoding issue found in file build.gradle Key: OFBIZ-8119 URL: https://issues.apache.org/jira/browse/OFBIZ-8119 Project: OFBiz Issue Type: Bug Components: ALL APPLICATIONS Affects Versions: Trunk Environment: Window10 java version "1.8.0_101" Reporter: fumiyoshi.to Priority: Minor I cann't build ofbiz when I run gradlew. I found utf-8 should be the default character encoding used by the comipiling work. eg. def defaultEncoding = 'UTF-8' tasks.withType(AbstractCompile)*.options*.encoding = defaultEncoding tasks.withType(GroovyCompile)*.groovyOptions*.encoding = defaultEncoding -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8118) Consistent menu names
Tanmay Muley created OFBIZ-8118: --- Summary: Consistent menu names Key: OFBIZ-8118 URL: https://issues.apache.org/jira/browse/OFBIZ-8118 Project: OFBiz Issue Type: Improvement Reporter: Tanmay Muley Fix For: Trunk Menu-name should be in upper camel case as per best practice. There are few places where menu-names are in lower camel case. Need to fix these to maintain consistency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8117) Maximise the utilisation of common labels in various manufacturing forms
[ https://issues.apache.org/jira/browse/OFBIZ-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-8117: Attachment: OFBIZ-8117-manufacturing-forms.patch This patch addresses the issue. > Maximise the utilisation of common labels in various manufacturing forms > > > Key: OFBIZ-8117 > URL: https://issues.apache.org/jira/browse/OFBIZ-8117 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: labels, refactoring > Attachments: OFBIZ-8117-manufacturing-forms.patch > > > There are many forms that could benefit from the application of common > labels. This ticket addresses that issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8117) Maximise the utilisation of common labels in various manufacturing forms
Pierre Smits created OFBIZ-8117: --- Summary: Maximise the utilisation of common labels in various manufacturing forms Key: OFBIZ-8117 URL: https://issues.apache.org/jira/browse/OFBIZ-8117 Project: OFBiz Issue Type: Sub-task Components: manufacturing Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits There are many forms that could benefit from the application of common labels. This ticket addresses that issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7343) Geo Location functionality of facility contact information screen is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-7343. --- Resolution: Fixed Fix Version/s: (was: Trunk) Release Branch 14.12 Release Branch 15.12 > Geo Location functionality of facility contact information screen is not > working > - > > Key: OFBIZ-7343 > URL: https://issues.apache.org/jira/browse/OFBIZ-7343 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Deepak Dixit > Fix For: Upcoming Branch, Release Branch 15.12, Release Branch > 14.12 > > Attachments: OFBIZ-7343.patch > > > Steps to regenerate : > 1) Log in into facility application. > 2) Select any facility and go to Contact Information. > 3) Click on "Geo Location" button under Postal Address section. > 4) In a new modal window is open with following error. > "ERROR rendering error page [/error/error.jsp], but here is the error text: > org.ofbiz.webapp.control.RequestHandlerException: Unknown request > [geoLocation]; this request does not exist or cannot be called directly. " -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7343) Geo Location functionality of facility contact information screen is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459448#comment-15459448 ] Deepak Dixit commented on OFBIZ-7343: - Thanks Pawan for your contribution Your Patch has been committed at Trunk at r#1759024 15.12 at r#1759028 14.12 at r#1759029 > Geo Location functionality of facility contact information screen is not > working > - > > Key: OFBIZ-7343 > URL: https://issues.apache.org/jira/browse/OFBIZ-7343 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Deepak Dixit > Fix For: Trunk, Upcoming Branch > > Attachments: OFBIZ-7343.patch > > > Steps to regenerate : > 1) Log in into facility application. > 2) Select any facility and go to Contact Information. > 3) Click on "Geo Location" button under Postal Address section. > 4) In a new modal window is open with following error. > "ERROR rendering error page [/error/error.jsp], but here is the error text: > org.ofbiz.webapp.control.RequestHandlerException: Unknown request > [geoLocation]; this request does not exist or cannot be called directly. " -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7343) Geo Location functionality of facility contact information screen is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459418#comment-15459418 ] Deepak Dixit commented on OFBIZ-7343: - Hi Jacques, I think we can use ?html escape sequence, its deprecated and Auto-escaping and output formats should be used but as we did not enabled the auto-escaping so for this case I am using html for escaping. > Geo Location functionality of facility contact information screen is not > working > - > > Key: OFBIZ-7343 > URL: https://issues.apache.org/jira/browse/OFBIZ-7343 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Deepak Dixit > Fix For: Trunk, Upcoming Branch > > Attachments: OFBIZ-7343.patch > > > Steps to regenerate : > 1) Log in into facility application. > 2) Select any facility and go to Contact Information. > 3) Click on "Geo Location" button under Postal Address section. > 4) In a new modal window is open with following error. > "ERROR rendering error page [/error/error.jsp], but here is the error text: > org.ofbiz.webapp.control.RequestHandlerException: Unknown request > [geoLocation]; this request does not exist or cannot be called directly. " -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459386#comment-15459386 ] Nicolas Malin commented on OFBIZ-7611: -- now I think also ;) It's nice to have this functionality for each entity, it's great improvement to homogenize this as best practice rule. > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7611.patch, OFBIZ-7611.patch > > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8050) No need to show "---" after selecting any option from drop-down in Find Screens.
[
https://issues.apache.org/jira/browse/OFBIZ-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459366#comment-15459366
]
Deepak Dixit commented on OFBIZ-8050:
-
Thanks Renuka for your contribution
Your patch has been committed at Trunk at r#1759018
> No need to show "---" after selecting any option from drop-down in Find
> Screens.
>
>
> Key: OFBIZ-8050
> URL: https://issues.apache.org/jira/browse/OFBIZ-8050
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Renuka Srishti
>Assignee: Deepak Dixit
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-8050.patch
>
>
> {noformat}
> At some places in drop-down it shows empty title. After selecting any option
> and perform search, it add '---' in drop-down list. If you choose "---" and
> perform search it will show the previous selected value.So no need to show
> "---" option.
> My preference is to remove "---" option.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8050) No need to show "---" after selecting any option from drop-down in Find Screens.
[
https://issues.apache.org/jira/browse/OFBIZ-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Dixit reassigned OFBIZ-8050:
---
Assignee: Deepak Dixit (was: Renuka Srishti)
> No need to show "---" after selecting any option from drop-down in Find
> Screens.
>
>
> Key: OFBIZ-8050
> URL: https://issues.apache.org/jira/browse/OFBIZ-8050
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Renuka Srishti
>Assignee: Deepak Dixit
> Attachments: OFBIZ-8050.patch
>
>
> {noformat}
> At some places in drop-down it shows empty title. After selecting any option
> and perform search, it add '---' in drop-down list. If you choose "---" and
> perform search it will show the previous selected value.So no need to show
> "---" option.
> My preference is to remove "---" option.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7602) Hide product sub menus while creating new product
[ https://issues.apache.org/jira/browse/OFBIZ-7602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459346#comment-15459346 ] Deepak Dixit commented on OFBIZ-7602: - Thanks Nameet for reporting the issue. This has been fixed at Trunk at r#1759014 15.12 at r#1759015 14.12 at r#1759017 > Hide product sub menus while creating new product > - > > Key: OFBIZ-7602 > URL: https://issues.apache.org/jira/browse/OFBIZ-7602 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Deepak Dixit >Priority: Minor > Fix For: Release Branch 14.12, Upcoming Branch, Release Branch > 15.12 > > Attachments: CreateProduct.png > > > 1. Open Catalog Manager > 2. Click "New Product" > 3. All the Sub Menus are visible. > If we navigate to any sub menu (say: Content) and try to create it, system > returns error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459302#comment-15459302 ] Deepak Dixit commented on OFBIZ-7611: - I think we can create new sub-ticket to use new concept. > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7611.patch, OFBIZ-7611.patch > > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7616) Add "changeByUserLoginId" field for PartyStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-7616. --- Resolution: Done Fix Version/s: Upcoming Branch > Add "changeByUserLoginId" field for PartyStatus > --- > > Key: OFBIZ-7616 > URL: https://issues.apache.org/jira/browse/OFBIZ-7616 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Deepak Dixit > Fix For: Upcoming Branch > > Attachments: OFBIZ-7616.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7616) Add "changeByUserLoginId" field for PartyStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459299#comment-15459299 ] Deepak Dixit commented on OFBIZ-7616: - Thanks Nameet for your contribution, your patch has been committed at r#1759012 > Add "changeByUserLoginId" field for PartyStatus > --- > > Key: OFBIZ-7616 > URL: https://issues.apache.org/jira/browse/OFBIZ-7616 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Deepak Dixit > Attachments: OFBIZ-7616.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7251) Update Payment Gateway Config data for Payment Gateway Authorize.net
[ https://issues.apache.org/jira/browse/OFBIZ-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459274#comment-15459274 ] Deepak Dixit commented on OFBIZ-7251: - Thanks Avanindra for your contribution Your patch has been committed at Trunk at r#1759005 15.12 at r#1759007 14.12 at r#1759008 > Update Payment Gateway Config data for Payment Gateway Authorize.net > - > > Key: OFBIZ-7251 > URL: https://issues.apache.org/jira/browse/OFBIZ-7251 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Avnindra Sharma >Assignee: Deepak Dixit >Priority: Minor > Attachments: OFBIZ-7251.patch > > > As per the https://community.developer.authorize.net, the transactionUrl has > been updated from https://certification.authorize.net/gateway/transact.dll to > https://test.authorize.net/gateway/transact.dll -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7251) Update Payment Gateway Config data for Payment Gateway Authorize.net
[ https://issues.apache.org/jira/browse/OFBIZ-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reassigned OFBIZ-7251: --- Assignee: Deepak Dixit > Update Payment Gateway Config data for Payment Gateway Authorize.net > - > > Key: OFBIZ-7251 > URL: https://issues.apache.org/jira/browse/OFBIZ-7251 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Avnindra Sharma >Assignee: Deepak Dixit >Priority: Minor > Attachments: OFBIZ-7251.patch > > > As per the https://community.developer.authorize.net, the transactionUrl has > been updated from https://certification.authorize.net/gateway/transact.dll to > https://test.authorize.net/gateway/transact.dll -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7986) Warning related to 'InventoryItemAndLocation' entity on server start
[ https://issues.apache.org/jira/browse/OFBIZ-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-7986. --- Resolution: Fixed > Warning related to 'InventoryItemAndLocation' entity on server start > - > > Key: OFBIZ-7986 > URL: https://issues.apache.org/jira/browse/OFBIZ-7986 > Project: OFBiz > Issue Type: Bug >Reporter: Deepak Nigam >Assignee: Deepak Dixit >Priority: Trivial > Fix For: Upcoming Branch, Release Branch 15.12, Release Branch > 14.12 > > Attachments: OFBIZ-7986.patch > > > On starting ofbiz server following error is coming at console : > 2016-08-27 11:53:54,084 |delegator-startup-1 |ModelViewEntity |I| > [InventoryItemAndLocation]: Throwing out field alias in view entity because > one already exists with the alias name [inventoryItemTypeId] and field name > [PR(Product).inventoryItemTypeId], existing field name is > [II.inventoryItemTypeId] 2016-08-27 11:53:54,088 |delegator-startup-1 > |ModelViewEntity |I| [ProductInventoryItem]: Throwing out field alias in view > entity because one already exists with the alias name [inventoryItemTypeId] > and field name [II(InventoryItem).inventoryItemTypeId], existing field name > is [PR.inventoryItemTypeId] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7986) Warning related to 'InventoryItemAndLocation' entity on server start
[ https://issues.apache.org/jira/browse/OFBIZ-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459260#comment-15459260 ] Deepak Dixit commented on OFBIZ-7986: - This has been fixed at Trunk at r#1759002 15.12 at r#1759003 14.12 at r#1759004 > Warning related to 'InventoryItemAndLocation' entity on server start > - > > Key: OFBIZ-7986 > URL: https://issues.apache.org/jira/browse/OFBIZ-7986 > Project: OFBiz > Issue Type: Bug >Reporter: Deepak Nigam >Assignee: Deepak Dixit >Priority: Trivial > Fix For: Release Branch 14.12, Upcoming Branch, Release Branch > 15.12 > > Attachments: OFBIZ-7986.patch > > > On starting ofbiz server following error is coming at console : > 2016-08-27 11:53:54,084 |delegator-startup-1 |ModelViewEntity |I| > [InventoryItemAndLocation]: Throwing out field alias in view entity because > one already exists with the alias name [inventoryItemTypeId] and field name > [PR(Product).inventoryItemTypeId], existing field name is > [II.inventoryItemTypeId] 2016-08-27 11:53:54,088 |delegator-startup-1 > |ModelViewEntity |I| [ProductInventoryItem]: Throwing out field alias in view > entity because one already exists with the alias name [inventoryItemTypeId] > and field name [II(InventoryItem).inventoryItemTypeId], existing field name > is [PR.inventoryItemTypeId] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-7986) Warning related to 'InventoryItemAndLocation' entity on server start
[ https://issues.apache.org/jira/browse/OFBIZ-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reopened OFBIZ-7986: - Assignee: Deepak Dixit (was: Jacques Le Roux) Reopening issue, there is typo in field name. Also need to fix warning for ProductInventoryItem entity. > Warning related to 'InventoryItemAndLocation' entity on server start > - > > Key: OFBIZ-7986 > URL: https://issues.apache.org/jira/browse/OFBIZ-7986 > Project: OFBiz > Issue Type: Bug >Reporter: Deepak Nigam >Assignee: Deepak Dixit >Priority: Trivial > Fix For: Release Branch 14.12, Upcoming Branch, Release Branch > 15.12 > > Attachments: OFBIZ-7986.patch > > > On starting ofbiz server following error is coming at console : > 2016-08-27 11:53:54,084 |delegator-startup-1 |ModelViewEntity |I| > [InventoryItemAndLocation]: Throwing out field alias in view entity because > one already exists with the alias name [inventoryItemTypeId] and field name > [PR(Product).inventoryItemTypeId], existing field name is > [II.inventoryItemTypeId] 2016-08-27 11:53:54,088 |delegator-startup-1 > |ModelViewEntity |I| [ProductInventoryItem]: Throwing out field alias in view > entity because one already exists with the alias name [inventoryItemTypeId] > and field name [II(InventoryItem).inventoryItemTypeId], existing field name > is [PR.inventoryItemTypeId] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7390) Print PDF functionality throws exception on Inventory Average Cost screen
[ https://issues.apache.org/jira/browse/OFBIZ-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit updated OFBIZ-7390: Component/s: product > Print PDF functionality throws exception on Inventory Average Cost screen > - > > Key: OFBIZ-7390 > URL: https://issues.apache.org/jira/browse/OFBIZ-7390 > Project: OFBiz > Issue Type: Bug > Components: product >Reporter: Avnindra Sharma >Assignee: Deepak Dixit > Fix For: Release Branch 14.12, Upcoming Branch, Release Branch > 15.12 > > Attachments: OFBIZ-7390.patch > > > Navigate to Inventory Average Cost screen, print pdf button throws exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7390) Print PDF functionality throws exception on Inventory Average Cost screen
[ https://issues.apache.org/jira/browse/OFBIZ-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459228#comment-15459228 ] Deepak Dixit commented on OFBIZ-7390: - Thanks Avnindra for your contribution. Your patch has been committed at Trunk at r#1758997 15.12 at r#1758998 14.12 at r#1759000 > Print PDF functionality throws exception on Inventory Average Cost screen > - > > Key: OFBIZ-7390 > URL: https://issues.apache.org/jira/browse/OFBIZ-7390 > Project: OFBiz > Issue Type: Bug >Reporter: Avnindra Sharma >Assignee: Deepak Dixit > Attachments: OFBIZ-7390.patch > > > Navigate to Inventory Average Cost screen, print pdf button throws exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7956) Updating various Dutch labels in WorkEffortUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459224#comment-15459224 ] Pierre Smits commented on OFBIZ-7956: - Thanks Jacques. > Updating various Dutch labels in WorkEffortUiLabels.xml > --- > > Key: OFBIZ-7956 > URL: https://issues.apache.org/jira/browse/OFBIZ-7956 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Hans Bakker > Fix For: Upcoming Branch > > Attachments: OFBIZ-7956-WorkEffortUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7011) Failure in Payment Capture process when ERROR is returned in referenceNum in paymentGatewayResponse
[ https://issues.apache.org/jira/browse/OFBIZ-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459156#comment-15459156 ] Jacques Le Roux commented on OFBIZ-7011: Thanks Deepak! > Failure in Payment Capture process when ERROR is returned in referenceNum in > paymentGatewayResponse > --- > > Key: OFBIZ-7011 > URL: https://issues.apache.org/jira/browse/OFBIZ-7011 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Avnindra Sharma >Assignee: Deepak Dixit >Priority: Minor > Fix For: Release Branch 14.12, Upcoming Branch, Release Branch > 15.12 > > Attachments: OFBIZ-7011.patch > > > When there is slow/no response from authorize.net while captuing payment, > corrupt data is prepaed in paymentGatewayResponse with "ERROR" in > refereneNum. > So while capturing the payment again it returns error as it finds the payment > gateway response for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7390) Print PDF functionality throws exception on Inventory Average Cost screen
[ https://issues.apache.org/jira/browse/OFBIZ-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reassigned OFBIZ-7390: --- Assignee: Deepak Dixit (was: Avnindra Sharma) > Print PDF functionality throws exception on Inventory Average Cost screen > - > > Key: OFBIZ-7390 > URL: https://issues.apache.org/jira/browse/OFBIZ-7390 > Project: OFBiz > Issue Type: Bug >Reporter: Avnindra Sharma >Assignee: Deepak Dixit > Attachments: OFBIZ-7390.patch > > > Navigate to Inventory Average Cost screen, print pdf button throws exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-8115) Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse)
[ https://issues.apache.org/jira/browse/OFBIZ-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-8115: Reopening, there maybe still an issue with the point 2 > Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse) > - > > Key: OFBIZ-8115 > URL: https://issues.apache.org/jira/browse/OFBIZ-8115 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > At r1758927 I tried to fixe a bunch of closes missing, reported as warnings > in Eclipse > Jacopo noticed and reported on dev ML > http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: > # you are adding a close statement to code that already had the close > statement in the "finally" block; your modification actually introduces a > code pattern that is not correct (if an exception is thrown your close > statement are not executed) > # I suspect that you are closing the socket connection too early in > PcChargeApi > So I reverted r1758927 to check the issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7011) Failure in Payment Capture process when ERROR is returned in referenceNum in paymentGatewayResponse
[ https://issues.apache.org/jira/browse/OFBIZ-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-7011. --- Resolution: Fixed Fix Version/s: Release Branch 14.12 Release Branch 15.12 Upcoming Branch > Failure in Payment Capture process when ERROR is returned in referenceNum in > paymentGatewayResponse > --- > > Key: OFBIZ-7011 > URL: https://issues.apache.org/jira/browse/OFBIZ-7011 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Avnindra Sharma >Assignee: Deepak Dixit >Priority: Minor > Fix For: Upcoming Branch, Release Branch 15.12, Release Branch > 14.12 > > Attachments: OFBIZ-7011.patch > > > When there is slow/no response from authorize.net while captuing payment, > corrupt data is prepaed in paymentGatewayResponse with "ERROR" in > refereneNum. > So while capturing the payment again it returns error as it finds the payment > gateway response for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7011) Failure in Payment Capture process when ERROR is returned in referenceNum in paymentGatewayResponse
[ https://issues.apache.org/jira/browse/OFBIZ-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459134#comment-15459134 ] Deepak Dixit commented on OFBIZ-7011: - This has been backported at 15.12 at r#1758994 14.12 at r#1758995 > Failure in Payment Capture process when ERROR is returned in referenceNum in > paymentGatewayResponse > --- > > Key: OFBIZ-7011 > URL: https://issues.apache.org/jira/browse/OFBIZ-7011 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Avnindra Sharma >Assignee: Deepak Dixit >Priority: Minor > Fix For: Release Branch 14.12, Upcoming Branch, Release Branch > 15.12 > > Attachments: OFBIZ-7011.patch > > > When there is slow/no response from authorize.net while captuing payment, > corrupt data is prepaed in paymentGatewayResponse with "ERROR" in > refereneNum. > So while capturing the payment again it returns error as it finds the payment > gateway response for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8108) Scrum: Consistent form name
[ https://issues.apache.org/jira/browse/OFBIZ-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-8108: Attachment: OFBIZ-8108.patch Missed some files in previous patch. Uploading the updated patch with changes. > Scrum: Consistent form name > --- > > Key: OFBIZ-8108 > URL: https://issues.apache.org/jira/browse/OFBIZ-8108 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/scrum >Reporter: Tanmay Muley >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8108.patch, OFBIZ-8108.patch > > > Change all form names to upper camel case for consistency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8099) Common: Consistent form name
[ https://issues.apache.org/jira/browse/OFBIZ-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-8099: Attachment: OFBIZ-8099.patch Missed some files in previous patch. Uploading the updated patch with changes. > Common: Consistent form name > > > Key: OFBIZ-8099 > URL: https://issues.apache.org/jira/browse/OFBIZ-8099 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Tanmay Muley >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8099.patch, OFBIZ-8099.patch, OFBIZ-8099.patch > > > Change all form names to upper camel case for consistency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8090) Workeffort: Consistent form name
[ https://issues.apache.org/jira/browse/OFBIZ-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-8090: Attachment: OFBIZ-8090.patch Missed some files in previous patch. Uploading the updated patch with changes. > Workeffort: Consistent form name > > > Key: OFBIZ-8090 > URL: https://issues.apache.org/jira/browse/OFBIZ-8090 > Project: OFBiz > Issue Type: Sub-task > Components: workeffort >Reporter: Tanmay Muley >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8090.patch, OFBIZ-8090.patch > > > Change all form names to upper camel case for consistency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8089) Product: Consistent form name
[ https://issues.apache.org/jira/browse/OFBIZ-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-8089: Attachment: OFBIZ-8089.patch Missed some files in previous patch. Uploading the updated patch with changes. > Product: Consistent form name > - > > Key: OFBIZ-8089 > URL: https://issues.apache.org/jira/browse/OFBIZ-8089 > Project: OFBiz > Issue Type: Sub-task > Components: party >Reporter: Tanmay Muley >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8089.patch, OFBIZ-8089.patch > > > Change all form names to upper camel case for consistency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8088) Party: Consistent form name
[ https://issues.apache.org/jira/browse/OFBIZ-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-8088: Attachment: OFBIZ-8088.patch Missed some files in previous patch. Uploading the updated patch with changes. > Party: Consistent form name > --- > > Key: OFBIZ-8088 > URL: https://issues.apache.org/jira/browse/OFBIZ-8088 > Project: OFBiz > Issue Type: Sub-task > Components: party >Reporter: Tanmay Muley >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8088.patch, OFBIZ-8088.patch > > > Change all form names to upper camel case for consistency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7956) Updating various Dutch labels in WorkEffortUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7956. -- Resolution: Done Assignee: Hans Bakker (was: Pierre Smits) Fix Version/s: Upcoming Branch Thanks Pierre, Your patch is in trunk at revision: 1758991 I let the last review to Hans (I don't know Dutch) > Updating various Dutch labels in WorkEffortUiLabels.xml > --- > > Key: OFBIZ-7956 > URL: https://issues.apache.org/jira/browse/OFBIZ-7956 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Hans Bakker > Fix For: Upcoming Branch > > Attachments: OFBIZ-7956-WorkEffortUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7969) Enable adding a content to an agreement
[ https://issues.apache.org/jira/browse/OFBIZ-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458928#comment-15458928 ] Leila Mekika commented on OFBIZ-7969: - Hi Deepak, Sorry I miss this one. Here is a new version of the patch > Enable adding a content to an agreement > --- > > Key: OFBIZ-7969 > URL: https://issues.apache.org/jira/browse/OFBIZ-7969 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-7969.patch, OFBIZ-7969_V2 .patch, OFBIZ-7969_V3 > .patch, OFBIZ-7969_V3 .patch > > > This add a screen in accounting component to allow uploading a file or attach > an existing content to an agreement. This can be useful to attach agreement > related contract or files. > To test this functionnality, you need to reload seed data, create an > agreement and go to page : > http://localhost:8080/accounting/control/EditAgreementContents?agreementId= -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7969) Enable adding a content to an agreement
[ https://issues.apache.org/jira/browse/OFBIZ-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-7969: Attachment: OFBIZ-7969_V3 .patch > Enable adding a content to an agreement > --- > > Key: OFBIZ-7969 > URL: https://issues.apache.org/jira/browse/OFBIZ-7969 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-7969.patch, OFBIZ-7969_V2 .patch, OFBIZ-7969_V3 > .patch, OFBIZ-7969_V3 .patch > > > This add a screen in accounting component to allow uploading a file or attach > an existing content to an agreement. This can be useful to attach agreement > related contract or files. > To test this functionnality, you need to reload seed data, create an > agreement and go to page : > http://localhost:8080/accounting/control/EditAgreementContents?agreementId= -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8116) Add tasks from diffrent project on the same invoice
[ https://issues.apache.org/jira/browse/OFBIZ-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Montalbano Florian updated OFBIZ-8116: -- Attachment: OFBIZ-8116.patch Here is a patch to enable this improvement. On the page https://localhost:8443/projectmgr/control/projectBilling?projectId=9000 , there is a new form which can be used to add time to an invoice selected from a drop-down. The code is heavily inspired from already existent form and service. This is a fully optionnal functionnality. > Add tasks from diffrent project on the same invoice > --- > > Key: OFBIZ-8116 > URL: https://issues.apache.org/jira/browse/OFBIZ-8116 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/projectmgr >Affects Versions: Trunk >Reporter: Montalbano Florian > Labels: billing, hours, invoice, project > Attachments: OFBIZ-8116.patch > > > Some client may want a unique invoice billing time from several project. > We can achieve that by allowing the user to select an invoice wich can be > completed on the screen > https://localhost:8443/projectmgr/control/projectBilling?projectId=9000 . > To keep integrity, this invoice needs to be : > - at status INVOICE_IN_PROGRESS > - the party to bill must be the same for the two project > This is a first step to enable billing Scrum project an Project on the same > invoice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8116) Add tasks from diffrent project on the same invoice
Montalbano Florian created OFBIZ-8116: - Summary: Add tasks from diffrent project on the same invoice Key: OFBIZ-8116 URL: https://issues.apache.org/jira/browse/OFBIZ-8116 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Trunk Reporter: Montalbano Florian Some client may want a unique invoice billing time from several project. We can achieve that by allowing the user to select an invoice wich can be completed on the screen https://localhost:8443/projectmgr/control/projectBilling?projectId=9000 . To keep integrity, this invoice needs to be : - at status INVOICE_IN_PROGRESS - the party to bill must be the same for the two project This is a first step to enable billing Scrum project an Project on the same invoice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8004) Add UI labels for success / error messages in solr component
[ https://issues.apache.org/jira/browse/OFBIZ-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-8004: Attachment: OFBIZ-8004.patch Here is the updated patch. > Add UI labels for success / error messages in solr component > > > Key: OFBIZ-8004 > URL: https://issues.apache.org/jira/browse/OFBIZ-8004 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/solr >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-8004.patch, OFBIZ-8004.patch > > > Add UI labels for success / error messages in java files of solr component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8011) Add UI labels for success / error messages in product component
[ https://issues.apache.org/jira/browse/OFBIZ-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-8011: Attachment: OFBIZ-8011.patch Here is the updated patch. > Add UI labels for success / error messages in product component > --- > > Key: OFBIZ-8011 > URL: https://issues.apache.org/jira/browse/OFBIZ-8011 > Project: OFBiz > Issue Type: Sub-task > Components: product >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-8011.patch, OFBIZ-8011.patch > > > Add UI labels for success / error messages in java files of product component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7980) Add UI labels for success / error messages in common component
[ https://issues.apache.org/jira/browse/OFBIZ-7980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7980: Attachment: OFBIZ-7980.patch Here is the updated patch. > Add UI labels for success / error messages in common component > -- > > Key: OFBIZ-7980 > URL: https://issues.apache.org/jira/browse/OFBIZ-7980 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7980.patch, OFBIZ-7980.patch > > > Add UI labels for success / error messages in java files of common component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8002) Add UI labels for success / error messages in marketing component
[ https://issues.apache.org/jira/browse/OFBIZ-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-8002: Attachment: OFBIZ-8002.patch Here is the updated patch. > Add UI labels for success / error messages in marketing component > - > > Key: OFBIZ-8002 > URL: https://issues.apache.org/jira/browse/OFBIZ-8002 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-8002.patch, OFBIZ-8002.patch > > > Add UI labels for success / error messages in java files of marketing > component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7999) Add UI labels for success / error messages in workeffort component
[ https://issues.apache.org/jira/browse/OFBIZ-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7999: Attachment: OFBIZ-7999.patch Here is the updated patch. > Add UI labels for success / error messages in workeffort component > -- > > Key: OFBIZ-7999 > URL: https://issues.apache.org/jira/browse/OFBIZ-7999 > Project: OFBiz > Issue Type: Sub-task > Components: workeffort >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7999.patch, OFBIZ-7999.patch > > > Add UI labels for success / error messages in java files of workeffort > component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7998) Add UI labels for success / error messages in service component
[ https://issues.apache.org/jira/browse/OFBIZ-7998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7998: Attachment: OFBIZ-7998.patch Here is the updated patch. > Add UI labels for success / error messages in service component > --- > > Key: OFBIZ-7998 > URL: https://issues.apache.org/jira/browse/OFBIZ-7998 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7998.patch, OFBIZ-7998.patch > > > Add UI labels for success / error messages in java files of service component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7996) Add UI labels for success / error messages in party component
[ https://issues.apache.org/jira/browse/OFBIZ-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7996: Attachment: OFBIZ-7996.patch Here is the updated patch. > Add UI labels for success / error messages in party component > - > > Key: OFBIZ-7996 > URL: https://issues.apache.org/jira/browse/OFBIZ-7996 > Project: OFBiz > Issue Type: Sub-task > Components: party >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7996.patch, OFBIZ-7996.patch > > > Add UI labels for success / error messages in java files of party component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7994) Add UI labels for success / error messages in order component
[ https://issues.apache.org/jira/browse/OFBIZ-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7994: Attachment: OFBIZ-7994.patch Here is the updated patch. > Add UI labels for success / error messages in order component > - > > Key: OFBIZ-7994 > URL: https://issues.apache.org/jira/browse/OFBIZ-7994 > Project: OFBiz > Issue Type: Sub-task > Components: order >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7994.patch, OFBIZ-7994.patch > > > Add UI labels for success / error messages in java files of order component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7991) Add UI labels for success / error messages in example component
[ https://issues.apache.org/jira/browse/OFBIZ-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7991: Attachment: OFBIZ-7991.patch Here is the updated patch. > Add UI labels for success / error messages in example component > --- > > Key: OFBIZ-7991 > URL: https://issues.apache.org/jira/browse/OFBIZ-7991 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/example >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7991.patch, OFBIZ-7991.patch > > > Add UI labels for success / error messages in java files of example component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7993) Add UI labels for success / error messages in oagis component
[ https://issues.apache.org/jira/browse/OFBIZ-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7993: Attachment: OFBIZ-7993.patch Here is the updated patch. > Add UI labels for success / error messages in oagis component > - > > Key: OFBIZ-7993 > URL: https://issues.apache.org/jira/browse/OFBIZ-7993 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/oagis >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7993.patch, OFBIZ-7993.patch > > > Add UI labels for success / error messages in java files of oagis component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7990) Add UI labels for success / error messages in ebay component
[ https://issues.apache.org/jira/browse/OFBIZ-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7990: Attachment: OFBIZ-7990.patch Here is the updated patch. > Add UI labels for success / error messages in ebay component > > > Key: OFBIZ-7990 > URL: https://issues.apache.org/jira/browse/OFBIZ-7990 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/ebay >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7990.patch, OFBIZ-7990.patch > > > Add UI labels for success / error messages in java files of ebay component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7987) Add UI labels for success / error messages in content component
[ https://issues.apache.org/jira/browse/OFBIZ-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7987: Attachment: OFBIZ-7987.patch Here is the updated patch. > Add UI labels for success / error messages in content component > --- > > Key: OFBIZ-7987 > URL: https://issues.apache.org/jira/browse/OFBIZ-7987 > Project: OFBiz > Issue Type: Sub-task > Components: content >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7987.patch, OFBIZ-7987.patch > > > Add UI labels for success / error messages in java files of content component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7726) Add UI labels for success / error messages in accounting component
[ https://issues.apache.org/jira/browse/OFBIZ-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7726: Attachment: OFBIZ-7726.patch Here is the updated patch. > Add UI labels for success / error messages in accounting component > -- > > Key: OFBIZ-7726 > URL: https://issues.apache.org/jira/browse/OFBIZ-7726 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Tanmay Muley >Assignee: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7726.patch, OFBIZ-7726.patch > > > Add UI labels for success / error messages in java files of accounting > component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7979) Add UI labels for success / error messages in birt component
[ https://issues.apache.org/jira/browse/OFBIZ-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanmay Muley updated OFBIZ-7979: Attachment: OFBIZ-7979.patch Here is the updated patch. > Add UI labels for success / error messages in birt component > > > Key: OFBIZ-7979 > URL: https://issues.apache.org/jira/browse/OFBIZ-7979 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/birt >Reporter: Tanmay Muley >Priority: Minor > Attachments: OFBIZ-7979.patch, OFBIZ-7979.patch > > > Add UI labels for success / error messages in java files of birt component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-8115) Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse)
[ https://issues.apache.org/jira/browse/OFBIZ-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-8115. -- Resolution: Fixed > Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse) > - > > Key: OFBIZ-8115 > URL: https://issues.apache.org/jira/browse/OFBIZ-8115 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > At r1758927 I tried to fixe a bunch of closes missing, reported as warnings > in Eclipse > Jacopo noticed and reported on dev ML > http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: > # you are adding a close statement to code that already had the close > statement in the "finally" block; your modification actually introduces a > code pattern that is not correct (if an exception is thrown your close > statement are not executed) > # I suspect that you are closing the socket connection too early in > PcChargeApi > So I reverted r1758927 to check the issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-8115) Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse)
[ https://issues.apache.org/jira/browse/OFBIZ-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458508#comment-15458508 ] Jacques Le Roux edited comment on OFBIZ-8115 at 9/2/16 1:27 PM: *Point 1)* The best option when closing resources (which implement AutoCloseable) is actually to use the try-with-resources statement. At least when there are no performance issues. I have fixed the issue (only in DatabaseUtil.java) this way because * there are not performance issues, we anyway create a Statement in both cases, we don't reuse one. * The finally part is cleaner I have also used the try-with-resources statement in other places where it fitted. There is only 1 place where I was undecided: ScriptUtil.parseScript() which uses GroovyUtil.parseClass(). I put only a logError() there and returned null. I did not throw an IOException because else it spreads everywhere in FlexibleStringExpander. Here introducing Optional would be better, but I have no time for that today. Done at revision: 1758951 was (Author: jacques.le.roux): *Point 1)* The best option when closing resources (which implement AutoCloseable) is actually to use the try-with-resources statement. At least when there are no performance issues. I have fixed the issue (only in DatabaseUtil.java) this way because * there are not performance issues, we anyway create a Statement in both cases, we don't reuse one. * The finally part is cleaner I have also used the try-with-resources statement in other places where it fitted. There is only 1 place where I was undecided: ScriptUtil.parseScript() which uses GroovyUtil.parseClass(). I put only a logError() there and returned null. I did not throw an IOException because else it spreads everywhere in FlexibleStringExpander. Here introducing Optional would be better, but I have no time or that today. Done at revision: 1758951 > Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse) > - > > Key: OFBIZ-8115 > URL: https://issues.apache.org/jira/browse/OFBIZ-8115 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > At r1758927 I tried to fixe a bunch of closes missing, reported as warnings > in Eclipse > Jacopo noticed and reported on dev ML > http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: > # you are adding a close statement to code that already had the close > statement in the "finally" block; your modification actually introduces a > code pattern that is not correct (if an exception is thrown your close > statement are not executed) > # I suspect that you are closing the socket connection too early in > PcChargeApi > So I reverted r1758927 to check the issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-8115) Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse)
[ https://issues.apache.org/jira/browse/OFBIZ-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458254#comment-15458254 ] Jacques Le Roux edited comment on OFBIZ-8115 at 9/2/16 11:38 AM: - I see no problem with the point 2, but the point 1 is more complex (I wonder why Eclipse would be wrong) and I'll double check all details... was (Author: jacques.le.roux): I see not problem with the point 2, but the point 1 is more complex (I wonder why Eclipse would be wrong) and I'll double check all details... > Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse) > - > > Key: OFBIZ-8115 > URL: https://issues.apache.org/jira/browse/OFBIZ-8115 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > At r1758927 I tried to fixe a bunch of closes missing, reported as warnings > in Eclipse > Jacopo noticed and reported on dev ML > http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: > # you are adding a close statement to code that already had the close > statement in the "finally" block; your modification actually introduces a > code pattern that is not correct (if an exception is thrown your close > statement are not executed) > # I suspect that you are closing the socket connection too early in > PcChargeApi > So I reverted r1758927 to check the issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8115) Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse)
[ https://issues.apache.org/jira/browse/OFBIZ-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458254#comment-15458254 ] Jacques Le Roux commented on OFBIZ-8115: I see not problem with the point 2, but the point 1 is more complex (I wonder why Eclipse would be wrong) and I'll double check all details... > Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse) > - > > Key: OFBIZ-8115 > URL: https://issues.apache.org/jira/browse/OFBIZ-8115 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > At r1758927 I tried to fixe a bunch of closes missing, reported as warnings > in Eclipse > Jacopo noticed and reported on dev ML > http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: > # you are adding a close statement to code that already had the close > statement in the "finally" block; your modification actually introduces a > code pattern that is not correct (if an exception is thrown your close > statement are not executed) > # I suspect that you are closing the socket connection too early in > PcChargeApi > So I reverted r1758927 to check the issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8115) Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse)
[ https://issues.apache.org/jira/browse/OFBIZ-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-8115: --- Description: At r1758927 I tried to fixe a bunch of closes missing, reported as warnings in Eclipse Jacopo noticed and reported on dev ML http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: # you are adding a close statement to code that already had the close statement in the "finally" block; your modification actually introduces a code pattern that is not correct (if an exception is thrown your close statement are not executed) # I suspect that you are closing the socket connection too early in PcChargeApi So I reverted r1758927 to check the issues was: At r1758927 I tried to fixe a bunch of closes missing, reported as warnings in Eclipse Jacopo noticed and reported on dev ML http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: # you are adding a close statement to code that already had the close statement in the "finally" block; your modification actually introduces a code pattern that is not correct (if an exception is thrown your close statement are not executed) # I suspect that you are closing the socket connection too early in PcChargeApi So I reverted r1758927 to check the issues > Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse) > - > > Key: OFBIZ-8115 > URL: https://issues.apache.org/jira/browse/OFBIZ-8115 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > At r1758927 I tried to fixe a bunch of closes missing, reported as warnings > in Eclipse > Jacopo noticed and reported on dev ML > http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: > # you are adding a close statement to code that already had the close > statement in the "finally" block; your modification actually introduces a > code pattern that is not correct (if an exception is thrown your close > statement are not executed) > # I suspect that you are closing the socket connection too early in > PcChargeApi > So I reverted r1758927 to check the issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8115) Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse)
Jacques Le Roux created OFBIZ-8115: -- Summary: Fixe a bunch of small leaks (closes missing, reported as warnings in Eclipse) Key: OFBIZ-8115 URL: https://issues.apache.org/jira/browse/OFBIZ-8115 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch At r1758927 I tried to fixe a bunch of closes missing, reported as warnings in Eclipse Jacopo noticed and reported on dev ML http://markmail.org/message/b4hvzi7foftfq3j5 2 possible issues: # you are adding a close statement to code that already had the close statement in the "finally" block; your modification actually introduces a code pattern that is not correct (if an exception is thrown your close statement are not executed) # I suspect that you are closing the socket connection too early in PcChargeApi So I reverted r1758927 to check the issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8113) Maximise the utilisation of common labels in various order forms
[ https://issues.apache.org/jira/browse/OFBIZ-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-8113: Attachment: OFBIZ-8113-order-forms-v2.patch Revised patch, as the first one contained an error. > Maximise the utilisation of common labels in various order forms > > > Key: OFBIZ-8113 > URL: https://issues.apache.org/jira/browse/OFBIZ-8113 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: labels, refactoring > Attachments: OFBIZ-8113-order-forms-v2.patch, > OFBIZ-8113-order-forms.patch > > > There are many forms in the order component that could benefit from the > application of common labels. This ticket addresses that issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8114) The "Only Not Used Labels" option of the Label Manager is broken
[ https://issues.apache.org/jira/browse/OFBIZ-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-8114: --- Description: This is due to the introduction of ServiceUtil.getResource() at r1757979 for OFBIZ-7912 (was: This is due to the introduction of ServiceUtil.getResource() at OFBIZ-7912) > The "Only Not Used Labels" option of the Label Manager is broken > > > Key: OFBIZ-8114 > URL: https://issues.apache.org/jira/browse/OFBIZ-8114 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > This is due to the introduction of ServiceUtil.getResource() at r1757979 for > OFBIZ-7912 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7912) Enforce noninstantiability to ServiceUtil class
[
https://issues.apache.org/jira/browse/OFBIZ-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458195#comment-15458195
]
Jacques Le Roux commented on OFBIZ-7912:
Hi guys,
I just noticed r1757979 broke the Label Manager, please see OFBIZ-8114
> Enforce noninstantiability to ServiceUtil class
> ---
>
> Key: OFBIZ-7912
> URL: https://issues.apache.org/jira/browse/OFBIZ-7912
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Affects Versions: Trunk
>Reporter: Rishi Solanki
>Assignee: Arun Patidar
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7912.patch
>
>
> - Make class as final.
> - Add a private constructor.
> - Make following public static final variables as private;
> {code}
> public static final String resource = "ServiceErrorUiLabels";
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (OFBIZ-7912) Enforce noninstantiability to ServiceUtil class
[
https://issues.apache.org/jira/browse/OFBIZ-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-7912:
> Enforce noninstantiability to ServiceUtil class
> ---
>
> Key: OFBIZ-7912
> URL: https://issues.apache.org/jira/browse/OFBIZ-7912
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Affects Versions: Trunk
>Reporter: Rishi Solanki
>Assignee: Arun Patidar
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7912.patch
>
>
> - Make class as final.
> - Add a private constructor.
> - Make following public static final variables as private;
> {code}
> public static final String resource = "ServiceErrorUiLabels";
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-8114) The "Only Not Used Labels" option of the Label Manager is broken
Jacques Le Roux created OFBIZ-8114: -- Summary: The "Only Not Used Labels" option of the Label Manager is broken Key: OFBIZ-8114 URL: https://issues.apache.org/jira/browse/OFBIZ-8114 Project: OFBiz Issue Type: Bug Components: framework/webtools Affects Versions: Upcoming Branch Reporter: Jacques Le Roux Assignee: Jacques Le Roux Fix For: Upcoming Branch This is due to the introduction of ServiceUtil.getResource() at OFBIZ-7912 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-6899) Overview of payment methods in party profile misses function to set company check payment
[ https://issues.apache.org/jira/browse/OFBIZ-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divesh Dutta resolved OFBIZ-6899. - Resolution: Fixed > Overview of payment methods in party profile misses function to set company > check payment > - > > Key: OFBIZ-6899 > URL: https://issues.apache.org/jira/browse/OFBIZ-6899 > Project: OFBiz > Issue Type: New Feature > Components: accounting, order, party, specialpurpose/ecommerce >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Divesh Dutta > Labels: check, payment > Fix For: Upcoming Branch > > Attachments: CC_1.png, CC_2.png, CC_3.png, CC_4.png, > OFBIZ-6899.patch, OFBIZ-6899.patch, OFBIZ-6899.patch > > > The payment methods overview in the party profile shows various options to > define and create a payment method. > However there is no option to create payment method for a company check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6899) Overview of payment methods in party profile misses function to set company check payment
[ https://issues.apache.org/jira/browse/OFBIZ-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458109#comment-15458109 ] Divesh Dutta commented on OFBIZ-6899: - Patch is committed in revision number 1758926 in trunk. Thanks all of you for discussions. Thanks to Jagpreet for providing the patch. Assigning this ticket to Swapnil for verification and closure of this ticket. > Overview of payment methods in party profile misses function to set company > check payment > - > > Key: OFBIZ-6899 > URL: https://issues.apache.org/jira/browse/OFBIZ-6899 > Project: OFBiz > Issue Type: New Feature > Components: accounting, order, party, specialpurpose/ecommerce >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Divesh Dutta > Labels: check, payment > Fix For: Upcoming Branch > > Attachments: CC_1.png, CC_2.png, CC_3.png, CC_4.png, > OFBIZ-6899.patch, OFBIZ-6899.patch, OFBIZ-6899.patch > > > The payment methods overview in the party profile shows various options to > define and create a payment method. > However there is no option to create payment method for a company check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8109) Maximise the utilisation of the Label CommonType in various framework forms
[ https://issues.apache.org/jira/browse/OFBIZ-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457949#comment-15457949 ] Pierre Smits commented on OFBIZ-8109: - Where possible. Keep in mind that each form needs to be evaluated to determine the appropriate semantics. Simple find/replace might lead to undesired results. > Maximise the utilisation of the Label CommonType in various framework forms > --- > > Key: OFBIZ-8109 > URL: https://issues.apache.org/jira/browse/OFBIZ-8109 > Project: OFBiz > Issue Type: Sub-task > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: labels > Attachments: OFBIZ-8109-framework-forms.patch > > > Various forms in component(s) the framework stack use a TypeId variant. This > issue is about applying the CommonLabel label where it is possible in these > forms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8109) Maximise the utilisation of the Label CommonType in various framework forms
[ https://issues.apache.org/jira/browse/OFBIZ-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457921#comment-15457921 ] Jacques Le Roux commented on OFBIZ-8109: When you look at the concerned screens, this is a moot point indeed. Do you want to remove all specific types, like CommonGeoType, and use only CommonType everywhere? > Maximise the utilisation of the Label CommonType in various framework forms > --- > > Key: OFBIZ-8109 > URL: https://issues.apache.org/jira/browse/OFBIZ-8109 > Project: OFBiz > Issue Type: Sub-task > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: labels > Attachments: OFBIZ-8109-framework-forms.patch > > > Various forms in component(s) the framework stack use a TypeId variant. This > issue is about applying the CommonLabel label where it is possible in these > forms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8113) Maximise the utilisation of common labels in various order forms
[ https://issues.apache.org/jira/browse/OFBIZ-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-8113: Attachment: OFBIZ-8113-order-forms.patch This patch addresses the issue. > Maximise the utilisation of common labels in various order forms > > > Key: OFBIZ-8113 > URL: https://issues.apache.org/jira/browse/OFBIZ-8113 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: labels, refactoring > Attachments: OFBIZ-8113-order-forms.patch > > > There are many forms in the order component that could benefit from the > application of common labels. This ticket addresses that issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6880) Boostrap Basic Theme freezed FireFox 44
[ https://issues.apache.org/jira/browse/OFBIZ-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6880. -- Resolution: Cannot Reproduce Assignee: Jacques Le Roux Thanks for the reminder Taher, I believe it's due to my complicated FF config. Anyway I could not reproduce, so closing > Boostrap Basic Theme freezed FireFox 44 > --- > > Key: OFBIZ-6880 > URL: https://issues.apache.org/jira/browse/OFBIZ-6880 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Bootstrap theme >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Blocker > Attachments: Image 089.png, Image 090.png > > > On my momentum after trying Rainbow Stone, I just tried Boostrap themes, and > got FF 44 freezed. I could not stop the failing script, nor stop FF, but > debuging it stopped the freeze. I stopped there and I will attach the > screenshoots which will, I hope, explain better than me what happened > I was wondering why we did not merge this branch. This is clearly a blocker > !Image 089.png! > !Image 090.png! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-5522: --- Comment: was deleted (was: Thanks my problem got solved.) > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-5522: --- Comment: was deleted (was: [ Consequently, you should keep in thoughts the items tend to be relocated according to his or her desperation. Also you can provide a get in touch with up to be able to a wide range of the shifting companies and also understand their particular strategy to going the different items. https://www.imofreedownloadforpc.com/) > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6433) Unable to Export PDF from Jasper in Ofbiz
[ https://issues.apache.org/jira/browse/OFBIZ-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457825#comment-15457825 ] Taher Alkhateeb commented on OFBIZ-6433: Also this request is minor, and probably no longer relevant. > Unable to Export PDF from Jasper in Ofbiz > - > > Key: OFBIZ-6433 > URL: https://issues.apache.org/jira/browse/OFBIZ-6433 > Project: OFBiz > Issue Type: Bug > Environment: Ubuntu >Reporter: Sachin Manjule >Priority: Critical > > Unable to Export PDF from Jasper in Ofbiz, > Please provide step how to export PDF from Ofbiz, I am getting error > Attribute "uuid" must be declared for element type "jasperReport". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6625) EcomSEO generates an error when used in multi-tenancy setup
[
https://issues.apache.org/jira/browse/OFBIZ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457820#comment-15457820
]
Taher Alkhateeb commented on OFBIZ-6625:
I recommend classifyingthis Jira as minor
> EcomSEO generates an error when used in multi-tenancy setup
> ---
>
> Key: OFBIZ-6625
> URL: https://issues.apache.org/jira/browse/OFBIZ-6625
> Project: OFBiz
> Issue Type: Bug
> Components: specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Critical
> Labels: multi-tenant
> Fix For: Upcoming Branch
>
> Attachments: seocontextfilter.patch
>
>
> When using the ecomseo application of the ecommerce component in a tenant the
> tenant entity can't be accessed, and the following error is returned.
> {code} [java] 2015-09-17 22:44:33,906 |http-bio-8443-exec-8
> |GenericDelegator |I| Can't access entity of entityGroup =
> org.ofbiz.tenant using tenant delegator default#enantId, use base delegator
> instead
> [java] 2015-09-17 22:44:33,906 |http-bio-8443-exec-8 |GenericDelegator
>|E| Failure in findByCondition operation for entity [Tenant]:
> org.ofbiz.entity.GenericEntityException: There is no datasource (Helper)
> configured for the entity-group [org.ofbiz.tenant]; was trying to find
> datasource (helper) for entity [Tenant]. Rolling back transaction.
> [java] org.ofbiz.entity.GenericEntityException: There is no datasource
> (Helper) configured for the entity-group [org.ofbiz.tenant]; was trying to
> find datasource (helper) for entity [Tenant]
> [java] at
> org.ofbiz.entity.GenericDelegator.getEntityHelper(GenericDelegator.java:544)
> ~[ofbiz-entity.jar:?]
> [java] at
> org.ofbiz.entity.GenericDelegator.find(GenericDelegator.java:1774)
> ~[ofbiz-entity.jar:?]
> [java] at
> org.ofbiz.entity.GenericDelegator.findList(GenericDelegator.java:1811)
> [ofbiz-entity.jar:?]
> [java] at
> org.ofbiz.product.category.SeoContextFilter.doFilter(SeoContextFilter.java:300)
> [ofbiz-product.jar:?]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.ofbiz.product.category.SeoContentUrlFilter.doFilter(SeoContentUrlFilter.java:105)
> [ofbiz-product.jar:?]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.ofbiz.product.category.CatalogUrlFilter.doFilter(CatalogUrlFilter.java:338)
> [ofbiz-product.jar:?]
> [java] at
> org.ofbiz.product.category.CatalogUrlSeoFilter.doFilter(CatalogUrlSeoFilter.java:68)
> [ofbiz-product.jar:?]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
> [tomcat-7.0.59-catalina.jar:7.0.59]
> [java] at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
> [tomcat-7.0.59-tomcat-coyote.jar:7.0.59]
> [java] at
>
[jira] [Commented] (OFBIZ-6645) order confirmation via ecommerce (request-uri="emailorder"
[ https://issues.apache.org/jira/browse/OFBIZ-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457813#comment-15457813 ] Taher Alkhateeb commented on OFBIZ-6645: I would classify this as minor. Just a bunch of errors in the log. > order confirmation via ecommerce (request-uri="emailorder" > -- > > Key: OFBIZ-6645 > URL: https://issues.apache.org/jira/browse/OFBIZ-6645 > Project: OFBiz > Issue Type: Bug > Components: order, specialpurpose/ecommerce >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Critical > Labels: ecommerce, order_confirmation > Attachments: error.log > > > When completing an order via ecommerce, the confirmation of order is to be > sent out via request-uri="emailorder". > This generates in a lot of errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7096) Inventory received are not getting reserved based on set Est. Delivery Date over Sales Order
[ https://issues.apache.org/jira/browse/OFBIZ-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457809#comment-15457809 ] Taher Alkhateeb commented on OFBIZ-7096: priority is minor here. The order and inventory systems are operational otherwise. > Inventory received are not getting reserved based on set Est. Delivery Date > over Sales Order > > > Key: OFBIZ-7096 > URL: https://issues.apache.org/jira/browse/OFBIZ-7096 > Project: OFBiz > Issue Type: Bug >Reporter: Swapnil Shah >Assignee: Divesh Dutta >Priority: Critical > Attachments: SO1002.png, SO1003.png, SO1004.png > > > Generally system would carry multiple sales order for a SKU with different > Est.Delivery Date(EDD) and inventory might not be available that time when > orders were created/approved. > Once we start receiving the inventory then reservations gets auto-triggered > and allocated based on created/approved date by overlooking the EDD > altogether. > A simple scenario could be that we have 3 different orders created in system > at 3 different time stamps as follows and all 3 are backordered: > Order A>> Created on 05/21 10 AM >> EDD: 5/25 > Order B>> Created on 05/21 11 AM >> EDD: 5/27 > Order C>> Created on 05/21 12 AM >> EDD: 5/23 > As soon as inventory is received it first get allocated to Order A whereas > Order C is supposed to ship first even though it got approved later. > Expected Behavior: System should first honor the EDD and if its not set then > use the existing criteria of honoring Created/Approved time stamp for > allocating the reservations > Please refer to attached screenshots for reference -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7166) Return process fails on receiving
[ https://issues.apache.org/jira/browse/OFBIZ-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457801#comment-15457801 ] Taher Alkhateeb commented on OFBIZ-7166: The priority of this jira should be minor at best. Setting Jiras with high priority means a serious affect on the system which I think is not the case here > Return process fails on receiving > - > > Key: OFBIZ-7166 > URL: https://issues.apache.org/jira/browse/OFBIZ-7166 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Deepak Dixit >Priority: Critical > Attachments: OFBIZ-7166.patch, ReturnPage.png > > > This issue will not regenerate with the test processors. > I actually tried with test account of Authorize.net and setup > "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. > Steps to Regenerate: > 1. Create order and quick ship entire order. > 2. Create return from order screen. > 3. Accept Return. > 4. Try to Receive return. > Issue: > Page is broken with error message > "Error in Service [aimCCRefund]: No authorization transaction found; cannot > refund". Also see the attach screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7741) Address scope peculiarities within search/find functionality of projectmgr
[ https://issues.apache.org/jira/browse/OFBIZ-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457796#comment-15457796 ] Taher Alkhateeb commented on OFBIZ-7741: I believe this should be minor or trivial.. Definitely not critical > Address scope peculiarities within search/find functionality of projectmgr > -- > > Key: OFBIZ-7741 > URL: https://issues.apache.org/jira/browse/OFBIZ-7741 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/projectmgr >Reporter: Pierre Smits >Priority: Critical > > Currently the search/find functions in the projectmgr component also > retrieves projects a user is not a participant in. This is especially > critical regarding projects with scope 'WES_PRIVATE - private' or > 'WES_CONFIDENTIAL - confidential'. > These project may only be search for/found by users that are exlicit > participants of the projects. This over ruless the generic permissions of > 'PROJECTMGR_ADMIN' or 'PROJECTMGR_VIEW'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6880) Boostrap Basic Theme freezed FireFox 44
[ https://issues.apache.org/jira/browse/OFBIZ-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457787#comment-15457787 ] Taher Alkhateeb commented on OFBIZ-6880: is this still relevant? Why is it a blocking task? This does not qualify even as critical > Boostrap Basic Theme freezed FireFox 44 > --- > > Key: OFBIZ-6880 > URL: https://issues.apache.org/jira/browse/OFBIZ-6880 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Bootstrap theme >Reporter: Jacques Le Roux >Priority: Blocker > Attachments: Image 089.png, Image 090.png > > > On my momentum after trying Rainbow Stone, I just tried Boostrap themes, and > got FF 44 freezed. I could not stop the failing script, nor stop FF, but > debuging it stopped the freeze. I stopped there and I will attach the > screenshoots which will, I hope, explain better than me what happened > I was wondering why we did not merge this branch. This is clearly a blocker > !Image 089.png! > !Image 090.png! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6066) Tenant specific components are visible/accessible in any tenant instance
[ https://issues.apache.org/jira/browse/OFBIZ-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457784#comment-15457784 ] Taher Alkhateeb commented on OFBIZ-6066: This is not a blocking task, at most it would be major, probably more minor. Also references to ant make it probably outdated and should be closed > Tenant specific components are visible/accessible in any tenant instance > > > Key: OFBIZ-6066 > URL: https://issues.apache.org/jira/browse/OFBIZ-6066 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 14.12, Trunk >Reporter: Pierre Smits >Priority: Blocker > Labels: component, tenant > > Tenant specific components should only be visible/accessible by users of the > specified tenant. > However, because data of the tenant specific component can be loaded into any > tenant (including the master rmdbs) through ./ant load-data or via the import > function of webtools, the tenant specific component is exposed to all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6065) Data of tenant specific component gets loaded in all instances
[ https://issues.apache.org/jira/browse/OFBIZ-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457780#comment-15457780 ] Taher Alkhateeb commented on OFBIZ-6065: This is not a blocking task and no longer relevant. Please close > Data of tenant specific component gets loaded in all instances > -- > > Key: OFBIZ-6065 > URL: https://issues.apache.org/jira/browse/OFBIZ-6065 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 14.12, Trunk, 14.12.01 >Reporter: Pierre Smits >Priority: Blocker > Labels: component, data, tenant > > When performing a ./ant load-data variant or using the import function in > webtools data of tenant specific component gets loaded into any tenant > (including master) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7728) Removal of jars lead to build errors
[ https://issues.apache.org/jira/browse/OFBIZ-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1545#comment-1545 ] Taher Alkhateeb commented on OFBIZ-7728: please close. Not an issue. > Removal of jars lead to build errors > > > Key: OFBIZ-7728 > URL: https://issues.apache.org/jira/browse/OFBIZ-7728 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS, framework >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Blocker > > When executing the changes proposed in OFBIZ-7534 and deleting all external > libraries, the build process fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
