Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [aspectj-users] Implementation of party and partyroles

Hi again,

I had some off-list response that my question was not clear enough. Let
me try to rephrase it a littl bit.

What I am trying to achieve is that the roles that are being played by
Company instances can be assigned dynamically.
I could declare Employer, Manufacturer, Carrier and Insurer as
interfaces and define an aspect that adds the interface to a particular
class using declare parents construct but then every instance would play
those roles no?
I would like that some instances will play only the Employer and
Manufacturer roles, others will play the Insurer roles and yet another
will play the Carrier role.

I hope this clarifies things.

Regards,

Rudi.

-----Original Message-----
From: Vankeirsbilck, Rudi. (BE - Merelbeke)
[mailto:ruvankeirsbilck@xxxxxx] 
Sent: dinsdag 22 juli 2003 14:37
To: aspectj-users@xxxxxxxxxxx
Subject: [aspectj-users] Implementation of party and partyroles


Hi all,

Consider the party analysis design pattern and link that with the role
analysis design pattern.

You can imagine the abstract class Party with two concrete subclasses:
Person and Company. You can also image the abstract class PartyRole with
two abstract subclasses PersonRole and CompanyRole, both having (as an
example) the following respective concrete subclasses:

PersonRole: Employee, Customer
CompanyRole: Employer, Manufacturer, Carrier, Insurer

So far, I have only seen compile time implementations of aspects, i.e.
the code is weaved into the .class files and every instances has or
doesn't have the aspect code. Is this a limitation of AspectJ or is it
possible to implement the role classes with aspects and assign the
aspects at runtime on an instance basis? How would you do that with
AspectJ?

Many thanks,

Rudi.


-----------------------------------------------------------------------


This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and is
protected by law.  If you are not the intended recipient, you should
delete this message.  Any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly
prohibited.


_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users
- This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and is
protected by law.  - If you are not the intended recipient, you should
delete this message and are hereby notified that any disclosure,
copying, or distribution of this message, or the taking of any action
based on it, is strictly prohibited.


-----------------------------------------------------------------------


This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message.  Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.




Back to the top