In regards to the parameter reflection stuff, I can't find anything in 1.6 other than using Introspector.getBeanInfo(Class<?>).getMethodDescriptors() and MethodDescriptor.getParameterDescriptors(). From what I recall, Introspector is rather slow for this sort of situation and is mostly used in GUIs that deal with JavaBeans.
On 2 June 2014 21:20, Matt Sicker <[email protected]> wrote: > On 2 June 2014 21:14, Gary Gregory <[email protected]> wrote: >> >> Well, my point is that you'd just use an annotation. What the annotation >> is, I do not know. I'm not crazy about the category idea in general because >> I am one typo away on a late night from getting stuck. If the code does not >> compile, that's easier to fix. >> > > I agree on that. It's terribly frustrating to deal with runtime problems > that should have been detectable at compile time. Perhaps instead of > categories we had a meta-annotation that describes a plugin category, and > then plugins can use a category annotation instead of the parameter? We > could really use annotations like this to make things more typed with less > typing. > > -- > Matt Sicker <[email protected]> > -- Matt Sicker <[email protected]>
