Re: [Discussion] Creating a unified service-library component

Let me join in here, Nicolas. I'd like to think about this but had not the time yet. Michael Am 13.03.18 um 16:41 schrieb Nicolas Malin: Hello Taher, I will reply to this thread please give me sometime :) Nicolas On 13/03/2018 16:03, Taher Alkhateeb wrote: Thank you all for your kind

Re: [Discussion] Creating a unified service-library component

Hello Taher, I will reply to this thread please give me sometime :) Nicolas On 13/03/2018 16:03, Taher Alkhateeb wrote: Thank you all for your kind feedback. I gathered in here 3 generally positive replies to the proposal. I will create a JIRA for this task for which volunteers are _highly_

Re: [Discussion] Creating a unified service-library component

Thank you all for your kind feedback. I gathered in here 3 generally positive replies to the proposal. I will create a JIRA for this task for which volunteers are _highly_ appreciated. Thank you Rishi also for stepping in. I do not fancy lazy consensus in important design decisions, so some

Re: [Discussion] Creating a unified service-library component

Yes possibly folders, and more likely just file names. For example: service-library/ ├── ofbiz-component.xml └── services ├── accounting-services.xml ├── content-services.xml ├── humanres-services.xml ├── manufacturing-services.xml ├── marketing-services.xml ├──

Re: [Discussion] Creating a unified service-library component

On 7 March 2018 at 16:57, Taher Alkhateeb wrote: > Yeah I am proposing one big component to house all services. The reason is > that it makes no sense in separating them because they are tightly coupled > and depend on each other heavily (because they share the full

Re: [Discussion] Creating a unified service-library component

Hi Paul, Yeah I am proposing one big component to house all services. The reason is that it makes no sense in separating them because they are tightly coupled and depend on each other heavily (because they share the full data model) As I mentioned in my first email, we can perhaps create a new

Re: [Discussion] Creating a unified service-library component

Thanks Taher, I agree with your idea. I agree that most services can and should be decoupled from user interfaces. As you say if a service exists only to support a UI, it can stay with the UI component. Services that only make sense to support AJAX calls would be one example. If most services

Re: [Discussion] Creating a unified service-library component

+1 for the idea for having services at top and then use them whenever required, the only thing comes in my mind (also mentioned by Paul in the thread) what to do with the cross component services. Also once the services moved then how to customize them as per requirements. But we can finalize the

Re: [Discussion] Creating a unified service-library component

Hi Paul, Good points and questions. Inline ... On Mar 5, 2018 2:36 AM, "Paul Foxworthy" wrote: On 5 March 2018 at 00:45, Taher Alkhateeb wrote: > I think If you look at both the "data model" and "services" in OFBiz > you will notice the

Re: [Discussion] Creating a unified service-library component

Hi Taher, I like the idea, Initially we can move all the entity-auto services to service-library, and slowly move other services that can be move to service-library. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Mon, Mar 5, 2018 at 5:05 AM, Paul Foxworthy

Re: [Discussion] Creating a unified service-library component

On 5 March 2018 at 00:45, Taher Alkhateeb wrote: > I think If you look at both the "data model" and "services" in OFBiz > you will notice the following: > > - They are highly coupled and everything is connected to everything > (orders, parties, work efforts,

[Discussion] Creating a unified service-library component

Hello Everyone, I think If you look at both the "data model" and "services" in OFBiz you will notice the following: - They are highly coupled and everything is connected to everything (orders, parties, work efforts, contents, etc ...) - They are independent of the user interface. In fact you can