OFBiz › OFBiz - User

party component dependency on accounting

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

22 messages Options

Chris Snow-3

party component dependency on accounting

In the party component, there is a view dependent on the accounting
component:

<view-entity entity-name="PartyAcctgPrefAndGroup"
package-name="org.ofbiz.party.party"
title="PartyAcctgPreference and PartyGroup Entity">
<member-entity entity-alias="PTYACCPREF"
entity-name="PartyAcctgPreference"/>
<member-entity entity-alias="PTYGROUP" entity-name="PartyGroup"/>
<alias entity-alias="PTYACCPREF" name="partyId"/>
<alias entity-alias="PTYACCPREF" name="baseCurrencyUomId"/>
<alias entity-alias="PTYGROUP" name="groupName"/>
<view-link entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
<key-map field-name="partyId"/>
</view-link>
</view-entity>

Should this view be relocated to the accounting component?

Many thanks in advance...

Rishi Solanki

Re: party component dependency on accounting

+1 for this change, as defining a view entity in xml is static one its not
dynamic creation at run time.

Rishi Solanki
Enterprise Software Developer
HotWax Media Pvt. Ltd.

On Sat, Feb 6, 2010 at 4:16 AM, Christopher Snow <
[hidden email]> wrote:

> In the party component, there is a view dependent on the accounting
> component:
>
> <view-entity entity-name="PartyAcctgPrefAndGroup"
> package-name="org.ofbiz.party.party"
> title="PartyAcctgPreference and PartyGroup Entity">
> <member-entity entity-alias="PTYACCPREF"
> entity-name="PartyAcctgPreference"/>
> <member-entity entity-alias="PTYGROUP" entity-name="PartyGroup"/>
> <alias entity-alias="PTYACCPREF" name="partyId"/>
> <alias entity-alias="PTYACCPREF" name="baseCurrencyUomId"/>
> <alias entity-alias="PTYGROUP" name="groupName"/>
> <view-link entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
> <key-map field-name="partyId"/>
> </view-link>
> </view-entity>
>
> Should this view be relocated to the accounting component?
>
> Many thanks in advance...
>

Jacopo Cappellato-4

Re: party component dependency on accounting

In reply to this post by Chris Snow-3

Hi Christopher,

no, the PartyAcctgPreference entity is defined in the accounting component (it is used to define accounting preferences for a given organization) and so it cannot be moved to the party component.

Kind regards,

Jacopo

On Feb 5, 2010, at 11:46 PM, Christopher Snow wrote:

> In the party component, there is a view dependent on the accounting component:
>
> <view-entity entity-name="PartyAcctgPrefAndGroup"
> package-name="org.ofbiz.party.party"
> title="PartyAcctgPreference and PartyGroup Entity">
> <member-entity entity-alias="PTYACCPREF" entity-name="PartyAcctgPreference"/>
> <member-entity entity-alias="PTYGROUP" entity-name="PartyGroup"/>
> <alias entity-alias="PTYACCPREF" name="partyId"/>
> <alias entity-alias="PTYACCPREF" name="baseCurrencyUomId"/>
> <alias entity-alias="PTYGROUP" name="groupName"/>
> <view-link entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
> <key-map field-name="partyId"/>
> </view-link>
> </view-entity>
>
> Should this view be relocated to the accounting component?
>
> Many thanks in advance...

Adrian Crum-2

Re: party component dependency on accounting

Also keep in mind that interdependency between some components is intentional and sometimes necessary. Think about it - how do you create an invoice without a party?

-Adrian

--- On Sat, 2/6/10, Jacopo Cappellato <[hidden email]> wrote:

> From: Jacopo Cappellato <[hidden email]>
> Subject: Re: party component dependency on accounting
> To: [hidden email]
> Date: Saturday, February 6, 2010, 12:01 AM
> Hi Christopher,
>
> no, the PartyAcctgPreference entity is defined in the
> accounting component (it is used to define accounting
> preferences for a given organization) and so it cannot be
> moved to the party component.
>
> Kind regards,
>
> Jacopo
>
> On Feb 5, 2010, at 11:46 PM, Christopher Snow wrote:
>
> > In the party component, there is a view dependent on
> the accounting component:
> >
> >   <view-entity
> entity-name="PartyAcctgPrefAndGroup"
> >
>    package-name="org.ofbiz.party.party"
> >
>    title="PartyAcctgPreference and PartyGroup
> Entity">
> >    <member-entity
> entity-alias="PTYACCPREF"
> entity-name="PartyAcctgPreference"/>
> >    <member-entity
> entity-alias="PTYGROUP" entity-name="PartyGroup"/>
> >    <alias
> entity-alias="PTYACCPREF" name="partyId"/>
> >    <alias
> entity-alias="PTYACCPREF"
> name="baseCurrencyUomId"/>
> >    <alias
> entity-alias="PTYGROUP" name="groupName"/>
> >    <view-link
> entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
> >
>    <key-map field-name="partyId"/>
> >    </view-link>
> >   </view-entity>
> >
> > Should this view be relocated to the accounting
> component?
> >
> > Many thanks in advance...
>
>

Abdullah Shaikh

Re: party component dependency on accounting

I guess we can remove this kind on interdependency too by having services to
communicate with other components instead of using a class of some other
component to directly call a method.

As Adrian said, we can create an invoice without party, but we can have
services using which the account & party component can interact, this way
the components can work independent of each other and can interact with
other component only when required using services.

For example party is dependent on invoice, and to interact with invoice a
class of invoice component is being used, in this case its necessary to have
the invoice component too, and if interaction would have been using
services, the party component would have compiled/run successfully and would
have failed only when services related to invoice are required and for this
the user could add the invoice component.

I don't know if I am missing something, but I feel that the interaction
between components using services would help in eliminating the component
interdependency.

- Abdullah

On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]> wrote:

> Also keep in mind that interdependency between some components is
> intentional and sometimes necessary. Think about it - how do you create an
> invoice without a party?
>
> -Adrian
>
> --- On Sat, 2/6/10, Jacopo Cappellato <[hidden email]>
> wrote:
>
> > From: Jacopo Cappellato <[hidden email]>
> > Subject: Re: party component dependency on accounting
> > To: [hidden email]
> > Date: Saturday, February 6, 2010, 12:01 AM
> > Hi Christopher,
> >
> > no, the PartyAcctgPreference entity is defined in the
> > accounting component (it is used to define accounting
> > preferences for a given organization) and so it cannot be
> > moved to the party component.
> >
> > Kind regards,
> >
> > Jacopo
> >
> > On Feb 5, 2010, at 11:46 PM, Christopher Snow wrote:
> >
> > > In the party component, there is a view dependent on
> > the accounting component:
> > >
> > > <view-entity
> > entity-name="PartyAcctgPrefAndGroup"
> > >
> > package-name="org.ofbiz.party.party"
> > >
> > title="PartyAcctgPreference and PartyGroup
> > Entity">
> > > <member-entity
> > entity-alias="PTYACCPREF"
> > entity-name="PartyAcctgPreference"/>
> > > <member-entity
> > entity-alias="PTYGROUP" entity-name="PartyGroup"/>
> > > <alias
> > entity-alias="PTYACCPREF" name="partyId"/>
> > > <alias
> > entity-alias="PTYACCPREF"
> > name="baseCurrencyUomId"/>
> > > <alias
> > entity-alias="PTYGROUP" name="groupName"/>
> > > <view-link
> > entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
> > >
> > <key-map field-name="partyId"/>
> > > </view-link>
> > > </view-entity>
> > >
> > > Should this view be relocated to the accounting
> > component?
> > >
> > > Many thanks in advance...
> >
> >
>
>
>
>

Adrian Crum-2

Re: party component dependency on accounting

I didn't say that. I asked "How do you create an invoice without a party?" An invoice implies two parties - the party being billed and the party doing the billing.

-Adrian

--- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]> wrote:

