It is not a superset of the existing SQLTransformer. We tried to implement as many features of the existing one as possible, but really focused on the features we needed at the time. Also, it would not be backwards compatible, as the XML driving it is different. So, I don't think it could replace it, it would probably make sense to have this be an additional transformer. ..
Sounds good, so it could be an alternate SQLTransformer.
Maybe we'll put it in the scratchpad so as not to confuse users as to which transformer is the "official" one. Later on, it would be good to merge features between the existing SQLTransformer, yours, and the ESQL stuff, as some people have been planning already. So I think it's good to have yours in CVS even if it's not widely used at first.
We have many examples of how to use it, but a lot of them are fairly customer specific. So, I could send some of them to you, but would flag the ones that you cannot share. (Maybe you could just change the table names or something like that) I do have a small project we worked on that I could share the code for that...
The best thing would be if you can create a [PATCH] and post it to bugzilla as described in
http://cocoon.apache.org/2.1/howto/howto-patch.html. You can also add a zipped archive of your additional files instead of an actual CVS patch if it's more convenient, but it's more work for us to integrate.
Please include only stuff that you agree to donate to the project in your patch. It will (eventually) be reviewed by a commiter for inclusion in the CVS.
Thanks! -Bertrand
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
