I was joking, don’t worry - we are open for constructive critic and we are listening.

Roman

Thank you for dropping a line here.

BTW, I apologize for pushing hard on the XAF team.
I’m trying to restrain myself now))

Best regards,
Rinat

1. Thank you for suggestion, but do not worry about this. I’m not using this approach anywhere close to production yet (may be there will be something more flexible and simple). Besides, adding tiny method to the ReflectionDictionary was not hard at all.

If you want to implement this in the XPO sources, then you could simply add some “void RegisterAs{T,I}() where T:I” method, that would ask for the XPClassInfo for T and reregister it as I.

However, it would be nice, if the XPO team could remove self-locks from the Session code. It hurts to see these booby traps around.

2. If you check out the ORM+IoC series, then you would notice that I’m creating objects outside the XPO (even if they are requested by the ObjectLoader) just to have these instances injected with the dependencies by IoC (Session happens to get in there same way as well)

Best regards,
Rinat

You can create a custom dictionary class and override its XPDictionary.CanGetClassInfoByType virtual method to return a persistent class info for a given interface type. In addition, your base persistent object class must provide a constructor with the Session and XPClassInfo parameters, so that XPO can create an instance of it.

If my suggestion doesn’t work for you, please submit your sample project to our Support Center. We’ll look for a solution.

XPDictionary.CanGetClassInfoByType
XPDictionary.QueryClassInfo
XPClassInfo.CreateObjectInstance

I did not check myself - just a note.

Thank you for the comment. Yes, I’ve seen them all.

But, as you can see from this ORM+IOC series, queries ask the XPO (via IoC) not for the specific BO (i.e. Account), but for the IAccount interface behind it, since we are completely decoupling from the implementation.

I could not find any simple solution to make the dictionary recognize the Account when it is being asked for IAccount, so I had to register the ClassInfo manually one more time with the interface.

Did I miss something?

Best regards,
Rinat

There is no need to change XPO source, because XPO already provides methods to help you with your task. Below is the list of classes and their members, at which we advise you to take look.

XPDictionary.QueryClassInfo

ReflectionDictionary.ResolveClassInfoByName
ReflectionDictionary.ResolveClassInfoByType

XPDictionary.CanGetClassInfoByType
XPClassInfo.CreateObjectInstance

XPBaseObject..ctor(Session, XPClassInfo)

Thank you,
Nick
Developer Express Support