Re: 13.07 release plan
I am going to prepare the candidate release artifacts and then start a vote. Regards, Jacopo On Sep 19, 2014, at 5:17 PM, Adrian Crum adrian.c...@sandglass-software.com wrote: I would like to see some recent trunk fixes backported to the R13 branch - like the Jacopo's EE sequencer fix, and Adam's EE encryption fix. I may have time to work on one or more of those this weekend. But don't let that be a blocker - we can still create a binary release now, and then another one after those are backported. Adrian Crum Sandglass Software www.sandglass-software.com On 9/19/2014 3:29 PM, Jacopo Cappellato wrote: There is no commitment on dates, the dates on the website are just tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a predefined list of planned tickets to be resolved. However I think it is good time to prepare for the publication of the new release, since the stabilization phase has been pretty long already. What other think? I can prepare the release artifacts and start a vote in a few days if we are all ok. Jacopo On Sep 19, 2014, at 3:49 PM, Ron Wheeler rwhee...@artifact-software.com wrote: I am new here but since I started to get active Release 13.07 has missed 2 published release dates. I have also found out that some people are already using it in production environment and are starting to worry about changes to 13.07 data structures and functionality that are being suggested as part of bug fixes to 13.07 as part of the release. Beta, RC1, RC2 planned? Is there a list of tasks that need to be done to release the first 13.07 release which is currently scheduled for next week? Have they been assigned and accepted? When will they be completed? There seems to be a lot of spare energy in the group at the moment and it would be good to channel it into getting the release done. Are there documentation or other non-coding tasks that need to be finished? I understand that this is an open source project with volunteers but there still needs to be some commitment to dates. They may slip but it should be absolutely clear why they slipped and a commitment from the PMC to see that the revised dates are met once the PMC has published the new dates. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: specialpurpose in R13.07 demo
in my opinion it is better to run the demo on the exact copy of the release branch. Jacopo On May 30, 2014, at 2:28 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, For the R13.07 demo I think we should set an external property from trunk into specialpurpose for some (those which make sense) components. I created this svn external property: specialpurpose/assetmaint/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/assetmaint specialpurpose/birt/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/birt specialpurpose/cmssite/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/cmssite specialpurpose/ebay/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/ebay specialpurpose/ebaystore/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/ebaystore specialpurpose/example/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/example specialpurpose/exampleext/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/exampleext specialpurpose/googlecheckout/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/googlecheckout specialpurpose/lucene/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/lucene specialpurpose/myportal/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/myportal specialpurpose/projectmgr/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/projectmgr specialpurpose/scrum/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/scrum specialpurpose/webpos/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/webpos What do you think? Jacques
Re: specialpurpose in R13.07 demo
Also, since (by design) the specialpurpose components there could be incompatible components (i.e. specialpurpose/a causes side effects in specialpurpose/b), or alternative components (i.e. specialpurpose/a is a different implementation of the same features of specialpurpose/b) or components that override some of the screens published by the applications (i.e. specialpurpose/a replaces applications/a screen with a custom version), we should, by default, disable (most of) them and provide a README file with the information on how to enable them selectively. Jacopo On Sep 30, 2014, at 8:38 AM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: in my opinion it is better to run the demo on the exact copy of the release branch. Jacopo On May 30, 2014, at 2:28 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, For the R13.07 demo I think we should set an external property from trunk into specialpurpose for some (those which make sense) components. I created this svn external property: specialpurpose/assetmaint/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/assetmaint specialpurpose/birt/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/birt specialpurpose/cmssite/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/cmssite specialpurpose/ebay/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/ebay specialpurpose/ebaystore/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/ebaystore specialpurpose/example/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/example specialpurpose/exampleext/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/exampleext specialpurpose/googlecheckout/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/googlecheckout specialpurpose/lucene/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/lucene specialpurpose/myportal/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/myportal specialpurpose/projectmgr/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/projectmgr specialpurpose/scrum/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/scrum specialpurpose/webpos/ https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/webpos What do you think? Jacques
[jira] [Commented] (OFBIZ-5762) Duplicated 'ALSO_BOUGHT' associations in product details page
[ https://issues.apache.org/jira/browse/OFBIZ-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152898#comment-14152898 ] Anahita Goljahani commented on OFBIZ-5762: -- Hi Jacques, thanks. Anahita Duplicated 'ALSO_BOUGHT' associations in product details page - Key: OFBIZ-5762 URL: https://issues.apache.org/jira/browse/OFBIZ-5762 Project: OFBiz Issue Type: Bug Components: order, specialpurpose/ecommerce Affects Versions: Trunk Reporter: Anahita Goljahani Assignee: Jacques Le Roux Priority: Minor Fix For: 13.07.01, Upcoming Branch, 12.04.06, 11.04.07 Attachments: alsoBoughtPatch.patch I have noticed an undesired behavior when two products are associated by the ALSO_BOUGHT association type. Specifically, when a product, e.g., Tiny Gizmo (productId = GZ-1000), is associated to another product, e.g., Micro Chrome Widget (productIdTo = WG-), by setting productAssocTypeId equal to ALSO_BOUGHT in ProductAssoc, the Tiny Gizmo web page in the ecommerce site correctly shows the Micro Chrome Widget as Customers who bought this item also bought:. Accordingly with the current software behavior, even if Micro Chrome Widget (productId = WG-) was not explicitly associated to Tiny Gizmo (productIdTo = GZ-1000), also the Micro Chrome Widget web page shows Tiny Gizmo as Customers who bought this item also bought:, which may be useful in cases where the 'ALSO_BOUGHT' association is meant to be necessarily bidirectional, i.e., if prodA is associated to prodB, then prodB is associated to prodA and vice-versa. However, when the user wants to express the symmetric nature of the relationship by explicitly associating both Tiny Gizmo to Micro Chrome Widget and Micro Chrome Widget to Tiny Gizmo in ProductAssoc, the system erroneously shows the associated products twice, both in the Tiny Gizmo and Micro Chrome web pages. The undesired behavior can be reproduced as follows: # Run OFBiz with demo data # import the following associations from the OFBiz XML Data Import form {code} ProductAssoc productId=GZ-1000 productIdTo=WG- productAssocTypeId=ALSO_BOUGHT fromDate=2014-09-02 12:00:00.000/ ProductAssoc productId=WG- productIdTo=GZ-1000 productAssocTypeId=ALSO_BOUGHT fromDate=2014-09-02 12:00:00.000/ {code} # click on Tiny Gizmo or Micro Chrome Widget from the main page of the ecommerce site. The attached patch modifies the above behavior as follows: - if only prodA (productId = prodA) is associated to prodB (productIdTo = prodB) in ProductAssoc, and not vice-versa, only prodA web page shows prodB as Customers who bought this item also bought:. This means that the 'ALSO_BOUGHT' association type becomes not necessarily bidirectional by default, which is in accordance with most common algorithms for the automatic generation of WHO BOUGHT X ALSO BOUGHT Y recommendations that may produce bidirectional associations for some couple of products and not for others, based on conditional probabilities and actual users behavior; - in those specific cases in which the association is actually bidirectional for a certain couple of products (prodA, prodB), i.e., both 'prodA to prodB' and 'prodB to prodA' associations are present in ProductAssoc, associated products are shown only ones in prodA and prodB web pages. The patch simply sets the value of the parameter bidirectional to its default value, i.e., false, when alsoBoughtProducts are collected by calling getAssociatedProducts() from applications/order/webapp/ordermgr/WEB-INF/actions/entry/catalog/ProductDetail.groovy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5455) images not stored in SystemProperty location
[ https://issues.apache.org/jira/browse/OFBIZ-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato updated OFBIZ-5455: - Fix Version/s: (was: Upcoming Branch) (was: 13.07.01) images not stored in SystemProperty location Key: OFBIZ-5455 URL: https://issues.apache.org/jira/browse/OFBIZ-5455 Project: OFBiz Issue Type: Bug Components: content, product Affects Versions: Trunk, 13.07.01 Environment: Multi Server, Multi Tenant Reporter: Pierre Smits Assignee: Ashish Vijaywargiya Attachments: OFBIZ-5455.patch In a multi server multi tenant setup we have defined a shared data location for storage of images etc. We have set this location in table SystemProperty as an override to the default location in catalog properties Our definition is: SystemProperty createdStamp=2014-01-03 11:30:01.892 createdTxStamp=2014-01-03 11:30:01.892 description=Default path of product images lastUpdatedStamp=2014-01-03 11:30:01.892 lastUpdatedTxStamp=2014-01-03 11:30:01.892 systemPropertyId=image.server.path systemPropertyValue=/test-data/tenant1/images/products systemResourceId=catalog/ However, this setting is not used when uploading an additional image in catalog of the tenant. In stead the default location (as in catalog.properties) is used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5455) images not stored in SystemProperty location
[ https://issues.apache.org/jira/browse/OFBIZ-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato updated OFBIZ-5455: - Affects Version/s: 13.07.01 Trunk images not stored in SystemProperty location Key: OFBIZ-5455 URL: https://issues.apache.org/jira/browse/OFBIZ-5455 Project: OFBiz Issue Type: Bug Components: content, product Affects Versions: Trunk, 13.07.01 Environment: Multi Server, Multi Tenant Reporter: Pierre Smits Assignee: Ashish Vijaywargiya Attachments: OFBIZ-5455.patch In a multi server multi tenant setup we have defined a shared data location for storage of images etc. We have set this location in table SystemProperty as an override to the default location in catalog properties Our definition is: SystemProperty createdStamp=2014-01-03 11:30:01.892 createdTxStamp=2014-01-03 11:30:01.892 description=Default path of product images lastUpdatedStamp=2014-01-03 11:30:01.892 lastUpdatedTxStamp=2014-01-03 11:30:01.892 systemPropertyId=image.server.path systemPropertyValue=/test-data/tenant1/images/products systemResourceId=catalog/ However, this setting is not used when uploading an additional image in catalog of the tenant. In stead the default location (as in catalog.properties) is used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5788) ClassCastException in DataResourceWorker.getDataResourceStream method
[ https://issues.apache.org/jira/browse/OFBIZ-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato closed OFBIZ-5788. ClassCastException in DataResourceWorker.getDataResourceStream method - Key: OFBIZ-5788 URL: https://issues.apache.org/jira/browse/OFBIZ-5788 Project: OFBiz Issue Type: Bug Components: content Affects Versions: Release Branch 13.07, Trunk Reporter: Deepak Dixit Assignee: Nicolas Malin Priority: Minor Fix For: 13.07.01, Upcoming Branch Attachments: OFBIZ-5788.patch, screenshot-1.png I am getting following error while accessing DataResourceWorker.getDataResourceStream() {quote} 20140925162041093 |-0.0.0.0-8443-exec-7 |RequestHandler |E| Request stream caused an error with the following message: Error calling event: org.ofbiz.webapp.event.EventHandlerException: Problems processing event: java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long (java.lang.Integer cannot be cast to java.lang.Long) {quote} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] [RELEASE] Apache OFBiz 13.07.01
This is the vote thread to publish the first release from the release13.07 branch. For a description of release naming and strategy see http://ofbiz.apache.org/download.html The release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ and are: * apache-ofbiz-13.07.01.zip * KEYS: text file with keys * apache-ofbiz-13.07.01.zip.asc: the detached signature file * apache-ofbiz-13.07.01.zip.md5, apache-ofbiz-13.07.01.zip.sha: checksum hashes Please download and test the zip file (*) and its signature and checksums (for instructions see http://www.apache.org/info/verification.html). Vote: [ +1] release as Apache OFBiz 13.07.01 [ -1] do not release This vote will be open for about 5 days. For more details about this process please read http://www.apache.org/foundation/voting.html Kind Regards, Jacopo (*) run at least: ant load-demo run-tests and verify that all tests are successful
Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
Hi Jacopo, I am not sure how much work was done on jackrabbit, but I think it would be useful to keep the jackrabbit20120501 branch. We were considering looking into the jcr component for integration with our system given that work was already done on it. Taher Alkhateeb On Tue, Sep 30, 2014 at 10:31 AM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
Re: jacrabbit branches A lot of work was put in there, and functionality was fairly complete when Sascha couldn't find the time anymore to work on this. Re: OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23 This is still ongoing. Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 9:52 AM, Taher Alkhateeb slidingfilame...@gmail.com wrote: Hi Jacopo, I am not sure how much work was done on jackrabbit, but I think it would be useful to keep the jackrabbit20120501 branch. We were considering looking into the jcr component for integration with our system given that work was already done on it. Taher Alkhateeb On Tue, Sep 30, 2014 at 10:31 AM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
executioncontext20091231 is a working copy of the security redesign: https://cwiki.apache.org/confluence/display/OFBTECH/OFBiz+Security+Redesign I still hope there will be some interest in it some day. Adrian Crum Sandglass Software www.sandglass-software.com On 9/30/2014 8:31 AM, Jacopo Cappellato wrote: What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
Ok, here is the list of candidates for removal updated (I have removed the 2 branches mentioned by Taher and Pierre): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Jacopo On Sep 30, 2014, at 9:56 AM, Pierre Smits pierre.sm...@gmail.com wrote: Re: jacrabbit branches A lot of work was put in there, and functionality was fairly complete when Sascha couldn't find the time anymore to work on this. Re: OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23 This is still ongoing. Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 9:52 AM, Taher Alkhateeb slidingfilame...@gmail.com wrote: Hi Jacopo, I am not sure how much work was done on jackrabbit, but I think it would be useful to keep the jackrabbit20120501 branch. We were considering looking into the jcr component for integration with our system given that work was already done on it. Taher Alkhateeb On Tue, Sep 30, 2014 at 10:31 AM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
New list after Adrian's feedback: • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Jacopo On Sep 30, 2014, at 9:59 AM, Adrian Crum adrian.c...@sandglass-software.com wrote: executioncontext20091231 is a working copy of the security redesign: https://cwiki.apache.org/confluence/display/OFBTECH/OFBiz+Security+Redesign I still hope there will be some interest in it some day. Adrian Crum Sandglass Software www.sandglass-software.com On 9/30/2014 8:31 AM, Jacopo Cappellato wrote: What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
[VOTE] PROJECTMGR in upcoming release
The Project Mgt component in the Special Purpose stack contains a set of functionalities for: - creating and managing projects (including GANTT charts) - assign phases and task to projects - assign resources to projects and tasks - enable users to write time spent on project tasks - allow third parties to gain insight in project progress and to register requests - generate invoices on time spent re time/material projects This set of functionalities is for any Professional Services organisation executing time/material projects, that provides secondment services and for those organisations that do internal projects and needs time writing. This component should be included in the release. If you agree, please cast your vote: +1 , meaning include in upcoming release 0 , meaning no opinion -1 , meaning exclude in upcoming release Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
We can remove jquery branch for sure, as we merged moved to jquery library completely. Thanks Regards — Deepak Dixit On Sep 30, 2014, at 1:32 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: New list after Adrian's feedback: • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Jacopo On Sep 30, 2014, at 9:59 AM, Adrian Crum adrian.c...@sandglass-software.com wrote: executioncontext20091231 is a working copy of the security redesign: https://cwiki.apache.org/confluence/display/OFBTECH/OFBiz+Security+Redesign I still hope there will be some interest in it some day. Adrian Crum Sandglass Software www.sandglass-software.com On 9/30/2014 8:31 AM, Jacopo Cappellato wrote: What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/ smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] PROJECTMGR in upcoming release
On Sep 30, 2014, at 10:07 AM, Pierre Smits pierre.sm...@gmail.com wrote: This component should be included in the release. If you agree, please cast your vote: +1 , meaning include in upcoming release 0 , meaning no opinion -1 , meaning exclude in upcoming release Please clarify what you mean with upcoming release. Do you mean in the upcoming new release branch (i.e. release14.10)? Jacopo
Re: [VOTE] [RELEASE] Apache OFBiz 13.07.01
-1 ecommerce is broken on release13.07 branch, ReferenceError: jQuery is not defined” error occurred on js console. It might be due to query library update, Need to fix the js path for ecommerce component. Thanks Regards — Deepak Dixit On Sep 30, 2014, at 1:16 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: This is the vote thread to publish the first release from the release13.07 branch. For a description of release naming and strategy see http://ofbiz.apache.org/download.html The release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ and are: * apache-ofbiz-13.07.01.zip * KEYS: text file with keys * apache-ofbiz-13.07.01.zip.asc: the detached signature file * apache-ofbiz-13.07.01.zip.md5, apache-ofbiz-13.07.01.zip.sha: checksum hashes Please download and test the zip file (*) and its signature and checksums (for instructions see http://www.apache.org/info/verification.html). Vote: [ +1] release as Apache OFBiz 13.07.01 [ -1] do not release This vote will be open for about 5 days. For more details about this process please read http://www.apache.org/foundation/voting.html Kind Regards, Jacopo (*) run at least: ant load-demo run-tests and verify that all tests are successful smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] [RELEASE] Apache OFBiz 13.07.01
ouch... thanks for catching this Deepak! Let's cancel this vote for now. Jacopo On Sep 30, 2014, at 10:23 AM, Deepak Dixit deepak.di...@hotwaxmedia.com wrote: -1 ecommerce is broken on release13.07 branch, ReferenceError: jQuery is not defined” error occurred on js console. It might be due to query library update, Need to fix the js path for ecommerce component. Thanks Regards — Deepak Dixit On Sep 30, 2014, at 1:16 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: This is the vote thread to publish the first release from the release13.07 branch. For a description of release naming and strategy see http://ofbiz.apache.org/download.html The release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ and are: * apache-ofbiz-13.07.01.zip * KEYS: text file with keys * apache-ofbiz-13.07.01.zip.asc: the detached signature file * apache-ofbiz-13.07.01.zip.md5, apache-ofbiz-13.07.01.zip.sha: checksum hashes Please download and test the zip file (*) and its signature and checksums (for instructions see http://www.apache.org/info/verification.html). Vote: [ +1] release as Apache OFBiz 13.07.01 [ -1] do not release This vote will be open for about 5 days. For more details about this process please read http://www.apache.org/foundation/voting.html Kind Regards, Jacopo (*) run at least: ant load-demo run-tests and verify that all tests are successful
[jira] [Created] (OFBIZ-5789) Fix the js path for ecommerce
Deepak Dixit created OFBIZ-5789: --- Summary: Fix the js path for ecommerce Key: OFBIZ-5789 URL: https://issues.apache.org/jira/browse/OFBIZ-5789 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 13.07 Reporter: Deepak Dixit Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5789) Fix the js path for ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit updated OFBIZ-5789: Attachment: OFBIZ-5789.patch Here is the patch for the fix. Fix the js path for ecommerce -- Key: OFBIZ-5789 URL: https://issues.apache.org/jira/browse/OFBIZ-5789 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 13.07 Reporter: Deepak Dixit Priority: Minor Attachments: OFBIZ-5789.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] [RELEASE] Apache OFBiz 13.07.01
Open ticket for the issue and attached patch for the fix. Here is the link for ticket https://issues.apache.org/jira/browse/OFBIZ-5789 Thanks Regards — Deepak Dixit On Sep 30, 2014, at 1:57 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: ouch... thanks for catching this Deepak! Let's cancel this vote for now. Jacopo On Sep 30, 2014, at 10:23 AM, Deepak Dixit deepak.di...@hotwaxmedia.com wrote: -1 ecommerce is broken on release13.07 branch, ReferenceError: jQuery is not defined” error occurred on js console. It might be due to query library update, Need to fix the js path for ecommerce component. Thanks Regards — Deepak Dixit On Sep 30, 2014, at 1:16 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: This is the vote thread to publish the first release from the release13.07 branch. For a description of release naming and strategy see http://ofbiz.apache.org/download.html The release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ and are: * apache-ofbiz-13.07.01.zip * KEYS: text file with keys * apache-ofbiz-13.07.01.zip.asc: the detached signature file * apache-ofbiz-13.07.01.zip.md5, apache-ofbiz-13.07.01.zip.sha: checksum hashes Please download and test the zip file (*) and its signature and checksums (for instructions see http://www.apache.org/info/verification.html). Vote: [ +1] release as Apache OFBiz 13.07.01 [ -1] do not release This vote will be open for about 5 days. For more details about this process please read http://www.apache.org/foundation/voting.html Kind Regards, Jacopo (*) run at least: ant load-demo run-tests and verify that all tests are successful smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] PROJECTMGR in upcoming release
The title implies that it is to keep it in the release you're planning to exclude it from. Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 10:11 AM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: On Sep 30, 2014, at 10:07 AM, Pierre Smits pierre.sm...@gmail.com wrote: This component should be included in the release. If you agree, please cast your vote: +1 , meaning include in upcoming release 0 , meaning no opinion -1 , meaning exclude in upcoming release Please clarify what you mean with upcoming release. Do you mean in the upcoming new release branch (i.e. release14.10)? Jacopo
Re: [VOTE] PROJECTMGR in upcoming release
Ok, got it. The release process that the OFBiz community is following is based on a feature freeze phase, that for the 13.07 branch started more than one year ago, during which only bug fixes are backported. This is done in order to stabilize the branch before an official release is done. Since the projectmgr component has never been part of the 13.07 branch then it may be unsafe to include it now just before the release is issued. It would be better to discuss its inclusion in the upcoming new release branch where it could be stabilized and bug fixed. Regards, Jacopo On Sep 30, 2014, at 11:15 AM, Pierre Smits pierre.sm...@gmail.com wrote: The title implies that it is to keep it in the release you're planning to exclude it from. Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 10:11 AM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: On Sep 30, 2014, at 10:07 AM, Pierre Smits pierre.sm...@gmail.com wrote: This component should be included in the release. If you agree, please cast your vote: +1 , meaning include in upcoming release 0 , meaning no opinion -1 , meaning exclude in upcoming release Please clarify what you mean with upcoming release. Do you mean in the upcoming new release branch (i.e. release14.10)? Jacopo
Re: [VOTE] PROJECTMGR in upcoming release
Jacopo, Back then there were already strong objections to excluding components from the release. I recall that Hans also wanted to keep the SCRUM component in the release, as well as there were proponents for BIRT and other components. These are good additions to the feature set of OFBiz and may be in use already by community members. It would be best that you solicit the advice of the entire community before a decision on excluding components from any release is taken. This affects more participants in this project than just you and the committers. Regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: Ok, got it. The release process that the OFBiz community is following is based on a feature freeze phase, that for the 13.07 branch started more than one year ago, during which only bug fixes are backported. This is done in order to stabilize the branch before an official release is done. Since the projectmgr component has never been part of the 13.07 branch then it may be unsafe to include it now just before the release is issued. It would be better to discuss its inclusion in the upcoming new release branch where it could be stabilized and bug fixed. Regards, Jacopo
[jira] [Created] (OFBIZ-5790) Json string parameters as a service input are not recognized by OFBiz ServiceEventHandler.
Amardeep Singh Jhajj created OFBIZ-5790: --- Summary: Json string parameters as a service input are not recognized by OFBiz ServiceEventHandler. Key: OFBIZ-5790 URL: https://issues.apache.org/jira/browse/OFBIZ-5790 Project: OFBiz Issue Type: Bug Affects Versions: Trunk, Release Branch 13.07 Reporter: Amardeep Singh Jhajj I was trying to pass the Json string as a input to a service, but is not recognized by ServiceEventHandler. Example Json String- {faciltyId: WebStoreWarehouse} I worked on this issue and attached a patch here. Here I have used Jackson Json library for parsing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5790) Json string parameters as a service input are not recognized by OFBiz ServiceEventHandler.
[ https://issues.apache.org/jira/browse/OFBIZ-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amardeep Singh Jhajj updated OFBIZ-5790: Attachment: jackson-databind-2.4.2.jar jackson-core-2.4.2.jar jackson-annotations-2.4.0.jar OFBIZ-5790.patch Json string parameters as a service input are not recognized by OFBiz ServiceEventHandler. -- Key: OFBIZ-5790 URL: https://issues.apache.org/jira/browse/OFBIZ-5790 Project: OFBiz Issue Type: Bug Affects Versions: Release Branch 13.07, Trunk Reporter: Amardeep Singh Jhajj Attachments: OFBIZ-5790.patch, jackson-annotations-2.4.0.jar, jackson-core-2.4.2.jar, jackson-databind-2.4.2.jar I was trying to pass the Json string as a input to a service, but is not recognized by ServiceEventHandler. Example Json String- {faciltyId: WebStoreWarehouse} I worked on this issue and attached a patch here. Here I have used Jackson Json library for parsing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: svn commit: r1627940 - /ofbiz/trunk/framework/entity/src/org/ofbiz/entity/util/EntityQuery.java
+1 Thanks Scott. Pranay Pandey HotWax Media http://www.hotwaxmedia.com On Sep 27, 2014, at 3:29 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: This is really an amazing contribution! Thank you Scott. Jacopo On Sep 27, 2014, at 11:22 AM, lekt...@apache.org wrote: Author: lektran Date: Sat Sep 27 09:22:31 2014 New Revision: 1627940 URL: http://svn.apache.org/r1627940 Log: OFBIZ-4053 Implement an entity query builder to be used as a friendlier API for executing entity queries. Entry point is the static EntityQuery.use(Delegator) method which will then return an EntityQuery instance whose methods support method chaining to set query options. The query can then be executed using the first(), list(), iterator() and one() methods which respectively return: - The first result from a result set - The full list of results from a result set - An EntityListIterator to iterate over a result set - The single record from a query that will return only one record (such as a lookup by primary key) Added: ofbiz/trunk/framework/entity/src/org/ofbiz/entity/util/EntityQuery.java (with props) Added: ofbiz/trunk/framework/entity/src/org/ofbiz/entity/util/EntityQuery.java URL: http://svn.apache.org/viewvc/ofbiz/trunk/framework/entity/src/org/ofbiz/entity/util/EntityQuery.java?rev=1627940view=auto == --- ofbiz/trunk/framework/entity/src/org/ofbiz/entity/util/EntityQuery.java (added) +++ ofbiz/trunk/framework/entity/src/org/ofbiz/entity/util/EntityQuery.java Sat Sep 27 09:22:31 2014 @@ -0,0 +1,416 @@ +/*** + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * License); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + ***/ +package org.ofbiz.entity.util; + +import java.sql.Timestamp; +import java.util.Arrays; +import java.util.List; +import java.util.Map; +import java.util.Set; + +import org.ofbiz.base.util.Debug; +import org.ofbiz.base.util.UtilMisc; +import org.ofbiz.entity.Delegator; +import org.ofbiz.entity.GenericEntityException; +import org.ofbiz.entity.GenericValue; +import org.ofbiz.entity.condition.EntityCondition; +import org.ofbiz.entity.model.DynamicViewEntity; +import org.ofbiz.entity.util.EntityFindOptions; +import org.ofbiz.entity.util.EntityListIterator; +import org.ofbiz.entity.util.EntityUtil; + +/** + * Used to setup various options for and subsequently execute entity queries. + * + * All methods to set options modify the EntityQuery instance then return this modified object to allow method call chaining. It is + * important to note that this object is not immutable and is modified internally, and returning EntityQuery is just a + * self reference for convenience. + * + * After a query the object can be further modified and then used to perform another query if desired. + */ +public class EntityQuery { + +public static final String module = EntityQuery.class.getName(); + +private Delegator delegator; +private String entityName = null; +private DynamicViewEntity dynamicViewEntity = null; +private boolean useCache = false; +private EntityCondition whereEntityCondition = null; +private SetString fieldsToSelect = null; +private ListString orderBy = null; +private Integer resultSetType = EntityFindOptions.TYPE_FORWARD_ONLY; +private Integer fetchSize = null; +private Integer maxRows = null; +private Boolean distinct = null; +private EntityCondition havingEntityCondition = null; +private boolean filterByDate = false; +private Timestamp filterByDateMoment; + + + +/** Construct an EntityQuery object for use against the specified Delegator + * @param delegator - The delegator instance to use for the query + * @return Returns a new EntityQuery object + */ +public static EntityQuery use(Delegator delegator) { +return new EntityQuery(delegator); +} + +/** Construct an EntityQuery object for use against the specified Delegator + * @param
[jira] [Updated] (OFBIZ-5790) Json string parameters as a service input are not recognized by OFBiz ServiceEventHandler.
[ https://issues.apache.org/jira/browse/OFBIZ-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum updated OFBIZ-5790: --- Priority: Minor (was: Major) Affects Version/s: (was: Release Branch 13.07) Issue Type: Improvement (was: Bug) Json string parameters as a service input are not recognized by OFBiz ServiceEventHandler. -- Key: OFBIZ-5790 URL: https://issues.apache.org/jira/browse/OFBIZ-5790 Project: OFBiz Issue Type: Improvement Affects Versions: Trunk Reporter: Amardeep Singh Jhajj Priority: Minor Attachments: OFBIZ-5790.patch, jackson-annotations-2.4.0.jar, jackson-core-2.4.2.jar, jackson-databind-2.4.2.jar I was trying to pass the Json string as a input to a service, but is not recognized by ServiceEventHandler. Example Json String- {faciltyId: WebStoreWarehouse} I worked on this issue and attached a patch here. Here I have used Jackson Json library for parsing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-5791) CommonUiLabels.xml - malformed XML
Josip Almasi created OFBIZ-5791: --- Summary: CommonUiLabels.xml - malformed XML Key: OFBIZ-5791 URL: https://issues.apache.org/jira/browse/OFBIZ-5791 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 13.07 Reporter: Josip Almasi Priority: Trivial Whoever deleted Shark didn't do it well:) There's still a line in CommonUiLabels, value xml:lang=csShark/value without property enclosure. This doesn't affect ofbiz in anyway. It did affect a script of mine though. Still, it's a malformed XML. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5791) CommonUiLabels.xml - malformed XML
[ https://issues.apache.org/jira/browse/OFBIZ-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josip Almasi updated OFBIZ-5791: Attachment: OFBIZ-5791.patch removes shark line CommonUiLabels.xml - malformed XML -- Key: OFBIZ-5791 URL: https://issues.apache.org/jira/browse/OFBIZ-5791 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 13.07 Reporter: Josip Almasi Priority: Trivial Attachments: OFBIZ-5791.patch Whoever deleted Shark didn't do it well:) There's still a line in CommonUiLabels, value xml:lang=csShark/value without property enclosure. This doesn't affect ofbiz in anyway. It did affect a script of mine though. Still, it's a malformed XML. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5790) Json string parameters as a service input are not recognized by OFBiz ServiceEventHandler.
[ https://issues.apache.org/jira/browse/OFBIZ-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153075#comment-14153075 ] Adrian Crum commented on OFBIZ-5790: Using Jackson has been discussed in other issues. The patch is not generic enough to be included in the project. It would be better to replace our existing home-grown JSON parser with Jackson, then integrate it with the service engine in a more generic way. Json string parameters as a service input are not recognized by OFBiz ServiceEventHandler. -- Key: OFBIZ-5790 URL: https://issues.apache.org/jira/browse/OFBIZ-5790 Project: OFBiz Issue Type: Improvement Affects Versions: Trunk Reporter: Amardeep Singh Jhajj Priority: Minor Attachments: OFBIZ-5790.patch, jackson-annotations-2.4.0.jar, jackson-core-2.4.2.jar, jackson-databind-2.4.2.jar I was trying to pass the Json string as a input to a service, but is not recognized by ServiceEventHandler. Example Json String- {faciltyId: WebStoreWarehouse} I worked on this issue and attached a patch here. Here I have used Jackson Json library for parsing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5726) Convert ProdCatalog CRUD service from simple to entity-auto
[ https://issues.apache.org/jira/browse/OFBIZ-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin closed OFBIZ-5726. Resolution: Fixed Assignee: Nicolas Malin (was: Jacques Le Roux) Done on trunk at revision 1628405 Convert ProdCatalog CRUD service from simple to entity-auto --- Key: OFBIZ-5726 URL: https://issues.apache.org/jira/browse/OFBIZ-5726 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 13.07, Trunk Reporter: Nicolas Malin Assignee: Nicolas Malin Priority: Trivial Labels: entity-auto, service Fix For: Upcoming Branch Attachments: OFBIZ-5726.patch I convert the ProdCatalog CRUD service to entity-auto. I have just a dout on method addProductCategoryToProdCatalog because we lost with entity-auto the test {quote} if-empty field=productCategory add-errorfail-property resource=ProductUiLabels property=ProductCategoryNotFoundForCategoryID//add-error /if-empty check-errors/ {quote} I run manual test : * create/update catalog * create/update/delete category association * create/update/delete party association I run ./ant clean-all load-demo run-tests with success -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5726) Convert ProdCatalog CRUD service from simple to entity-auto
[ https://issues.apache.org/jira/browse/OFBIZ-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-5726: - Fix Version/s: Upcoming Branch Convert ProdCatalog CRUD service from simple to entity-auto --- Key: OFBIZ-5726 URL: https://issues.apache.org/jira/browse/OFBIZ-5726 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 13.07, Trunk Reporter: Nicolas Malin Assignee: Jacques Le Roux Priority: Trivial Labels: entity-auto, service Fix For: Upcoming Branch Attachments: OFBIZ-5726.patch I convert the ProdCatalog CRUD service to entity-auto. I have just a dout on method addProductCategoryToProdCatalog because we lost with entity-auto the test {quote} if-empty field=productCategory add-errorfail-property resource=ProductUiLabels property=ProductCategoryNotFoundForCategoryID//add-error /if-empty check-errors/ {quote} I run manual test : * create/update catalog * create/update/delete category association * create/update/delete party association I run ./ant clean-all load-demo run-tests with success -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-5791) CommonUiLabels.xml - malformed XML
[ https://issues.apache.org/jira/browse/OFBIZ-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin reassigned OFBIZ-5791: Assignee: Nicolas Malin CommonUiLabels.xml - malformed XML -- Key: OFBIZ-5791 URL: https://issues.apache.org/jira/browse/OFBIZ-5791 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 13.07 Reporter: Josip Almasi Assignee: Nicolas Malin Priority: Trivial Attachments: OFBIZ-5791.patch Whoever deleted Shark didn't do it well:) There's still a line in CommonUiLabels, value xml:lang=csShark/value without property enclosure. This doesn't affect ofbiz in anyway. It did affect a script of mine though. Still, it's a malformed XML. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5791) CommonUiLabels.xml - malformed XML
[ https://issues.apache.org/jira/browse/OFBIZ-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin closed OFBIZ-5791. CommonUiLabels.xml - malformed XML -- Key: OFBIZ-5791 URL: https://issues.apache.org/jira/browse/OFBIZ-5791 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 13.07 Reporter: Josip Almasi Assignee: Nicolas Malin Priority: Trivial Fix For: 13.07.01 Attachments: OFBIZ-5791.patch Whoever deleted Shark didn't do it well:) There's still a line in CommonUiLabels, value xml:lang=csShark/value without property enclosure. This doesn't affect ofbiz in anyway. It did affect a script of mine though. Still, it's a malformed XML. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
I update OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ every week, and plan to merge it when I will get enough continuous time. Also I'd like to keep webhelp-2012-12-07 as long as a Neogia (now rather ofbiz.fr) addon will not be officially released I think we should keep the 2 jackrabbit branches except if we are sure about dropping the older one. The late one should be kept IMO. I don't know if 2013_RemoveJavolution is still a WIP? I'm sure jquery can be dropped For the rest I have no clear ideas. Jacques Le 30/09/2014 09:31, Jacopo Cappellato a écrit : What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
Inline Le 30/09/2014 10:01, Jacopo Cappellato a écrit : • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ Initialized by me, but the gap is really important with the trunk, I prefer restart from scratch • 20120209RemoveBsh/ • 20120329_portletWidget/ I just ask before. • 2013_RemoveJavolution/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ I just check what contains exactly before delete it, I will interesting by continue HMTL5 implantation • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/
Re: svn commit: r1628405 - in /ofbiz/trunk/applications/product: script/org/ofbiz/product/catalog/CatalogServices.xml servicedef/services.xml
Hi Nicolas, When possible please put a least the number of the Jira issue in commit, it's easier to follow things (links are even easier ;) Thanks Jacques Le 30/09/2014 13:59, nma...@apache.org a écrit : Author: nmalin Date: Tue Sep 30 11:59:29 2014 New Revision: 1628405 URL: http://svn.apache.org/r1628405 Log: Convert the ProdCatalog CRUD simple service to entity-auto Modified: ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml ofbiz/trunk/applications/product/servicedef/services.xml Modified: ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml?rev=1628405r1=1628404r2=1628405view=diff == --- ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml (original) +++ ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml Tue Sep 30 11:59:29 2014 @@ -20,92 +20,6 @@ under the License. simple-methods xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=http://ofbiz.apache.org/dtds/simple-methods-v2.xsd; -simple-method method-name=createProdCatalog short-description=Create an ProdCatalog -make-value value-field=newEntity entity-name=ProdCatalog/ -set-nonpk-fields map=parameters value-field=newEntity/ - -if-empty field=parameters.prodCatalogId -sequenced-id sequence-name=ProdCatalog field=newEntity.prodCatalogId/ -else -set field=newEntity.prodCatalogId from-field=parameters.prodCatalogId/ -check-id field=newEntity.prodCatalogId/ -check-errors/ -/else -/if-empty -field-to-result field=newEntity.prodCatalogId result-name=prodCatalogId/ - -create-value value-field=newEntity/ -/simple-method -simple-method method-name=updateProdCatalog short-description=Update an ProdCatalog -entity-one entity-name=ProdCatalog value-field=prodCatalog/ -set-nonpk-fields map=parameters value-field=prodCatalog/ -store-value value-field=prodCatalog/ -/simple-method -simple-method method-name=deleteProdCatalog short-description=Delete an ProdCatalog -entity-one entity-name=ProdCatalog value-field=prodCatalog/ -remove-value value-field=prodCatalog/ -/simple-method - -simple-method method-name=addProductCategoryToProdCatalog short-description=Add Category To ProdCatalog -!-- Check that the ProductCategory exists -- -entity-one entity-name=ProductCategory value-field=productCategory/ -if-empty field=productCategory -add-errorfail-property resource=ProductUiLabels property=ProductCategoryNotFoundForCategoryID//add-error -/if-empty -check-errors/ - -make-value value-field=newEntity entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=newEntity/ -set-nonpk-fields map=parameters value-field=newEntity/ - -if-empty field=newEntity.fromDate -now-timestamp field=nowTimestamp/ -set from-field=nowTimestamp field=newEntity.fromDate/ -/if-empty - -create-value value-field=newEntity/ -/simple-method -simple-method method-name=updateProductCategoryToProdCatalog short-description=Remove ContactMech From ProdCatalog - -make-value value-field=lookupPKMap entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=lookupPKMap/ -find-by-primary-key entity-name=ProdCatalogCategory map=lookupPKMap value-field=prodCatalogCategory/ -set-nonpk-fields map=parameters value-field=prodCatalogCategory/ -store-value value-field=prodCatalogCategory/ -/simple-method -simple-method method-name=removeProductCategoryFromProdCatalog short-description=Remove ContactMech From ProdCatalog - -make-value value-field=lookupPKMap entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=lookupPKMap/ -find-by-primary-key entity-name=ProdCatalogCategory map=lookupPKMap value-field=prodCatalogCategory/ -remove-value value-field=prodCatalogCategory/ -/simple-method - -!-- Party and Catalog services -- -simple-method method-name=addProdCatalogToParty short-description=Add ProdCatalog To Party -make-value value-field=newEntity entity-name=ProdCatalogRole/ -set-pk-fields map=parameters value-field=newEntity/ -set-nonpk-fields map=parameters value-field=newEntity/ - -if-empty field=newEntity.fromDate -now-timestamp field=newEntity.fromDate/ -/if-empty - -create-value value-field=newEntity/ -/simple-method -simple-method method-name=updateProdCatalogToParty
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
On Sep 30, 2014, at 6:23 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: I update OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ every week, and plan to merge it when I will get enough continuous time. Got it. Also I'd like to keep webhelp-2012-12-07 as long as a Neogia (now rather ofbiz.fr) addon will not be officially released Got it. I think we should keep the 2 jackrabbit branches except if we are sure about dropping the older one. The late one should be kept IMO. I have already removed from the list the newest jackrabbit branch (there are 3): the two ones you see in this list are two older copies. I don't know if 2013_RemoveJavolution is still a WIP? I'm sure jquery can be dropped For the rest I have no clear ideas. Jacques Le 30/09/2014 09:31, Jacopo Cappellato a écrit : What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
Hi Nicolas, On Sep 30, 2014, at 6:28 PM, Nicolas Malin nicolas.ma...@nereide.fr wrote: • 20120329_portletWidget/ I just ask before. do you mean that we should keep it? Jacopo
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
On Sep 30, 2014, at 6:49 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: I think we should keep the 2 jackrabbit branches except if we are sure about dropping the older one. The late one should be kept IMO. I have already removed from the list the newest jackrabbit branch (there are 3): the two ones you see in this list are two older copies. I was wrong (got confused with the executionframework): there are 2 jackrabbit instances. Jacopo
[jira] [Assigned] (OFBIZ-5789) Fix the js path for ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-5789: -- Assignee: Jacques Le Roux Fix the js path for ecommerce -- Key: OFBIZ-5789 URL: https://issues.apache.org/jira/browse/OFBIZ-5789 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 13.07 Reporter: Deepak Dixit Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-5789.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5789) Fix the js path for ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-5789. -- Resolution: Fixed Fix Version/s: Upcoming Branch Thanks Deepak, Your patch is commited inR13.07 I added jquery-migrate-1.2.1.js in CommonPopUpDecorator at r1628491. Fix the js path for ecommerce -- Key: OFBIZ-5789 URL: https://issues.apache.org/jira/browse/OFBIZ-5789 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 13.07 Reporter: Deepak Dixit Assignee: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-5789.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] [RELEASE] Apache OFBiz 13.07.01
Good catch Deepak, it's fixed Jacques Le 30/09/2014 10:57, Deepak Dixit a écrit : Open ticket for the issue and attached patch for the fix. Here is the link for ticket https://issues.apache.org/jira/browse/OFBIZ-5789 Thanks Regards — Deepak Dixit On Sep 30, 2014, at 1:57 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: ouch... thanks for catching this Deepak! Let's cancel this vote for now. Jacopo On Sep 30, 2014, at 10:23 AM, Deepak Dixit deepak.di...@hotwaxmedia.com wrote: -1 ecommerce is broken on release13.07 branch, ReferenceError: jQuery is not defined” error occurred on js console. It might be due to query library update, Need to fix the js path for ecommerce component. Thanks Regards — Deepak Dixit On Sep 30, 2014, at 1:16 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: This is the vote thread to publish the first release from the release13.07 branch. For a description of release naming and strategy see http://ofbiz.apache.org/download.html The release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ and are: * apache-ofbiz-13.07.01.zip * KEYS: text file with keys * apache-ofbiz-13.07.01.zip.asc: the detached signature file * apache-ofbiz-13.07.01.zip.md5, apache-ofbiz-13.07.01.zip.sha: checksum hashes Please download and test the zip file (*) and its signature and checksums (for instructions see http://www.apache.org/info/verification.html). Vote: [ +1] release as Apache OFBiz 13.07.01 [ -1] do not release This vote will be open for about 5 days. For more details about this process please read http://www.apache.org/foundation/voting.html Kind Regards, Jacopo (*) run at least: ant load-demo run-tests and verify that all tests are successful
[jira] [Created] (OFBIZ-5792) Provide form widget drop-down find type control
Christian Carlow created OFBIZ-5792: --- Summary: Provide form widget drop-down find type control Key: OFBIZ-5792 URL: https://issues.apache.org/jira/browse/OFBIZ-5792 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Form widgets should be extended to support drop-down-find controls to provide filtering options similar to those available for the text-find control such as equals, empty, and notEqual. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
Hi jacopo • 20120329_portletWidget/ I just ask before. do you mean that we should keep it? Or delete it, I will ask to people has been worked on it before :) Jacopo
Re: svn commit: r1628405 - in /ofbiz/trunk/applications/product: script/org/ofbiz/product/catalog/CatalogServices.xml servicedef/services.xml
Ho, sorry Jacques, I misunderstood this : Also, not everone knows how jira works. Or confluence. Or AutoConfigMaintenceWidgetApplication. What you may thing as a sensible cross-reference(OFBIZ-, debbugs ) may mean nothing to the person reading your changelog. (https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities) I read and understood do not set issue reference, but I totally wrong. It's more do not issue reference only !. Thanks for this remark, I will correct my commit's comment the next time. Nicolas Le 30/09/2014 18:43, Jacques Le Roux a écrit : Hi Nicolas, When possible please put a least the number of the Jira issue in commit, it's easier to follow things (links are even easier ;) Thanks Jacques Le 30/09/2014 13:59, nma...@apache.org a écrit : Author: nmalin Date: Tue Sep 30 11:59:29 2014 New Revision: 1628405 URL: http://svn.apache.org/r1628405 Log: Convert the ProdCatalog CRUD simple service to entity-auto Modified: ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml ofbiz/trunk/applications/product/servicedef/services.xml Modified: ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml?rev=1628405r1=1628404r2=1628405view=diff == --- ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml (original) +++ ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml Tue Sep 30 11:59:29 2014 @@ -20,92 +20,6 @@ under the License. simple-methods xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=http://ofbiz.apache.org/dtds/simple-methods-v2.xsd; -simple-method method-name=createProdCatalog short-description=Create an ProdCatalog -make-value value-field=newEntity entity-name=ProdCatalog/ -set-nonpk-fields map=parameters value-field=newEntity/ - -if-empty field=parameters.prodCatalogId -sequenced-id sequence-name=ProdCatalog field=newEntity.prodCatalogId/ -else -set field=newEntity.prodCatalogId from-field=parameters.prodCatalogId/ -check-id field=newEntity.prodCatalogId/ -check-errors/ -/else -/if-empty -field-to-result field=newEntity.prodCatalogId result-name=prodCatalogId/ - -create-value value-field=newEntity/ -/simple-method -simple-method method-name=updateProdCatalog short-description=Update an ProdCatalog -entity-one entity-name=ProdCatalog value-field=prodCatalog/ -set-nonpk-fields map=parameters value-field=prodCatalog/ -store-value value-field=prodCatalog/ -/simple-method -simple-method method-name=deleteProdCatalog short-description=Delete an ProdCatalog -entity-one entity-name=ProdCatalog value-field=prodCatalog/ -remove-value value-field=prodCatalog/ -/simple-method - -simple-method method-name=addProductCategoryToProdCatalog short-description=Add Category To ProdCatalog -!-- Check that the ProductCategory exists -- -entity-one entity-name=ProductCategory value-field=productCategory/ -if-empty field=productCategory -add-errorfail-property resource=ProductUiLabels property=ProductCategoryNotFoundForCategoryID//add-error -/if-empty -check-errors/ - -make-value value-field=newEntity entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=newEntity/ -set-nonpk-fields map=parameters value-field=newEntity/ - -if-empty field=newEntity.fromDate -now-timestamp field=nowTimestamp/ -set from-field=nowTimestamp field=newEntity.fromDate/ -/if-empty - -create-value value-field=newEntity/ -/simple-method -simple-method method-name=updateProductCategoryToProdCatalog short-description=Remove ContactMech From ProdCatalog - -make-value value-field=lookupPKMap entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=lookupPKMap/ -find-by-primary-key entity-name=ProdCatalogCategory map=lookupPKMap value-field=prodCatalogCategory/ -set-nonpk-fields map=parameters value-field=prodCatalogCategory/ -store-value value-field=prodCatalogCategory/ -/simple-method -simple-method method-name=removeProductCategoryFromProdCatalog short-description=Remove ContactMech From ProdCatalog - -make-value value-field=lookupPKMap entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=lookupPKMap/ -find-by-primary-key entity-name=ProdCatalogCategory map=lookupPKMap value-field=prodCatalogCategory/ -remove-value
Re: svn commit: r1628405 - in /ofbiz/trunk/applications/product: script/org/ofbiz/product/catalog/CatalogServices.xml servicedef/services.xml
Also, please put the revision number in the Jira issue. That helps others doing research on changes. Adrian Crum Sandglass Software www.sandglass-software.com On 9/30/2014 5:43 PM, Jacques Le Roux wrote: Hi Nicolas, When possible please put a least the number of the Jira issue in commit, it's easier to follow things (links are even easier ;) Thanks Jacques Le 30/09/2014 13:59, nma...@apache.org a écrit : Author: nmalin Date: Tue Sep 30 11:59:29 2014 New Revision: 1628405 URL: http://svn.apache.org/r1628405 Log: Convert the ProdCatalog CRUD simple service to entity-auto Modified: ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml ofbiz/trunk/applications/product/servicedef/services.xml Modified: ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml?rev=1628405r1=1628404r2=1628405view=diff == --- ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml (original) +++ ofbiz/trunk/applications/product/script/org/ofbiz/product/catalog/CatalogServices.xml Tue Sep 30 11:59:29 2014 @@ -20,92 +20,6 @@ under the License. simple-methods xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=http://ofbiz.apache.org/dtds/simple-methods-v2.xsd; -simple-method method-name=createProdCatalog short-description=Create an ProdCatalog -make-value value-field=newEntity entity-name=ProdCatalog/ -set-nonpk-fields map=parameters value-field=newEntity/ - -if-empty field=parameters.prodCatalogId -sequenced-id sequence-name=ProdCatalog field=newEntity.prodCatalogId/ -else -set field=newEntity.prodCatalogId from-field=parameters.prodCatalogId/ -check-id field=newEntity.prodCatalogId/ -check-errors/ -/else -/if-empty -field-to-result field=newEntity.prodCatalogId result-name=prodCatalogId/ - -create-value value-field=newEntity/ -/simple-method -simple-method method-name=updateProdCatalog short-description=Update an ProdCatalog -entity-one entity-name=ProdCatalog value-field=prodCatalog/ -set-nonpk-fields map=parameters value-field=prodCatalog/ -store-value value-field=prodCatalog/ -/simple-method -simple-method method-name=deleteProdCatalog short-description=Delete an ProdCatalog -entity-one entity-name=ProdCatalog value-field=prodCatalog/ -remove-value value-field=prodCatalog/ -/simple-method - -simple-method method-name=addProductCategoryToProdCatalog short-description=Add Category To ProdCatalog -!-- Check that the ProductCategory exists -- -entity-one entity-name=ProductCategory value-field=productCategory/ -if-empty field=productCategory -add-errorfail-property resource=ProductUiLabels property=ProductCategoryNotFoundForCategoryID//add-error -/if-empty -check-errors/ - -make-value value-field=newEntity entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=newEntity/ -set-nonpk-fields map=parameters value-field=newEntity/ - -if-empty field=newEntity.fromDate -now-timestamp field=nowTimestamp/ -set from-field=nowTimestamp field=newEntity.fromDate/ -/if-empty - -create-value value-field=newEntity/ -/simple-method -simple-method method-name=updateProductCategoryToProdCatalog short-description=Remove ContactMech From ProdCatalog - -make-value value-field=lookupPKMap entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=lookupPKMap/ -find-by-primary-key entity-name=ProdCatalogCategory map=lookupPKMap value-field=prodCatalogCategory/ -set-nonpk-fields map=parameters value-field=prodCatalogCategory/ -store-value value-field=prodCatalogCategory/ -/simple-method -simple-method method-name=removeProductCategoryFromProdCatalog short-description=Remove ContactMech From ProdCatalog - -make-value value-field=lookupPKMap entity-name=ProdCatalogCategory/ -set-pk-fields map=parameters value-field=lookupPKMap/ -find-by-primary-key entity-name=ProdCatalogCategory map=lookupPKMap value-field=prodCatalogCategory/ -remove-value value-field=prodCatalogCategory/ -/simple-method - -!-- Party and Catalog services -- -simple-method method-name=addProdCatalogToParty short-description=Add ProdCatalog To Party -make-value value-field=newEntity entity-name=ProdCatalogRole/ -set-pk-fields map=parameters value-field=newEntity/ -set-nonpk-fields map=parameters value-field=newEntity/ - -if-empty field=newEntity.fromDate -now-timestamp
Re: Housekeeping of the OFBiz svn tree: removing some old/unused experimental branches
20120329_portletWidget and webhelp-2012-12-07 have been migrated as addon on ofbizextra so you can remove its. They are available for trunk and 13.07. Olivier Le 30/09/2014 10:02, Jacopo Cappellato a écrit : New list after Adrian's feedback: • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Jacopo On Sep 30, 2014, at 9:59 AM, Adrian Crum adrian.c...@sandglass-software.com wrote: executioncontext20091231 is a working copy of the security redesign: https://cwiki.apache.org/confluence/display/OFBTECH/OFBiz+Security+Redesign I still hope there will be some interest in it some day. Adrian Crum Sandglass Software www.sandglass-software.com On 9/30/2014 8:31 AM, Jacopo Cappellato wrote: What do you think about removing some old and no more active experimental branches? Please let me know what are the ones we should keep. Here is the current list of experimental branches (*): • 2015ScreenWidgetRedesign/ • 20111205EmailHandling/ • 20120209RemoveBsh/ • 20120329_portletWidget/ • 2013_RemoveJavolution/ • OFBIZ-5312-ofbiz-ecommerce-seo-2013-10-23/ • addbirt/ • executioncontext20090716/ • executioncontext20090812/ • executioncontext20091231/ • frontendNewTheme2013-05-10/ • htmlfive_20110529/ • improved-entityengine-features-20120528/ • jackrabbit20100709/ • jackrabbit20120501/ • jquery/ • multitenant20100310/ • webhelp-2012-12-07/ Regards, Jacopo (*) https://svn.apache.org/repos/asf/ofbiz/branches/
[jira] [Commented] (OFBIZ-5789) Fix the js path for ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14154355#comment-14154355 ] Deepak Dixit commented on OFBIZ-5789: - Thanks Jacques. Fix the js path for ecommerce -- Key: OFBIZ-5789 URL: https://issues.apache.org/jira/browse/OFBIZ-5789 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 13.07 Reporter: Deepak Dixit Assignee: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-5789.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
OFBIZ manual??
Hi all, I am trying to understand what ofbiz is, its uses and capabilities. I have been messing around with it for about a year or two, on and off. I have tried understading it from the end user point of view, but the interface is too complicated and have to spend days trying to do something trivial that I can do in seconds in my proprietary wms, like adding a test order to the system, in many cases I have get java errors that only the devs should be able to see and they are unrecoverable. I need some help getting to some documentation on how to use the product, as I am evaluating to use it as a wms platform. but I can not use it out of the box for my purposes, since it seems very unpolished and buggy. Thanks for any help..