You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Scott Sanders <ss...@nextance.com> on 2002/05/29 07:33:06 UTC
RE: Digester - why is peekParams() package-protected?
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:msmith@dorado.com]
Sent: Tuesday, May 28, 2002 10:39 PM
To: commons-dev@jakarta.apache.org
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:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Digester - why is peekParams() package-protected?
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Wed, 29 May 2002, robert burrell donkin wrote:
> Date: Wed, 29 May 2002 19:36:05 +0100
> From: robert burrell donkin <ro...@mac.com>
> Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> Subject: Re: Digester - why is peekParams() package-protected?
>
> On Wednesday, May 29, 2002, at 06:33 AM, Scott Sanders wrote:
>
> > 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?
>
> it'll be hard to code effective CallParamRule subclasses without making it
> public.
>
> so i'm +1
>
Likewise ... makes sense to me.
> - robert
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Digester - why is peekParams() package-protected?
Posted by robert burrell donkin <ro...@mac.com>.
On Wednesday, May 29, 2002, at 06:33 AM, Scott Sanders wrote:
> 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?
it'll be hard to code effective CallParamRule subclasses without making it
public.
so i'm +1
- robert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>