This content has been marked as final.
Show 4 replies
-
1. Re: Configurator and MethodJoinpoints replacement
alesj Mar 18, 2008 11:40 AM (in response to alesj)Or I can use the PropertyInfo.getFieldInfo and use this API from JoinpointFactory:
FieldGetJoinpoint getFieldGetJoinpoint(FieldInfo fieldInfo) throws JoinpointException; FieldSetJoinpoint getFieldSetJoinpoint(FieldInfo fieldInfo) throws JoinpointException;
Again ugly, but effective. -
2. Re: Configurator and MethodJoinpoints replacement
adrian.brock Mar 18, 2008 11:56 AM (in response to alesj)No this goes back to the configurator tidyup task you just closed.
These methods are no longer used except by the obsolete "OldConfigureAction".
They should have been removed (and so should the obsolete action). -
3. Re: Configurator and MethodJoinpoints replacement
alesj Mar 18, 2008 12:05 PM (in response to alesj)"adrian@jboss.org" wrote:
No this goes back to the configurator tidyup task you just closed.
These methods are no longer used except by the obsolete "OldConfigureAction".
They should have been removed (and so should the obsolete action).
OK, I'll reopen the task then.
So, what exactly has to go out of Configurator then?
Since I had no idea tidyup involved that part. -
4. Re: Configurator and MethodJoinpoints replacement
adrian.brock Mar 18, 2008 12:10 PM (in response to alesj)"alesj" wrote:
So, what exactly has to go out of Configurator then?
Since I had no idea tidyup involved that part.
The idea was to reduce it to what actually gets used
and to make it more comprehensible (if possible).
Its just a helper class that's been through so many iterations that there's
all sorts of unused cruft in there.
The property stuff has long since changed to a get/set on the Bean/PropertyInfo
but that doesn't mean the Configurator knew this. :-)