OpenAccess and dynamic Persistence Changes / Extensbility?

Thread is closed for posting
2 posts, 0 answers
  1. Jörg B.
    Jörg B. avatar
    8 posts
    Member since:
    Jul 2009

    Posted 25 Apr 2010 Link to this post

    Good morning,

    I am currently evaluating OpenAccess for an internally used product where we will have extensibility built in in regards of certain types. Basically we have 'Projects', and each project can have a list if IProjectElements, and the default implementations will be extended by 'plugins' so that other business units can provide and use their own elements.

    Now from an extensbility point of view this works perfectly fine with MEF, but I am not sure about the (OpenAccess) persistence part. Up until now we are/were using an oodbms system and adding new assemblies 'just worked' because the oodb picked them up and stored the new object graph & instances 'natively', but how do I do that with OpenAccess where I have to specify the mapping sort of upfront. I also don't want to transport the OpenAccess dependency into each single extension so I'll probably introduce my own 'store this class & these and that properties/fields'-attributes, but can I tell OpenAccess during runtime which classes/fields etc have been added and/or what do I have to do to dynamically change/update the persistence layer via OpenAccess? Is there any way to hook into that?

    Just doing a far away 'can do with reasonable amount of efforts'-check here... any experiences/ideas/suggestions?

    Cheers and thanks,
  2. Jordan
    Jordan avatar
    547 posts

    Posted 26 Apr 2010 Link to this post

    Hi Jörg Battermann,

    Thank you for writing.
    The project that you are describing sounds very interesting indeed.

    In order to have a dynamic persistent model you could use the "artificial fields" feature of OpenAccess.
    You can look at the following links for more information:

    However, in order to be able to help you more I will need some more information about your project.
    Do I understand correctly that the different implementations of IProjectElement will have some added fields (other than the ones from the interface) and you want to be able to persist those?
    It will be very helpful if you can share more details about the project elements. What is the default implementation? What will be an example implementation in an add-in? What fields do you want to persist and how?

    Also, in order to be able to persist project element settings from the add-ins without having a reference to OpenAccess you will definitely need some kind of service that will make available this functionality to the add-ins.

    Best wishes,
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Back to Top