Re: Naming Conventions

[Aditya Sharma]

Hi Craig,

Yes, You can not send any attachment to mailing list.

https://commons.apache.org/mail-lists.html

*Note:* please don't send patches or attachments to any of the mailing
lists. Patches are best handled via the *Issue Tracking* system. Otherwise,
please upload the file to a public server and include the URL in the mail.

Thanks and Regards,
*Aditya Sharma* | Enterprise Software Engineer
HotWax Systems 

On Wed, Jul 19, 2017 at 8:53 AM, Craig Parker  wrote:

> There was supposed to be an image attached. No images on the mailing list
> allowed? It's here if it didn't make the trip:
>
> http://fossfolks.com/screen-layout.png
>
>
>
> On 07/18/2017 11:13 PM, Craig Parker wrote:
>
>> This may be nit-picky, but I'm thinking it might be important down the
>> road as docs get a makeover. What are these areas officially called that
>> I've numbered in the screenshot? There looks to be an equivalent in
>> whatever theme I'm using.
>>
>> 1. Menu
>> 2. Sub menu? (flies out in one theme)
>> 3. Links area?
>> 4. Work area?
>>
>>
>

Re: Naming Conventions

[Craig Parker]

There was supposed to be an image attached. No images on the mailing 
list allowed? It's here if it didn't make the trip:


http://fossfolks.com/screen-layout.png


On 07/18/2017 11:13 PM, Craig Parker wrote:
This may be nit-picky, but I'm thinking it might be important down the 
road as docs get a makeover. What are these areas officially called 
that I've numbered in the screenshot? There looks to be an equivalent 
in whatever theme I'm using.


1. Menu
2. Sub menu? (flies out in one theme)
3. Links area?
4. Work area?

Naming Conventions

[Craig Parker]

This may be nit-picky, but I'm thinking it might be important down the 
road as docs get a makeover. What are these areas officially called that 
I've numbered in the screenshot? There looks to be an equivalent in 
whatever theme I'm using.


1. Menu
2. Sub menu? (flies out in one theme)
3. Links area?
4. Work area?

Re: GL Patch

[Paul Foxworthy]

Hi Craig,

The version will probably be in the footer of the web pages. Look for
example at the dark grey stuff at the bottom of
https://demo-trunk.ofbiz.apache.org/catalog/control/main .

Cheers

Paul Foxworthy


On 26 June 2017 at 04:59, Craig Parker  wrote:

> I'm looking at OFBIZ-9429.patch, and wondering how to apply it to a
> current install. I'm not sure which version I'm running though, can't see
> it in any of the unzipped files yet and I don't know where to find it in
> the software menu.
>
> I used the main download zip, I beleive it was the first one to use
> gradle, and I don't think I've reinstalled since any updates came out --
> I'm guessing 16.11.01. Is there a "how to apply a patch" doc somewhere? Was
> this email something for the dev list, or should I have asked over at user?
>
>
>
>


-- 
Coherent Software Australia Pty Ltd
PO Box 2773
Cheltenham Vic 3192
Australia

Phone: +61 3 9585 6788
Web: http://www.coherentsoftware.com.au/
Email: i...@coherentsoftware.com.au

Re: [PROPOSAL] Environment variable configuration

[gil portenseigne]

Hello Guys,

I just created https://issues.apache.org/jira/browse/OFBIZ-9498

You can test it out with the provided patch.

And James, I just tested two launch to instances with different 
environment properties with no issue (different JVM args and database 
connections)


Cheers

Gil

On 06/07/2017 22:07, gil portenseigne wrote:

Hi James,

inline

On 06/07/2017 12:12, James Yong wrote:

Hi Gil,

Some afterthought questions with the proposed change:
1) Can it support multiple OFBiz instances on the same server?
Using different shell process to launch the multiple OFBiz instances, 
i think that it's possible to set environment variable dedicated to 
each OFBiz instance.
2) Can we store encrypted values for some of the environment 
variables like database credentials?
You can store whatever value you want into environment variable, but 
you must adapt OFBiz to decrypt the value.


Thanks all for your feedback, i'll work on trunk to make it available 
soon (within a new Jira)


Regards

Gil

Re: Restore common-theme with ofbiz-framework

[Nicolas Malin]

Hi Taher, I understand the motivation but my work it's currently 
unstable. I continue to centralize the theme configuration for more 
stabilization.


Nicolas


