Hi,
I am confused. Here is a snippet from the documentation:
>> A proxy reference is based on the original proxy class concept. The main
difference is that the >>ReferenceDescriptor defines when to use a proxy
class and not the ClassDescriptor.
>>In the following mapping the class ProductGroup is not defined to be a
proxy class in it's >>ClassDescriptor. Only for shown relationship a proxy
of ProductGroup should be used:
Now this is the ObjectReferenceDescriptor.java snippet:
public Class getItemProxyClass() throws PersistenceBrokerException
{
if (m_ProxyOfItems == null)
{
m_ProxyOfItems = getClassDescriptor().getRepository().
getDescriptorFor(m_ClassOfItems).getProxyClass(); <<< proxy
comes from descriptor
}
return m_ProxyOfItems;
}
The code goes to the reference class's class descriptor and tries to get the
proxy class from there, and the only way it can happen is if the proxy IS
defined there. If this is correct, it means that the only way a reference
proxy would work is if the class-descriptor for the corresponding reference
class is defined, contrary to the documentation. It also discards a fairly
important optimization feature because now the user is confined to using
proxies globally across any handling of the main class which will probably
take a substantial hit during the population of collections.
Is there something I am missing in this picture?
--Bill.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
