> > >Another options is to move all the shared functionality to helper classes or >components and reuse them in both places. > >Konstantin > > If there is a reason to use this functionality at the transformer layer, I'm not against the idea. I've yet to hear a use case though. The only ones I can think of don't make much sense or are outstandingly bad practice or could be accomplished other ways anyhow. Any thoughts?
-Andy > > >>:) >> >> >>PS SQLTransformer code might be messy. But functionality it >>provides is >>valuable to some (many?) users. >> >>Vadim >> >> >> >>>-Andy >>> >>> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, email: [EMAIL PROTECTED] >> >> >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]