[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipselink-users] Virtual Metlhods | questions
- From: Gaurav Malhotra <gaurav.malhotra@xxxxxxxxxx>
- Date: Tue, 17 Jul 2012 10:19:40 -0700 (PDT)
- Delivered-to: email@example.com
It will be fine, if we uses some internal method for value holders. But
please give hint, how different attribute accessor will work as chris
> Hi Gaurav,
> Chris is right here. The way indirection works for 1-1 mappings in
> EclipseLink, means that EclipseLink needs access to a method that will
> the valueholder itself. With weaving enabled, we weave a special method
> the object for each mapping.
> The question here is whether the same method needs to be used to access
> map from Groovy or if you could have an internal method EclipseLink uses
> store the valueholders and a public method that is used to retrieve the
> On 17/07/2012 10:43 AM, Gaurav Malhotra wrote:
>> I am trying to implement "Dynamic Fields" i.e. extension to
>> which could be used in groovy logic as we call it dynamic logic.Dynamic
>> fields can be added dynamically at runtime (deployed cluster application
>> which also uses TLG). Currently in my sample code I use "EntryProcessor"
>> which is trigger the creation of mapping on all the nodes in the cluster.
>> Example, if we add dynamic field - "phoneNumber" to the Eomployee, it
>> should be possible to access it like employee.phoneNumber.number. Hence
>> suit our use case (its simple) and we would not like to weave
>> getPhoneNumber method/attribute etc magically into the entity using asm.
>> Hence VirtualMethods implementation best suits our business usage
>> So I think I cannot use any other attribute accessor.
> eclipselink-users mailing list
View this message in context: http://old.nabble.com/Virtual-Metlhods-%7C-questions-tp34172077p34174961.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.