Problems while PUSH and PULL entity sync process in POS

Hi all ! I have been trying to setup pos sync following step by step instruction here https://cwiki.apache.org/confluence/display/OFBIZ/Sync+Setup+Notes+and+Example But I wonder about 2 points: 6,7,8 & 9 6.Load EntitySync record for PULL on MCS instance (the OFBiz instance which runs the MCS) 7

Re: Planning the next releases

On 26/02/14 04:48, Pierre Smits wrote: Jacopo, Now, I don't know what that means when having set up the domain name for a tenant as the means to access the tenant environment. Apparently that has been developed to have a unique uri per tenant. this is an essential feature if you want run seperat

[jira] [Commented] (OFBIZ-5319) Exporting data of tenant also exports data in entity Tenant and TenantDataSource

[ https://issues.apache.org/jira/browse/OFBIZ-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912122#comment-13912122 ] Pierre Smits commented on OFBIZ-5319: - Jacques, The patch attached to OFBIZ-4130 will

Re: Planning the next releases

Jacopo, I also would like to understand what that means. And what I don't understand I can't recreate it also. As far as conditions go, I will elaborate here under what conditions we have tested the patch. We created a virtual test setup consisting of 1 webserver (Apache HTTP) and 1 app server (

[jira] [Commented] (OFBIZ-5319) Exporting data of tenant also exports data in entity Tenant and TenantDataSource

[ https://issues.apache.org/jira/browse/OFBIZ-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911651#comment-13911651 ] Jacques Le Roux commented on OFBIZ-5319: Any patch for this one? > Exporting data

[jira] [Commented] (OFBIZ-4130) Tenant super user (tenant admin) can view all database details of all tenants

[ https://issues.apache.org/jira/browse/OFBIZ-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911645#comment-13911645 ] Jacques Le Roux commented on OFBIZ-4130: Pierre told me bq. Way to test is: first

[jira] [Created] (OFBIZ-5548) Improve production run task declarations to allow for rejected by-products from workers to be determined

Christian Carlow created OFBIZ-5548: --- Summary: Improve production run task declarations to allow for rejected by-products from workers to be determined Key: OFBIZ-5548 URL: https://issues.apache.org/jira/browse/

[jira] [Issue Comment Deleted] (OFBIZ-5319) Exporting data of tenant also exports data in entity Tenant and TenantDataSource

[ https://issues.apache.org/jira/browse/OFBIZ-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-5319: --- Comment: was deleted (was: Pierre told me bq. Way to test is: first create 2 new tenants wit

[jira] [Commented] (OFBIZ-5319) Exporting data of tenant also exports data in entity Tenant and TenantDataSource

[ https://issues.apache.org/jira/browse/OFBIZ-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911644#comment-13911644 ] Jacques Le Roux commented on OFBIZ-5319: Pierre told me bq. Way to test is: first

Re: Planning the next releases

On Feb 25, 2014, at 12:11 PM, Pierre Smits wrote: > As for OFBIZ-5319, this will be resolved when the patch provided in > OFBiz-4130 has been committed. I have tried to stay out of this because I am not particularly interested in the specific feature and I didn't want to be involved in a fight;

Re: Planning the next releases

Sounds good to me, thanks for the specialpurpose folder not being part of the release branches reminder, I tend to forget it. This simplifies things and was a good idea... Jacques Le 25/02/2014 10:22, Jacopo Cappellato a écrit : Considering that the last release branch (13.07) was created in J

Re: Planning the next releases

Ha yes, sorry Pierre, did not spot the patch. I will have a look at it Jacques Le 25/02/2014 12:11, Pierre Smits a écrit : Jacques, As I have stated in the comments regarding OFBIZ-4130, Hans has is own solution in his own environment (growerp). Based on that he is stating that there is no iss

Re: Planning the next releases

Jacques, As I have stated in the comments regarding OFBIZ-4130, Hans has is own solution in his own environment (growerp). Based on that he is stating that there is no issue. Which is shortsighted, as many will not have that with a default OFBiz implementation. His setup is not OFBiz! Furthermor

Re: Planning the next releases

Considering that the last release branch (13.07) was created in July 2013, and after that we also backported a series of refactoring, we will probably wait for a few months before creating the new one: this could happen sometimes during the summer or early autumn. As regards the Solr component:

Re: Planning the next releases

Hi Pierre, OFBIZ-4130 is a (still disputed, at least by Hans) bug so it could be committed after the release in the branch and be part of a minor release For OFBIZ-5319 it's the same, we can't wait to release if we have no patch... Jacques Le 25/02/2014 09:24, Pierre Smits a écrit : As issues

Re: Planning the next releases

I'm neutral as well. I'm only concerned by the next freeze, where I'd like to merge the SEO branch and hopefully commit the Solr component before we freeze (and maybe some other stuff I don't remember at the moment) Jacques Le 24/02/2014 16:51, Jacopo Cappellato a écrit : Are we ready to sta

Re: Planning the next releases

As issues OFBIZ-4130 and OFBIZ-5319 aren't resolved I am not in favour of releasing it, given the implications regarding the multi-tenancy aspect. Pierre Smits *ORRTIZ.COM

Re: Different login screen in Webtools

I have rerad the entire thread and must say, given that we at ORRTIZ.com mainly do multi-tenancy, that having a page stating a userID and password is an unwanted aspect. Per tenant we create a new superuserId and associated password the moment we instantiate it. But that is our personal approach t