[jira] [Commented] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393306#comment-15393306 ] Gil Portenseigne commented on OFBIZ-7808: - Hi Jacques, it must be this one : http://markmail.org/message/5bun2i5bmnr7hix4 > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375263#comment-15375263 ] Gil Portenseigne commented on OFBIZ-7763: - Yes Jacques, i did hesitated to implement it like that, i will try and test this upgrade next week, if no-one has already done it since. > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: Upcoming Branch > > Attachments: OFBIZ-7763.patch, beanshell-removal-part1.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372765#comment-15372765 ] Gil Portenseigne commented on OFBIZ-7763: - Yes I tried to be clear enough in code to ease improvement, this trick is there to avoid going through the 1600+ use-when in the codebase, adding "context." to each variable. But i do not know where to write it down other than in the code itself. (thanks for the review by the way) > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: Upcoming Branch > > Attachments: OFBIZ-7763.patch, beanshell-removal-part1.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7622) Add "changeByUserLoginId" field for CustRequestStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372618#comment-15372618 ] Gil Portenseigne commented on OFBIZ-7622: - Adding an option to desactivate logging of status changes (like store.login.history.on.service.auth property) is good for your concern. Being active by default. But i don't see the point to track every change on every table, i think it's a bit to much. The audit log system will suffice to monitor sensible processes in my opinion. > Add "changeByUserLoginId" field for CustRequestStatus > - > > Key: OFBIZ-7622 > URL: https://issues.apache.org/jira/browse/OFBIZ-7622 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Julien NICOLAS > Attachments: OFBIZ-7622.patch, OFBIZ-7622.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-7763. --- > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: Upcoming Branch > > Attachments: OFBIZ-7763.patch, beanshell-removal-part1.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne resolved OFBIZ-7763. - Resolution: Fixed Fix Version/s: Upcoming Branch Commited in trunk r1752231 Thanks Jacopo for your patch, Deepak and Rishi for the subtasks and Nicolas for the review. > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: Upcoming Branch > > Attachments: OFBIZ-7763.patch, beanshell-removal-part1.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7763: Attachment: (was: OFBIZ-7763.patch) > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-7763.patch, beanshell-removal-part1.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7763: Attachment: OFBIZ-7763.patch Last rev of my patch, i will commit it soon > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-7763.patch, OFBIZ-7763.patch, > beanshell-removal-part1.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7763: Attachment: (was: OFBIZ-7763.patch) > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-7763.patch, OFBIZ-7763.patch, > beanshell-removal-part1.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7743) Move files in gradle folder to a location within base component of the framework stack
[ https://issues.apache.org/jira/browse/OFBIZ-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370331#comment-15370331 ] Gil Portenseigne commented on OFBIZ-7743: - I think the point Jacques tried to raise was that files of peripherical tools like scm, build-tool, scripts, etc., are not part of the OFBiz framework. So there is no need to put them into the framework folder. > Move files in gradle folder to a location within base component of the > framework stack > -- > > Key: OFBIZ-7743 > URL: https://issues.apache.org/jira/browse/OFBIZ-7743 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits > > Currently the gradle folder and its content is in the root of the OFBiz > implementation. This should be - as part of the framework stack - reside in > the base component of the framework folder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7763: Attachment: OFBIZ-7763.patch This patch, fix all use-when using groovyShell instead of bsh, compiling with all bsh lib removed. I was forced to analyse expression to identify the groovy variable, to set non existent one in context to null in binding, avoiding Exception... I will reread it this week-end, it needs more tests... Any comments and tests are welcome. > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-7763.patch, OFBIZ-7763.patch, > beanshell-removal-part1.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system
[ https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7534: Attachment: OFBizRemoteJarList.csv This is the last revision with the missing lib and some fix/comments > Migrate OFBiz from Apache Ant to Gradle build system > > > Key: OFBIZ-7534 > URL: https://issues.apache.org/jira/browse/OFBIZ-7534 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Labels: ant, build-tools, gradle > Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, > OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, > OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, > gradle-wrapper.jar > > > This is a major refactoring task referring to the [email > thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle] > in which the community voted for the switch after a proposal from the PMC > The purpose of this JIRA is to achieve the following objectives > - Fully implement a working compiling system in Gradle that passes all tests > - Remove all ant and maven build scripts from the system > - update the documentation of the system to reflect these changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367290#comment-15367290 ] Gil Portenseigne commented on OFBIZ-7763: - [~deepak.dixit] keep in mind thats an unfinished work, do not hesitate to comment/improve it :) > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-7763.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7763) Replace bshInterpreter with groovyShell
[ https://issues.apache.org/jira/browse/OFBIZ-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7763: Attachment: OFBIZ-7763.patch This patch is that I started to do a month ago about the subject, the new issue implying these changes is that variable in use-when needs "context." prefix to be interprated by groovyShell. > Replace bshInterpreter with groovyShell > --- > > Key: OFBIZ-7763 > URL: https://issues.apache.org/jira/browse/OFBIZ-7763 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-7763.patch > > > To support the migration to gradle, removing bsh.jar dependency from the > project, and improve readability and fonctionnalities following > [~deepak.dixit] idea expressed here > https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7763) Replace bshInterpreter with groovyShell
Gil Portenseigne created OFBIZ-7763: --- Summary: Replace bshInterpreter with groovyShell Key: OFBIZ-7763 URL: https://issues.apache.org/jira/browse/OFBIZ-7763 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Gil Portenseigne Assignee: Gil Portenseigne To support the migration to gradle, removing bsh.jar dependency from the project, and improve readability and fonctionnalities following [~deepak.dixit] idea expressed here https://issues.apache.org/jira/browse/OFBIZ-7576?focusedCommentId=15347972 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system
[ https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7534: Attachment: OFBizRemoteJarList.csv Tomcat annotation update, thanks [~jacopoc] > Migrate OFBiz from Apache Ant to Gradle build system > > > Key: OFBIZ-7534 > URL: https://issues.apache.org/jira/browse/OFBIZ-7534 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Labels: ant, build-tools, gradle > Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, > OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, > OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, build.gradle, > gradle-wrapper.jar > > > This is a major refactoring task referring to the [email > thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle] > in which the community voted for the switch after a proposal from the PMC > The purpose of this JIRA is to achieve the following objectives > - Fully implement a working compiling system in Gradle that passes all tests > - Remove all ant and maven build scripts from the system > - update the documentation of the system to reflect these changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system
[ https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7534: Attachment: OFBizRemoteJarList.csv > Migrate OFBiz from Apache Ant to Gradle build system > > > Key: OFBIZ-7534 > URL: https://issues.apache.org/jira/browse/OFBIZ-7534 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Labels: ant, build-tools, gradle > Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, > OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, > OFBizRemoteJarList.csv, build.gradle, gradle-wrapper.jar > > > This is a major refactoring task referring to the [email > thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle] > in which the community voted for the switch after a proposal from the PMC > The purpose of this JIRA is to achieve the following objectives > - Fully implement a working compiling system in Gradle that passes all tests > - Remove all ant and maven build scripts from the system > - update the documentation of the system to reflect these changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system
[ https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7534: Attachment: OFBizRemoteJarList.csv The csv file containing references to the remote libs is joined, https://framacalc.org/OFBizRemoteJarList remains active if more work is needed. > Migrate OFBiz from Apache Ant to Gradle build system > > > Key: OFBIZ-7534 > URL: https://issues.apache.org/jira/browse/OFBIZ-7534 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Labels: ant, build-tools, gradle > Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, > OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, > build.gradle, gradle-wrapper.jar > > > This is a major refactoring task referring to the [email > thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle] > in which the community voted for the switch after a proposal from the PMC > The purpose of this JIRA is to achieve the following objectives > - Fully implement a working compiling system in Gradle that passes all tests > - Remove all ant and maven build scripts from the system > - update the documentation of the system to reflect these changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system
[ https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360484#comment-15360484 ] Gil Portenseigne edited comment on OFBIZ-7534 at 7/3/16 9:38 AM: - All help is welcome, we need to find a get the correct jcenter URL ( bintray.com/bintray/jcenter ) for each jar mentionned in the post. The goal is to replace the jar in OFBiz by the corresponding remote one. For that purpose we created a framacalc to store the references for each jar : https://framacalc.org/OFBizRemoteJarList Feel free to edit it to add the corresponding remote you found and for each be sure to get the right lib, if uncertain : # delete the local lib # download the remote lib to the same location # compile The syntax to follow is : Syntax: '::' Example: 'org.apache.commons:commons-dbcp2:2.1.1' was (Author: gil portenseigne): All help is welcome, we need to find a get the correct jcenter URL ( bintray.com/bintray/jcenter ) for each jar mentionned in the post. The goal is to replace the jar in OFBiz by the corresponding remote one. For that purpose we created a framacalc to store the references for each jar : https://framacalc.org/OFBizRemoteJarList Feel free to edit it to add the corresponding remote you found and for each be sure to get the right lib, if uncertain : # delete the local lib # download the remote lib to the same location # compile > Migrate OFBiz from Apache Ant to Gradle build system > > > Key: OFBIZ-7534 > URL: https://issues.apache.org/jira/browse/OFBIZ-7534 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Labels: ant, build-tools, gradle > Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, > OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, build.gradle, > gradle-wrapper.jar > > > This is a major refactoring task referring to the [email > thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle] > in which the community voted for the switch after a proposal from the PMC > The purpose of this JIRA is to achieve the following objectives > - Fully implement a working compiling system in Gradle that passes all tests > - Remove all ant and maven build scripts from the system > - update the documentation of the system to reflect these changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system
[ https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360484#comment-15360484 ] Gil Portenseigne commented on OFBIZ-7534: - All help is welcome, we need to find a get the correct jcenter URL ( bintray.com/bintray/jcenter ) for each jar mentionned in the post. The goal is to replace the jar in OFBiz by the corresponding remote one. For that purpose we created a framacalc to store the references for each jar : https://framacalc.org/OFBizRemoteJarList Feel free to edit it to add the corresponding remote you found and for each be sure to get the right lib, if uncertain : # delete the local lib # download the remote lib to the same location # compile > Migrate OFBiz from Apache Ant to Gradle build system > > > Key: OFBIZ-7534 > URL: https://issues.apache.org/jira/browse/OFBIZ-7534 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Labels: ant, build-tools, gradle > Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, > OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, build.gradle, > gradle-wrapper.jar > > > This is a major refactoring task referring to the [email > thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle] > in which the community voted for the switch after a proposal from the PMC > The purpose of this JIRA is to achieve the following objectives > - Fully implement a working compiling system in Gradle that passes all tests > - Remove all ant and maven build scripts from the system > - update the documentation of the system to reflect these changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7205) Create party resume not working. ResumeId doesn't have text field to enter
[ https://issues.apache.org/jira/browse/OFBIZ-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321610#comment-15321610 ] Gil Portenseigne commented on OFBIZ-7205: - Thank you for your detailed answer. The fix i just commit did fix the functionnality in both component. >From my point of view, partymgr application is a global component about >managing general party data out of a particular process, as an integrator, it >can be used for data maintenance, and to build its own component using the >screens/forms/services/etc. of the partymgr application. So i see no problem >having the functionnality in it. > Create party resume not working. ResumeId doesn't have text field to enter > -- > > Key: OFBIZ-7205 > URL: https://issues.apache.org/jira/browse/OFBIZ-7205 > Project: OFBiz > Issue Type: Bug > Components: humanres, party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Amardeep Singh Jhajj >Assignee: Gil Portenseigne > Fix For: 14.12.01, 15.12.01, 13.07.04 > > Attachments: OFBIZ-7205-Screen-Shot.png, OFBIZ-7205.patch > > > Please refer attached screenshot. > Steps to regenerate: > 1. Go to > https://localhost:8443/partymgr/control/EditPartyResumes?partyId=admin. > 2. Create Resume form does not have ResumeId text field. Cannot add resume to > party from here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7205) Create party resume not working. ResumeId doesn't have text field to enter
[ https://issues.apache.org/jira/browse/OFBIZ-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-7205. --- > Create party resume not working. ResumeId doesn't have text field to enter > -- > > Key: OFBIZ-7205 > URL: https://issues.apache.org/jira/browse/OFBIZ-7205 > Project: OFBiz > Issue Type: Bug > Components: humanres, party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Amardeep Singh Jhajj >Assignee: Gil Portenseigne > Fix For: 14.12.01, 15.12.01, 13.07.04 > > Attachments: OFBIZ-7205-Screen-Shot.png, OFBIZ-7205.patch > > > Please refer attached screenshot. > Steps to regenerate: > 1. Go to > https://localhost:8443/partymgr/control/EditPartyResumes?partyId=admin. > 2. Create Resume form does not have ResumeId text field. Cannot add resume to > party from here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7205) Create party resume not working. ResumeId doesn't have text field to enter
[ https://issues.apache.org/jira/browse/OFBIZ-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321579#comment-15321579 ] Gil Portenseigne edited comment on OFBIZ-7205 at 6/8/16 10:41 PM: -- There was a bit more than the missing field, in this patch i fixed : - Fix the partyResume entity-one for EditPartyResumes screen - Fix use-when condition on partyId and submit fields in EditPartyResume form - Fix the edit and delete link to allow modification and refresh with partyId in context. was (Author: gil portenseigne): There was a bit more than the missing field, in this patch i fixed : - the partyResume entity-one - use-when condition on partyId field - use-when condition on submit button (for the label) - delete link to refresh with partyId in context. > Create party resume not working. ResumeId doesn't have text field to enter > -- > > Key: OFBIZ-7205 > URL: https://issues.apache.org/jira/browse/OFBIZ-7205 > Project: OFBiz > Issue Type: Bug > Components: humanres, party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Amardeep Singh Jhajj >Assignee: Gil Portenseigne > Attachments: OFBIZ-7205-Screen-Shot.png, OFBIZ-7205.patch > > > Please refer attached screenshot. > Steps to regenerate: > 1. Go to > https://localhost:8443/partymgr/control/EditPartyResumes?partyId=admin. > 2. Create Resume form does not have ResumeId text field. Cannot add resume to > party from here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7205) Create party resume not working. ResumeId doesn't have text field to enter
[ https://issues.apache.org/jira/browse/OFBIZ-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7205: Component/s: humanres > Create party resume not working. ResumeId doesn't have text field to enter > -- > > Key: OFBIZ-7205 > URL: https://issues.apache.org/jira/browse/OFBIZ-7205 > Project: OFBiz > Issue Type: Bug > Components: humanres, party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Amardeep Singh Jhajj >Assignee: Gil Portenseigne > Attachments: OFBIZ-7205-Screen-Shot.png, OFBIZ-7205.patch > > > Please refer attached screenshot. > Steps to regenerate: > 1. Go to > https://localhost:8443/partymgr/control/EditPartyResumes?partyId=admin. > 2. Create Resume form does not have ResumeId text field. Cannot add resume to > party from here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7205) Create party resume not working. ResumeId doesn't have text field to enter
[ https://issues.apache.org/jira/browse/OFBIZ-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-7205: Attachment: OFBIZ-7205.patch There was a bit more than the missing field, in this patch i fixed : - the partyResume entity-one - use-when condition on partyId field - use-when condition on submit button (for the label) - delete link to refresh with partyId in context. > Create party resume not working. ResumeId doesn't have text field to enter > -- > > Key: OFBIZ-7205 > URL: https://issues.apache.org/jira/browse/OFBIZ-7205 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Amardeep Singh Jhajj >Assignee: Gil Portenseigne > Attachments: OFBIZ-7205-Screen-Shot.png, OFBIZ-7205.patch > > > Please refer attached screenshot. > Steps to regenerate: > 1. Go to > https://localhost:8443/partymgr/control/EditPartyResumes?partyId=admin. > 2. Create Resume form does not have ResumeId text field. Cannot add resume to > party from here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7205) Create party resume not working. ResumeId doesn't have text field to enter
[ https://issues.apache.org/jira/browse/OFBIZ-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne reassigned OFBIZ-7205: --- Assignee: Gil Portenseigne (was: Amardeep Singh Jhajj) > Create party resume not working. ResumeId doesn't have text field to enter > -- > > Key: OFBIZ-7205 > URL: https://issues.apache.org/jira/browse/OFBIZ-7205 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Amardeep Singh Jhajj >Assignee: Gil Portenseigne > Attachments: OFBIZ-7205-Screen-Shot.png > > > Please refer attached screenshot. > Steps to regenerate: > 1. Go to > https://localhost:8443/partymgr/control/EditPartyResumes?partyId=admin. > 2. Create Resume form does not have ResumeId text field. Cannot add resume to > party from here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7205) Create party resume not working. ResumeId doesn't have text field to enter
[ https://issues.apache.org/jira/browse/OFBIZ-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320271#comment-15320271 ] Gil Portenseigne commented on OFBIZ-7205: - Tell me if i'm wrong but the Human Ressource component Goal is to manage our society employees. Partymgr goal is to manage every known party in the system. In some cases, i would like to manage skills/CV of any party, without him employed in my company ? Skill/CV are a general data applying to a party, so why not leave it into partymgr ? > Create party resume not working. ResumeId doesn't have text field to enter > -- > > Key: OFBIZ-7205 > URL: https://issues.apache.org/jira/browse/OFBIZ-7205 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Amardeep Singh Jhajj >Assignee: Amardeep Singh Jhajj > Attachments: OFBIZ-7205-Screen-Shot.png > > > Please refer attached screenshot. > Steps to regenerate: > 1. Go to > https://localhost:8443/partymgr/control/EditPartyResumes?partyId=admin. > 2. Create Resume form does not have ResumeId text field. Cannot add resume to > party from here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6783) Refactor the start component
[ https://issues.apache.org/jira/browse/OFBIZ-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315834#comment-15315834 ] Gil Portenseigne commented on OFBIZ-6783: - Hi Taher, Reading your code is very pleasant, i did test your last patch and did not meet any problems with it, testing several smoke tests. The "run tests", without the accounting test (that is not related), show no failure. > Refactor the start component > > > Key: OFBIZ-6783 > URL: https://issues.apache.org/jira/browse/OFBIZ-6783 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Labels: framework, main, refactoring, start > Attachments: OFBIZ-6783-hiddenfiles.patch, OFBIZ-6783.patch, > OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, > OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, > OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, > OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, > OFBIZ-6783.patch, OFBIZ-6783.patch, StartCommandUtil.java, error.log, > ofbiz.log > > > Looking at the main method and design of Start.java and the start component > overall looks ugly. The things I would like to fix so far are: > - the files are too long > - some variables are not even needed (loaderArgs?) > - the level of abstraction is wrong > - main throws an exception! > - the arguments processing logic is terrible, need to move it to commons-cli > It's just so messy and ugly to look at. So for me refactoring starts at > Start! Given that this is an important component, I will provide a patch to > be reviewed by the community before committing just to be on the safe side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6783) Refactor the start component
[ https://issues.apache.org/jira/browse/OFBIZ-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297855#comment-15297855 ] Gil Portenseigne commented on OFBIZ-6783: - I just did the same on ubuntu with java version "1.8.0_72". No issue found ! > Refactor the start component > > > Key: OFBIZ-6783 > URL: https://issues.apache.org/jira/browse/OFBIZ-6783 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Labels: framework, main, refactoring, start > Attachments: OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, > OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, > OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, OFBIZ-6783.patch, > OFBIZ-6783.patch, OFBIZ-6783.patch, StartCommandUtil.java > > > Looking at the main method and design of Start.java and the start component > overall looks ugly. The things I would like to fix so far are: > - the files are too long > - some variables are not even needed (loaderArgs?) > - the level of abstraction is wrong > - main throws an exception! > - the arguments processing logic is terrible, need to move it to commons-cli > It's just so messy and ugly to look at. So for me refactoring starts at > Start! Given that this is an important component, I will provide a patch to > be reviewed by the community before committing just to be on the safe side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5703) When we delete uploaded project content then it is deletes but form is coming in update mode with content Id
[ https://issues.apache.org/jira/browse/OFBIZ-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-5703. --- > When we delete uploaded project content then it is deletes but form is > coming in update mode with content Id > --- > > Key: OFBIZ-5703 > URL: https://issues.apache.org/jira/browse/OFBIZ-5703 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/projectmgr >Affects Versions: 11.04.04, Trunk, 12.04.04 >Reporter: Dhiraj Gupta >Assignee: Divesh Dutta > Fix For: 14.12.01, 15.12.01 > > Attachments: OFBIZ-5703.patch > > > When We go to this link > http://demo-trunk-ofbiz.apache.org/projectmgr/control/main, project name list > is diaplay. We click on project name button link, this will lead to project > profile.We click on content sub menus this will open the upload form and > list of the uploaded content.When we delete the uploaded contnent form > list > then it will delete but form is come in update mode with content Id below > list. > Thanks > Dhiraj -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-5703) When we delete uploaded project content then it is deletes but form is coming in update mode with content Id
[ https://issues.apache.org/jira/browse/OFBIZ-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne resolved OFBIZ-5703. - Resolution: Fixed Fix Version/s: 15.12.01 14.12.01 I commit th fix in : Trunk : 1740415 15.12 : 1740416 14.12 : 1740417 Thanks Dhiraj, Jacques and Divesh. Concerning the on-event-update-area, i tested it, it works fine with auto-parameters-*, i will try to put an example in example component to show a usecase, but not tonight :) Indeed there is not much of auto-parameters-* use in the code base, but i found it a very interesting feature buying some time when developping and use it often in my daily work. > When we delete uploaded project content then it is deletes but form is > coming in update mode with content Id > --- > > Key: OFBIZ-5703 > URL: https://issues.apache.org/jira/browse/OFBIZ-5703 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/projectmgr >Affects Versions: 11.04.04, Trunk, 12.04.04 >Reporter: Dhiraj Gupta >Assignee: Divesh Dutta > Fix For: 14.12.01, 15.12.01 > > Attachments: OFBIZ-5703.patch > > > When We go to this link > http://demo-trunk-ofbiz.apache.org/projectmgr/control/main, project name list > is diaplay. We click on project name button link, this will lead to project > profile.We click on content sub menus this will open the upload form and > list of the uploaded content.When we delete the uploaded contnent form > list > then it will delete but form is come in update mode with content Id below > list. > Thanks > Dhiraj -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5703) When we delete uploaded project content then it is deletes but form is coming in update mode with content Id
[ https://issues.apache.org/jira/browse/OFBIZ-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-5703: Attachment: OFBIZ-5703.patch Hi All, I just check the issue, actually it seems to be a regression, i didn't track the origin, because I think there were good improvement (you'll see in the patch), so i fix the issue with this patch. The regression was that the didn't care about default-entity-name="WorkEffortContent" anymore. Now it analyse it to guess the good parameters, same problem with auto-parameters-service is fixed. I just applied the patch on trunk, will try it on release since it's a bug. > When we delete uploaded project content then it is deletes but form is > coming in update mode with content Id > --- > > Key: OFBIZ-5703 > URL: https://issues.apache.org/jira/browse/OFBIZ-5703 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/projectmgr >Affects Versions: 11.04.04, Trunk, 12.04.04 >Reporter: Dhiraj Gupta >Assignee: Divesh Dutta > Attachments: OFBIZ-5703.patch > > > When We go to this link > http://demo-trunk-ofbiz.apache.org/projectmgr/control/main, project name list > is diaplay. We click on project name button link, this will lead to project > profile.We click on content sub menus this will open the upload form and > list of the uploaded content.When we delete the uploaded contnent form > list > then it will delete but form is come in update mode with content Id below > list. > Thanks > Dhiraj -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6977) Update content type data - sql queries
[ https://issues.apache.org/jira/browse/OFBIZ-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246539#comment-15246539 ] Gil Portenseigne edited comment on OFBIZ-6977 at 4/18/16 9:11 PM: -- Agree, we just think about it with [~soledad], it could be nice to make it generate a screen (via renderContentAsText service). this could offer us the choice to use, for example, the xls renderer currently in process, or any interesting handler. was (Author: gil portenseigne): Agree, we just think about it with Nicolas, it could be nice to make it generate a screen (via renderContentAsText service). this could offer us the choice to use, for example, the xls renderer currently in process, or any interesting handler. > Update content type data - sql queries > -- > > Key: OFBIZ-6977 > URL: https://issues.apache.org/jira/browse/OFBIZ-6977 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-6977-ContentTypeData.xml.patch > > > Adding a new content type for sql queries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6977) Update content type data - sql queries
[ https://issues.apache.org/jira/browse/OFBIZ-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246539#comment-15246539 ] Gil Portenseigne commented on OFBIZ-6977: - Agree, we just think about it with Nicolas, it could be nice to make it generate a screen (via renderContentAsText service). this could offer us the choice to use, for example, the xls renderer currently in process, or any interesting handler. > Update content type data - sql queries > -- > > Key: OFBIZ-6977 > URL: https://issues.apache.org/jira/browse/OFBIZ-6977 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-6977-ContentTypeData.xml.patch > > > Adding a new content type for sql queries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6977) Update content type data - sql queries
[ https://issues.apache.org/jira/browse/OFBIZ-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246369#comment-15246369 ] Gil Portenseigne commented on OFBIZ-6977: - This JIRA is related to OFBIZ-3946. It has already been made with poi, to generate xls results. I didn't try it, just review quickly, but patch needs some refactoring, it creates framework to content dependency. There is also a good comment from Adrian for database type compatibility : [Comment|https://issues.apache.org/jira/browse/OFBIZ-3946?focusedCommentId=13206466=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13206466] > Update content type data - sql queries > -- > > Key: OFBIZ-6977 > URL: https://issues.apache.org/jira/browse/OFBIZ-6977 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-6977-ContentTypeData.xml.patch > > > Adding a new content type for sql queries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6944) streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
[
https://issues.apache.org/jira/browse/OFBIZ-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne closed OFBIZ-6944.
---
> streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
>
>
> Key: OFBIZ-6944
> URL: https://issues.apache.org/jira/browse/OFBIZ-6944
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
> Fix For: 14.12.01, 15.12.01, 13.07.04
>
> Attachments: OFBIZ-6944.patch
>
>
> When using request ViewBinaryDataResource?dataResourceId=10015 with a
> OTHER_OBJECT dataResourceTypeId, we meet the error :
> {quote}org.ofbiz.webapp.view.ViewHandlerException: The dataResourceTypeId
> [OTHER_OBJECT] is not supported in streamDataResource{quote}
> This is relative to an existing TODO in DataResourceWorker.java :
> {code}// TODO: remove this method in favor of getDataResourceStream {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6944) streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
[
https://issues.apache.org/jira/browse/OFBIZ-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240767#comment-15240767
]
Gil Portenseigne commented on OFBIZ-6944:
-
Ok, Thanks for your feedback, i will take care of that tonight !
> streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
>
>
> Key: OFBIZ-6944
> URL: https://issues.apache.org/jira/browse/OFBIZ-6944
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
> Attachments: OFBIZ-6944.patch
>
>
> When using request ViewBinaryDataResource?dataResourceId=10015 with a
> OTHER_OBJECT dataResourceTypeId, we meet the error :
> {quote}org.ofbiz.webapp.view.ViewHandlerException: The dataResourceTypeId
> [OTHER_OBJECT] is not supported in streamDataResource{quote}
> This is relative to an existing TODO in DataResourceWorker.java :
> {code}// TODO: remove this method in favor of getDataResourceStream {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6990) Add Example for Compound Screen Widget
[ https://issues.apache.org/jira/browse/OFBIZ-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236709#comment-15236709 ] Gil Portenseigne commented on OFBIZ-6990: - Hi James, I tested you patch with OFBIZ-4090.patch, it works fine for me. Concerning you patch, there are some formatting issues. The xml part contains lots of tabs, it's best to follow OFBiz coding convention https://cwiki.apache.org/confluence/display/OFBADMIN/Coding+Conventions , using 4 spaces for indentation. You add some uneeded empty lines (for example in controller.xml part). Nothing More, it's working like a charm, is there something blocking commiting OFBIZ-4090 ? i didn't review it in details... > Add Example for Compound Screen Widget > -- > > Key: OFBIZ-6990 > URL: https://issues.apache.org/jira/browse/OFBIZ-6990 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/example >Affects Versions: Trunk >Reporter: james yong >Priority: Minor > Attachments: OFBIZ-6990.patch > > > An example to test out Compound Screen Widget -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6944) streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
[
https://issues.apache.org/jira/browse/OFBIZ-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235721#comment-15235721
]
Gil Portenseigne edited comment on OFBIZ-6944 at 4/11/16 6:52 PM:
--
Actually, like TODO says, i replace a method updating an outpuStream, with
another one returning ByteArrayInputStream, and used
{code} os.write(IOUtils.toByteArray((ByteArrayInputStream)
resourceData.get("stream")));{code}
That make it works, but i find it a bit awkward. I guess commiting it won't
harm...
was (Author: gil portenseigne):
Actually, like TODO says, i replace a method updating an outpuStream, with
another one returning ByteArrayInputStream, and used
os.write(IOUtils.toByteArray((ByteArrayInputStream)
resourceData.get("stream")));
That make it works, but i find it a bit awkward. I guess commiting it won't
harm...
> streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
>
>
> Key: OFBIZ-6944
> URL: https://issues.apache.org/jira/browse/OFBIZ-6944
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
> Attachments: OFBIZ-6944.patch
>
>
> When using request ViewBinaryDataResource?dataResourceId=10015 with a
> OTHER_OBJECT dataResourceTypeId, we meet the error :
> {quote}org.ofbiz.webapp.view.ViewHandlerException: The dataResourceTypeId
> [OTHER_OBJECT] is not supported in streamDataResource{quote}
> This is relative to an existing TODO in DataResourceWorker.java :
> {code}// TODO: remove this method in favor of getDataResourceStream {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6944) streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
[
https://issues.apache.org/jira/browse/OFBIZ-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235721#comment-15235721
]
Gil Portenseigne commented on OFBIZ-6944:
-
Actually, like TODO says, i replace a method updating an outpuStream, with
another one returning ByteArrayInputStream, and used
os.write(IOUtils.toByteArray((ByteArrayInputStream)
resourceData.get("stream")));
That make it works, but i find it a bit awkward. I guess commiting it won't
harm...
> streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
>
>
> Key: OFBIZ-6944
> URL: https://issues.apache.org/jira/browse/OFBIZ-6944
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
> Attachments: OFBIZ-6944.patch
>
>
> When using request ViewBinaryDataResource?dataResourceId=10015 with a
> OTHER_OBJECT dataResourceTypeId, we meet the error :
> {quote}org.ofbiz.webapp.view.ViewHandlerException: The dataResourceTypeId
> [OTHER_OBJECT] is not supported in streamDataResource{quote}
> This is relative to an existing TODO in DataResourceWorker.java :
> {code}// TODO: remove this method in favor of getDataResourceStream {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (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
]
Gil Portenseigne resolved OFBIZ-6927.
-
Resolution: Fixed
Fix Version/s: (was: Trunk)
Release Branch 15.12
Upcoming Branch
Commited in :
trunk: r1735738
15.12: r1735739
Thanks Pierre for reporting and testing issue
> 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, Release Branch 15.12
>Reporter: Pierre Smits
>Assignee: Gil Portenseigne
> Labels: modalwindow, renderer
> Fix For: Upcoming Branch, Release Branch 15.12
>
> Attachments: OFBIZ-6927.patch, Screen Shot 2016-03-18 at
> 09.42.00.png, Screen Shot 2016-03-18 at 09.42.39.png
>
>
> 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] [Commented] (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:comment-tabpanel=15201158#comment-15201158
]
Gil Portenseigne commented on OFBIZ-6927:
-
Hi Pierre, i just try it, didn't manage to reproduce the bug... I tried on New
Example button in example component. Can you give me some steps ?
Thanks
> 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] [Closed] (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
]
Gil Portenseigne closed OFBIZ-6927.
---
> 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, Release Branch 15.12
>Reporter: Pierre Smits
>Assignee: Gil Portenseigne
> Labels: modalwindow, renderer
> Fix For: Upcoming Branch, Release Branch 15.12
>
> Attachments: OFBIZ-6927.patch, Screen Shot 2016-03-18 at
> 09.42.00.png, Screen Shot 2016-03-18 at 09.42.39.png
>
>
> 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] [Updated] (OFBIZ-6944) streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
[
https://issues.apache.org/jira/browse/OFBIZ-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne updated OFBIZ-6944:
Attachment: OFBIZ-6944.patch
This patch fix the issue, got some doubt about it, i appreciate any reviews...
> streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
>
>
> Key: OFBIZ-6944
> URL: https://issues.apache.org/jira/browse/OFBIZ-6944
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
> Attachments: OFBIZ-6944.patch
>
>
> When using request ViewBinaryDataResource?dataResourceId=10015 with a
> OTHER_OBJECT dataResourceTypeId, we meet the error :
> {quote}org.ofbiz.webapp.view.ViewHandlerException: The dataResourceTypeId
> [OTHER_OBJECT] is not supported in streamDataResource{quote}
> This is relative to an existing TODO in DataResourceWorker.java :
> {code}// TODO: remove this method in favor of getDataResourceStream {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-6944) streamDataResource do not manage OTHER_OBJECT dataResourceTypeId
Gil Portenseigne created OFBIZ-6944:
---
Summary: streamDataResource do not manage OTHER_OBJECT
dataResourceTypeId
Key: OFBIZ-6944
URL: https://issues.apache.org/jira/browse/OFBIZ-6944
Project: OFBiz
Issue Type: Bug
Components: content
Affects Versions: Trunk
Reporter: Gil Portenseigne
Assignee: Gil Portenseigne
When using request ViewBinaryDataResource?dataResourceId=10015 with a
OTHER_OBJECT dataResourceTypeId, we meet the error :
{quote}org.ofbiz.webapp.view.ViewHandlerException: The dataResourceTypeId
[OTHER_OBJECT] is not supported in streamDataResource{quote}
This is relative to an existing TODO in DataResourceWorker.java :
{code}// TODO: remove this method in favor of getDataResourceStream {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-6943) Problem uploading data resource other than image in DB
Gil Portenseigne created OFBIZ-6943:
---
Summary: Problem uploading data resource other than image in DB
Key: OFBIZ-6943
URL: https://issues.apache.org/jira/browse/OFBIZ-6943
Project: OFBiz
Issue Type: Bug
Components: content
Affects Versions: Trunk
Reporter: Gil Portenseigne
Assignee: Gil Portenseigne
When in content.properties, content.upload.always.local.file is set to false,
uploading video, audio or other than image data is not possible.
{code}|E| Failure in create operation for entity [OtherDataResource]:
org.ofbiz.entity.GenericEntityException: Error while inserting:
[GenericEntity:OtherDataResource][createdStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
lim=1599972
cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
[dataResourceContent] of entity OtherDataResource:
(java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
transaction.{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6943) Problem uploading data resource other than image in DB
[
https://issues.apache.org/jira/browse/OFBIZ-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202677#comment-15202677
]
Gil Portenseigne commented on OFBIZ-6943:
-
Feel free to create a Jira :)
> Problem uploading data resource other than image in DB
> --
>
> Key: OFBIZ-6943
> URL: https://issues.apache.org/jira/browse/OFBIZ-6943
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
>
> When in content.properties, content.upload.always.local.file is set to false,
> uploading video, audio or other than image data is not possible.
> {quote}Failure in create operation for entity [OtherDataResource]:
> org.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:OtherDataResource][createdStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
> lim=1599972
> cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
> [dataResourceContent] of entity OtherDataResource:
> (java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
> transaction.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (OFBIZ-6943) Problem uploading data resource other than image in DB
[
https://issues.apache.org/jira/browse/OFBIZ-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne closed OFBIZ-6943.
---
> Problem uploading data resource other than image in DB
> --
>
> Key: OFBIZ-6943
> URL: https://issues.apache.org/jira/browse/OFBIZ-6943
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
> Fix For: 14.12.01, Upcoming Branch, 15.12.01
>
>
> When in content.properties, content.upload.always.local.file is set to false,
> uploading video, audio or other than image data is not possible.
> {quote}Failure in create operation for entity [OtherDataResource]:
> org.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:OtherDataResource][createdStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
> lim=1599972
> cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
> [dataResourceContent] of entity OtherDataResource:
> (java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
> transaction.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OFBIZ-6943) Problem uploading data resource other than image in DB
[
https://issues.apache.org/jira/browse/OFBIZ-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne resolved OFBIZ-6943.
-
Resolution: Fixed
Fix Version/s: 15.12.01
Upcoming Branch
14.12.01
Commited in
trunk : 1735742
15.12 : 1735743
14.12 : 1735744
> Problem uploading data resource other than image in DB
> --
>
> Key: OFBIZ-6943
> URL: https://issues.apache.org/jira/browse/OFBIZ-6943
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
> Fix For: 14.12.01, Upcoming Branch, 15.12.01
>
>
> When in content.properties, content.upload.always.local.file is set to false,
> uploading video, audio or other than image data is not possible.
> {quote}Failure in create operation for entity [OtherDataResource]:
> org.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:OtherDataResource][createdStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
> lim=1599972
> cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
> [dataResourceContent] of entity OtherDataResource:
> (java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
> transaction.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6943) Problem uploading data resource other than image in DB
[
https://issues.apache.org/jira/browse/OFBIZ-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202678#comment-15202678
]
Gil Portenseigne commented on OFBIZ-6943:
-
Yep, i just commited a fix where data type was bad defined into entitymodel,
after that, it works fine.
> Problem uploading data resource other than image in DB
> --
>
> Key: OFBIZ-6943
> URL: https://issues.apache.org/jira/browse/OFBIZ-6943
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
>
> When in content.properties, content.upload.always.local.file is set to false,
> uploading video, audio or other than image data is not possible.
> {quote}Failure in create operation for entity [OtherDataResource]:
> org.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:OtherDataResource][createdStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
> lim=1599972
> cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
> [dataResourceContent] of entity OtherDataResource:
> (java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
> transaction.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-6943) Problem uploading data resource other than image in DB
[
https://issues.apache.org/jira/browse/OFBIZ-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne updated OFBIZ-6943:
Description:
When in content.properties, content.upload.always.local.file is set to false,
uploading video, audio or other than image data is not possible.
{quote}Failure in create operation for entity [OtherDataResource]:
org.ofbiz.entity.GenericEntityException: Error while inserting:
[GenericEntity:OtherDataResource][createdStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
lim=1599972
cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
[dataResourceContent] of entity OtherDataResource:
(java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
transaction.{quote}
was:
When in content.properties, content.upload.always.local.file is set to false,
uploading video, audio or other than image data is not possible.
{quote}|E| Failure in create operation for entity [OtherDataResource]:
org.ofbiz.entity.GenericEntityException: Error while inserting:
[GenericEntity:OtherDataResource][createdStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
lim=1599972
cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
[dataResourceContent] of entity OtherDataResource:
(java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
transaction.{quote}
> Problem uploading data resource other than image in DB
> --
>
> Key: OFBIZ-6943
> URL: https://issues.apache.org/jira/browse/OFBIZ-6943
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
>
> When in content.properties, content.upload.always.local.file is set to false,
> uploading video, audio or other than image data is not possible.
> {quote}Failure in create operation for entity [OtherDataResource]:
> org.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:OtherDataResource][createdStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
> lim=1599972
> cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
> [dataResourceContent] of entity OtherDataResource:
> (java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
> transaction.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-6943) Problem uploading data resource other than image in DB
[
https://issues.apache.org/jira/browse/OFBIZ-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne updated OFBIZ-6943:
Description:
When in content.properties, content.upload.always.local.file is set to false,
uploading video, audio or other than image data is not possible.
{quote}|E| Failure in create operation for entity [OtherDataResource]:
org.ofbiz.entity.GenericEntityException: Error while inserting:
[GenericEntity:OtherDataResource][createdStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
lim=1599972
cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
[dataResourceContent] of entity OtherDataResource:
(java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
transaction.{quote}
was:
When in content.properties, content.upload.always.local.file is set to false,
uploading video, audio or other than image data is not possible.
{code}|E| Failure in create operation for entity [OtherDataResource]:
org.ofbiz.entity.GenericEntityException: Error while inserting:
[GenericEntity:OtherDataResource][createdStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
lim=1599972
cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
[dataResourceContent] of entity OtherDataResource:
(java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
transaction.{code}
> Problem uploading data resource other than image in DB
> --
>
> Key: OFBIZ-6943
> URL: https://issues.apache.org/jira/browse/OFBIZ-6943
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
>
> When in content.properties, content.upload.always.local.file is set to false,
> uploading video, audio or other than image data is not possible.
> {quote}|E| Failure in create operation for entity [OtherDataResource]:
> org.ofbiz.entity.GenericEntityException: Error while inserting:
> [GenericEntity:OtherDataResource][createdStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][createdTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)][dataResourceContent,java.nio.HeapByteBuffer[pos=0
> lim=1599972
> cap=1599972](java.nio.HeapByteBuffer)][dataResourceId,1(java.lang.String)][lastUpdatedStamp,2016-03-19
> 09:56:21.464(java.sql.Timestamp)][lastUpdatedTxStamp,2016-03-19
> 09:56:21.095(java.sql.Timestamp)] (SQL Exception while setting value on field
> [dataResourceContent] of entity OtherDataResource:
> (java.io.NotSerializableException: java.nio.HeapByteBuffer)). Rolling back
> transaction.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (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
]
Gil Portenseigne reassigned OFBIZ-6927:
---
Assignee: Gil Portenseigne
> 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
>Assignee: Gil Portenseigne
> Labels: modalwindow, renderer
> Fix For: Trunk
>
> Attachments: Screen Shot 2016-03-18 at 09.42.00.png, Screen Shot
> 2016-03-18 at 09.42.39.png
>
>
> 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] [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
]
Gil Portenseigne updated OFBIZ-6927:
Affects Version/s: Release Branch 15.12
> 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, Release Branch 15.12
>Reporter: Pierre Smits
>Assignee: Gil Portenseigne
> Labels: modalwindow, renderer
> Fix For: Trunk
>
> Attachments: OFBIZ-6927.patch, Screen Shot 2016-03-18 at
> 09.42.00.png, Screen Shot 2016-03-18 at 09.42.39.png
>
>
> 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] [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
]
Gil Portenseigne updated OFBIZ-6927:
Attachment: OFBIZ-6927.patch
Height and width attributes were not implemented in renderLink method in
MacroMenuRenderer.
> 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
>Assignee: Gil Portenseigne
> Labels: modalwindow, renderer
> Fix For: Trunk
>
> Attachments: OFBIZ-6927.patch, Screen Shot 2016-03-18 at
> 09.42.00.png, Screen Shot 2016-03-18 at 09.42.39.png
>
>
> 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] [Updated] (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-4183: Sprint: Bug Crush Event - 21/2/2015, Community Day 1 - 2016 (was: Bug Crush Event - 21/2/2015) > Screen Link Ajax Windows > > > Key: OFBIZ-4183 > URL: https://issues.apache.org/jira/browse/OFBIZ-4183 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Sascha Rodekamp >Assignee: Adrian Crum > Fix For: Trunk > > Attachments: LayeredLink_new.jpg, Unbenannt.jpg > > > Hi, > i created a new Screen a link in a layered JS Box (see Screenshot). > It looks nice and is helpful in some cases. > Is this interesting for the trunk? > Cheers > Sascha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6882) Extend the PostalAddress entity with additional elements
[ https://issues.apache.org/jira/browse/OFBIZ-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15136209#comment-15136209 ] Gil Portenseigne commented on OFBIZ-6882: - Thanks for the reference, but the main wonder was the *within the postalAddress context*, saying that it "is an administrative body with some degree of control over a geographic area", i do not know a case where city is not enough to define a postalAddress, and where municipality is needed ? It might just be an informative field %? (thinking about it while writing, it's good to me to add it, but i surely won't use it) > Extend the PostalAddress entity with additional elements > > > Key: OFBIZ-6882 > URL: https://issues.apache.org/jira/browse/OFBIZ-6882 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Labels: 3rdParty, Shipment, integration > Attachments: OFBIZ-6882-party-PostalAddress.patch > > > Various modern day 3rd party delivery solutions (e.g. PostNL in The > Netherlands) require that elements are delivered separately, so that > addresses can be checked more easily. > Current definition of the PostalAddress doesn't have separation of: > * street name > * house number > * house number addition or extension -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6882) Extend the PostalAddress entity with additional elements
[ https://issues.apache.org/jira/browse/OFBIZ-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15136200#comment-15136200 ] Gil Portenseigne edited comment on OFBIZ-6882 at 2/7/16 9:22 AM: - True, but i think that adding functionnality in datamodel must be done with adding fields in standard OOTB forms. That way, we can see easily the functionnality, then the implementer hide the not needed fields. was (Author: gil portenseigne): True, but i think that adding functionnality in datamodel must be done with adding fields in standard OOTB forms. That way, we can see easily the functionnality, the the implementer hide the not needed fields. > Extend the PostalAddress entity with additional elements > > > Key: OFBIZ-6882 > URL: https://issues.apache.org/jira/browse/OFBIZ-6882 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Labels: 3rdParty, Shipment, integration > Attachments: OFBIZ-6882-party-PostalAddress.patch > > > Various modern day 3rd party delivery solutions (e.g. PostNL in The > Netherlands) require that elements are delivered separately, so that > addresses can be checked more easily. > Current definition of the PostalAddress doesn't have separation of: > * street name > * house number > * house number addition or extension -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6882) Extend the PostalAddress entity with additional elements
[ https://issues.apache.org/jira/browse/OFBIZ-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15136200#comment-15136200 ] Gil Portenseigne commented on OFBIZ-6882: - True, but i think that adding functionnality in datamodel must be done with adding fields in standard OOTB forms. That way, we can see easily the functionnality, the the implementer hide the not needed fields. > Extend the PostalAddress entity with additional elements > > > Key: OFBIZ-6882 > URL: https://issues.apache.org/jira/browse/OFBIZ-6882 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Labels: 3rdParty, Shipment, integration > Attachments: OFBIZ-6882-party-PostalAddress.patch > > > Various modern day 3rd party delivery solutions (e.g. PostNL in The > Netherlands) require that elements are delivered separately, so that > addresses can be checked more easily. > Current definition of the PostalAddress doesn't have separation of: > * street name > * house number > * house number addition or extension -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6882) Extend the PostalAddress entity with additional elements
[ https://issues.apache.org/jira/browse/OFBIZ-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15136196#comment-15136196 ] Gil Portenseigne commented on OFBIZ-6882: - Hi, I hardly understand the difference between a Municipality and a City within the postalAddress context. Could you show me an example/explain me the diff ? Thanks > Extend the PostalAddress entity with additional elements > > > Key: OFBIZ-6882 > URL: https://issues.apache.org/jira/browse/OFBIZ-6882 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Labels: 3rdParty, Shipment, integration > Attachments: OFBIZ-6882-party-PostalAddress.patch > > > Various modern day 3rd party delivery solutions (e.g. PostNL in The > Netherlands) require that elements are delivered separately, so that > addresses can be checked more easily. > Current definition of the PostalAddress doesn't have separation of: > * street name > * house number > * house number addition or extension -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6869) Jgrowl enhancement i18n and centered
[ https://issues.apache.org/jira/browse/OFBIZ-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6869: Attachment: OFBIZ-6869-2.patch Add properties in widget.properties, for easy customization of JGrowl alert. > Jgrowl enhancement i18n and centered > > > Key: OFBIZ-6869 > URL: https://issues.apache.org/jira/browse/OFBIZ-6869 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-6869-2.patch, OFBIZ-6869.patch > > > Current implementation show message in top left corner with no translation of > english "show more/less" label. > This improvment make the jgrowl message appear in the center of the screen, > with internationalized label, and little format corrections -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6869) Jgrowl enhancement i18n and centered
[ https://issues.apache.org/jira/browse/OFBIZ-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-6869. --- Enhancement commited in trunk r1728351 > Jgrowl enhancement i18n and centered > > > Key: OFBIZ-6869 > URL: https://issues.apache.org/jira/browse/OFBIZ-6869 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-6869-2.patch, OFBIZ-6869.patch > > > Current implementation show message in top left corner with no translation of > english "show more/less" label. > This improvment make the jgrowl message appear in the center of the screen, > with internationalized label, and little format corrections -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6877) Update various party labels regarding the dutch locale
[
https://issues.apache.org/jira/browse/OFBIZ-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131029#comment-15131029
]
Gil Portenseigne commented on OFBIZ-6877:
-
Hi Pierre,
The translation already exist as :
{code}
البريد الالكتروني للفاتورة
Rechnungs E-Mail-Adresse
Billing (AP) Email
Correo electrónico de facturación
Adresse courriel de facturation
देयकांकन(बिलिंग)(एपी) ईमेल
Email Fatturazione (AP)
請求(AP)Eメール
Factuur e-mailadres
E-mail para cobrança
Эл. почта по вопросам оплаты (AP)
อีเมล์ใบเสร็จ (AP)
Thư điện tử thanh toán
寄账单电子邮件
寄送帳單電子郵件
{code}
and
{code}
Haupt-E-Mail-Adresse
Primary Email Address
Correo electrónico principal
Adresse courriel principale
प्राथमिक ईमेल पता
Indirizzo Primario Email
主Eメールアドレス
Primair emailadres
E-mail principal
Adresa Primara Email
Основной адрес эл.почты
ที่อยู่อีเมล์ที่สำคัญ
Thư điện tử chính
第一个电子邮件地址
第一個電子郵件位址
{code}
In PartyEntityLabel.xml
These are good enough ?
And i see no use of PRIMARY_EMAIL as a label.
> Update various party labels regarding the dutch locale
> ---
>
> Key: OFBIZ-6877
> URL: https://issues.apache.org/jira/browse/OFBIZ-6877
> Project: OFBiz
> Issue Type: Improvement
> Components: party
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Labels: Nederlands
> Attachments: OFBIZ-6867-PartyLabels.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6869) Jgrowl enhancement i18n and centered
[ https://issues.apache.org/jira/browse/OFBIZ-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127882#comment-15127882 ] Gil Portenseigne commented on OFBIZ-6869: - Yes, i will look into it ! > Jgrowl enhancement i18n and centered > > > Key: OFBIZ-6869 > URL: https://issues.apache.org/jira/browse/OFBIZ-6869 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-6869.patch > > > Current implementation show message in top left corner with no translation of > english "show more/less" label. > This improvment make the jgrowl message appear in the center of the screen, > with internationalized label, and little format corrections -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6869) Jgrowl enhancement i18n and centered
Gil Portenseigne created OFBIZ-6869: --- Summary: Jgrowl enhancement i18n and centered Key: OFBIZ-6869 URL: https://issues.apache.org/jira/browse/OFBIZ-6869 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Gil Portenseigne Assignee: Gil Portenseigne Priority: Trivial Fix For: Upcoming Branch Current implementation show message in top left corner with no translation of english "show more/less" label. This improvment make the jgrowl message appear in the center of the screen, with internationalized label, and little format corrections -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6869) Jgrowl enhancement i18n and centered
[ https://issues.apache.org/jira/browse/OFBIZ-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6869: Attachment: OFBIZ-6869.patch This patch fix the width to 600px, make the message centered, use of labels, and speed up the display for a better UX > Jgrowl enhancement i18n and centered > > > Key: OFBIZ-6869 > URL: https://issues.apache.org/jira/browse/OFBIZ-6869 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-6869.patch > > > Current implementation show message in top left corner with no translation of > english "show more/less" label. > This improvment make the jgrowl message appear in the center of the screen, > with internationalized label, and little format corrections -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6703) Cannot create more than one lead in the SFA component by same user
[ https://issues.apache.org/jira/browse/OFBIZ-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-6703. --- > Cannot create more than one lead in the SFA component by same user > -- > > Key: OFBIZ-6703 > URL: https://issues.apache.org/jira/browse/OFBIZ-6703 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk >Reporter: Taher Alkhateeb >Assignee: Gil Portenseigne > Fix For: 14.12.01, Upcoming Branch > > > Repeat steps: > # go to SFA component and click on leads > # click on create new > # fill mandatory information and save > # repeat the above steps again and observe failure > The reason for the failure is that the implementation of the createLead > service tries to create a PartyRole of type OWNER every time a lead is > created. So it works only the first time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-6703) Cannot create more than one lead in the SFA component by same user
[ https://issues.apache.org/jira/browse/OFBIZ-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne reopened OFBIZ-6703: - Assignee: Gil Portenseigne (was: Taher Alkhateeb) > Cannot create more than one lead in the SFA component by same user > -- > > Key: OFBIZ-6703 > URL: https://issues.apache.org/jira/browse/OFBIZ-6703 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk >Reporter: Taher Alkhateeb >Assignee: Gil Portenseigne > Fix For: 14.12.01, Upcoming Branch > > > Repeat steps: > # go to SFA component and click on leads > # click on create new > # fill mandatory information and save > # repeat the above steps again and observe failure > The reason for the failure is that the implementation of the createLead > service tries to create a PartyRole of type OWNER every time a lead is > created. So it works only the first time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6703) Cannot create more than one lead in the SFA component by same user
[ https://issues.apache.org/jira/browse/OFBIZ-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010735#comment-15010735 ] Gil Portenseigne commented on OFBIZ-6703: - Yes I will ! > Cannot create more than one lead in the SFA component by same user > -- > > Key: OFBIZ-6703 > URL: https://issues.apache.org/jira/browse/OFBIZ-6703 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Fix For: 14.12.01, Upcoming Branch > > > Repeat steps: > # go to SFA component and click on leads > # click on create new > # fill mandatory information and save > # repeat the above steps again and observe failure > The reason for the failure is that the implementation of the createLead > service tries to create a PartyRole of type OWNER every time a lead is > created. So it works only the first time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-6703) Cannot create more than one lead in the SFA component by same user
[ https://issues.apache.org/jira/browse/OFBIZ-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne resolved OFBIZ-6703. - Resolution: Fixed Fixed in Trunk r1714974 14.12 r1714975 Thanks all ! > Cannot create more than one lead in the SFA component by same user > -- > > Key: OFBIZ-6703 > URL: https://issues.apache.org/jira/browse/OFBIZ-6703 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk >Reporter: Taher Alkhateeb >Assignee: Gil Portenseigne > Fix For: 14.12.01, Upcoming Branch > > > Repeat steps: > # go to SFA component and click on leads > # click on create new > # fill mandatory information and save > # repeat the above steps again and observe failure > The reason for the failure is that the implementation of the createLead > service tries to create a PartyRole of type OWNER every time a lead is > created. So it works only the first time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5750) Convert Party entites CRUD service from simple to entity-auto
[
https://issues.apache.org/jira/browse/OFBIZ-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne closed OFBIZ-5750.
---
> Convert Party entites CRUD service from simple to entity-auto
> -
>
> Key: OFBIZ-5750
> URL: https://issues.apache.org/jira/browse/OFBIZ-5750
> Project: OFBiz
> Issue Type: Improvement
> Components: party
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Jacques Le Roux
>Priority: Trivial
> Labels: crud, entity-auto
> Fix For: 14.12.01, Upcoming Branch
>
> Attachments: OFBIZ-5750.patch, OFBIZ-5750.patch
>
>
> I converted CRUD service to entity-auto for :
> PartyRole
> PostalAddressBoundary
> PartyClassification
> PartyClassificationGroup
> PartyAttribute
> Vendor
> PartyCarrierAccount
> Only entity with their services present on PartyServices.xml
> I change the PartyRole attributes service like that
> {code}
> -
> - optional="false"/>
> +
> {code}
> The currently simple method haven't a specific resolution if the partyId
> isn't pass, so the service failed with database constraint error.
> I run manual test from Party Profile screen with success (except for
> PostalAddressBoundary that haven't standard screen, so call by runService)
> and I run ./ant clean-all load-demo run-tests without error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OFBIZ-5750) Convert Party entites CRUD service from simple to entity-auto
[
https://issues.apache.org/jira/browse/OFBIZ-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne resolved OFBIZ-5750.
-
Resolution: Fixed
Fix Version/s: Upcoming Branch
Fixed in
Trunk r1714976
14.12 r1714977
I did review all createPartyRole service call in *.*, and replace some of the
occurence with ensurePartyRole, one in SubscriptionServices.java that could
cause issue, and others to ease the readability.
The ones i left were mainly used in party creation...
> Convert Party entites CRUD service from simple to entity-auto
> -
>
> Key: OFBIZ-5750
> URL: https://issues.apache.org/jira/browse/OFBIZ-5750
> Project: OFBiz
> Issue Type: Improvement
> Components: party
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Jacques Le Roux
>Priority: Trivial
> Labels: crud, entity-auto
> Fix For: 14.12.01, Upcoming Branch
>
> Attachments: OFBIZ-5750.patch, OFBIZ-5750.patch
>
>
> I converted CRUD service to entity-auto for :
> PartyRole
> PostalAddressBoundary
> PartyClassification
> PartyClassificationGroup
> PartyAttribute
> Vendor
> PartyCarrierAccount
> Only entity with their services present on PartyServices.xml
> I change the PartyRole attributes service like that
> {code}
> -
> - optional="false"/>
> +
> {code}
> The currently simple method haven't a specific resolution if the partyId
> isn't pass, so the service failed with database constraint error.
> I run manual test from Party Profile screen with success (except for
> PostalAddressBoundary that haven't standard screen, so call by runService)
> and I run ./ant clean-all load-demo run-tests without error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6703) Cannot create more than one lead in the SFA component by same user
[ https://issues.apache.org/jira/browse/OFBIZ-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010675#comment-15010675 ] Gil Portenseigne commented on OFBIZ-6703: - Hi all, Sorry for waking up a bit late on this subject, but the best way to fix this bug was replacing createPartyRole service call by ensurePartyRole service, which is done for this use. Indeed the entity-auto improvments made by Nicolas did not check every createPartyRole usage, leading to this kind of bug. Reverting entity-auto implementation is a bad solution, bringing back createPartyRole/ensurePartyRole service usage duplication, and createPartyRole naming as a CRUD service to a different one... Hans, Internal check is already done by ensurePartyRole, it was just the information missing here ! > Cannot create more than one lead in the SFA component by same user > -- > > Key: OFBIZ-6703 > URL: https://issues.apache.org/jira/browse/OFBIZ-6703 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Fix For: 14.12.01, Upcoming Branch > > > Repeat steps: > # go to SFA component and click on leads > # click on create new > # fill mandatory information and save > # repeat the above steps again and observe failure > The reason for the failure is that the implementation of the createLead > service tries to create a PartyRole of type OWNER every time a lead is > created. So it works only the first time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5750) Convert Party entites CRUD service from simple to entity-auto
[
https://issues.apache.org/jira/browse/OFBIZ-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010678#comment-15010678
]
Gil Portenseigne commented on OFBIZ-5750:
-
Hi Taher,
I just add a comment here OFBIZ-6703 that will present another (better?) fix
proposal.
> Convert Party entites CRUD service from simple to entity-auto
> -
>
> Key: OFBIZ-5750
> URL: https://issues.apache.org/jira/browse/OFBIZ-5750
> Project: OFBiz
> Issue Type: Improvement
> Components: party
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Jacques Le Roux
>Priority: Trivial
> Labels: crud, entity-auto
> Fix For: 14.12.01
>
> Attachments: OFBIZ-5750.patch, OFBIZ-5750.patch
>
>
> I converted CRUD service to entity-auto for :
> PartyRole
> PostalAddressBoundary
> PartyClassification
> PartyClassificationGroup
> PartyAttribute
> Vendor
> PartyCarrierAccount
> Only entity with their services present on PartyServices.xml
> I change the PartyRole attributes service like that
> {code}
> -
> - optional="false"/>
> +
> {code}
> The currently simple method haven't a specific resolution if the partyId
> isn't pass, so the service failed with database constraint error.
> I run manual test from Party Profile screen with success (except for
> PostalAddressBoundary that haven't standard screen, so call by runService)
> and I run ./ant clean-all load-demo run-tests without error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (OFBIZ-6714) Removing unexplained TODO from Manufacturing services
[ https://issues.apache.org/jira/browse/OFBIZ-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-6714. --- > Removing unexplained TODO from Manufacturing services > -- > > Key: OFBIZ-6714 > URL: https://issues.apache.org/jira/browse/OFBIZ-6714 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Gil Portenseigne >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-6714-ProductionRun.java.patch > > > There are unexplained TODO references in java code files in the manufacturing > components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6714) Removing unexplained TODO from Manufacturing services
[ https://issues.apache.org/jira/browse/OFBIZ-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14997394#comment-14997394 ] Gil Portenseigne commented on OFBIZ-6714: - Indeed this TODO is here for more than 9 years and the method seems complete :). > Removing unexplained TODO from Manufacturing services > -- > > Key: OFBIZ-6714 > URL: https://issues.apache.org/jira/browse/OFBIZ-6714 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: OFBIZ-6714-ProductionRun.java.patch > > > There are unexplained TODO references in java code files in the manufacturing > components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6714) Removing unexplained TODO from Manufacturing services
[ https://issues.apache.org/jira/browse/OFBIZ-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne reassigned OFBIZ-6714: --- Assignee: Gil Portenseigne (was: Pierre Smits) > Removing unexplained TODO from Manufacturing services > -- > > Key: OFBIZ-6714 > URL: https://issues.apache.org/jira/browse/OFBIZ-6714 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Gil Portenseigne >Priority: Minor > Attachments: OFBIZ-6714-ProductionRun.java.patch > > > There are unexplained TODO references in java code files in the manufacturing > components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6700) Added some text for French language in ProductEntityLabels.xml, no functional change
[ https://issues.apache.org/jira/browse/OFBIZ-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972626#comment-14972626 ] Gil Portenseigne commented on OFBIZ-6700: - Thank you for your review ! > Added some text for French language in ProductEntityLabels.xml, no functional > change > > > Key: OFBIZ-6700 > URL: https://issues.apache.org/jira/browse/OFBIZ-6700 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Wai >Assignee: Gil Portenseigne > Fix For: 14.12.01, Upcoming Branch > > Attachments: OFBIZ-6700-14.12.patch, OFBIZ-6700.patch, > OFBIZ-6700.patch, OFBIZ-6700.patch > > > To the native French speaker, please review the translations to make sure > that the diction is correct. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6700) Added some text for French language in ProductEntityLabels.xml, no functional change
[ https://issues.apache.org/jira/browse/OFBIZ-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6700: Attachment: OFBIZ-6700-14.12.patch OFBIZ-6700.patch I did generate a patch for 14.12 (some manual inserts), for older branches there were too much problem applying it. > Added some text for French language in ProductEntityLabels.xml, no functional > change > > > Key: OFBIZ-6700 > URL: https://issues.apache.org/jira/browse/OFBIZ-6700 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Wai >Assignee: Gil Portenseigne > Attachments: OFBIZ-6700-14.12.patch, OFBIZ-6700.patch, > OFBIZ-6700.patch, OFBIZ-6700.patch > > > To the native French speaker, please review the translations to make sure > that the diction is correct. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6700) Added some text for French language in ProductEntityLabels.xml, no functional change
[ https://issues.apache.org/jira/browse/OFBIZ-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6700: Fix Version/s: Upcoming Branch 14.12.01 Issue Type: Improvement (was: Bug) > Added some text for French language in ProductEntityLabels.xml, no functional > change > > > Key: OFBIZ-6700 > URL: https://issues.apache.org/jira/browse/OFBIZ-6700 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Wai >Assignee: Gil Portenseigne > Fix For: 14.12.01, Upcoming Branch > > Attachments: OFBIZ-6700-14.12.patch, OFBIZ-6700.patch, > OFBIZ-6700.patch, OFBIZ-6700.patch > > > To the native French speaker, please review the translations to make sure > that the diction is correct. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6700) Added some text for French language in ProductEntityLabels.xml, no functional change
[ https://issues.apache.org/jira/browse/OFBIZ-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-6700. --- > Added some text for French language in ProductEntityLabels.xml, no functional > change > > > Key: OFBIZ-6700 > URL: https://issues.apache.org/jira/browse/OFBIZ-6700 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Wai >Assignee: Gil Portenseigne > Fix For: 14.12.01, Upcoming Branch > > Attachments: OFBIZ-6700-14.12.patch, OFBIZ-6700.patch, > OFBIZ-6700.patch, OFBIZ-6700.patch > > > To the native French speaker, please review the translations to make sure > that the diction is correct. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-6700) Added some text for French language in ProductEntityLabels.xml, no functional change
[ https://issues.apache.org/jira/browse/OFBIZ-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne resolved OFBIZ-6700. - Resolution: Implemented Thanks Wai, your reviewed patch is commited at : Trunk : r1710317 R14.12 : r1710318 > Added some text for French language in ProductEntityLabels.xml, no functional > change > > > Key: OFBIZ-6700 > URL: https://issues.apache.org/jira/browse/OFBIZ-6700 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Wai >Assignee: Gil Portenseigne > Fix For: 14.12.01, Upcoming Branch > > Attachments: OFBIZ-6700-14.12.patch, OFBIZ-6700.patch, > OFBIZ-6700.patch, OFBIZ-6700.patch > > > To the native French speaker, please review the translations to make sure > that the diction is correct. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6700) Added some text for French language in ProductEntityLabels.xml, no functional change
[ https://issues.apache.org/jira/browse/OFBIZ-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne reassigned OFBIZ-6700: --- Assignee: Gil Portenseigne > Added some text for French language in ProductEntityLabels.xml, no functional > change > > > Key: OFBIZ-6700 > URL: https://issues.apache.org/jira/browse/OFBIZ-6700 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Wai >Assignee: Gil Portenseigne > Attachments: OFBIZ-6700.patch > > > To the native French speaker, please review the translations to make sure > that the diction is correct. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6700) Added some text for French language in ProductEntityLabels.xml, no functional change
[ https://issues.apache.org/jira/browse/OFBIZ-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6700: Attachment: OFBIZ-6700.patch I went thru it and update it ! You did a Good Job, french is not a simple language :) I will reread it all in fresh morning before committing. > Added some text for French language in ProductEntityLabels.xml, no functional > change > > > Key: OFBIZ-6700 > URL: https://issues.apache.org/jira/browse/OFBIZ-6700 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Wai >Assignee: Gil Portenseigne > Attachments: OFBIZ-6700.patch, OFBIZ-6700.patch > > > To the native French speaker, please review the translations to make sure > that the diction is correct. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6236) Integration of OFBiz and Magento ecommerce for providing Order Management support
[ https://issues.apache.org/jira/browse/OFBIZ-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14954550#comment-14954550 ] Gil Portenseigne commented on OFBIZ-6236: - +1 for having it inside OFBiz, i do not see any point keeping it outside of the Apache world. > Integration of OFBiz and Magento ecommerce for providing Order Management > support > - > > Key: OFBIZ-6236 > URL: https://issues.apache.org/jira/browse/OFBIZ-6236 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Trunk >Reporter: Arun Patidar >Priority: Trivial > Attachments: Magento-Setup-Guide.pdf, OFBIZ-6236.patch, > OFBiz_Connect-1.0.0.tgz > > > Integration of OFBiz and Magento Ecommerce for providing Order Management > support. > We can use OFBiz ERP system for handling Magento orders work-flow till > fulfilment. > Featrures: > This integration can be use to provide Order and Warehouse Management to the > orders placed via Magento E-commerce store. > -- Imports store data and configuartion settings from Magento store > -- Imports Shipping configuration > -- Imports Categories > -- Imports Products along with images path > -- One time import inventory count of products > -- Import pending orders from Magento > -- Sync Cancel and Held orders between Magento and OFBiz > -- Push shipment details and tracking code to Magento > -- Refund amoung using CreditMemo feature of Magento > Once the setup would be done, there are scheduled services that checks orders > in Magento every hour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6659) When i working with Login with Linkedin In of biz the it is not showing UI part
[
https://issues.apache.org/jira/browse/OFBIZ-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14949974#comment-14949974
]
Gil Portenseigne commented on OFBIZ-6659:
-
Hi Jawahar,
As this is an improvement, it has not been commited in the release branch (only
bugfix are commited in the release branch), so you need to apply the patch
given by Shi, attached to this Jira. This patch will create the component for
you in your checkout release branch.
HTH
> When i working with Login with Linkedin In of biz the it is not showing UI
> part
> ---
>
> Key: OFBIZ-6659
> URL: https://issues.apache.org/jira/browse/OFBIZ-6659
> Project: OFBiz
> Issue Type: Bug
> Components: specialpurpose/passport
>Affects Versions: 12.04.05
> Environment: windows
>Reporter: jawahar
>Assignee: Jacques Le Roux
> Attachments: OFBiz-6659-passport-release12.04.patch,
> screenshot-1.png, screenshot-2.png, screenshot-3.jpg
>
>
> {code}
> org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen
> [component://passport/widget/PassportScreens.xml#ListThirdPartyLogins]:
> java.lang.IllegalArgumentException: Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method (Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method)
>
> exception report
> --
> [java] Error in request handler:
> [java] Exception: org.ofbiz.widget.screen.ScreenRenderException
> [java] Message: Error rendering screen
> [component://passport/widget/PassportScreens.xml#ListThirdPartyLogins]:
> java.lang.IllegalArgumentException: Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method (Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method)
> [java] cause
> -
> [java] Exception: java.lang.IllegalArgumentException
> [java] Message: Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method
> [java] stack trace
> ---
> [java] java.lang.IllegalArgumentException: Error running script at
> location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6659) When i working with Login with Linkedin In of biz the it is not showing UI part
[
https://issues.apache.org/jira/browse/OFBIZ-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14949976#comment-14949976
]
Gil Portenseigne commented on OFBIZ-6659:
-
Haha, indeed, that's a good trick ;) ! Here is the link
http://svn.apache.org/viewvc/ofbiz/branches/release12.04/specialpurpose/?pathrev=1706654
> When i working with Login with Linkedin In of biz the it is not showing UI
> part
> ---
>
> Key: OFBIZ-6659
> URL: https://issues.apache.org/jira/browse/OFBIZ-6659
> Project: OFBiz
> Issue Type: Bug
> Components: specialpurpose/passport
>Affects Versions: 12.04.05
> Environment: windows
>Reporter: jawahar
>Assignee: Jacques Le Roux
> Attachments: OFBiz-6659-passport-release12.04.patch,
> screenshot-1.png, screenshot-2.png, screenshot-3.jpg
>
>
> {code}
> org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen
> [component://passport/widget/PassportScreens.xml#ListThirdPartyLogins]:
> java.lang.IllegalArgumentException: Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method (Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method)
>
> exception report
> --
> [java] Error in request handler:
> [java] Exception: org.ofbiz.widget.screen.ScreenRenderException
> [java] Message: Error rendering screen
> [component://passport/widget/PassportScreens.xml#ListThirdPartyLogins]:
> java.lang.IllegalArgumentException: Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method (Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method)
> [java] cause
> -
> [java] Exception: java.lang.IllegalArgumentException
> [java] Message: Error running script at location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method
> [java] stack trace
> ---
> [java] java.lang.IllegalArgumentException: Error running script at
> location
> [component://passport/webapp/passport/WEB-INF/actions/login/getThirdPartyLogins.groovy]:
> java.lang.IllegalArgumentException: You must pass an even sized array to the
> toMap method
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (OFBIZ-6637) Work Effort Month Calendar View Is Broken
[ https://issues.apache.org/jira/browse/OFBIZ-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-6637. --- > Work Effort Month Calendar View Is Broken > - > > Key: OFBIZ-6637 > URL: https://issues.apache.org/jira/browse/OFBIZ-6637 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Adrian Crum >Assignee: Gil Portenseigne > Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch > > Attachments: OFBIZ-6637.patch > > > The Work Effort Month calendar view does not work. The screen does not > display: > https://localhost:8443/workeffort/control/calendar?period=month > and CPU utilization remains high. It appears to be in an endless loop. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14951317#comment-14951317 ] Gil Portenseigne commented on OFBIZ-6654: - oops :p Thanks for the reminder > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch > > Attachments: OFBIZ-6654.patch, screenshot-1.png, screenshot-2.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-6654. --- > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch > > Attachments: OFBIZ-6654.patch, screenshot-1.png, screenshot-2.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne resolved OFBIZ-6654. - Resolution: Fixed Commited in trunk r1707791 R14.12 r1707792 R13.07 r1707793 R12.04 r1707794 > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch > > Attachments: OFBIZ-6654.patch, screenshot-1.png, screenshot-2.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14909124#comment-14909124 ] Gil Portenseigne commented on OFBIZ-6654: - Many thanks for the feedback, it's what i imagined, and I guess actual date-time will be stored on a new workeffort for each day. > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-6654.patch, screenshot-1.png, screenshot-2.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. > Haven't tested it on branches... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6637) Work Effort Month Calendar View Is Broken
[ https://issues.apache.org/jira/browse/OFBIZ-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6637: Affects Version/s: (was: Upcoming Branch) Release Branch 12.04 Release Branch 13.07 Release Branch 14.12 Trunk Fix Version/s: Upcoming Branch 13.07.03 12.04.06 14.12.01 > Work Effort Month Calendar View Is Broken > - > > Key: OFBIZ-6637 > URL: https://issues.apache.org/jira/browse/OFBIZ-6637 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Adrian Crum >Assignee: Gil Portenseigne > Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch > > Attachments: OFBIZ-6637.patch > > > The Work Effort Month calendar view does not work. The screen does not > display: > https://localhost:8443/workeffort/control/calendar?period=month > and CPU utilization remains high. It appears to be in an endless loop. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6654: Affects Version/s: Release Branch 12.04 Release Branch 13.07 Release Branch 14.12 Fix Version/s: Upcoming Branch 13.07.03 12.04.06 14.12.01 Description: I created DAILY_GRIND recurrent workeffort with estimated start date to 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed every day in the month. was: I created DAILY_GRIND recurrent workeffort with estimated start date to 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed every day in the month. Haven't tested it on branches... > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch > > Attachments: OFBIZ-6654.patch, screenshot-1.png, screenshot-2.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6654: Attachment: OFBIZ-6654.patch Better fix, ignoring temporal expression for actual dated workeffort > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch > > Attachments: OFBIZ-6654.patch, screenshot-1.png, screenshot-2.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6654: Attachment: (was: OFBIZ-6654.patch) > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch > > Attachments: OFBIZ-6654.patch, screenshot-1.png, screenshot-2.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6654: Attachment: screenshot-1.png > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: screenshot-1.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. > Haven't tested it on branches... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
Gil Portenseigne created OFBIZ-6654: --- Summary: Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate Key: OFBIZ-6654 URL: https://issues.apache.org/jira/browse/OFBIZ-6654 Project: OFBiz Issue Type: Bug Components: workeffort Affects Versions: Trunk Reporter: Gil Portenseigne Assignee: Gil Portenseigne Attachments: screenshot-1.png I created DAILY_GRIND recurrent workeffort with estimated start date to 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed every day in the month. Haven't tested it on branches... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908719#comment-14908719 ] Gil Portenseigne commented on OFBIZ-6654: - Yeah, Temporal Expression are fine in my tests > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-6654.patch, screenshot-1.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. > Haven't tested it on branches... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6654) Display of a recurrent workeffort in workeffort calendar do not respect estimatedStart/CompletionDate
[ https://issues.apache.org/jira/browse/OFBIZ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-6654: Attachment: OFBIZ-6654.patch I might be missing something in the second loop of the service, but this patch will make the display of a estimatedXXX recurrent workeffort good > Display of a recurrent workeffort in workeffort calendar do not respect > estimatedStart/CompletionDate > - > > Key: OFBIZ-6654 > URL: https://issues.apache.org/jira/browse/OFBIZ-6654 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne > Attachments: OFBIZ-6654.patch, screenshot-1.png > > > I created DAILY_GRIND recurrent workeffort with estimated start date to > 2015-09-02 and estimated completion date to 2015-09-22. The task is displayed > every day in the month. > Haven't tested it on branches... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
