Well, you _should_ start as protective as possible, and then open up from there.
Sounds like you have a need for it to be public. I have no objections. Robert? Craig? Scott -----Original Message----- From: Matt Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 10:39 PM To: [EMAIL PROTECTED] Subject: Digester - why is peekParams() package-protected? 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