Le 18/07/2017 à 16:54, Taher Alkhateeb a écrit :

Hi Nicolas,

Great stuff, I'm not sure what everyone thinks but I prefer if we can
try to get your work incorporated back into the code base as early as
possible and to start completing the work from there.

On Tue, Jul 18, 2017 at 5:38 PM, Nicolas Malin  wrote:

Michael,

I finished to restore my work on common-theme from ofbiz to ofbiz-framework
:
https://github.com/apache/ofbiz-framework/compare/trunk...nmalin:common-theme?expand=1

Now I will work on the java object to manage the widget theme on user
session.

Nicolas

--
logoNrd 
 Nicolas Malin
The apache way  : *Openness* Technical decisions
are made publicly
informat...@nereide.fr
8 rue des Déportés 37000 TOURS, 02 47 50 30 54

Apache OFBiz |The Apache Way
|ofbiz-fr |réseau LE

Re: [Proposal] moving all data in applications to the data-model component

[Nicolas Malin]

+1


Le 14/07/2017 à 11:59, Taher Alkhateeb a écrit :

  Hello Everyone,

Data loading in OFBiz is quite fragile. A small change could crash the
system and finding out the reason can be difficult. I really felt the
pain of this when trying to disentangle the framework from data
dependencies on plugins [1].

I've been thinking about a solution to reduce fragility, and here are
my thoughts:
- The less data files the better.
- The less data the better.
- The less distance (e.g. same directory) between data files the better.
- No circular dependencies (file dependencies should be like a tree).
- Fail fast [2].

Therefore, I suggest the following action points:
- Create a directory structure similar to [3] in the datamodel component.
- For any data that two or more files depend on, immediately move it
to the common-.xml file.
- For any data that does not belong to any domain (e.g. marketing,
content, etc ..) move it to the common-.xml.
- Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
- Gradually and carefully move data from all applications to the
datamodel component as per above guidelines.
- Cleanup and refactor the data as we move it including any tests that
depend on it.

What do you think of this proposal? Does it sound reasonable? Also
given the size of what I'm proposing I think we need multiple people
to work on this. So is anyone interested in taking part in this
initiative?

Cheers,

Taher Alkhateeb

[1] https://issues.apache.org/jira/browse/OFBIZ-9322
[2] 
https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb950999e8f8e869a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
[3] directory structure:
data/
├── demo
│   ├── accounting-demo.xml
│   ├── common-demo.xml
│   ├── content-demo.xml
│   ├── humanres-demo.xml
│   ├── manufacturing-demo.xml
│   ├── marketing-demo.xml
│   ├── order-demo.xml
│   ├── party-demo.xml
│   ├── product-demo.xml
│   ├── shipment-demo.xml
│   └── workeffort-demo.xml
├── seed
│   ├── accounting-seed.xml
│   ├── common-seed.xml
│   ├── content-seed.xml
│   ├── humanres-seed.xml
│   ├── manufacturing-seed.xml
│   ├── marketing-seed.xml
│   ├── order-seed.xml
│   ├── party-seed.xml
│   ├── product-seed.xml
│   ├── shipment-seed.xml
│   └── workeffort-seed.xml
└── seed-initial
 ├── accounting-seed-initial.xml
 ├── common-seed-initial.xml
 ├── content-seed-initial.xml
 ├── humanres-seed-initial.xml
 ├── manufacturing-seed-initial.xml
 ├── marketing-seed-initial.xml
 ├── order-seed-initial.xml
 ├── party-seed-initial.xml
 ├── product-seed-initial.xml
 ├── shipment-seed-initial.xml
 └── workeffort-seed-initial.xml

Re: Restore common-theme with ofbiz-framework

[Taher Alkhateeb]

Hi Nicolas,

Great stuff, I'm not sure what everyone thinks but I prefer if we can
try to get your work incorporated back into the code base as early as
possible and to start completing the work from there.

On Tue, Jul 18, 2017 at 5:38 PM, Nicolas Malin  wrote:
> Michael,
>
> I finished to restore my work on common-theme from ofbiz to ofbiz-framework
> :
> https://github.com/apache/ofbiz-framework/compare/trunk...nmalin:common-theme?expand=1
>
> Now I will work on the java object to manage the widget theme on user
> session.
>
> Nicolas
>
> --
> logoNrd 
> Nicolas Malin
> The apache way  : *Openness* Technical decisions
> are made publicly
> informat...@nereide.fr
> 8 rue des Déportés 37000 TOURS, 02 47 50 30 54
>
> Apache OFBiz |The Apache Way
> |ofbiz-fr |réseau LE
> 