> From: Abdullah Shaikh <[hidden email]>
> Subject: Re: party component dependency on accounting
> To: [hidden email]
> Date: Saturday, February 6, 2010, 12:30 AM
> I guess we can remove this kind on
> interdependency too by having services to
> communicate with other components instead of using a class
> of some other
> component to directly call a method.
>
> As Adrian said, we can create an invoice without party, but
> we can have
> services using which the account & party component can
> interact, this way
> the components can work independent of each other and can
> interact with
> other component only when required using services.
>
> For example party is dependent on invoice, and to interact
> with invoice a
> class of invoice component is being used, in this case its
> necessary to have
> the invoice component too, and if interaction would have
> been using
> services, the party component would have compiled/run
> successfully and would
> have failed only when services related to invoice are
> required and for this
> the user could add the invoice component.
>
> I don't know if I am missing something, but I feel that the
> interaction
> between components using services would help in eliminating
> the component
> interdependency.
>
>
> - Abdullah
>
> On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]>
> wrote:
>
> > Also keep in mind that interdependency between some
> components is
> > intentional and sometimes necessary. Think about it -
> how do you create an
> > invoice without a party?
> >
> > -Adrian
> >
> > --- On Sat, 2/6/10, Jacopo Cappellato <[hidden email]>
> > wrote:
> >
> > > From: Jacopo Cappellato <[hidden email]>
> > > Subject: Re: party component dependency on
> accounting
> > > To: [hidden email]
> > > Date: Saturday, February 6, 2010, 12:01 AM
> > > Hi Christopher,
> > >
> > > no, the PartyAcctgPreference entity is defined in
> the
> > > accounting component (it is used to define
> accounting
> > > preferences for a given organization) and so it
> cannot be
> > > moved to the party component.
> > >
> > > Kind regards,
> > >
> > > Jacopo
> > >
> > > On Feb 5, 2010, at 11:46 PM, Christopher Snow
> wrote:
> > >
> > > > In the party component, there is a view
> dependent on
> > > the accounting component:
> > > >
> > > >   <view-entity
> > > entity-name="PartyAcctgPrefAndGroup"
> > > >
> > >
> package-name="org.ofbiz.party.party"
> > > >
> > > title="PartyAcctgPreference and
> PartyGroup
> > > Entity">
> > > >
>    <member-entity
> > > entity-alias="PTYACCPREF"
> > > entity-name="PartyAcctgPreference"/>
> > > >
>    <member-entity
> > > entity-alias="PTYGROUP"
> entity-name="PartyGroup"/>
> > > >    <alias
> > > entity-alias="PTYACCPREF"
> name="partyId"/>
> > > >    <alias
> > > entity-alias="PTYACCPREF"
> > > name="baseCurrencyUomId"/>
> > > >    <alias
> > > entity-alias="PTYGROUP"
> name="groupName"/>
> > > >
>    <view-link
> > > entity-alias="PTYACCPREF"
> rel-entity-alias="PTYGROUP">
> > > >
> > > <key-map
> field-name="partyId"/>
> > > >
>    </view-link>
> > > >   </view-entity>
> > > >
> > > > Should this view be relocated to the
> accounting
> > > component?
> > > >
> > > > Many thanks in advance...
> > >
> > >
> >
> >
> >
> >
>

Rishi Solanki

Re: party component dependency on accounting

In reply to this post by Jacopo Cappellato-4

Hi Jacopo,
Chris is asking to move view entity in to accounting which is currently in
the Party component. It is looking fine to me.
Please let me know if I misunderstood something.

Rishi Solanki
Enterprise Software Developer
HotWax Media Pvt. Ltd.

On Sat, Feb 6, 2010 at 1:31 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Hi Christopher,
>
> no, the PartyAcctgPreference entity is defined in the accounting component
> (it is used to define accounting preferences for a given organization) and
> so it cannot be moved to the party component.
>
> Kind regards,
>
> Jacopo
>
> On Feb 5, 2010, at 11:46 PM, Christopher Snow wrote:
>
> > In the party component, there is a view dependent on the accounting
> component:
> >
> > <view-entity entity-name="PartyAcctgPrefAndGroup"
> > package-name="org.ofbiz.party.party"
> > title="PartyAcctgPreference and PartyGroup Entity">
> > <member-entity entity-alias="PTYACCPREF"
> entity-name="PartyAcctgPreference"/>
> > <member-entity entity-alias="PTYGROUP" entity-name="PartyGroup"/>
> > <alias entity-alias="PTYACCPREF" name="partyId"/>
> > <alias entity-alias="PTYACCPREF" name="baseCurrencyUomId"/>
> > <alias entity-alias="PTYGROUP" name="groupName"/>
> > <view-link entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
> > <key-map field-name="partyId"/>
> > </view-link>
> > </view-entity>
> >
> > Should this view be relocated to the accounting component?
> >
> > Many thanks in advance...
>
>

Abdullah Shaikh

Re: party component dependency on accounting

In reply to this post by Adrian Crum-2

oops .. sorry, I meant "we can't create an invoice without party", which is
correct.

I just took your example for explaining further, my view points.

- Abdullah

On Sat, Feb 6, 2010 at 2:06 PM, Adrian Crum <[hidden email]> wrote:

> I didn't say that. I asked "How do you create an invoice without a party?"
> An invoice implies two parties - the party being billed and the party doing
> the billing.
>
> -Adrian
>
> --- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]> wrote:
>
> > From: Abdullah Shaikh <[hidden email]>
> > Subject: Re: party component dependency on accounting
> > To: [hidden email]
> > Date: Saturday, February 6, 2010, 12:30 AM
> > I guess we can remove this kind on
> > interdependency too by having services to
> > communicate with other components instead of using a class
> > of some other
> > component to directly call a method.
> >
> > As Adrian said, we can create an invoice without party, but
> > we can have
> > services using which the account & party component can
> > interact, this way
> > the components can work independent of each other and can
> > interact with
> > other component only when required using services.
> >
> > For example party is dependent on invoice, and to interact
> > with invoice a
> > class of invoice component is being used, in this case its
> > necessary to have
> > the invoice component too, and if interaction would have
> > been using
> > services, the party component would have compiled/run
> > successfully and would
> > have failed only when services related to invoice are
> > required and for this
> > the user could add the invoice component.
> >
> > I don't know if I am missing something, but I feel that the
> > interaction
> > between components using services would help in eliminating
> > the component
> > interdependency.
> >
> >
> > - Abdullah
> >
> > On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]>
> > wrote:
> >
> > > Also keep in mind that interdependency between some
> > components is
> > > intentional and sometimes necessary. Think about it -
> > how do you create an
> > > invoice without a party?
> > >
> > > -Adrian
> > >
> > > --- On Sat, 2/6/10, Jacopo Cappellato <
> [hidden email]>
> > > wrote:
> > >
> > > > From: Jacopo Cappellato <[hidden email]>
> > > > Subject: Re: party component dependency on
> > accounting
> > > > To: [hidden email]
> > > > Date: Saturday, February 6, 2010, 12:01 AM
> > > > Hi Christopher,
> > > >
> > > > no, the PartyAcctgPreference entity is defined in
> > the
> > > > accounting component (it is used to define
> > accounting
> > > > preferences for a given organization) and so it
> > cannot be
> > > > moved to the party component.
> > > >
> > > > Kind regards,
> > > >
> > > > Jacopo
> > > >
> > > > On Feb 5, 2010, at 11:46 PM, Christopher Snow
> > wrote:
> > > >
> > > > > In the party component, there is a view
> > dependent on
> > > > the accounting component:
> > > > >
> > > > > <view-entity
> > > > entity-name="PartyAcctgPrefAndGroup"
> > > > >
> > > >
> > package-name="org.ofbiz.party.party"
> > > > >
> > > > title="PartyAcctgPreference and
> > PartyGroup
> > > > Entity">
> > > > >
> > <member-entity
> > > > entity-alias="PTYACCPREF"
> > > > entity-name="PartyAcctgPreference"/>
> > > > >
> > <member-entity
> > > > entity-alias="PTYGROUP"
> > entity-name="PartyGroup"/>
> > > > > <alias
> > > > entity-alias="PTYACCPREF"
> > name="partyId"/>
> > > > > <alias
> > > > entity-alias="PTYACCPREF"
> > > > name="baseCurrencyUomId"/>
> > > > > <alias
> > > > entity-alias="PTYGROUP"
> > name="groupName"/>
> > > > >
> > <view-link
> > > > entity-alias="PTYACCPREF"
> > rel-entity-alias="PTYGROUP">
> > > > >
> > > > <key-map
> > field-name="partyId"/>
> > > > >
> > </view-link>
> > > > > </view-entity>
> > > > >
> > > > > Should this view be relocated to the
> > accounting
> > > > component?
> > > > >
> > > > > Many thanks in advance...
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
>
>
>
>

Chris Snow-3

Re: party component dependency on accounting

In reply to this post by Adrian Crum-2

Is the invoice dependent on party or partyId?

