I wanted to create a slight variation on the CallParamRule that passed the
matching element path to a certain parameter position on a method, as
opposed to the current implementation that passes an attribute value.
Unfortunately, I found I couldn't replicate the functionality provided by
CallParamRule without making my new class part of the
org.apache.digester.commons package, because Digester.peekParams() is
package-protected.

Putting my class in org.apache.digester.commons is a workable solution, but
pretty much a hack. Is there a particular reason that the methods around
getting/setting parameters are package-protected?

Thanks,
-Matt


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to