Restore common-theme with ofbiz-framework

[Nicolas Malin]

Michael,

I finished to restore my work on common-theme from ofbiz to 
ofbiz-framework : 
https://github.com/apache/ofbiz-framework/compare/trunk...nmalin:common-theme?expand=1


Now I will work on the java object to manage the widget theme on user 
session.


Nicolas

--
logoNrd 
Nicolas Malin
The apache way  : *Openness* Technical 
decisions are made publicly

informat...@nereide.fr
8 rue des Déportés 37000 TOURS, 02 47 50 30 54

Apache OFBiz |The Apache Way 
|ofbiz-fr |réseau LE 

Home Login page

[Ismail Al Kouz]

Hello Dears.

I have the problem when I'm Login to 
"https://127.0.0.1:8443/accounting/control/main"; with user not have a 
'permission' or 'security Group' to "accounting" Component
I Know that not be login to "accounting" , must be go to URL Component you have 
a  permission

How I can solve it or get  URL root for all component and all users

Thanks a lot.

Best Regards,

Re: [Proposal] moving all data in applications to the data-model component

[Ashish Vijaywargiya]

+1

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997 


On Fri, Jul 14, 2017 at 3:29 PM, Taher Alkhateeb  wrote:

>  Hello Everyone,
>
> Data loading in OFBiz is quite fragile. A small change could crash the
> system and finding out the reason can be difficult. I really felt the
> pain of this when trying to disentangle the framework from data
> dependencies on plugins [1].
>
> I've been thinking about a solution to reduce fragility, and here are
> my thoughts:
> - The less data files the better.
> - The less data the better.
> - The less distance (e.g. same directory) between data files the better.
> - No circular dependencies (file dependencies should be like a tree).
> - Fail fast [2].
>
> Therefore, I suggest the following action points:
> - Create a directory structure similar to [3] in the datamodel component.
> - For any data that two or more files depend on, immediately move it
> to the common-.xml file.
> - For any data that does not belong to any domain (e.g. marketing,
> content, etc ..) move it to the common-.xml.
> - Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
> - Gradually and carefully move data from all applications to the
> datamodel component as per above guidelines.
> - Cleanup and refactor the data as we move it including any tests that
> depend on it.
>
> What do you think of this proposal? Does it sound reasonable? Also
> given the size of what I'm proposing I think we need multiple people
> to work on this. So is anyone interested in taking part in this
> initiative?
>
> Cheers,
>
> Taher Alkhateeb
>
> [1] https://issues.apache.org/jira/browse/OFBIZ-9322
> [2] https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb950999e8f
> 8e869a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
> [3] directory structure:
> data/
> ├── demo
> │   ├── accounting-demo.xml
> │   ├── common-demo.xml
> │   ├── content-demo.xml
> │   ├── humanres-demo.xml
> │   ├── manufacturing-demo.xml
> │   ├── marketing-demo.xml
> │   ├── order-demo.xml
> │   ├── party-demo.xml
> │   ├── product-demo.xml
> │   ├── shipment-demo.xml
> │   └── workeffort-demo.xml
> ├── seed
> │   ├── accounting-seed.xml
> │   ├── common-seed.xml
> │   ├── content-seed.xml
> │   ├── humanres-seed.xml
> │   ├── manufacturing-seed.xml
> │   ├── marketing-seed.xml
> │   ├── order-seed.xml
> │   ├── party-seed.xml
> │   ├── product-seed.xml
> │   ├── shipment-seed.xml
> │   └── workeffort-seed.xml
> └── seed-initial
> ├── accounting-seed-initial.xml
> ├── common-seed-initial.xml
> ├── content-seed-initial.xml
> ├── humanres-seed-initial.xml
> ├── manufacturing-seed-initial.xml
> ├── marketing-seed-initial.xml
> ├── order-seed-initial.xml
> ├── party-seed-initial.xml
> ├── product-seed-initial.xml
> ├── shipment-seed-initial.xml
> └── workeffort-seed-initial.xml
>

Re: [Proposal] moving all data in applications to the data-model component

[Aditya Sharma]

+1

Thanks and Regards,
*Aditya Sharma* | Enterprise Software Engineer
HotWax Systems 



