[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipselink-users] Virtual Metlhods | questions
- From: Tom Ware <tom.ware@xxxxxxxxxx>
- Date: Tue, 17 Jul 2012 10:55:16 -0400
- Delivered-to: firstname.lastname@example.org
- Organization: Oracle Corporation
- User-agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
Chris is right here. The way indirection works for 1-1 mappings in
EclipseLink, means that EclipseLink needs access to a method that will return
the valueholder itself. With weaving enabled, we weave a special method into
the object for each mapping.
The question here is whether the same method needs to be used to access the
map from Groovy or if you could have an internal method EclipseLink uses to
store the valueholders and a public method that is used to retrieve the values?
On 17/07/2012 10:43 AM, Gaurav Malhotra wrote:
I am trying to implement "Dynamic Fields" i.e. extension to table/entity
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 Map
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 case.
So I think I cannot use any other attribute accessor.