On Tue, 28 Jan 2003, Baltz, Kenneth wrote:
> Date: Tue, 28 Jan 2003 12:59:20 -0800 > From: "Baltz, Kenneth" <[EMAIL PROTECTED]> > Reply-To: Jakarta Commons Users List <[EMAIL PROTECTED]> > To: Jakarta Commons Users List <[EMAIL PROTECTED]> > Subject: [Digester]Why must ObjectCreateFactories be public? > > Is there a reason that ObjectCreateFactories must be public? It seems to me > that if you call addFactoryCreate( String, Class ), then it shouldn't care > if your class is public. It would be very handy if we could use inner > classes as factories, but the public requirement makes this impossible. > Using ObjectCreateRule, Digester has to be able to dynamically instantiate your factory, so the constructor has to be public. If you use the FactoryCreateRule variant that accepts an ObjectCreationFactory *instance* (instead of the class name of the factory), it should not need to be public. > K.C. > Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