On Tue, Jul 18, 2017 at 3:08 PM, Sharan Foga  wrote:

> +1
>
> Thanks
> Sharan
>
>
> On 14/07/17 11:59, Taher Alkhateeb wrote:
>
>>   Hello Everyone,
>>
>> Data loading in OFBiz is quite fragile. A small change could crash the
>> system and finding out the reason can be difficult. I really felt the
>> pain of this when trying to disentangle the framework from data
>> dependencies on plugins [1].
>>
>> I've been thinking about a solution to reduce fragility, and here are
>> my thoughts:
>> - The less data files the better.
>> - The less data the better.
>> - The less distance (e.g. same directory) between data files the better.
>> - No circular dependencies (file dependencies should be like a tree).
>> - Fail fast [2].
>>
>> Therefore, I suggest the following action points:
>> - Create a directory structure similar to [3] in the datamodel component.
>> - For any data that two or more files depend on, immediately move it
>> to the common-.xml file.
>> - For any data that does not belong to any domain (e.g. marketing,
>> content, etc ..) move it to the common-.xml.
>> - Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
>> - Gradually and carefully move data from all applications to the
>> datamodel component as per above guidelines.
>> - Cleanup and refactor the data as we move it including any tests that
>> depend on it.
>>
>> What do you think of this proposal? Does it sound reasonable? Also
>> given the size of what I'm proposing I think we need multiple people
>> to work on this. So is anyone interested in taking part in this
>> initiative?
>>
>> Cheers,
>>
>> Taher Alkhateeb
>>
>> [1] https://issues.apache.org/jira/browse/OFBIZ-9322
>> [2] https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb95
>> 0999e8f8e869a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
>> [3] directory structure:
>> data/
>> ├── demo
>> │   ├── accounting-demo.xml
>> │   ├── common-demo.xml
>> │   ├── content-demo.xml
>> │   ├── humanres-demo.xml
>> │   ├── manufacturing-demo.xml
>> │   ├── marketing-demo.xml
>> │   ├── order-demo.xml
>> │   ├── party-demo.xml
>> │   ├── product-demo.xml
>> │   ├── shipment-demo.xml
>> │   └── workeffort-demo.xml
>> ├── seed
>> │   ├── accounting-seed.xml
>> │   ├── common-seed.xml
>> │   ├── content-seed.xml
>> │   ├── humanres-seed.xml
>> │   ├── manufacturing-seed.xml
>> │   ├── marketing-seed.xml
>> │   ├── order-seed.xml
>> │   ├── party-seed.xml
>> │   ├── product-seed.xml
>> │   ├── shipment-seed.xml
>> │   └── workeffort-seed.xml
>> └── seed-initial
>>  ├── accounting-seed-initial.xml
>>  ├── common-seed-initial.xml
>>  ├── content-seed-initial.xml
>>  ├── humanres-seed-initial.xml
>>  ├── manufacturing-seed-initial.xml
>>  ├── marketing-seed-initial.xml
>>  ├── order-seed-initial.xml
>>  ├── party-seed-initial.xml
>>  ├── product-seed-initial.xml
>>  ├── shipment-seed-initial.xml
>>  └── workeffort-seed-initial.xml
>>
>
>

Re: [Proposal] moving all data in applications to the data-model component

[Sharan Foga]

+1

Thanks
Sharan

On 14/07/17 11:59, Taher Alkhateeb wrote:

  Hello Everyone,

Data loading in OFBiz is quite fragile. A small change could crash the
system and finding out the reason can be difficult. I really felt the
pain of this when trying to disentangle the framework from data
dependencies on plugins [1].

I've been thinking about a solution to reduce fragility, and here are
my thoughts:
- The less data files the better.
- The less data the better.
- The less distance (e.g. same directory) between data files the better.
- No circular dependencies (file dependencies should be like a tree).
- Fail fast [2].

Therefore, I suggest the following action points:
- Create a directory structure similar to [3] in the datamodel component.
- For any data that two or more files depend on, immediately move it
to the common-.xml file.
- For any data that does not belong to any domain (e.g. marketing,
content, etc ..) move it to the common-.xml.
- Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
- Gradually and carefully move data from all applications to the
datamodel component as per above guidelines.
- Cleanup and refactor the data as we move it including any tests that
depend on it.

What do you think of this proposal? Does it sound reasonable? Also
given the size of what I'm proposing I think we need multiple people
to work on this. So is anyone interested in taking part in this
initiative?

