[jira] [Updated] (OFBIZ-6932) In the case of MARKETING_PKG_PICK the invoice gets created of product components, Ideally the invoice should be created of package.
[ https://issues.apache.org/jira/browse/OFBIZ-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-6932: --- Summary: In the case of MARKETING_PKG_PICK the invoice gets created of product components, Ideally the invoice should be created of package. (was: In the case of MARKETING_PKG_PICK the invoice gets created of product component, ideally the invoice should be created of package.) > In the case of MARKETING_PKG_PICK the invoice gets created of product > components, Ideally the invoice should be created of package. > --- > > Key: OFBIZ-6932 > URL: https://issues.apache.org/jira/browse/OFBIZ-6932 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad > > Steps to reproduce: > 1. Create sales order with MARKETING_PKG_PICK. > 2. Completed the order with its shipment. > 3. Invoice should be created. > Actual: Invoice created with its components. > Expected: Invoice should be created for its package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6932) In the case of MARKETING_PKG_PICK the invoice gets created of product component, ideally the invoice should be created of package.
Yashwant Dhakad created OFBIZ-6932: -- Summary: In the case of MARKETING_PKG_PICK the invoice gets created of product component, ideally the invoice should be created of package. Key: OFBIZ-6932 URL: https://issues.apache.org/jira/browse/OFBIZ-6932 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk Reporter: Yashwant Dhakad Steps to reproduce: 1. Create sales order with MARKETING_PKG_PICK. 2. Completed the order with its shipment. 3. Invoice should be created. Actual: Invoice created with its components. Expected: Invoice should be created for its package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6931) Add XLS renderer
Leila Mekika created OFBIZ-6931: --- Summary: Add XLS renderer Key: OFBIZ-6931 URL: https://issues.apache.org/jira/browse/OFBIZ-6931 Project: OFBiz Issue Type: New Feature Components: ALL COMPONENTS, framework Affects Versions: Trunk Reporter: Leila Mekika Priority: Minor Add a new renderer type in order to enable XLS file output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Release Information hopelessly outdated
http://ofbiz.apache.org/download.html needs an update in the Release Information. Some of the forecasted dates are from last year. Can someone who knows what was done and what is planned to be done, update this so that it makes sense. Should all references to 11.04.xx be removed and included in the superseded releases? Do we really want new users downloading 12.04? Ron -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
[jira] [Created] (OFBIZ-6930) HumanResDemoData.xml doesn't load
Pierre Smits created OFBIZ-6930: --- Summary: HumanResDemoData.xml doesn't load Key: OFBIZ-6930 URL: https://issues.apache.org/jira/browse/OFBIZ-6930 Project: OFBiz Issue Type: Bug Components: humanres Affects Versions: Trunk Reporter: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6929) DemoOrganisationData.xml doesn't load
Pierre Smits created OFBIZ-6929: --- Summary: DemoOrganisationData.xml doesn't load Key: OFBIZ-6929 URL: https://issues.apache.org/jira/browse/OFBIZ-6929 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Trunk Reporter: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6919) New implementation of Birt. Easier user possibility of report creation
[
https://issues.apache.org/jira/browse/OFBIZ-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15193331#comment-15193331
]
Jacques Le Roux commented on OFBIZ-6919:
OK, thanks François!
> New implementation of Birt. Easier user possibility of report creation
> --
>
> Key: OFBIZ-6919
> URL: https://issues.apache.org/jira/browse/OFBIZ-6919
> Project: OFBiz
> Issue Type: New Feature
> Components: specialpurpose/birt
>Affects Versions: Trunk
>Reporter: François Wurmser
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> This is a new implementation of Birt. It allows the creation of "report
> masters" by the developer, which will in turn let the user create its own
> reports. Data connection of report is fully generated by OFBiz based on
> report master. Design is user made.
> Filtering is made via content forms stored in the database ("FORM_COMBINED")
> data_resource.
> The patch should be available in a few days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6919) New implementation of Birt. Easier user possibility of report creation
[
https://issues.apache.org/jira/browse/OFBIZ-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15193223#comment-15193223
]
François Wurmser commented on OFBIZ-6919:
-
Hi,
Jacques, the current patch does not touch these libs. A first version of the
patch is ready, I have now left it to the people at Nereide (I just left
there). They should upload it at some point when they think it is ready.
François
> New implementation of Birt. Easier user possibility of report creation
> --
>
> Key: OFBIZ-6919
> URL: https://issues.apache.org/jira/browse/OFBIZ-6919
> Project: OFBiz
> Issue Type: New Feature
> Components: specialpurpose/birt
>Affects Versions: Trunk
>Reporter: François Wurmser
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> This is a new implementation of Birt. It allows the creation of "report
> masters" by the developer, which will in turn let the user create its own
> reports. Data connection of report is fully generated by OFBiz based on
> report master. Design is user made.
> Filtering is made via content forms stored in the database ("FORM_COMBINED")
> data_resource.
> The patch should be available in a few days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-6928) Have the layered model renderer work with EntityUtilProperties regarding retrieval of property values
[
https://issues.apache.org/jira/browse/OFBIZ-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-6928:
Summary: Have the layered model renderer work with EntityUtilProperties
regarding retrieval of property values (was: Have the layered model renderer
work with EntityUtil regarding retrieval of property values)
> Have the layered model renderer work with EntityUtilProperties regarding
> retrieval of property values
> -
>
> Key: OFBIZ-6928
> URL: https://issues.apache.org/jira/browse/OFBIZ-6928
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
> Labels: multi-tenant
> Fix For: Trunk
>
>
> Currently property values are retrieved through
> {code}
> UtilProperties.getPropertyValue
> {code} function
> This should be using EntityUtilProperties.GetPropertyValue function.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-6928) Have the layered model renderer work with EntityUtilProperties regarding retrieval of property values
[
https://issues.apache.org/jira/browse/OFBIZ-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-6928:
Description:
Currently property values are retrieved through
{code}
UtilProperties.getPropertyValue
{code} function
This should be using EntityUtilProperties.getPropertyValue function.
was:
Currently property values are retrieved through
{code}
UtilProperties.getPropertyValue
{code} function
This should be using EntityUtilProperties.GetPropertyValue function.
> Have the layered model renderer work with EntityUtilProperties regarding
> retrieval of property values
> -
>
> Key: OFBIZ-6928
> URL: https://issues.apache.org/jira/browse/OFBIZ-6928
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
> Labels: multi-tenant
> Fix For: Trunk
>
>
> Currently property values are retrieved through
> {code}
> UtilProperties.getPropertyValue
> {code} function
> This should be using EntityUtilProperties.getPropertyValue function.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-6928) Have the layered model renderer work with EntityUtil regarding retrieval of property values
Pierre Smits created OFBIZ-6928:
---
Summary: Have the layered model renderer work with EntityUtil
regarding retrieval of property values
Key: OFBIZ-6928
URL: https://issues.apache.org/jira/browse/OFBIZ-6928
Project: OFBiz
Issue Type: Sub-task
Components: framework
Affects Versions: Trunk
Reporter: Pierre Smits
Currently property values are retrieved through
{code}
UtilProperties.getPropertyValue
{code} function
This should be using EntityUtilProperties.GetPropertyValue function.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-6927) Layered-Modal menu item does not respect width and height parameters
[
https://issues.apache.org/jira/browse/OFBIZ-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-6927:
Description:
When using a link of type 'layered-modal' the renderer doesn't work with the
provided width and height parameters.
e.g.:
{code}{code} should show a modal window with width =1000 and height=600
pixels. However, the resulting code for the dialog yields:
{code}
autoOpen: false,
title: "New Production Run",
height: 600,
width: 800,
modal: true,
{code}
The used values are from the properties definitions.
was:
When using a link of type 'layered-modal' the renderer doesn't work with the
provided width and height parameters.
e.g.:
{code}{code} should show a modal window with width =1000 and height=600
pixels. However, the resulting code for the dialog yields:
{code}
autoOpen: false,
title: "New Production Run",
height: 600,
width: 800,
modal: true,
{code}
> Layered-Modal menu item does not respect width and height parameters
>
>
> Key: OFBIZ-6927
> URL: https://issues.apache.org/jira/browse/OFBIZ-6927
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
> Labels: modalwindow, renderer
> Fix For: Trunk
>
>
> When using a link of type 'layered-modal' the renderer doesn't work with the
> provided width and height parameters.
> e.g.:
> {code} height="600"/>{code} should show a modal window with width =1000 and
> height=600 pixels. However, the resulting code for the dialog yields:
> {code}
> autoOpen: false,
> title: "New Production Run",
> height: 600,
> width: 800,
> modal: true,
> {code}
> The used values are from the properties definitions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-6927) Layered-Modal menu item does not respect width and height parameters
Pierre Smits created OFBIZ-6927:
---
Summary: Layered-Modal menu item does not respect width and height
parameters
Key: OFBIZ-6927
URL: https://issues.apache.org/jira/browse/OFBIZ-6927
Project: OFBiz
Issue Type: Sub-task
Components: framework
Affects Versions: Trunk
Reporter: Pierre Smits
When using a link of type 'layered-modal' the renderer doesn't work with the
provided width and height parameters.
e.g.:
{code}{code} should show a modal window with width =1000 and height=600
pixels. However, the resulting code for the dialog yields:
{code}
autoOpen: false,
title: "New Production Run",
height: 600,
width: 800,
modal: true,
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6919) New implementation of Birt. Easier user possibility of report creation
[
https://issues.apache.org/jira/browse/OFBIZ-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15193116#comment-15193116
]
Jacques Le Roux commented on OFBIZ-6919:
I'm also interested about this with the hope that it will also update the
vulnerable libs we embed currently because of Birt (axis-1.4.jar, jaxrpc.jar,
saaj.jar, Tidy.jar, viewservlets.jar)
> New implementation of Birt. Easier user possibility of report creation
> --
>
> Key: OFBIZ-6919
> URL: https://issues.apache.org/jira/browse/OFBIZ-6919
> Project: OFBiz
> Issue Type: New Feature
> Components: specialpurpose/birt
>Affects Versions: Trunk
>Reporter: François Wurmser
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> This is a new implementation of Birt. It allows the creation of "report
> masters" by the developer, which will in turn let the user create its own
> reports. Data connection of report is fully generated by OFBiz based on
> report master. Design is user made.
> Filtering is made via content forms stored in the database ("FORM_COMBINED")
> data_resource.
> The patch should be available in a few days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-6913) Update Tomcat to 7.0.68
[ https://issues.apache.org/jira/browse/OFBIZ-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6913: --- Description: Today the Apache Tomcat Security Team revealed some security issues, we need to update Tomcat to 6.0.68 version https://tomcat.apache.org/security-7.html Notes: * R12.04 i concerned but we no longer update Tomcat there. * "OWASP Dependency Check" still reports issues with Tomcat but as explained at OFBIZ-6752 we don't care about them was: Today the Apache Tomcat Security Team revealed some security issues, we need to update Tomcat to 6.0.68 version https://tomcat.apache.org/security-7.html > Update Tomcat to 7.0.68 > --- > > Key: OFBIZ-6913 > URL: https://issues.apache.org/jira/browse/OFBIZ-6913 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: 14.12.01, 13.07.03, Upcoming Branch > > > Today the Apache Tomcat Security Team revealed some security issues, we need > to update Tomcat to 6.0.68 version > https://tomcat.apache.org/security-7.html > Notes: > * R12.04 i concerned but we no longer update Tomcat there. > * "OWASP Dependency Check" still reports issues with Tomcat but as explained > at OFBIZ-6752 we don't care about them -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6913) Update Tomcat to 7.0.68
[ https://issues.apache.org/jira/browse/OFBIZ-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6913: --- Description: Today the Apache Tomcat Security Team revealed some security issues, we need to update Tomcat to 6.0.68 version https://tomcat.apache.org/security-7.html Notes: * R12.04 is concerned but we no longer update Tomcat there. * "OWASP Dependency Check" still reports issues with Tomcat but as explained at OFBIZ-6752 we don't care about them was: Today the Apache Tomcat Security Team revealed some security issues, we need to update Tomcat to 6.0.68 version https://tomcat.apache.org/security-7.html Notes: * R12.04 i concerned but we no longer update Tomcat there. * "OWASP Dependency Check" still reports issues with Tomcat but as explained at OFBIZ-6752 we don't care about them > Update Tomcat to 7.0.68 > --- > > Key: OFBIZ-6913 > URL: https://issues.apache.org/jira/browse/OFBIZ-6913 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: 14.12.01, 13.07.03, Upcoming Branch > > > Today the Apache Tomcat Security Team revealed some security issues, we need > to update Tomcat to 6.0.68 version > https://tomcat.apache.org/security-7.html > Notes: > * R12.04 is concerned but we no longer update Tomcat there. > * "OWASP Dependency Check" still reports issues with Tomcat but as explained > at OFBIZ-6752 we don't care about them -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6913) Update Tomcat to 7.0.68
[ https://issues.apache.org/jira/browse/OFBIZ-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6913. -- Resolution: Fixed Fix Version/s: (was: 12.04.06) Done for trunk r1734912 R15.12 r1734913 R14.12 r1734914 R13.07 r1734915 As ever I forgot .classpath and LICENSE files, here they are. trunk r1734918 R15.12 r1734920 R14.12 r1734921 R13.07 r1734923 In trunk and R15.152, I decided to no longer move the new entries in.classpath which are not automatically alphabetically ordered by Eclipse. Since we should now use the given tool, no need for that. > Update Tomcat to 7.0.68 > --- > > Key: OFBIZ-6913 > URL: https://issues.apache.org/jira/browse/OFBIZ-6913 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: 14.12.01, 13.07.03, Upcoming Branch > > > Today the Apache Tomcat Security Team revealed some security issues, we need > to update Tomcat to 6.0.68 version > https://tomcat.apache.org/security-7.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6913) Update Tomcat to 7.0.68
[ https://issues.apache.org/jira/browse/OFBIZ-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15193112#comment-15193112 ] Jacques Le Roux edited comment on OFBIZ-6913 at 3/14/16 11:15 AM: -- Done for trunk r1734912 R15.12 r1734913 R14.12 r1734914 R13.07 r1734915 As ever I forgot .classpath and LICENSE files, here they are. trunk r1734918 R15.12 r1734920 R14.12 r1734921 R13.07 r1734923 In trunk and R15.12, I decided to no longer move the new entries in.classpath which are not automatically alphabetically ordered by Eclipse. Since we should now use the given tool, no need for that. was (Author: jacques.le.roux): Done for trunk r1734912 R15.12 r1734913 R14.12 r1734914 R13.07 r1734915 As ever I forgot .classpath and LICENSE files, here they are. trunk r1734918 R15.12 r1734920 R14.12 r1734921 R13.07 r1734923 In trunk and R15.152, I decided to no longer move the new entries in.classpath which are not automatically alphabetically ordered by Eclipse. Since we should now use the given tool, no need for that. > Update Tomcat to 7.0.68 > --- > > Key: OFBIZ-6913 > URL: https://issues.apache.org/jira/browse/OFBIZ-6913 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: 14.12.01, 13.07.03, Upcoming Branch > > > Today the Apache Tomcat Security Team revealed some security issues, we need > to update Tomcat to 6.0.68 version > https://tomcat.apache.org/security-7.html -- 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 ] Sharan Foga updated OFBIZ-5522: --- Comment: was deleted (was: Packers and Movers in Hyderabad at http://www.hirenmove.in/packers-and-movers/hyderabad.html Packers and Movers in Pune at http://www.expert5th.in/packers-and-movers-pune/ Packers and Movers in Delhi at http://www.hirenmove.in/packers-and-movers/delhi.html Packers and Movers in Gurgaon at http://www.hirenmove.in/packers-and-movers/gurgaon.html ) > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharan Foga updated OFBIZ-5522: --- Comment: was deleted (was: Packers and Movers in Pune at http://www.hirenmove.in/packers-and-movers/pune.html Packers and Movers in Bangalore at http://www.hirenmove.in/packers-and-movers/bangalore.html Packers and Movers in Hyderabad at http://www.expert5th.in/packers-and-movers-hyderabad/ Packers and Movers in Delhi at http://www.expert5th.in/packers-and-movers-delhi/ Packers and Movers in Mumbai at http://www.hirenmove.in/packers-and-movers/mumbai.html ) > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharan Foga updated OFBIZ-5522: --- Comment: was deleted (was: Packers and Movers in Pune at http://www.moveby5th.in/packers-and-movers-pune.html Packers and Movers in Bangalore at http://www.moveby5th.in/packers-and-movers-bangalore.html Packers and Movers in Gurgaon at http://www.expert5th.in/packers-and-movers-gurgaon/ Packers and Movers in Mumbai at http://www.moveby5th.in/packers-and-movers-mumbai.html ) > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharan Foga updated OFBIZ-5522: --- Comment: was deleted (was: Packers and Movers in Hyderabad at http://www.moveby5th.in/packers-and-movers-hyderabad.html Packers and Movers in Bangalore at http://www.expert5th.in/packers-and-movers-bangalore/ Packers and Movers in Delhi at http://www.moveby5th.in/packers-and-movers-delhi.html Packers and Movers in Gurgaon at http://www.moveby5th.in/packers-and-movers-gurgaon.html ) > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192901#comment-15192901 ] Packers and Movers Delhi commented on OFBIZ-5522: - Packers and Movers in Pune at http://www.moveby5th.in/packers-and-movers-pune.html Packers and Movers in Bangalore at http://www.moveby5th.in/packers-and-movers-bangalore.html Packers and Movers in Gurgaon at http://www.expert5th.in/packers-and-movers-gurgaon/ Packers and Movers in Mumbai at http://www.moveby5th.in/packers-and-movers-mumbai.html > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192900#comment-15192900 ] Packers and Movers Delhi commented on OFBIZ-5522: - Packers and Movers in Hyderabad at http://www.moveby5th.in/packers-and-movers-hyderabad.html Packers and Movers in Bangalore at http://www.expert5th.in/packers-and-movers-bangalore/ Packers and Movers in Delhi at http://www.moveby5th.in/packers-and-movers-delhi.html Packers and Movers in Gurgaon at http://www.moveby5th.in/packers-and-movers-gurgaon.html > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192899#comment-15192899 ] Packers and Movers Delhi commented on OFBIZ-5522: - Packers and Movers in Pune at http://www.hirenmove.in/packers-and-movers/pune.html Packers and Movers in Bangalore at http://www.hirenmove.in/packers-and-movers/bangalore.html Packers and Movers in Hyderabad at http://www.expert5th.in/packers-and-movers-hyderabad/ Packers and Movers in Delhi at http://www.expert5th.in/packers-and-movers-delhi/ Packers and Movers in Mumbai at http://www.hirenmove.in/packers-and-movers/mumbai.html > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192898#comment-15192898 ] Packers and Movers Delhi commented on OFBIZ-5522: - Packers and Movers in Hyderabad at http://www.hirenmove.in/packers-and-movers/hyderabad.html Packers and Movers in Pune at http://www.expert5th.in/packers-and-movers-pune/ Packers and Movers in Delhi at http://www.hirenmove.in/packers-and-movers/delhi.html Packers and Movers in Gurgaon at http://www.hirenmove.in/packers-and-movers/gurgaon.html > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
