> > I guess it's time for me to jump into the discussion of
> > sharing tools :-) If I can I would like to share an
> > introspector between struts and velocity. I have a feeling
> > that the structs introspector is more complete so I
> > would be all for using the struts introspector and it
> > can probably be done :-)
> >
>
> It should be feasible to share this. The needs look to be reasonably similar.
>
> I recently refactored this family of classes to have no dependencies on other Struts
> APIs (or even on servlet APIs for that matter). Future enhancement plans include
> support for PropertyEditor classes (to let apps customize the property<-->String
> translations necessary when going to and from an HTML page) and bean properties that
>are
> Collections (treating them sort of like indexed or array-based properties), which
>would
> also benefit both Velocity and Struts.
I think it's totally feasible. The idea of a pluggable introspector
came up on the vel-dev list a couple weeks ago and that's probably
a good idea and if that were done then we could probably share
the introspector that's in struts. Velocity has some non-standard
behavior like picking values out of Maps, but the introspector
proper could probably be shared without much work.
If I could get the struts introspector working in velocity
maybe we could make that the first tool placed in the
org.apache.util package! :-) We'll show them we
can play nice ;-)
jvz.