Cheers,

Taher Alkhateeb

[1] https://issues.apache.org/jira/browse/OFBIZ-9322
[2] 
https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb950999e8f8e869a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
[3] directory structure:
data/
├── demo
│   ├── accounting-demo.xml
│   ├── common-demo.xml
│   ├── content-demo.xml
│   ├── humanres-demo.xml
│   ├── manufacturing-demo.xml
│   ├── marketing-demo.xml
│   ├── order-demo.xml
│   ├── party-demo.xml
│   ├── product-demo.xml
│   ├── shipment-demo.xml
│   └── workeffort-demo.xml
├── seed
│   ├── accounting-seed.xml
│   ├── common-seed.xml
│   ├── content-seed.xml
│   ├── humanres-seed.xml
│   ├── manufacturing-seed.xml
│   ├── marketing-seed.xml
│   ├── order-seed.xml
│   ├── party-seed.xml
│   ├── product-seed.xml
│   ├── shipment-seed.xml
│   └── workeffort-seed.xml
└── seed-initial
 ├── accounting-seed-initial.xml
 ├── common-seed-initial.xml
 ├── content-seed-initial.xml
 ├── humanres-seed-initial.xml
 ├── manufacturing-seed-initial.xml
 ├── marketing-seed-initial.xml
 ├── order-seed-initial.xml
 ├── party-seed-initial.xml
 ├── product-seed-initial.xml
 ├── shipment-seed-initial.xml
 └── workeffort-seed-initial.xml

Re: [Proposal] moving all data in applications to the data-model component

[Devanshu Vyas]

+1

Thanks & Regards,
Devanshu Vyas.

On Fri, Jul 14, 2017 at 3:29 PM, Taher Alkhateeb  wrote:

>  Hello Everyone,
>
> Data loading in OFBiz is quite fragile. A small change could crash the
> system and finding out the reason can be difficult. I really felt the
> pain of this when trying to disentangle the framework from data
> dependencies on plugins [1].
>
> I've been thinking about a solution to reduce fragility, and here are
> my thoughts:
> - The less data files the better.
> - The less data the better.
> - The less distance (e.g. same directory) between data files the better.
> - No circular dependencies (file dependencies should be like a tree).
> - Fail fast [2].
>
> Therefore, I suggest the following action points:
> - Create a directory structure similar to [3] in the datamodel component.
> - For any data that two or more files depend on, immediately move it
> to the common-.xml file.
> - For any data that does not belong to any domain (e.g. marketing,
> content, etc ..) move it to the common-.xml.
> - Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
> - Gradually and carefully move data from all applications to the
> datamodel component as per above guidelines.
> - Cleanup and refactor the data as we move it including any tests that
> depend on it.
>
> What do you think of this proposal? Does it sound reasonable? Also
> given the size of what I'm proposing I think we need multiple people
> to work on this. So is anyone interested in taking part in this
> initiative?
>
> Cheers,
>
> Taher Alkhateeb
>
> [1] https://issues.apache.org/jira/browse/OFBIZ-9322
> [2] https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb950999e8f
> 8e869a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
> [3] directory structure:
> data/
> ├── demo
> │   ├── accounting-demo.xml
> │   ├── common-demo.xml
> │   ├── content-demo.xml
> │   ├── humanres-demo.xml
> │   ├── manufacturing-demo.xml
> │   ├── marketing-demo.xml
> │   ├── order-demo.xml
> │   ├── party-demo.xml
> │   ├── product-demo.xml
> │   ├── shipment-demo.xml
> │   └── workeffort-demo.xml
> ├── seed
> │   ├── accounting-seed.xml
> │   ├── common-seed.xml
> │   ├── content-seed.xml
> │   ├── humanres-seed.xml
> │   ├── manufacturing-seed.xml
> │   ├── marketing-seed.xml
> │   ├── order-seed.xml
> │   ├── party-seed.xml
> │   ├── product-seed.xml
> │   ├── shipment-seed.xml
> │   └── workeffort-seed.xml
> └── seed-initial
> ├── accounting-seed-initial.xml
> ├── common-seed-initial.xml
> ├── content-seed-initial.xml
> ├── humanres-seed-initial.xml
> ├── manufacturing-seed-initial.xml
> ├── marketing-seed-initial.xml
> ├── order-seed-initial.xml
> ├── party-seed-initial.xml
> ├── product-seed-initial.xml
> ├── shipment-seed-initial.xml
> └── workeffort-seed-initial.xml
>