> I didn't say that. I asked "How do you create an invoice without a party?"
> An invoice implies two parties - the party being billed and the party
> doing the billing.
>
> -Adrian
>
> --- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]> wrote:
>
>> From: Abdullah Shaikh <[hidden email]>
>> Subject: Re: party component dependency on accounting
>> To: [hidden email]
>> Date: Saturday, February 6, 2010, 12:30 AM
>> I guess we can remove this kind on
>> interdependency too by having services to
>> communicate with other components instead of using a class
>> of some other
>> component to directly call a method.
>>
>> As Adrian said, we can create an invoice without party, but
>> we can have
>> services using which the account & party component can
>> interact, this way
>> the components can work independent of each other and can
>> interact with
>> other component only when required using services.
>>
>> For example party is dependent on invoice, and to interact
>> with invoice a
>> class of invoice component is being used, in this case its
>> necessary to have
>> the invoice component too, and if interaction would have
>> been using
>> services, the party component would have compiled/run
>> successfully and would
>> have failed only when services related to invoice are
>> required and for this
>> the user could add the invoice component.
>>
>> I don't know if I am missing something, but I feel that the
>> interaction
>> between components using services would help in eliminating
>> the component
>> interdependency.
>>
>>
>> - Abdullah
>>
>> On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]>
>> wrote:
>>
>> > Also keep in mind that interdependency between some
>> components is
>> > intentional and sometimes necessary. Think about it -
>> how do you create an
>> > invoice without a party?
>> >
>> > -Adrian
>> >
>> > --- On Sat, 2/6/10, Jacopo Cappellato
>> <[hidden email]>
>> > wrote:
>> >
>> > > From: Jacopo Cappellato <[hidden email]>
>> > > Subject: Re: party component dependency on
>> accounting
>> > > To: [hidden email]
>> > > Date: Saturday, February 6, 2010, 12:01 AM
>> > > Hi Christopher,
>> > >
>> > > no, the PartyAcctgPreference entity is defined in
>> the
>> > > accounting component (it is used to define
>> accounting
>> > > preferences for a given organization) and so it
>> cannot be
>> > > moved to the party component.
>> > >
>> > > Kind regards,
>> > >
>> > > Jacopo
>> > >
>> > > On Feb 5, 2010, at 11:46 PM, Christopher Snow
>> wrote:
>> > >
>> > > > In the party component, there is a view
>> dependent on
>> > > the accounting component:
>> > > >
>> > > >   <view-entity
>> > > entity-name="PartyAcctgPrefAndGroup"
>> > > >
>> > >
>> package-name="org.ofbiz.party.party"
>> > > >
>> > > title="PartyAcctgPreference and
>> PartyGroup
>> > > Entity">
>> > > >
>>    <member-entity
>> > > entity-alias="PTYACCPREF"
>> > > entity-name="PartyAcctgPreference"/>
>> > > >
>>    <member-entity
>> > > entity-alias="PTYGROUP"
>> entity-name="PartyGroup"/>
>> > > >    <alias
>> > > entity-alias="PTYACCPREF"
>> name="partyId"/>
>> > > >    <alias
>> > > entity-alias="PTYACCPREF"
>> > > name="baseCurrencyUomId"/>
>> > > >    <alias
>> > > entity-alias="PTYGROUP"
>> name="groupName"/>
>> > > >
>>    <view-link
>> > > entity-alias="PTYACCPREF"
>> rel-entity-alias="PTYGROUP">
>> > > >
>> > > <key-map
>> field-name="partyId"/>
>> > > >
>>    </view-link>
>> > > >   </view-entity>
>> > > >
>> > > > Should this view be relocated to the
>> accounting
>> > > component?
>> > > >
>> > > > Many thanks in advance...
>> > >
>> > >
>> >
>> >
>> >
>> >
>>
>
>
>
>

--
Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP

Tel: 01453 890660
Mob: 07944 880950
Www: www.snowconsulting.co.uk

Adrian Crum-2

Re: party component dependency on accounting

Chris,

It's not rocket science. Think about it. An invoice is dependent upon many things: parties, inventory items, tax authorities, billing agreements, shipping methods, etc..

What are you trying to achieve?

-Adrian

--- On Sat, 2/6/10, Chris Snow <[hidden email]> wrote:

> From: Chris Snow <[hidden email]>
> Subject: Re: party component dependency on accounting
> To: [hidden email]
> Date: Saturday, February 6, 2010, 12:54 AM
> Is the invoice dependent on party or
> partyId?
>
> > I didn't say that. I asked "How do you create an
> invoice without a party?"
> > An invoice implies two parties - the party being
> billed and the party
> > doing the billing.
> >
> > -Adrian
> >
> > --- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]>
> wrote:
> >
> >> From: Abdullah Shaikh <[hidden email]>
> >> Subject: Re: party component dependency on
> accounting
> >> To: [hidden email]
> >> Date: Saturday, February 6, 2010, 12:30 AM
> >> I guess we can remove this kind on
> >> interdependency too by having services to
> >> communicate with other components instead of using
> a class
> >> of some other
> >> component to directly call a method.
> >>
> >> As Adrian said, we can create an invoice without
> party, but
> >> we can have
> >> services using which the account & party
> component can
> >> interact, this way
> >> the components can work independent of each other
> and can
> >> interact with
> >> other component only when required using
> services.
> >>
> >> For example party is dependent on invoice, and to
> interact
> >> with invoice a
> >> class of invoice component is being used, in this
> case its
> >> necessary to have
> >> the invoice component too, and if interaction
> would have
> >> been using
> >> services, the party component would have
> compiled/run
> >> successfully and would
> >> have failed only when services related to invoice
> are
> >> required and for this
> >> the user could add the invoice component.
> >>
> >> I don't know if I am missing something, but I feel
> that the
> >> interaction
> >> between components using services would help in
> eliminating
> >> the component
> >> interdependency.
> >>
> >>
> >> - Abdullah
> >>
> >> On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]>
> >> wrote:
> >>
> >> > Also keep in mind that interdependency
> between some
> >> components is
> >> > intentional and sometimes necessary. Think
> about it -
> >> how do you create an
> >> > invoice without a party?
> >> >
> >> > -Adrian
> >> >
> >> > --- On Sat, 2/6/10, Jacopo Cappellato
> >> <[hidden email]>
> >> > wrote:
> >> >
> >> > > From: Jacopo Cappellato <[hidden email]>
> >> > > Subject: Re: party component dependency
> on
> >> accounting
> >> > > To: [hidden email]
> >> > > Date: Saturday, February 6, 2010, 12:01
> AM
> >> > > Hi Christopher,
> >> > >
> >> > > no, the PartyAcctgPreference entity is
> defined in
> >> the
> >> > > accounting component (it is used to
> define
> >> accounting
> >> > > preferences for a given organization)
> and so it
> >> cannot be
> >> > > moved to the party component.
> >> > >
> >> > > Kind regards,
> >> > >
> >> > > Jacopo
> >> > >
> >> > > On Feb 5, 2010, at 11:46 PM, Christopher
> Snow
> >> wrote:
> >> > >
> >> > > > In the party component, there is a
> view
> >> dependent on
> >> > > the accounting component:
> >> > > >
> >> > > >   <view-entity
> >> > > entity-name="PartyAcctgPrefAndGroup"
> >> > > >
> >> > >
> >> package-name="org.ofbiz.party.party"
> >> > > >
> >> > > title="PartyAcctgPreference and
> >> PartyGroup
> >> > > Entity">
> >> > > >
> >>    <member-entity
> >> > > entity-alias="PTYACCPREF"
> >> > > entity-name="PartyAcctgPreference"/>
> >> > > >
> >>    <member-entity
> >> > > entity-alias="PTYGROUP"
> >> entity-name="PartyGroup"/>
> >> > > >    <alias
> >> > > entity-alias="PTYACCPREF"
> >> name="partyId"/>
> >> > > >    <alias
> >> > > entity-alias="PTYACCPREF"
> >> > > name="baseCurrencyUomId"/>
> >> > > >    <alias
> >> > > entity-alias="PTYGROUP"
> >> name="groupName"/>
> >> > > >
> >>    <view-link
> >> > > entity-alias="PTYACCPREF"
> >> rel-entity-alias="PTYGROUP">
> >> > > >
> >> > > <key-map
> >> field-name="partyId"/>
> >> > > >
> >>    </view-link>
> >> > > >   </view-entity>
> >> > > >
> >> > > > Should this view be relocated to
> the
> >> accounting
> >> > > component?
> >> > > >
> >> > > > Many thanks in advance...
> >> > >
> >> > >
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> >
> >
>
>
> --
> Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP
>
> Tel: 01453 890660
> Mob: 07944 880950
> Www: www.snowconsulting.co.uk
>
>

