my 2 cents:
- Move all classes in org.apache.pivot.wtkx to org.apache.pivot.beans
Does this mean that it moves from pivot-wtk to pivot-core? Good.
- Rename @WTKX to @BXML
Why not use the standard @Resource annotation of JSR-250 (Common
Annotations) which is specifically designed for dependency injection?
Common Annotations are part of Java 6 SE. See
http://en.wikipedia.org/wiki/JSR_250 . Also note that most DI tools
such as Spring already support @Resource.
Alas, the @Resources annotation of JSR-299 name-clashes with Pivot's
Resources class, so that would need to be resolved...
Other than that I don't care about the refactoring. I don't plan to
use the Serializer for anything besides gui instantiation.
Dirk.
Zitat von Greg Brown <[email protected]>:
Any comments on this? cc'ing the user list for additional feedback.
On Apr 19, 2010, at 9:34 AM, Greg Brown wrote:
Hi all,
I'd be very interested in any comments on this new ticket I entered
this morning:
https://issues.apache.org/jira/browse/PIVOT-470
The fact that WTKXSerializer doesn't have any dependencies on WTK
is almost a strong enough argument on its own to move it to
pivot-core. However, I think the concept of using it to support DI
and AOP is very interesting. I'd like to know what others think.
G