Re: [Proposal] moving all data in applications to the data-model component

[Deepak Dixit]

+1 ,

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Tue, Jul 18, 2017 at 2:29 PM, Sakke Ferraris  wrote:

> Hi,
>
> I just joined, and I'd like to help on this.
>
> BR, Sakke Ferraris
>
> -Ursprungligt meddelande-
> Från: James Yong [mailto:jamesy...@apache.org]
> Skickat: den 18 juli 2017 10:45
> Till: dev@ofbiz.apache.org
> Ämne: Re: [Proposal] moving all data in applications to the data-model
> component
>
> +1
>
> Regards,
> James Yong
>
> On 2017-07-14 17:59 (+0800), Taher Alkhateeb 
> wrote:
> >  Hello Everyone,
> >
> > Data loading in OFBiz is quite fragile. A small change could crash the
> > system and finding out the reason can be difficult. I really felt the
> > pain of this when trying to disentangle the framework from data
> > dependencies on plugins [1].
> >
> > I've been thinking about a solution to reduce fragility, and here are
> > my thoughts:
> > - The less data files the better.
> > - The less data the better.
> > - The less distance (e.g. same directory) between data files the better.
> > - No circular dependencies (file dependencies should be like a tree).
> > - Fail fast [2].
> >
> > Therefore, I suggest the following action points:
> > - Create a directory structure similar to [3] in the datamodel component.
> > - For any data that two or more files depend on, immediately move it
> > to the common-.xml file.
> > - For any data that does not belong to any domain (e.g. marketing,
> > content, etc ..) move it to the common-.xml.
> > - Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
> > - Gradually and carefully move data from all applications to the
> > datamodel component as per above guidelines.
> > - Cleanup and refactor the data as we move it including any tests that
> > depend on it.
> >
> > What do you think of this proposal? Does it sound reasonable? Also
> > given the size of what I'm proposing I think we need multiple people
> > to work on this. So is anyone interested in taking part in this
> > initiative?
> >
> > Cheers,
> >
> > Taher Alkhateeb
> >
> > [1] https://issues.apache.org/jira/browse/OFBIZ-9322
> > [2]
> > https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb950999e8f8e8
> > 69a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
> > [3] directory structure:
> > data/
> > ├── demo
> > │   ├── accounting-demo.xml
> > │   ├── common-demo.xml
> > │   ├── content-demo.xml
> > │   ├── humanres-demo.xml
> > │   ├── manufacturing-demo.xml
> > │   ├── marketing-demo.xml
> > │   ├── order-demo.xml
> > │   ├── party-demo.xml
> > │   ├── product-demo.xml
> > │   ├── shipment-demo.xml
> > │   └── workeffort-demo.xml
> > ├── seed
> > │   ├── accounting-seed.xml
> > │   ├── common-seed.xml
> > │   ├── content-seed.xml
> > │   ├── humanres-seed.xml
> > │   ├── manufacturing-seed.xml
> > │   ├── marketing-seed.xml
> > │   ├── order-seed.xml
> > │   ├── party-seed.xml
> > │   ├── product-seed.xml
> > │   ├── shipment-seed.xml
> > │   └── workeffort-seed.xml
> > └── seed-initial
> > ├── accounting-seed-initial.xml
> > ├── common-seed-initial.xml
> > ├── content-seed-initial.xml
> > ├── humanres-seed-initial.xml
> > ├── manufacturing-seed-initial.xml
> > ├── marketing-seed-initial.xml
> > ├── order-seed-initial.xml
> > ├── party-seed-initial.xml
> > ├── product-seed-initial.xml
> > ├── shipment-seed-initial.xml
> > └── workeffort-seed-initial.xml
> >
>

SV: [Proposal] moving all data in applications to the data-model component

[Sakke Ferraris]

Hi,

I just joined, and I'd like to help on this.

BR, Sakke Ferraris

-Ursprungligt meddelande-
Från: James Yong [mailto:jamesy...@apache.org] 
Skickat: den 18 juli 2017 10:45
Till: dev@ofbiz.apache.org
Ämne: Re: [Proposal] moving all data in applications to the data-model component

+1

Regards,
James Yong