Chris Snow-3

Re: party component dependency on accounting

Hi Adrian,

If we have the Accounting component dependent on the Party component
just for because we need a partyId, then the components can more easily
be separated. If it is just a partyId, then the Id could come from
another system entirely. (i.e. SOA).

However, if the Accounting component is dependent on Party services,
separation get more tricky.

Am I making any sense?

Cheers,

Chris

Adrian Crum wrote:

> Chris,
>
> It's not rocket science. Think about it. An invoice is dependent upon many things: parties, inventory items, tax authorities, billing agreements, shipping methods, etc..
>
> What are you trying to achieve?
>
> -Adrian
>
>
> --- On Sat, 2/6/10, Chris Snow <[hidden email]> wrote:
>
>
>> From: Chris Snow <[hidden email]>
>> Subject: Re: party component dependency on accounting
>> To: [hidden email]
>> Date: Saturday, February 6, 2010, 12:54 AM
>> Is the invoice dependent on party or
>> partyId?
>>
>>
>>> I didn't say that. I asked "How do you create an
>>>
>> invoice without a party?"
>>
>>> An invoice implies two parties - the party being
>>>
>> billed and the party
>>
>>> doing the billing.
>>>
>>> -Adrian
>>>
>>> --- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]>
>>>
>> wrote:
>>
>>>> From: Abdullah Shaikh <[hidden email]>
>>>> Subject: Re: party component dependency on
>>>>
>> accounting
>>
>>>> To: [hidden email]
>>>> Date: Saturday, February 6, 2010, 12:30 AM
>>>> I guess we can remove this kind on
>>>> interdependency too by having services to
>>>> communicate with other components instead of using
>>>>
>> a class
>>
>>>> of some other
>>>> component to directly call a method.
>>>>
>>>> As Adrian said, we can create an invoice without
>>>>
>> party, but
>>
>>>> we can have
>>>> services using which the account & party
>>>>
>> component can
>>
>>>> interact, this way
>>>> the components can work independent of each other
>>>>
>> and can
>>
>>>> interact with
>>>> other component only when required using
>>>>
>> services.
>>
>>>> For example party is dependent on invoice, and to
>>>>
>> interact
>>
>>>> with invoice a
>>>> class of invoice component is being used, in this
>>>>
>> case its
>>
>>>> necessary to have
>>>> the invoice component too, and if interaction
>>>>
>> would have
>>
>>>> been using
>>>> services, the party component would have
>>>>
>> compiled/run
>>
>>>> successfully and would
>>>> have failed only when services related to invoice
>>>>
>> are
>>
>>>> required and for this
>>>> the user could add the invoice component.
>>>>
>>>> I don't know if I am missing something, but I feel
>>>>
>> that the
>>
>>>> interaction
>>>> between components using services would help in
>>>>
>> eliminating
>>
>>>> the component
>>>> interdependency.
>>>>
>>>>
>>>> - Abdullah
>>>>
>>>> On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]>
>>>> wrote:
>>>>
>>>>
>>>>> Also keep in mind that interdependency
>>>>>
>> between some
>>
>>>> components is
>>>>
>>>>> intentional and sometimes necessary. Think
>>>>>
>> about it -
>>
>>>> how do you create an
>>>>
>>>>> invoice without a party?
>>>>>
>>>>> -Adrian
>>>>>
>>>>> --- On Sat, 2/6/10, Jacopo Cappellato
>>>>>
>>>> <[hidden email]>
>>>>
>>>>> wrote:
>>>>>
>>>>>
>>>>>> From: Jacopo Cappellato <[hidden email]>
>>>>>> Subject: Re: party component dependency
>>>>>>
>> on
>>
>>>> accounting
>>>>
>>>>>> To: [hidden email]
>>>>>> Date: Saturday, February 6, 2010, 12:01
>>>>>>
>> AM
>>
>>>>>> Hi Christopher,
>>>>>>
>>>>>> no, the PartyAcctgPreference entity is
>>>>>>
>> defined in
>>
>>>> the
>>>>
>>>>>> accounting component (it is used to
>>>>>>
>> define
>>
>>>> accounting
>>>>
>>>>>> preferences for a given organization)
>>>>>>
>> and so it
>>
>>>> cannot be
>>>>
>>>>>> moved to the party component.
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>> Jacopo
>>>>>>
>>>>>> On Feb 5, 2010, at 11:46 PM, Christopher
>>>>>>
>> Snow
>>
>>>> wrote:
>>>>
>>>>>>> In the party component, there is a
>>>>>>>
>> view
>>
>>>> dependent on
>>>>
>>>>>> the accounting component:
>>>>>>
>>>>>>> <view-entity
>>>>>>>
>>>>>> entity-name="PartyAcctgPrefAndGroup"
>>>>>>
>>>>>>
>>>>>>
>>>> package-name="org.ofbiz.party.party"
>>>>
>>>>>> title="PartyAcctgPreference and
>>>>>>
>>>> PartyGroup
>>>>
>>>>>> Entity">
>>>>>>
>>>>>>>
>>>>>>>
>>>> <member-entity
>>>>
>>>>>> entity-alias="PTYACCPREF"
>>>>>> entity-name="PartyAcctgPreference"/>
>>>>>>
>>>>>>>
>>>>>>>
>>>> <member-entity
>>>>
>>>>>> entity-alias="PTYGROUP"
>>>>>>
>>>> entity-name="PartyGroup"/>
>>>>
>>>>>>> <alias
>>>>>>>
>>>>>> entity-alias="PTYACCPREF"
>>>>>>
>>>> name="partyId"/>
>>>>
>>>>>>> <alias
>>>>>>>
>>>>>> entity-alias="PTYACCPREF"
>>>>>> name="baseCurrencyUomId"/>
>>>>>>
>>>>>>> <alias
>>>>>>>
>>>>>> entity-alias="PTYGROUP"
>>>>>>
>>>> name="groupName"/>
>>>>
>>>>>>>
>>>>>>>
>>>> <view-link
>>>>
>>>>>> entity-alias="PTYACCPREF"
>>>>>>
>>>> rel-entity-alias="PTYGROUP">
>>>>
>>>>>> <key-map
>>>>>>
>>>> field-name="partyId"/>
>>>>
>>>>>>>
>>>>>>>
>>>> </view-link>
>>>>
>>>>>>> </view-entity>
>>>>>>>
>>>>>>> Should this view be relocated to
>>>>>>>
>> the
>>
>>>> accounting
>>>>
>>>>>> component?
>>>>>>
>>>>>>> Many thanks in advance...
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>> --
>> Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP
>>
>> Tel: 01453 890660
>> Mob: 07944 880950
>> Www: www.snowconsulting.co.uk
>>
>>
>>
>
>
>
>

hans_bakker

Re: party component dependency on accounting

In reply to this post by Chris Snow-3

Chris i agree with you, the party component should not be dependent on
the accounting component.

The accounting component however should be dependent on the party
component. what is a payment without a party?

David made a nice dependency document on that:
http://cwiki.apache.org/confluence/display/OFBADMIN/Component+and
+Component+Set+Dependencies

regards,
Hans

On Fri, 2010-02-05 at 22:46 +0000, Christopher Snow wrote:

--
Antwebsystems.com: Quality OFBiz services for competitive rates

Adrian Crum-2

Re: party component dependency on accounting

In reply to this post by Chris Snow-3

Chris,

Since you didn't answer my question on what you are trying to achieve, I'm going to guess: You are trying to achieve component independence.

That will not happen. Some components are inherently dependent on each other.

-Adrian

--- On Sat, 2/6/10, Christopher Snow <[hidden email]> wrote:

