[jira] [Updated] (OFBIZ-5364) Incorrect quantityNotAvailable for OrderItemShipGrpInvRes when issuing items to shipments
[ https://issues.apache.org/jira/browse/OFBIZ-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-5364: - Attachment: OFBIZ-5364-1.patch Incorrect quantityNotAvailable for OrderItemShipGrpInvRes when issuing items to shipments - Key: OFBIZ-5364 URL: https://issues.apache.org/jira/browse/OFBIZ-5364 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Release Branch 12.04 Reporter: Christian Carlow Assignee: Ashish Vijaywargiya Attachments: OFBIZ-5364-1.patch, OFBIZ-5364.patch The quantityNotAvailable field of OrderItemShipGrpRes seems to reflect incorrect numbers after shipment issuances occur. To reproduct: 1. Create an order for DemoCustCompany for a quantity of 100 of a product having no inventory quantity 2. Create a second ship group on the Shipping page 3. Assign half of the order item quantity (50) to the second ship group created and then finish creating the order 4. Click the New Shipment for Ship Group button for the first ship group and navigate to the Order Items page 5. On the Order Items page, notice the issue quantity field is blank because no inventory exist yet to be issued to the shipment. 6. Navigate to the WebstoreWarehouse Receive Inventory page and receive a quantity of 1 for the order item product to increase the inventory by 1 7. Refresh the Shipment Order Items page and you'll see the issue quantity change to 1 because the inventoryItemId created in the last step was assigned to the orderItemShipGrpInvRes for this item. 8. Now change from ship group 1 to ship group 2 and notice the issue quantity is blank 9. Assign a quantity of 1 to the second ship group and click the Issue All button 10. Change the ship group back to 1 and notice the quantity in the issue text box is still 1 It seems like the issue text box in step 10 should be 0 instead of 1 since the inventory item quantity was used for ship group 2. Does anyone disagree? Could I be misinterpreting the way the OrderItemShipGrpInvRes is supposed to work? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5364) Incorrect quantityNotAvailable for OrderItemShipGrpInvRes when issuing items to shipments
[ https://issues.apache.org/jira/browse/OFBIZ-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14285823#comment-14285823 ] youssef khaye commented on OFBIZ-5364: -- I'am trying to fix the testMultipleInventoryItemIssuance test failure and i came across current Issue. I'am not so good at business rule, But I don't think we have the good solution for this Issue ( cancel OISGIR and recreate theme). This issue occurs when we issue an inventory item from one ship group to another ship group To fix this I suggest to add the ineventoryItemId when selecting OISGIRs to cancel reserve look to attached patch OFBIZ-5364-1.patch Incorrect quantityNotAvailable for OrderItemShipGrpInvRes when issuing items to shipments - Key: OFBIZ-5364 URL: https://issues.apache.org/jira/browse/OFBIZ-5364 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Release Branch 12.04 Reporter: Christian Carlow Assignee: Ashish Vijaywargiya Attachments: OFBIZ-5364-1.patch, OFBIZ-5364.patch The quantityNotAvailable field of OrderItemShipGrpRes seems to reflect incorrect numbers after shipment issuances occur. To reproduct: 1. Create an order for DemoCustCompany for a quantity of 100 of a product having no inventory quantity 2. Create a second ship group on the Shipping page 3. Assign half of the order item quantity (50) to the second ship group created and then finish creating the order 4. Click the New Shipment for Ship Group button for the first ship group and navigate to the Order Items page 5. On the Order Items page, notice the issue quantity field is blank because no inventory exist yet to be issued to the shipment. 6. Navigate to the WebstoreWarehouse Receive Inventory page and receive a quantity of 1 for the order item product to increase the inventory by 1 7. Refresh the Shipment Order Items page and you'll see the issue quantity change to 1 because the inventoryItemId created in the last step was assigned to the orderItemShipGrpInvRes for this item. 8. Now change from ship group 1 to ship group 2 and notice the issue quantity is blank 9. Assign a quantity of 1 to the second ship group and click the Issue All button 10. Change the ship group back to 1 and notice the quantity in the issue text box is still 1 It seems like the issue text box in step 10 should be 0 instead of 1 since the inventory item quantity was used for ship group 2. Does anyone disagree? Could I be misinterpreting the way the OrderItemShipGrpInvRes is supposed to work? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-5901) findParty screens show all party when the user uses some filters
youssef khaye created OFBIZ-5901: Summary: findParty screens show all party when the user uses some filters Key: OFBIZ-5901 URL: https://issues.apache.org/jira/browse/OFBIZ-5901 Project: OFBiz Issue Type: Bug Components: party Affects Versions: Trunk Reporter: youssef khaye the service findParty constructs a list of conditions, to filter search results, but does not apply them when it executes the search. In other words, when the old Delegator API was replaced by the EntityQuery, the search condition were omitted. see the commit 1641043 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5901) findParty screens show all party when the user uses some filters
[ https://issues.apache.org/jira/browse/OFBIZ-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-5901: - Attachment: OFBIZ-5901.patch findParty screens show all party when the user uses some filters Key: OFBIZ-5901 URL: https://issues.apache.org/jira/browse/OFBIZ-5901 Project: OFBiz Issue Type: Bug Components: party Affects Versions: Trunk Reporter: youssef khaye Attachments: OFBIZ-5901.patch the service findParty constructs a list of conditions, to filter search results, but does not apply them when it executes the search. In other words, when the old Delegator API was replaced by the EntityQuery, the search condition were omitted. see the commit 1641043 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5875) Example component causes null pointer exception message on page
[ https://issues.apache.org/jira/browse/OFBIZ-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14211281#comment-14211281 ] youssef khaye commented on OFBIZ-5875: -- Hi jacques, I confirm, It's an issue OOTB, you only need to go the example component and you can see menu without any elements. reading the code its seems that one constructor from ModelMenuItem was remove recently, so menu items created dynamically (for example portalPage children) has no modelMenu assigned. thanks. Example component causes null pointer exception message on page --- Key: OFBIZ-5875 URL: https://issues.apache.org/jira/browse/OFBIZ-5875 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Trunk Reporter: Wai Attachments: OFBIZ-5875.patch When user selects the Example component, a null pointer exception happens and stack trace is shown on the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-5227) forms with sort field does not work when the areaId use UEL expression
youssef khaye created OFBIZ-5227: Summary: forms with sort field does not work when the areaId use UEL expression Key: OFBIZ-5227 URL: https://issues.apache.org/jira/browse/OFBIZ-5227 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: youssef khaye the method createAjaxParamsFromUpdateAreas used when generating a sort field does expand a string like the similar one used when generating a submit field. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-5227) forms with sort field does not work when the areaId use UEL expression
[ https://issues.apache.org/jira/browse/OFBIZ-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-5227: - Attachment: fix_non_expnded_ajax_param_for_sort_field.patch this patch fixes the issue forms with sort field does not work when the areaId use UEL expression -- Key: OFBIZ-5227 URL: https://issues.apache.org/jira/browse/OFBIZ-5227 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: youssef khaye Attachments: fix_non_expnded_ajax_param_for_sort_field.patch the method createAjaxParamsFromUpdateAreas used when generating a sort field does expand a string like the similar one used when generating a submit field. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-5099) XML file containg Byte order mark
youssef khaye created OFBIZ-5099: Summary: XML file containg Byte order mark Key: OFBIZ-5099 URL: https://issues.apache.org/jira/browse/OFBIZ-5099 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk, Release Branch 12.04 Environment: Mac osx Reporter: youssef khaye Priority: Minor Only one text files in ofbiz have a UTF-8 BOM (Byte Order Mark). applications/order/widget/ordermgr/LookupScreens.xml copy paste wikipedia : he Unicode Standard permits the BOM in UTF-8, but does not require or recommend its use. Byte order has no meaning in UTF-8, so its only use in UTF-8 is to signal at the start that the text stream is encoded in UTF-8. It seem that UTF-8 BOM generate problem only on Mac plaform when reading file with the java Reader class. I have not searched why, it seems more easy to remove BOM from this file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-5099) XML file containg Byte order mark
[ https://issues.apache.org/jira/browse/OFBIZ-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-5099: - Attachment: LookupScreens.xml xml file without the BOM caracters ! XML file containg Byte order mark - Key: OFBIZ-5099 URL: https://issues.apache.org/jira/browse/OFBIZ-5099 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk, Release Branch 12.04 Environment: Mac osx Reporter: youssef khaye Priority: Minor Attachments: LookupScreens.xml Only one text files in ofbiz have a UTF-8 BOM (Byte Order Mark). applications/order/widget/ordermgr/LookupScreens.xml copy paste wikipedia : he Unicode Standard permits the BOM in UTF-8, but does not require or recommend its use. Byte order has no meaning in UTF-8, so its only use in UTF-8 is to signal at the start that the text stream is encoded in UTF-8. It seem that UTF-8 BOM generate problem only on Mac plaform when reading file with the java Reader class. I have not searched why, it seems more easy to remove BOM from this file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4448) Date time field with input method set to time-drop-down is not working correctly
Date time field with input method set to time-drop-down is not working correctly Key: OFBIZ-4448 URL: https://issues.apache.org/jira/browse/OFBIZ-4448 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: youssef khaye Priority: Minor when a field of type date-time with input method set to time-dropandown and it's step attibute set to 5 (for example). It shows a wroing default value in minutes drop-down in when minutes are greater than (60 - step/2) for 11:58 it show 11:00 instead of 12 : 00. a solution for that particular case is to show 11:55 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4448) Date time field with input method set to time-drop-down is not working correctly
[ https://issues.apache.org/jira/browse/OFBIZ-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-4448: - Attachment: date-time-drop-down.patch this patch should fix this issue by handling this specific case when generating the source code of the minutes drop-down input Date time field with input method set to time-drop-down is not working correctly Key: OFBIZ-4448 URL: https://issues.apache.org/jira/browse/OFBIZ-4448 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: youssef khaye Priority: Minor Attachments: date-time-drop-down.patch when a field of type date-time with input method set to time-dropandown and it's step attibute set to 5 (for example). It shows a wroing default value in minutes drop-down in when minutes are greater than (60 - step/2) for 11:58 it show 11:00 instead of 12 : 00. a solution for that particular case is to show 11:55 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4448) Date time field with input method set to time-drop-down is not working correctly
[ https://issues.apache.org/jira/browse/OFBIZ-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-4448: - Comment: was deleted (was: this patch should fix this issue by handling this specific case when generating the source code of the minutes drop-down input) Date time field with input method set to time-drop-down is not working correctly Key: OFBIZ-4448 URL: https://issues.apache.org/jira/browse/OFBIZ-4448 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: youssef khaye Assignee: Erwan de FERRIERES Priority: Minor Attachments: date-time-drop-down.patch when a field of type date-time with input method set to time-dropandown and it's step attibute set to 5 (for example). It shows a wroing default value in minutes drop-down in when minutes are greater than (60 - step/2) for 11:58 it show 11:00 instead of 12 : 00. a solution for that particular case is to show 11:55 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4448) Date time field with input method set to time-drop-down is not working correctly
[ https://issues.apache.org/jira/browse/OFBIZ-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-4448: - Attachment: date-time-drop-down.patch Date time field with input method set to time-drop-down is not working correctly Key: OFBIZ-4448 URL: https://issues.apache.org/jira/browse/OFBIZ-4448 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: youssef khaye Assignee: Erwan de FERRIERES Priority: Minor Attachments: date-time-drop-down.patch, date-time-drop-down.patch when a field of type date-time with input method set to time-dropandown and it's step attibute set to 5 (for example). It shows a wroing default value in minutes drop-down in when minutes are greater than (60 - step/2) for 11:58 it show 11:00 instead of 12 : 00. a solution for that particular case is to show 11:55 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (OFBIZ-4164) ajaxUpdateAreas not working
ajaxUpdateAreas not working --- Key: OFBIZ-4164 URL: https://issues.apache.org/jira/browse/OFBIZ-4164 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: ubuntu 10.04, FF 3.16.13 Reporter: youssef khaye When using multiple on-event-update-area for a form submit, it yields in an ajaxSubmitFormUpdateAreas and that does not work currently. Without being a javascript expert, i can propose a patch to fix this issue. I think it is a problem of variable visibility scope inside the loop. Setting the jQueyr.ajax async option to false resolved the issue. In the following patch, i used a name-spacing technique to ensure the parameters visibility inside callback function. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OFBIZ-4164) ajaxUpdateAreas not working
[ https://issues.apache.org/jira/browse/OFBIZ-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-4164: - Attachment: selectall.js.patch ajaxUpdateAreas not working --- Key: OFBIZ-4164 URL: https://issues.apache.org/jira/browse/OFBIZ-4164 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: ubuntu 10.04, FF 3.16.13 Reporter: youssef khaye Labels: jQuery Attachments: selectall.js.patch When using multiple on-event-update-area for a form submit, it yields in an ajaxSubmitFormUpdateAreas and that does not work currently. Without being a javascript expert, i can propose a patch to fix this issue. I think it is a problem of variable visibility scope inside the loop. Setting the jQueyr.ajax async option to false resolved the issue. In the following patch, i used a name-spacing technique to ensure the parameters visibility inside callback function. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-2020) Using one Ofbiz instance with multiple databases
[ https://issues.apache.org/jira/browse/OFBIZ-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672986#action_12672986 ] youssef khaye commented on OFBIZ-2020: -- The main problème i get now is when changing the delegator on userLogin event, all already existing users get their work done on the new database but not the one they requested. In Other words, i thought that a session is created for each user, so that i put the delegator and dispatcher info in the session, meanwhile, this make those delegator and dispatcher available for everybody. Exemple: i used two users admin : connects to database delegator flexadmin: connects to databse company1 -admin connect and plan a job( serviceName: myService ) that append the userLoginId delegator (both giot from dispatchContext) in a file. -now flexadmin connect and plan an other job (serviceName: myOtherService) that append the same info to the same file. I expected that my file will contain the loginId and delegator name for both user in an alternative way. But in my file i have only the flexadmin userloginId and delegator (he loged in after the admin). which means that the last user who logged in changes the delegator for all existing users. Using one Ofbiz instance with multiple databases Key: OFBIZ-2020 URL: https://issues.apache.org/jira/browse/OFBIZ-2020 Project: OFBiz Issue Type: New Feature Affects Versions: SVN trunk Reporter: youssef khaye Fix For: SVN trunk Attachments: entitymodel.xml.rej, ofbiz-multi.patch, ofbiz-multi.patch, ofbiz-multi.patch I want to share my work with you implementing the use of one OFBiz instance with multiple databases, by defining multiple delegators, in the entityengine.xml, one for each databases. this is useful when we implementing ofbiz for semi-independent subsidiaries of one company having users allowed to use two or more databases. This involve mainly the user authentication procedure by asking for a company name in the login form. This company name represents a delegator name that describe a specific subsidiary database. After a successful user login operation, the passed company name is used to retrieve the corresponding delegator. The method CoreEvents.chageDelegator is modified to change the delegator of related Dispatcher and JobManager. Of course I needed to store the delegator name in the GenericValue UserLogin to navigate among different ofbiz applications keeping the same original database. I also provided a kind of mechanism to activate or deactivates the use of multi-delegator by adding a multi.delegator property in the security.properties configuration file that when set true, cause the ofbiz to display he company field in the login form and do the necessary work to switch from default database to the provided one. I will be open to discuss any suggestion for improving this issue. Following is a patch for current ofbiz trunk version: -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2088) strange behavior of OFBIZ adding product to the shopping cart
strange behavior of OFBIZ adding product to the shopping cart - Key: OFBIZ-2088 URL: https://issues.apache.org/jira/browse/OFBIZ-2088 Project: OFBiz Issue Type: Bug Components: specialpurpose/webpos Affects Versions: SVN trunk Reporter: youssef khaye when I click on add to cart affter adding a productId in the form the Webpos increments the quantity of a diffrent product in the cart(actually the first one is always incremented even i already have the same product in the cart), if the cart was empty it show an error No product information passed, not adding anything to cart. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2020) Using one Ofbiz instance with multiple databases
[ https://issues.apache.org/jira/browse/OFBIZ-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12651132#action_12651132 ] youssef khaye commented on OFBIZ-2020: -- Hi Mr Jones; Thanks for your interesting. Reading your comment makes me think of the matter, It seems to be more significant to create a dispatcher in the same time with a delegator if someone request a connection for a database without them already created, and why not a new jobmanager too. This would solve the issue because every dispatcher with its own (jobManager,delegator) will continue working with their DB. Since the issue of multi delegator can be very useful in a production environment, I will be volunteer to accomplish the necessary work, of course with the guidance of persons like you and Mr Le Roux. Best regards. Using one Ofbiz instance with multiple databases Key: OFBIZ-2020 URL: https://issues.apache.org/jira/browse/OFBIZ-2020 Project: OFBiz Issue Type: New Feature Affects Versions: SVN trunk Reporter: youssef khaye Assignee: Jacques Le Roux Fix For: SVN trunk Attachments: entitymodel.xml.rej, ofbiz-multi.patch, ofbiz-multi.patch, ofbiz-multi.patch I want to share my work with you implementing the use of one OFBiz instance with multiple databases, by defining multiple delegators, in the entityengine.xml, one for each databases. this is useful when we implementing ofbiz for semi-independent subsidiaries of one company having users allowed to use two or more databases. This involve mainly the user authentication procedure by asking for a company name in the login form. This company name represents a delegator name that describe a specific subsidiary database. After a successful user login operation, the passed company name is used to retrieve the corresponding delegator. The method CoreEvents.chageDelegator is modified to change the delegator of related Dispatcher and JobManager. Of course I needed to store the delegator name in the GenericValue UserLogin to navigate among different ofbiz applications keeping the same original database. I also provided a kind of mechanism to activate or deactivates the use of multi-delegator by adding a multi.delegator property in the security.properties configuration file that when set true, cause the ofbiz to display he company field in the login form and do the necessary work to switch from default database to the provided one. I will be open to discuss any suggestion for improving this issue. Following is a patch for current ofbiz trunk version: -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2020) Using one Ofbiz instance with multiple databases
[ https://issues.apache.org/jira/browse/OFBIZ-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650060#action_12650060 ] youssef khaye commented on OFBIZ-2020: -- Hi Jacques, It was a great pleasure to read from you. For the relative path issue I did the nessecery. My old patch was made from the 705872, revesion and i was surprised when you told that didn't work. I make a newer patch on the old revision 705872, then I updated my project before doing the eclipse create patch. To be sure that will work, I applied the patch on the base version and still working. Best regards. Using one Ofbiz instance with multiple databases Key: OFBIZ-2020 URL: https://issues.apache.org/jira/browse/OFBIZ-2020 Project: OFBiz Issue Type: New Feature Affects Versions: SVN trunk Reporter: youssef khaye Assignee: Jacques Le Roux Fix For: SVN trunk Attachments: entitymodel.xml.rej, ofbiz-multi.patch, ofbiz-multi.patch I want to share my work with you implementing the use of one OFBiz instance with multiple databases, by defining multiple delegators, in the entityengine.xml, one for each databases. this is useful when we implementing ofbiz for semi-independent subsidiaries of one company having users allowed to use two or more databases. This involve mainly the user authentication procedure by asking for a company name in the login form. This company name represents a delegator name that describe a specific subsidiary database. After a successful user login operation, the passed company name is used to retrieve the corresponding delegator. The method CoreEvents.chageDelegator is modified to change the delegator of related Dispatcher and JobManager. Of course I needed to store the delegator name in the GenericValue UserLogin to navigate among different ofbiz applications keeping the same original database. I also provided a kind of mechanism to activate or deactivates the use of multi-delegator by adding a multi.delegator property in the security.properties configuration file that when set true, cause the ofbiz to display he company field in the login form and do the necessary work to switch from default database to the provided one. I will be open to discuss any suggestion for improving this issue. Following is a patch for current ofbiz trunk version: -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2020) Using one Ofbiz instance with multiple databases
[ https://issues.apache.org/jira/browse/OFBIZ-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] youssef khaye updated OFBIZ-2020: - Attachment: ofbiz-multi.patch Using one Ofbiz instance with multiple databases Key: OFBIZ-2020 URL: https://issues.apache.org/jira/browse/OFBIZ-2020 Project: OFBiz Issue Type: New Feature Affects Versions: SVN trunk Reporter: youssef khaye Assignee: Jacques Le Roux Fix For: SVN trunk Attachments: entitymodel.xml.rej, ofbiz-multi.patch, ofbiz-multi.patch, ofbiz-multi.patch I want to share my work with you implementing the use of one OFBiz instance with multiple databases, by defining multiple delegators, in the entityengine.xml, one for each databases. this is useful when we implementing ofbiz for semi-independent subsidiaries of one company having users allowed to use two or more databases. This involve mainly the user authentication procedure by asking for a company name in the login form. This company name represents a delegator name that describe a specific subsidiary database. After a successful user login operation, the passed company name is used to retrieve the corresponding delegator. The method CoreEvents.chageDelegator is modified to change the delegator of related Dispatcher and JobManager. Of course I needed to store the delegator name in the GenericValue UserLogin to navigate among different ofbiz applications keeping the same original database. I also provided a kind of mechanism to activate or deactivates the use of multi-delegator by adding a multi.delegator property in the security.properties configuration file that when set true, cause the ofbiz to display he company field in the login form and do the necessary work to switch from default database to the provided one. I will be open to discuss any suggestion for improving this issue. Following is a patch for current ofbiz trunk version: -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2020) Using one Ofbiz instance with multiple databases
[ https://issues.apache.org/jira/browse/OFBIZ-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650063#action_12650063 ] youssef khaye commented on OFBIZ-2020: -- Hi jacques again, For relative path, using eclipse, you can check ignore leading path name segment to overcome the issue. Best regards. Using one Ofbiz instance with multiple databases Key: OFBIZ-2020 URL: https://issues.apache.org/jira/browse/OFBIZ-2020 Project: OFBiz Issue Type: New Feature Affects Versions: SVN trunk Reporter: youssef khaye Assignee: Jacques Le Roux Fix For: SVN trunk Attachments: entitymodel.xml.rej, ofbiz-multi.patch, ofbiz-multi.patch, ofbiz-multi.patch I want to share my work with you implementing the use of one OFBiz instance with multiple databases, by defining multiple delegators, in the entityengine.xml, one for each databases. this is useful when we implementing ofbiz for semi-independent subsidiaries of one company having users allowed to use two or more databases. This involve mainly the user authentication procedure by asking for a company name in the login form. This company name represents a delegator name that describe a specific subsidiary database. After a successful user login operation, the passed company name is used to retrieve the corresponding delegator. The method CoreEvents.chageDelegator is modified to change the delegator of related Dispatcher and JobManager. Of course I needed to store the delegator name in the GenericValue UserLogin to navigate among different ofbiz applications keeping the same original database. I also provided a kind of mechanism to activate or deactivates the use of multi-delegator by adding a multi.delegator property in the security.properties configuration file that when set true, cause the ofbiz to display he company field in the login form and do the necessary work to switch from default database to the provided one. I will be open to discuss any suggestion for improving this issue. Following is a patch for current ofbiz trunk version: -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2020) Using one Ofbiz instance with multiple databases
[ https://issues.apache.org/jira/browse/OFBIZ-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12642790#action_12642790 ] youssef khaye commented on OFBIZ-2020: -- Thank you Freeman for the comment; I really dont understand wha do you means by entity-views across applications, but for sandbox i just switch the database of the JobManager to database of the user by changing the JobManager.delegator. Using one Ofbiz instance with multiple databases Key: OFBIZ-2020 URL: https://issues.apache.org/jira/browse/OFBIZ-2020 Project: OFBiz Issue Type: New Feature Affects Versions: SVN trunk Reporter: youssef khaye Fix For: SVN trunk Attachments: ofbiz-multi.patch I want to share my work with you implementing the use of one OFBiz instance with multiple databases, by defining multiple delegators, in the entityengine.xml, one for each databases. this is useful when we implementing ofbiz for semi-independent subsidiaries of one company having users allowed to use two or more databases. This involve mainly the user authentication procedure by asking for a company name in the login form. This company name represents a delegator name that describe a specific subsidiary database. After a successful user login operation, the passed company name is used to retrieve the corresponding delegator. The method CoreEvents.chageDelegator is modified to change the delegator of related Dispatcher and JobManager. Of course I needed to store the delegator name in the GenericValue UserLogin to navigate among different ofbiz applications keeping the same original database. I also provided a kind of mechanism to activate or deactivates the use of multi-delegator by adding a multi.delegator property in the security.properties configuration file that when set true, cause the ofbiz to display he company field in the login form and do the necessary work to switch from default database to the provided one. I will be open to discuss any suggestion for improving this issue. Following is a patch for current ofbiz trunk version: Index: /home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml === --- /home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml (revision 705872) +++ /home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml (working copy) @@ -2611,6 +2611,9 @@ /extend-entity extend-entity entity-name=UserLogin field name=partyId type=id/field +!--Begin specific : field used to store the delegator name along theuse session -- +field name=delegator type=id/field +!-- End Specific -- relation type=one fk-name=USER_PARTY rel-entity-name=Party key-map field-name=partyId/ /relation Index: /home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml === --- /home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml (revision 705872) +++ /home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml (working copy) @@ -1617,6 +1617,23 @@ value xml:lang=zh_CN十二月/value value xml:lang=zh十二月/value /property +property key=CommonCompany +value xml:lang=arالمؤسسة/value +value xml:lang=enCompany/value +value xml:lang=frEntreprise/value +/property property key=CommonDelete value xml:lang=arحذف/value value xml:lang=csSmazat/value Index: /home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java === --- /home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java (revision 705872) +++ /home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java (working copy) @@ -90,7 +90,7 @@ if (username == null) username = (String) context.get(username); String password = (String) context.get(login.password); if (password == null) password = (String) context.get(password); - +String userDelegatorName = (String) context.get(userDelegatorName); // get the visitId for the history entity String visitId = (String) context.get(visitId); @@ -193,7 +193,9 @@ // successful login no loggout flag, no need to change anything, so don't do the store doStore = false; } - +
[jira] Created: (OFBIZ-2020) Using on Ofbiz instance with multiple databases
Using on Ofbiz instance with multiple databases
---
Key: OFBIZ-2020
URL: https://issues.apache.org/jira/browse/OFBIZ-2020
Project: OFBiz
Issue Type: New Feature
Affects Versions: SVN trunk
Reporter: youssef khaye
Fix For: SVN trunk
I want to share my work with you implementing the use of one OFBiz instance
with multiple databases, by defining multiple delegators, in the
entityengine.xml, one for each databases. this is useful when we implementing
ofbiz for semi-independent subsidiaries of one company having users allowed to
use two or more databases.
This involve mainly the user authentication procedure by asking for a company
name in the login form. This company name represents a delegator name that
describe a specific subsidiary database. After a successful user login
operation, the passed company name is used to retrieve the corresponding
delegator. The method CoreEvents.chageDelegator is modified to change the
delegator of related Dispatcher and JobManager.
Of course I needed to store the delegator name in the GenericValue UserLogin to
navigate among different ofbiz applications keeping the same original database.
I also provided a kind of mechanism to activate or deactivates the use of
multi-delegator by adding a multi.delegator property in the
security.properties configuration file that when set true, cause the ofbiz to
display he company field in the login form and do the necessary work to switch
from default database to the provided one.
I will be open to discuss any suggestion for improving this issue.
Following is a patch for current ofbiz trunk version:
Index:
/home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml
===
--- /home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml
(revision 705872)
+++ /home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml
(working copy)
@@ -2611,6 +2611,9 @@
/extend-entity
extend-entity entity-name=UserLogin
field name=partyId type=id/field
+!--Begin specific : field used to store the delegator name along
theuse session --
+field name=delegator type=id/field
+!-- End Specific --
relation type=one fk-name=USER_PARTY rel-entity-name=Party
key-map field-name=partyId/
/relation
Index: /home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml
===
--- /home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml
(revision 705872)
+++ /home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml
(working copy)
@@ -1617,6 +1617,23 @@
value xml:lang=zh_CN十二月/value
value xml:lang=zh十二月/value
/property
+property key=CommonCompany
+value xml:lang=arالمؤسسة/value
+value xml:lang=enCompany/value
+value xml:lang=frEntreprise/value
+/property
property key=CommonDelete
value xml:lang=arحذف/value
value xml:lang=csSmazat/value
Index:
/home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java
===
---
/home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java
(revision 705872)
+++
/home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java
(working copy)
@@ -90,7 +90,7 @@
if (username == null) username = (String) context.get(username);
String password = (String) context.get(login.password);
if (password == null) password = (String) context.get(password);
-
+String userDelegatorName = (String) context.get(userDelegatorName);
// get the visitId for the history entity
String visitId = (String) context.get(visitId);
@@ -193,7 +193,9 @@
// successful login no loggout flag, no need
to change anything, so don't do the store
doStore = false;
}
-
+
if(true.equals(UtilProperties.getPropertyValue(security.properties,
multi.delegator))){
+userLogin.set(delegator, userDelegatorName);
+}
successfulLogin = Y;
if (!isServiceAuth) {
Index:
/home/youssef/workspace/ofbiz/framework/common/webcommon/includes/header.ftl
===
---
/home/youssef/workspace/ofbiz/framework/common/webcommon/includes/header.ftl
(revision 705872)
+++
[jira] Updated: (OFBIZ-2020) Using one Ofbiz instance with multiple databases
[
https://issues.apache.org/jira/browse/OFBIZ-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
youssef khaye updated OFBIZ-2020:
-
Attachment: ofbiz-multi.patch
Using one Ofbiz instance with multiple databases
Key: OFBIZ-2020
URL: https://issues.apache.org/jira/browse/OFBIZ-2020
Project: OFBiz
Issue Type: New Feature
Affects Versions: SVN trunk
Reporter: youssef khaye
Fix For: SVN trunk
Attachments: ofbiz-multi.patch
I want to share my work with you implementing the use of one OFBiz instance
with multiple databases, by defining multiple delegators, in the
entityengine.xml, one for each databases. this is useful when we implementing
ofbiz for semi-independent subsidiaries of one company having users allowed
to use two or more databases.
This involve mainly the user authentication procedure by asking for a company
name in the login form. This company name represents a delegator name that
describe a specific subsidiary database. After a successful user login
operation, the passed company name is used to retrieve the corresponding
delegator. The method CoreEvents.chageDelegator is modified to change the
delegator of related Dispatcher and JobManager.
Of course I needed to store the delegator name in the GenericValue UserLogin
to navigate among different ofbiz applications keeping the same original
database.
I also provided a kind of mechanism to activate or deactivates the use of
multi-delegator by adding a multi.delegator property in the
security.properties configuration file that when set true, cause the ofbiz to
display he company field in the login form and do the necessary work to
switch from default database to the provided one.
I will be open to discuss any suggestion for improving this issue.
Following is a patch for current ofbiz trunk version:
Index:
/home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml
===
---
/home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml
(revision 705872)
+++
/home/youssef/workspace/ofbiz/applications/party/entitydef/entitymodel.xml
(working copy)
@@ -2611,6 +2611,9 @@
/extend-entity
extend-entity entity-name=UserLogin
field name=partyId type=id/field
+!--Begin specific : field used to store the delegator name along
theuse session --
+field name=delegator type=id/field
+!-- End Specific --
relation type=one fk-name=USER_PARTY rel-entity-name=Party
key-map field-name=partyId/
/relation
Index:
/home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml
===
--- /home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml
(revision 705872)
+++ /home/youssef/workspace/ofbiz/framework/common/config/CommonUiLabels.xml
(working copy)
@@ -1617,6 +1617,23 @@
value xml:lang=zh_CN十二月/value
value xml:lang=zh十二月/value
/property
+property key=CommonCompany
+value xml:lang=arالمؤسسة/value
+value xml:lang=enCompany/value
+value xml:lang=frEntreprise/value
+/property
property key=CommonDelete
value xml:lang=arحذف/value
value xml:lang=csSmazat/value
Index:
/home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java
===
---
/home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java
(revision 705872)
+++
/home/youssef/workspace/ofbiz/framework/common/src/org/ofbiz/common/login/LoginServices.java
(working copy)
@@ -90,7 +90,7 @@
if (username == null) username = (String) context.get(username);
String password = (String) context.get(login.password);
if (password == null) password = (String) context.get(password);
-
+String userDelegatorName = (String) context.get(userDelegatorName);
// get the visitId for the history entity
String visitId = (String) context.get(visitId);
@@ -193,7 +193,9 @@
// successful login no loggout flag, no
need to change anything, so don't do the store
doStore = false;
}
-
+
if(true.equals(UtilProperties.getPropertyValue(security.properties,
multi.delegator))){
+userLogin.set(delegator,
userDelegatorName);
+}
successfulLogin = Y;
if