On 2017-07-14 17:59 (+0800), Taher Alkhateeb  
wrote: 
>  Hello Everyone,
> 
> Data loading in OFBiz is quite fragile. A small change could crash the 
> system and finding out the reason can be difficult. I really felt the 
> pain of this when trying to disentangle the framework from data 
> dependencies on plugins [1].
> 
> I've been thinking about a solution to reduce fragility, and here are 
> my thoughts:
> - The less data files the better.
> - The less data the better.
> - The less distance (e.g. same directory) between data files the better.
> - No circular dependencies (file dependencies should be like a tree).
> - Fail fast [2].
> 
> Therefore, I suggest the following action points:
> - Create a directory structure similar to [3] in the datamodel component.
> - For any data that two or more files depend on, immediately move it 
> to the common-.xml file.
> - For any data that does not belong to any domain (e.g. marketing, 
> content, etc ..) move it to the common-.xml.
> - Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
> - Gradually and carefully move data from all applications to the 
> datamodel component as per above guidelines.
> - Cleanup and refactor the data as we move it including any tests that 
> depend on it.
> 
> What do you think of this proposal? Does it sound reasonable? Also 
> given the size of what I'm proposing I think we need multiple people 
> to work on this. So is anyone interested in taking part in this 
> initiative?
> 
> Cheers,
> 
> Taher Alkhateeb
> 
> [1] https://issues.apache.org/jira/browse/OFBIZ-9322
> [2] 
> https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb950999e8f8e8
> 69a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
> [3] directory structure:
> data/
> ├── demo
> │   ├── accounting-demo.xml
> │   ├── common-demo.xml
> │   ├── content-demo.xml
> │   ├── humanres-demo.xml
> │   ├── manufacturing-demo.xml
> │   ├── marketing-demo.xml
> │   ├── order-demo.xml
> │   ├── party-demo.xml
> │   ├── product-demo.xml
> │   ├── shipment-demo.xml
> │   └── workeffort-demo.xml
> ├── seed
> │   ├── accounting-seed.xml
> │   ├── common-seed.xml
> │   ├── content-seed.xml
> │   ├── humanres-seed.xml
> │   ├── manufacturing-seed.xml
> │   ├── marketing-seed.xml
> │   ├── order-seed.xml
> │   ├── party-seed.xml
> │   ├── product-seed.xml
> │   ├── shipment-seed.xml
> │   └── workeffort-seed.xml
> └── seed-initial
> ├── accounting-seed-initial.xml
> ├── common-seed-initial.xml
> ├── content-seed-initial.xml
> ├── humanres-seed-initial.xml
> ├── manufacturing-seed-initial.xml
> ├── marketing-seed-initial.xml
> ├── order-seed-initial.xml
> ├── party-seed-initial.xml
> ├── product-seed-initial.xml
> ├── shipment-seed-initial.xml
> └── workeffort-seed-initial.xml
> 

Re: [Proposal] moving all data in applications to the data-model component

[James Yong]

+1

Regards,
James Yong

On 2017-07-14 17:59 (+0800), Taher Alkhateeb  
wrote: 
>  Hello Everyone,
> 
> Data loading in OFBiz is quite fragile. A small change could crash the
> system and finding out the reason can be difficult. I really felt the
> pain of this when trying to disentangle the framework from data
> dependencies on plugins [1].
> 
> I've been thinking about a solution to reduce fragility, and here are
> my thoughts:
> - The less data files the better.
> - The less data the better.
> - The less distance (e.g. same directory) between data files the better.
> - No circular dependencies (file dependencies should be like a tree).
> - Fail fast [2].
> 
> Therefore, I suggest the following action points:
> - Create a directory structure similar to [3] in the datamodel component.
> - For any data that two or more files depend on, immediately move it
> to the common-.xml file.
> - For any data that does not belong to any domain (e.g. marketing,
> content, etc ..) move it to the common-.xml.
> - Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
> - Gradually and carefully move data from all applications to the
> datamodel component as per above guidelines.
> - Cleanup and refactor the data as we move it including any tests that
> depend on it.
> 
> What do you think of this proposal? Does it sound reasonable? Also
> given the size of what I'm proposing I think we need multiple people
> to work on this. So is anyone interested in taking part in this
> initiative?
> 
> Cheers,
> 
> Taher Alkhateeb
> 
> [1] https://issues.apache.org/jira/browse/OFBIZ-9322
> [2] 
> https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb950999e8f8e869a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
> [3] directory structure:
> data/
> ├── demo
> │   ├── accounting-demo.xml
> │   ├── common-demo.xml
> │   ├── content-demo.xml
> │   ├── humanres-demo.xml
> │   ├── manufacturing-demo.xml
> │   ├── marketing-demo.xml
> │   ├── order-demo.xml
> │   ├── party-demo.xml
> │   ├── product-demo.xml
> │   ├── shipment-demo.xml
> │   └── workeffort-demo.xml
> ├── seed
> │   ├── accounting-seed.xml
> │   ├── common-seed.xml
> │   ├── content-seed.xml
> │   ├── humanres-seed.xml
> │   ├── manufacturing-seed.xml
> │   ├── marketing-seed.xml
> │   ├── order-seed.xml
> │   ├── party-seed.xml
> │   ├── product-seed.xml
> │   ├── shipment-seed.xml
> │   └── workeffort-seed.xml
> └── seed-initial
> ├── accounting-seed-initial.xml
> ├── common-seed-initial.xml
> ├── content-seed-initial.xml
> ├── humanres-seed-initial.xml
> ├── manufacturing-seed-initial.xml
> ├── marketing-seed-initial.xml
> ├── order-seed-initial.xml
> ├── party-seed-initial.xml
> ├── product-seed-initial.xml
> ├── shipment-seed-initial.xml
> └── workeffort-seed-initial.xml
> 