> From: Christopher Snow <[hidden email]>
> Subject: Re: party component dependency on accounting
> To: [hidden email]
> Date: Saturday, February 6, 2010, 1:18 AM
> Hi Adrian,
>
> If we have the Accounting component dependent on the Party
> component just for because we need a partyId, then the
> components can more easily be separated. If it is just
> a partyId, then the Id could come from another system
> entirely. (i.e. SOA).
>
> However, if the Accounting component is dependent on Party
> services, separation get more tricky.
>
> Am I making any sense?
>
> Cheers,
>
> Chris
>
> Adrian Crum wrote:
> > Chris,
> >
> > It's not rocket science. Think about it. An invoice is
> dependent upon many things: parties, inventory items, tax
> authorities, billing agreements, shipping methods, etc..
> >
> > What are you trying to achieve?
> >
> > -Adrian
> >
> >
> > --- On Sat, 2/6/10, Chris Snow <[hidden email]>
> wrote:
> >
> >
> >> From: Chris Snow <[hidden email]>
> >> Subject: Re: party component dependency on
> accounting
> >> To: [hidden email]
> >> Date: Saturday, February 6, 2010, 12:54 AM
> >> Is the invoice dependent on party or
> >> partyId?
> >>
> >>
> >>> I didn't say that. I asked "How do you create
> an
> >>>
> >> invoice without a party?"
> >>
> >>> An invoice implies two parties - the party
> being
> >>>
> >> billed and the party
> >>
> >>> doing the billing.
> >>>
> >>> -Adrian
> >>>
> >>> --- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]>
> >>>
> >> wrote:
> >>
> >>>> From: Abdullah Shaikh <[hidden email]>
> >>>> Subject: Re: party component dependency
> on
> >>>>
> >> accounting
> >>
> >>>> To: [hidden email]
> >>>> Date: Saturday, February 6, 2010, 12:30
> AM
> >>>> I guess we can remove this kind on
> >>>> interdependency too by having services to
> >>>> communicate with other components instead
> of using
> >>>>
> >> a class
> >>
> >>>> of some other
> >>>> component to directly call a method.
> >>>>
> >>>> As Adrian said, we can create an invoice
> without
> >>>>
> >> party, but
> >>
> >>>> we can have
> >>>> services using which the account &
> party
> >>>>
> >> component can
> >>
> >>>> interact, this way
> >>>> the components can work independent of
> each other
> >>>>
> >> and can
> >>
> >>>> interact with
> >>>> other component only when required using
> >>>>
> >> services.
> >>
> >>>> For example party is dependent on invoice,
> and to
> >>>>
> >> interact
> >>
> >>>> with invoice a
> >>>> class of invoice component is being used,
> in this
> >>>>
> >> case its
> >>
> >>>> necessary to have
> >>>> the invoice component too, and if
> interaction
> >>>>
> >> would have
> >>
> >>>> been using
> >>>> services, the party component would have
> >>>>
> >> compiled/run
> >>
> >>>> successfully and would
> >>>> have failed only when services related to
> invoice
> >>>>
> >> are
> >>
> >>>> required and for this
> >>>> the user could add the invoice component.
> >>>>
> >>>> I don't know if I am missing something,
> but I feel
> >>>>
> >> that the
> >>
> >>>> interaction
> >>>> between components using services would
> help in
> >>>>
> >> eliminating
> >>
> >>>> the component
> >>>> interdependency.
> >>>>
> >>>>
> >>>> - Abdullah
> >>>>
> >>>> On Sat, Feb 6, 2010 at 1:45 PM, Adrian
> Crum <[hidden email]>
> >>>> wrote:
> >>>>
> >>>>
> >>>>> Also keep in mind that
> interdependency
> >>>>>
>
> >> between some
> >>
> >>>> components is
> >>>>
> >>>>> intentional and sometimes necessary.
> Think
> >>>>>
>
> >> about it -
> >>
> >>>> how do you create an
> >>>>
> >>>>> invoice without a party?
> >>>>>
> >>>>> -Adrian
> >>>>>
> >>>>> --- On Sat, 2/6/10, Jacopo Cappellato
> >>>>>
>
> >>>> <[hidden email]>
> >>>>
> >>>>> wrote:
> >>>>>
> >>>>>
>
> >>>>>> From: Jacopo Cappellato <[hidden email]>
> >>>>>> Subject: Re: party component
> dependency
> >>>>>>
>
> >> on
> >>
> >>>> accounting
> >>>>
> >>>>>> To: [hidden email]
> >>>>>> Date: Saturday, February 6, 2010,
> 12:01
> >>>>>>
>
> >> AM
> >>
> >>>>>> Hi Christopher,
> >>>>>>
> >>>>>> no, the PartyAcctgPreference
> entity is
> >>>>>>
>
> >> defined in
> >>
> >>>> the
> >>>>
> >>>>>> accounting component (it is used
> to
> >>>>>>
>
> >> define
> >>
> >>>> accounting
> >>>>
> >>>>>> preferences for a given
> organization)
> >>>>>>
>
> >> and so it
> >>
> >>>> cannot be
> >>>>
> >>>>>> moved to the party component.
> >>>>>>
> >>>>>> Kind regards,
> >>>>>>
> >>>>>> Jacopo
> >>>>>>
> >>>>>> On Feb 5, 2010, at 11:46 PM,
> Christopher
> >>>>>>
>
> >> Snow
> >>
> >>>> wrote:
> >>>>
> >>>>>>> In the party component, there
> is a
> >>>>>>>
>
> >> view
> >>
> >>>> dependent on
> >>>>
> >>>>>> the accounting component:
> >>>>>>
>
> >>>>>>> <view-entity
> >>>>>>>
>
> >>>>>>
> entity-name="PartyAcctgPrefAndGroup"
> >>>>>>
>
>
> >>>> package-name="org.ofbiz.party.party"
> >>>>
> >>>>>>
>    title="PartyAcctgPreference and
> >>>>>>
>
> >>>> PartyGroup
> >>>>
> >>>>>> Entity">
> >>>>>>
>
> >>>>>>>
>
> >>>> <member-entity
> >>>>
> >>>>>> entity-alias="PTYACCPREF"
> >>>>>>
> entity-name="PartyAcctgPreference"/>
> >>>>>>
>
> >>>>>>>
>
> >>>> <member-entity
> >>>>
> >>>>>> entity-alias="PTYGROUP"
> >>>>>>
>
> >>>> entity-name="PartyGroup"/>
> >>>>
> >>>>>>>
> <alias
> >>>>>>>
>
> >>>>>> entity-alias="PTYACCPREF"
>
> >>>> name="partyId"/>
> >>>>
> >>>>>>>
> <alias
> >>>>>>>
>
> >>>>>> entity-alias="PTYACCPREF"
> >>>>>> name="baseCurrencyUomId"/>
> >>>>>>
>
> >>>>>>>
> <alias
> >>>>>>>
>
> >>>>>> entity-alias="PTYGROUP"
>
> >>>> name="groupName"/>
> >>>>
> >>>>>>>
>
> >>>> <view-link
> >>>>
> >>>>>> entity-alias="PTYACCPREF"
> >>>>>>
>
> >>>> rel-entity-alias="PTYGROUP">
> >>>>
> >>>>>>
>    <key-map
> >>>>>>
>
> >>>> field-name="partyId"/>
> >>>>
> >>>>>>>
>
> >>>> </view-link>
> >>>>
> >>>>>>>
> </view-entity>
> >>>>>>>
> >>>>>>> Should this view be relocated
> to
> >>>>>>>
>
> >> the
> >>
> >>>> accounting
> >>>>
> >>>>>> component?
> >>>>>>
>
> >>>>>>> Many thanks in advance...
> >>>>>>>
>
> >>>>>>
>
> >>>>>
> >>>>>
> >>>>>
>
> >>>
> >>>
> >>>
> >> -- Chris Snow - CEng MBCS CITP MBA (Tech Mgmt)
> (Open) CISSP
> >>
> >> Tel: 01453 890660
> >> Mob: 07944 880950
> >> Www: www.snowconsulting.co.uk
> >>
> >>
> >>
> >
> >
> >
>
>

Chris Snow-3

Re: party component dependency on accounting

Sorry for not answering your question Adrian, I WAS thinking about
component independence.

The point that I was trying to make was that ultimately, an invoice just
needs a partyId. It shouldn't matter to ofbiz if that partyId comes
from an external party management application.

Adrian Crum wrote:

> Chris,
>
> Since you didn't answer my question on what you are trying to achieve, I'm going to guess: You are trying to achieve component independence.
>
> That will not happen. Some components are inherently dependent on each other.
>
> -Adrian
>
>
> --- On Sat, 2/6/10, Christopher Snow <[hidden email]> wrote:
>
>
>> From: Christopher Snow <[hidden email]>
>> Subject: Re: party component dependency on accounting
>> To: [hidden email]
>> Date: Saturday, February 6, 2010, 1:18 AM
>> Hi Adrian,
>>
>> If we have the Accounting component dependent on the Party
>> component just for because we need a partyId, then the
>> components can more easily be separated. If it is just
>> a partyId, then the Id could come from another system
>> entirely. (i.e. SOA).
>>
>> However, if the Accounting component is dependent on Party
>> services, separation get more tricky.
>>
>> Am I making any sense?
>>
>> Cheers,
>>
>> Chris
>>
>>

