Description
From [email protected] on February 06, 2013 10:02:22
If I understand your process, it is quite feasible to create an additional utility class e.g. MultiArgumentConstructorAccess which will be able to execute creation of objects using your approach, but with an explicit constructor.
e.g. MultiConstructorAccess MultiArgumentConstructorAccess.get(Class type, Constructor constructor)
multiConstructorAccess.newInstance(Object... param)
This is needed for applications where effect of calling the default constructor can't be "fixed" after creation by calling of the setters (example: SWT, more exactly my code I am trying to migrate to your approach: https://github.com/milanaleksic/swt-gui-transformer/blob/master/swt-gui-transformer-core/src/main/java/net/milanaleksic/guitransformer/converters/ObjectConverter.java#L319).
SWT blocks the changing of the style to maintain the UI and OS-calls consistency (), so I can't call afterwards the "setStyle(...)" - there is no setter of this kind to call at all across the widget hierarchy. See here for example: http://osdir.com/ml/ide.eclipse.platform.swt.devel/2006-09/msg00026.html
Have you considered migration to github/bitbucket for easier pull request handling, so I can try to do this by myself and then send to you for approval?
Original issue: http://code.google.com/p/reflectasm/issues/detail?id=13