Re: [Proposal] moving all data in applications to the data-model component

[Michael Brohl]

+1

Michael

Am 14.07.17 um 11:59 schrieb Taher Alkhateeb:

  Hello Everyone,

Data loading in OFBiz is quite fragile. A small change could crash the
system and finding out the reason can be difficult. I really felt the
pain of this when trying to disentangle the framework from data
dependencies on plugins [1].

I've been thinking about a solution to reduce fragility, and here are
my thoughts:
- The less data files the better.
- The less data the better.
- The less distance (e.g. same directory) between data files the better.
- No circular dependencies (file dependencies should be like a tree).
- Fail fast [2].

Therefore, I suggest the following action points:
- Create a directory structure similar to [3] in the datamodel component.
- For any data that two or more files depend on, immediately move it
to the common-.xml file.
- For any data that does not belong to any domain (e.g. marketing,
content, etc ..) move it to the common-.xml.
- Maintain a strict dependency hierarchy of demo -> seed -> seed-initial.
- Gradually and carefully move data from all applications to the
datamodel component as per above guidelines.
- Cleanup and refactor the data as we move it including any tests that
depend on it.

What do you think of this proposal? Does it sound reasonable? Also
given the size of what I'm proposing I think we need multiple people
to work on this. So is anyone interested in taking part in this
initiative?

Cheers,

Taher Alkhateeb

[1] https://issues.apache.org/jira/browse/OFBIZ-9322
[2] 
https://lists.apache.org/thread.html/a18b5d4086a07ff34a0cb950999e8f8e869a6aa7efa2fc866a75a7b6@%3Cdev.ofbiz.apache.org%3E
[3] directory structure:
data/
├── demo
│   ├── accounting-demo.xml
│   ├── common-demo.xml
│   ├── content-demo.xml
│   ├── humanres-demo.xml
│   ├── manufacturing-demo.xml
│   ├── marketing-demo.xml
│   ├── order-demo.xml
│   ├── party-demo.xml
│   ├── product-demo.xml
│   ├── shipment-demo.xml
│   └── workeffort-demo.xml
├── seed
│   ├── accounting-seed.xml
│   ├── common-seed.xml
│   ├── content-seed.xml
│   ├── humanres-seed.xml
│   ├── manufacturing-seed.xml
│   ├── marketing-seed.xml
│   ├── order-seed.xml
│   ├── party-seed.xml
│   ├── product-seed.xml
│   ├── shipment-seed.xml
│   └── workeffort-seed.xml
└── seed-initial
 ├── accounting-seed-initial.xml
 ├── common-seed-initial.xml
 ├── content-seed-initial.xml
 ├── humanres-seed-initial.xml
 ├── manufacturing-seed-initial.xml
 ├── marketing-seed-initial.xml
 ├── order-seed-initial.xml
 ├── party-seed-initial.xml
 ├── product-seed-initial.xml
 ├── shipment-seed-initial.xml
 └── workeffort-seed-initial.xml




smime.p7s
Description: S/MIME Cryptographic Signature