Jacopo Cappellato-4

Re: party component dependency on accounting

In reply to this post by Rishi Solanki

I am really sorry Rishi (and Christopher): I completely misunderstood Christopher's initial question and I have caused confusion!
Yes, I agree that we should move the view to the accounting component.

Kind regards,

Jacopo

On Feb 6, 2010, at 9:41 AM, Rishi Solanki wrote:

> Hi Jacopo,
> Chris is asking to move view entity in to accounting which is currently in
> the Party component. It is looking fine to me.
> Please let me know if I misunderstood something.
>
> Rishi Solanki
> Enterprise Software Developer
> HotWax Media Pvt. Ltd.
>
>
> On Sat, Feb 6, 2010 at 1:31 PM, Jacopo Cappellato <
> [hidden email]> wrote:
>
>> Hi Christopher,
>>
>> no, the PartyAcctgPreference entity is defined in the accounting component
>> (it is used to define accounting preferences for a given organization) and
>> so it cannot be moved to the party component.
>>
>> Kind regards,
>>
>> Jacopo
>>
>> On Feb 5, 2010, at 11:46 PM, Christopher Snow wrote:
>>
>>> In the party component, there is a view dependent on the accounting
>> component:
>>>
>>> <view-entity entity-name="PartyAcctgPrefAndGroup"
>>> package-name="org.ofbiz.party.party"
>>> title="PartyAcctgPreference and PartyGroup Entity">
>>> <member-entity entity-alias="PTYACCPREF"
>> entity-name="PartyAcctgPreference"/>
>>> <member-entity entity-alias="PTYGROUP" entity-name="PartyGroup"/>
>>> <alias entity-alias="PTYACCPREF" name="partyId"/>
>>> <alias entity-alias="PTYACCPREF" name="baseCurrencyUomId"/>
>>> <alias entity-alias="PTYGROUP" name="groupName"/>
>>> <view-link entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
>>> <key-map field-name="partyId"/>
>>> </view-link>
>>> </view-entity>
>>>
>>> Should this view be relocated to the accounting component?
>>>
>>> Many thanks in advance...
>>
>>

Rishi Solanki

Re: party component dependency on accounting

No worries Jacopo our ultimate goal is to work in Profit of OFBiz project,
what you understand from Initial question in that case the answer was right.
Learn a lot from each commiter commits and all discussions and conclusion
drawn by you guys. Happy to working in OFBiz with great community.
:-)

Rishi Solanki
Enterprise Software Developer
HotWax Media Pvt. Ltd.

On Sat, Feb 6, 2010 at 3:43 PM, Jacopo Cappellato <
[hidden email]> wrote:

> I am really sorry Rishi (and Christopher): I completely misunderstood
> Christopher's initial question and I have caused confusion!
> Yes, I agree that we should move the view to the accounting component.
>
> Kind regards,
>
> Jacopo
>
> On Feb 6, 2010, at 9:41 AM, Rishi Solanki wrote:
>
> > Hi Jacopo,
> > Chris is asking to move view entity in to accounting which is currently
> in
> > the Party component. It is looking fine to me.
> > Please let me know if I misunderstood something.
> >
> > Rishi Solanki
> > Enterprise Software Developer
> > HotWax Media Pvt. Ltd.
> >
> >
> > On Sat, Feb 6, 2010 at 1:31 PM, Jacopo Cappellato <
> > [hidden email]> wrote:
> >
> >> Hi Christopher,
> >>
> >> no, the PartyAcctgPreference entity is defined in the accounting
> component
> >> (it is used to define accounting preferences for a given organization)
> and
> >> so it cannot be moved to the party component.
> >>
> >> Kind regards,
> >>
> >> Jacopo
> >>
> >> On Feb 5, 2010, at 11:46 PM, Christopher Snow wrote:
> >>
> >>> In the party component, there is a view dependent on the accounting
> >> component:
> >>>
> >>> <view-entity entity-name="PartyAcctgPrefAndGroup"
> >>> package-name="org.ofbiz.party.party"
> >>> title="PartyAcctgPreference and PartyGroup Entity">
> >>> <member-entity entity-alias="PTYACCPREF"
> >> entity-name="PartyAcctgPreference"/>
> >>> <member-entity entity-alias="PTYGROUP" entity-name="PartyGroup"/>
> >>> <alias entity-alias="PTYACCPREF" name="partyId"/>
> >>> <alias entity-alias="PTYACCPREF" name="baseCurrencyUomId"/>
> >>> <alias entity-alias="PTYGROUP" name="groupName"/>
> >>> <view-link entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
> >>> <key-map field-name="partyId"/>
> >>> </view-link>
> >>> </view-entity>
> >>>
> >>> Should this view be relocated to the accounting component?
> >>>
> >>> Many thanks in advance...
> >>
> >>
>
>

Bruno Busco

Re: party component dependency on accounting

So in general we are not trying to have absolute components
independance from each other.
We need only to define and agree on a components functional
hierarchical dependance and enforce it so that an higher level
component should be removed without any issue.

-Bruno

2010/2/6 Rishi Solanki <[hidden email]>:

> No worries Jacopo our ultimate goal is to work in Profit of OFBiz project,
> what you understand from Initial question in that case the answer was right.
> Learn a lot from each commiter commits and all discussions and conclusion
> drawn by you guys. Happy to working in OFBiz with great community.
> :-)
>
> Rishi Solanki
> Enterprise Software Developer
> HotWax Media Pvt. Ltd.
>
>
> On Sat, Feb 6, 2010 at 3:43 PM, Jacopo Cappellato <
> [hidden email]> wrote:
>
>> I am really sorry Rishi (and Christopher): I completely misunderstood
>> Christopher's initial question and I have caused confusion!
>> Yes, I agree that we should move the view to the accounting component.
>>
>> Kind regards,
>>
>> Jacopo
>>
>> On Feb 6, 2010, at 9:41 AM, Rishi Solanki wrote:
>>
>> > Hi Jacopo,
>> > Chris is asking to move view entity in to accounting which is currently
>> in
>> > the Party component. It is looking fine to me.
>> > Please let me know if I misunderstood something.
>> >
>> > Rishi Solanki
>> > Enterprise Software Developer
>> > HotWax Media Pvt. Ltd.
>> >
>> >
>> > On Sat, Feb 6, 2010 at 1:31 PM, Jacopo Cappellato <
>> > [hidden email]> wrote:
>> >
>> >> Hi Christopher,
>> >>
>> >> no, the PartyAcctgPreference entity is defined in the accounting
>> component
>> >> (it is used to define accounting preferences for a given organization)
>> and
>> >> so it cannot be moved to the party component.
>> >>
>> >> Kind regards,
>> >>
>> >> Jacopo
>> >>
>> >> On Feb 5, 2010, at 11:46 PM, Christopher Snow wrote:
>> >>
>> >>> In the party component, there is a view dependent on the accounting
>> >> component:
>> >>>
>> >>> <view-entity entity-name="PartyAcctgPrefAndGroup"
>> >>> package-name="org.ofbiz.party.party"
>> >>> title="PartyAcctgPreference and PartyGroup Entity">
>> >>> <member-entity entity-alias="PTYACCPREF"
>> >> entity-name="PartyAcctgPreference"/>
>> >>> <member-entity entity-alias="PTYGROUP" entity-name="PartyGroup"/>
>> >>> <alias entity-alias="PTYACCPREF" name="partyId"/>
>> >>> <alias entity-alias="PTYACCPREF" name="baseCurrencyUomId"/>
>> >>> <alias entity-alias="PTYGROUP" name="groupName"/>
>> >>> <view-link entity-alias="PTYACCPREF" rel-entity-alias="PTYGROUP">
>> >>> <key-map field-name="partyId"/>
>> >>> </view-link>
>> >>> </view-entity>
>> >>>
>> >>> Should this view be relocated to the accounting component?
>> >>>
>> >>> Many thanks in advance...
>> >>
>> >>
>>
>>
>

Ruth Hoffman-2

Re: party component dependency on accounting

In reply to this post by Adrian Crum-2

Hello Adrian:
Not necessarily. An "invoice" is a legal document. The use of an invoice
to bill a "party" is a business process. Perhaps you meant to say that
the creation of an invoice implies at least two parties?

Regards,
Ruth

Adrian Crum wrote:

> I didn't say that. I asked "How do you create an invoice without a party?" An invoice implies two parties - the party being billed and the party doing the billing.
>
> -Adrian
>
> --- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]> wrote:
>
>
>> From: Abdullah Shaikh <[hidden email]>
>> Subject: Re: party component dependency on accounting
>> To: [hidden email]
>> Date: Saturday, February 6, 2010, 12:30 AM
>> I guess we can remove this kind on
>> interdependency too by having services to
>> communicate with other components instead of using a class
>> of some other
>> component to directly call a method.
>>
>> As Adrian said, we can create an invoice without party, but
>> we can have
>> services using which the account & party component can
>> interact, this way
>> the components can work independent of each other and can
>> interact with
>> other component only when required using services.
>>
>> For example party is dependent on invoice, and to interact
>> with invoice a
>> class of invoice component is being used, in this case its
>> necessary to have
>> the invoice component too, and if interaction would have
>> been using
>> services, the party component would have compiled/run
>> successfully and would
>> have failed only when services related to invoice are
>> required and for this
>> the user could add the invoice component.
>>
>> I don't know if I am missing something, but I feel that the
>> interaction
>> between components using services would help in eliminating
>> the component
>> interdependency.
>>
>>
>> - Abdullah
>>
>> On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]>
>> wrote:
>>
>>
>>> Also keep in mind that interdependency between some
>>>
>> components is
>>
>>> intentional and sometimes necessary. Think about it -
>>>
>> how do you create an
>>
>>> invoice without a party?
>>>
>>> -Adrian
>>>
>>> --- On Sat, 2/6/10, Jacopo Cappellato <[hidden email]>
>>> wrote:
>>>
>>>
>>>> From: Jacopo Cappellato <[hidden email]>
>>>> Subject: Re: party component dependency on
>>>>
>> accounting
>>
>>>> To: [hidden email]
>>>> Date: Saturday, February 6, 2010, 12:01 AM
>>>> Hi Christopher,
>>>>
>>>> no, the PartyAcctgPreference entity is defined in
>>>>
>> the
>>
>>>> accounting component (it is used to define
>>>>
>> accounting
>>
>>>> preferences for a given organization) and so it
>>>>
>> cannot be
>>
>>>> moved to the party component.
>>>>
>>>> Kind regards,
>>>>
>>>> Jacopo
>>>>
>>>> On Feb 5, 2010, at 11:46 PM, Christopher Snow
>>>>
>> wrote:
>>
>>>>> In the party component, there is a view
>>>>>
>> dependent on
>>
>>>> the accounting component:
>>>>
>>>>> <view-entity
>>>>>
>>>> entity-name="PartyAcctgPrefAndGroup"
>>>>
>>>>
>>>>
>> package-name="org.ofbiz.party.party"
>>
>>>> title="PartyAcctgPreference and
>>>>
>> PartyGroup
>>
>>>> Entity">
>>>>
>>>>>
>>>>>
>> <member-entity
>>
>>>> entity-alias="PTYACCPREF"
>>>> entity-name="PartyAcctgPreference"/>
>>>>
>>>>>
>>>>>
>> <member-entity
>>
>>>> entity-alias="PTYGROUP"
>>>>
>> entity-name="PartyGroup"/>
>>
>>>>> <alias
>>>>>
>>>> entity-alias="PTYACCPREF"
>>>>
>> name="partyId"/>
>>
>>>>> <alias
>>>>>
>>>> entity-alias="PTYACCPREF"
>>>> name="baseCurrencyUomId"/>
>>>>
>>>>> <alias
>>>>>
>>>> entity-alias="PTYGROUP"
>>>>
>> name="groupName"/>
>>
>>>>>
>>>>>
>> <view-link
>>
>>>> entity-alias="PTYACCPREF"
>>>>
>> rel-entity-alias="PTYGROUP">
>>
>>>> <key-map
>>>>
>> field-name="partyId"/>
>>
>>>>>
>>>>>
>> </view-link>
>>
>>>>> </view-entity>
>>>>>
>>>>> Should this view be relocated to the
>>>>>
>> accounting
>>
>>>> component?
>>>>
>>>>> Many thanks in advance...
>>>>>
>>>>
>>>
>>>
>>>
>
>
>
>
>

Bruno Busco

Re: party component dependency on accounting

Ruth,
the discussion was about *components dependence* not about a
particular business process.
We are addressing the issue that it seems that right now it is not
possible to remove the accounting component while leaving the party
component into OFBiz.
This should be because the party should be used for things different
from what accounting component is designed for as so an installation
where party is present and not accounting should definitively be
possible.

Please help us stay focused ot the subject. We have already
difficulties to understand each other.

-Bruno

2010/2/6 Ruth Hoffman <[hidden email]>:

> Hello Adrian:
> Not necessarily. An "invoice" is a legal document. The use of an invoice to
> bill a "party" is a business process. Perhaps you meant to say that the
> creation of an invoice implies at least two parties?
>
> Regards,
> Ruth
>
> Adrian Crum wrote:
>>
>> I didn't say that. I asked "How do you create an invoice without a party?"
>> An invoice implies two parties - the party being billed and the party doing
>> the billing.
>>
>> -Adrian
>>
>> --- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]> wrote:
>>
>>
>>>
>>> From: Abdullah Shaikh <[hidden email]>
>>> Subject: Re: party component dependency on accounting
>>> To: [hidden email]
>>> Date: Saturday, February 6, 2010, 12:30 AM
>>> I guess we can remove this kind on
>>> interdependency too by having services to
>>> communicate with other components instead of using a class
>>> of some other
>>> component to directly call a method.
>>>
>>> As Adrian said, we can create an invoice without party, but
>>> we can have
>>> services using which the account & party component can
>>> interact, this way
>>> the components can work independent of each other and can
>>> interact with
>>> other component only when required using services.
>>>
>>> For example party is dependent on invoice, and to interact
>>> with invoice a
>>> class of invoice component is being used, in this case its
>>> necessary to have
>>> the invoice component too, and if interaction would have
>>> been using
>>> services, the party component would have compiled/run
>>> successfully and would
>>> have failed only when services related to invoice are
>>> required and for this
>>> the user could add the invoice component.
>>>
>>> I don't know if I am missing something, but I feel that the
>>> interaction
>>> between components using services would help in eliminating
>>> the component
>>> interdependency.
>>>
>>>
>>> - Abdullah
>>>
>>> On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]>
>>> wrote:
>>>
>>>
>>>>
>>>> Also keep in mind that interdependency between some
>>>>
>>>
>>> components is
>>>
>>>>
>>>> intentional and sometimes necessary. Think about it -
>>>>
>>>
>>> how do you create an
>>>
>>>>
>>>> invoice without a party?
>>>>
>>>> -Adrian
>>>>
>>>> --- On Sat, 2/6/10, Jacopo Cappellato
>>>> <[hidden email]>
>>>> wrote:
>>>>
>>>>
>>>>>
>>>>> From: Jacopo Cappellato <[hidden email]>
>>>>> Subject: Re: party component dependency on
>>>>>
>>>
>>> accounting
>>>
>>>>>
>>>>> To: [hidden email]
>>>>> Date: Saturday, February 6, 2010, 12:01 AM
>>>>> Hi Christopher,
>>>>>
>>>>> no, the PartyAcctgPreference entity is defined in
>>>>>
>>>
>>> the
>>>
>>>>>
>>>>> accounting component (it is used to define
>>>>>
>>>
>>> accounting
>>>
>>>>>
>>>>> preferences for a given organization) and so it
>>>>>
>>>
>>> cannot be
>>>
>>>>>
>>>>> moved to the party component.
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> Jacopo
>>>>>
>>>>> On Feb 5, 2010, at 11:46 PM, Christopher Snow
>>>>>
>>>
>>> wrote:
>>>
>>>>>>
>>>>>> In the party component, there is a view
>>>>>>
>>>
>>> dependent on
>>>
>>>>>
>>>>> the accounting component:
>>>>>
>>>>>>
>>>>>> <view-entity
>>>>>>
>>>>>
>>>>> entity-name="PartyAcctgPrefAndGroup"
>>>>>
>>>
>>> package-name="org.ofbiz.party.party"
>>>
>>>>>
>>>>> title="PartyAcctgPreference and
>>>>>
>>>
>>> PartyGroup
>>>
>>>>>
>>>>> Entity">
>>>>>
>>>>>>
>>>>>>
>>>
>>> <member-entity
>>>
>>>>>
>>>>> entity-alias="PTYACCPREF"
>>>>> entity-name="PartyAcctgPreference"/>
>>>>>
>>>>>>
>>>>>>
>>>
>>> <member-entity
>>>
>>>>>
>>>>> entity-alias="PTYGROUP"
>>>>>
>>>
>>> entity-name="PartyGroup"/>
>>>
>>>>>>
>>>>>> <alias
>>>>>>
>>>>>
>>>>> entity-alias="PTYACCPREF"
>>>
>>> name="partyId"/>
>>>
>>>>>>
>>>>>> <alias
>>>>>>
>>>>>
>>>>> entity-alias="PTYACCPREF"
>>>>> name="baseCurrencyUomId"/>
>>>>>
>>>>>>
>>>>>> <alias
>>>>>>
>>>>>
>>>>> entity-alias="PTYGROUP"
>>>
>>> name="groupName"/>
>>>
>>>>>>
>>>>>>
>>>
>>> <view-link
>>>
>>>>>
>>>>> entity-alias="PTYACCPREF"
>>>>>
>>>
>>> rel-entity-alias="PTYGROUP">
>>>
>>>>>
>>>>> <key-map
>>>>>
>>>
>>> field-name="partyId"/>
>>>
>>>>>>
>>>>>>
>>>
>>> </view-link>
>>>
>>>>>>
>>>>>> </view-entity>
>>>>>>
>>>>>> Should this view be relocated to the
>>>>>>
>>>
>>> accounting
>>>
>>>>>
>>>>> component?
>>>>>
>>>>>>
>>>>>> Many thanks in advance...
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>

Ruth Hoffman-2

Re: party component dependency on accounting

Hi Bruno:

Understood. I was just addressing Adrian's comment. IMO, component
dependency is all about business processes. What else would make one
piece of code dependent upon another? How would you know if there is or
should be a dependency unless you analyzed the process behind the logic?

Regards,
Ruth

Bruno Busco wrote:

> Ruth,
> the discussion was about *components dependence* not about a
> particular business process.
> We are addressing the issue that it seems that right now it is not
> possible to remove the accounting component while leaving the party
> component into OFBiz.
> This should be because the party should be used for things different
> from what accounting component is designed for as so an installation
> where party is present and not accounting should definitively be
> possible.
>
> Please help us stay focused ot the subject. We have already
> difficulties to understand each other.
>
> -Bruno
>
>
> 2010/2/6 Ruth Hoffman <[hidden email]>:
>
>> Hello Adrian:
>> Not necessarily. An "invoice" is a legal document. The use of an invoice to
>> bill a "party" is a business process. Perhaps you meant to say that the
>> creation of an invoice implies at least two parties?
>>
>> Regards,
>> Ruth
>>
>> Adrian Crum wrote:
>>
>>> I didn't say that. I asked "How do you create an invoice without a party?"
>>> An invoice implies two parties - the party being billed and the party doing
>>> the billing.
>>>
>>> -Adrian
>>>
>>> --- On Sat, 2/6/10, Abdullah Shaikh <[hidden email]> wrote:
>>>
>>>
>>>
>>>> From: Abdullah Shaikh <[hidden email]>
>>>> Subject: Re: party component dependency on accounting
>>>> To: [hidden email]
>>>> Date: Saturday, February 6, 2010, 12:30 AM
>>>> I guess we can remove this kind on
>>>> interdependency too by having services to
>>>> communicate with other components instead of using a class
>>>> of some other
>>>> component to directly call a method.
>>>>
>>>> As Adrian said, we can create an invoice without party, but
>>>> we can have
>>>> services using which the account & party component can
>>>> interact, this way
>>>> the components can work independent of each other and can
>>>> interact with
>>>> other component only when required using services.
>>>>
>>>> For example party is dependent on invoice, and to interact
>>>> with invoice a
>>>> class of invoice component is being used, in this case its
>>>> necessary to have
>>>> the invoice component too, and if interaction would have
>>>> been using
>>>> services, the party component would have compiled/run
>>>> successfully and would
>>>> have failed only when services related to invoice are
>>>> required and for this
>>>> the user could add the invoice component.
>>>>
>>>> I don't know if I am missing something, but I feel that the
>>>> interaction
>>>> between components using services would help in eliminating
>>>> the component
>>>> interdependency.
>>>>
>>>>
>>>> - Abdullah
>>>>
>>>> On Sat, Feb 6, 2010 at 1:45 PM, Adrian Crum <[hidden email]>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>> Also keep in mind that interdependency between some
>>>>>
>>>>>
>>>> components is
>>>>
>>>>
>>>>> intentional and sometimes necessary. Think about it -
>>>>>
>>>>>
>>>> how do you create an
>>>>
>>>>
>>>>> invoice without a party?
>>>>>
>>>>> -Adrian
>>>>>
>>>>> --- On Sat, 2/6/10, Jacopo Cappellato
>>>>> <[hidden email]>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> From: Jacopo Cappellato <[hidden email]>
>>>>>> Subject: Re: party component dependency on
>>>>>>
>>>>>>
>>>> accounting
>>>>
>>>>
>>>>>> To: [hidden email]
>>>>>> Date: Saturday, February 6, 2010, 12:01 AM
>>>>>> Hi Christopher,
>>>>>>
>>>>>> no, the PartyAcctgPreference entity is defined in
>>>>>>
>>>>>>
>>>> the
>>>>
>>>>
>>>>>> accounting component (it is used to define
>>>>>>
>>>>>>
>>>> accounting
>>>>
>>>>
>>>>>> preferences for a given organization) and so it
>>>>>>
>>>>>>
>>>> cannot be
>>>>
>>>>
>>>>>> moved to the party component.
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>> Jacopo
>>>>>>
>>>>>> On Feb 5, 2010, at 11:46 PM, Christopher Snow
>>>>>>
>>>>>>
>>>> wrote:
>>>>
>>>>
>>>>>>> In the party component, there is a view
>>>>>>>
>>>>>>>
>>>> dependent on
>>>>
>>>>
>>>>>> the accounting component:
>>>>>>
>>>>>>
>>>>>>> <view-entity
>>>>>>>
>>>>>>>
>>>>>> entity-name="PartyAcctgPrefAndGroup"
>>>>>>
>>>>>>
>>>> package-name="org.ofbiz.party.party"
>>>>
>>>>
>>>>>> title="PartyAcctgPreference and
>>>>>>
>>>>>>
>>>> PartyGroup
>>>>
>>>>
>>>>>> Entity">
>>>>>>
>>>>>>
>>>>>>>
>>>> <member-entity
>>>>
>>>>
>>>>>> entity-alias="PTYACCPREF"
>>>>>> entity-name="PartyAcctgPreference"/>
>>>>>>
>>>>>>
>>>>>>>
>>>> <member-entity
>>>>
>>>>
>>>>>> entity-alias="PTYGROUP"
>>>>>>
>>>>>>
>>>> entity-name="PartyGroup"/>
>>>>
>>>>
>>>>>>> <alias
>>>>>>>
>>>>>>>
>>>>>> entity-alias="PTYACCPREF"
>>>>>>
>>>> name="partyId"/>
>>>>
>>>>
>>>>>>> <alias
>>>>>>>
>>>>>>>
>>>>>> entity-alias="PTYACCPREF"
>>>>>> name="baseCurrencyUomId"/>
>>>>>>
>>>>>>
>>>>>>> <alias
>>>>>>>
>>>>>>>
>>>>>> entity-alias="PTYGROUP"
>>>>>>
>>>> name="groupName"/>
>>>>
>>>>
>>>>>>>
>>>> <view-link
>>>>
>>>>
>>>>>> entity-alias="PTYACCPREF"
>>>>>>
>>>>>>
>>>> rel-entity-alias="PTYGROUP">
>>>>
>>>>
>>>>>> <key-map
>>>>>>
>>>>>>
>>>> field-name="partyId"/>
>>>>
>>>>
>>>>>>>
>>>> </view-link>
>>>>
>>>>
>>>>>>> </view-entity>
>>>>>>>
>>>>>>> Should this view be relocated to the
>>>>>>>
>>>>>>>
>>>> accounting
>>>>
>>>>
>>>>>> component?
>>>>>>
>>>>>>
>>>>>>> Many thanks in advance...
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>
>