First off I would like to thank the developers for this project. Very nice!!
I have not completely reviewed the generated code or templates but I have a couple of comments and one question.
I have begun to modify the templates to return XML. I think this would be nice to have.
I am having a problem getting it to work at all with an Informix database but it's OK with MySQL. I am wondering if the wildcard character is causing a problem with the getTables call because no tables are returned. I've passed NULL and had success in other apps with that JDBC driver.
I would like to make the bean constructor public because I want to use these beans in Web Services. I have found serializable is necesary for these complex classes and a public constructor is necessary. Is there a problem with doing so?
TIA,
Carl
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Glad to see the beans are serializable now (I thought I got the latest source from CVS but maybe not). Is the serialVesionUID generated?
We have been using the XML with a couple of Web Services based applications. The changes are still a bit of a hack (I have not had time to refine them) but they suit our needs at the moment.
I just last night noticed the XML generated for loadByWhere() methods with field lists needs to be fixed.
Carl
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First off I would like to thank the developers for this project. Very nice!!
I have not completely reviewed the generated code or templates but I have a couple of comments and one question.
I have begun to modify the templates to return XML. I think this would be nice to have.
I am having a problem getting it to work at all with an Informix database but it's OK with MySQL. I am wondering if the wildcard character is causing a problem with the getTables call because no tables are returned. I've passed NULL and had success in other apps with that JDBC driver.
I would like to make the bean constructor public because I want to use these beans in Web Services. I have found serializable is necesary for these complex classes and a public constructor is necessary. Is there a problem with doing so?
TIA,
Carl
Hi,
the beans in cvs now are all implementing the serialisable interface
see http://cvs.sourceforge.net/viewcvs.py/sql2java/sql2java/src/templates/velocity/java/pertable/bean.java.vm?rev=1.2&view=auto
As per the public constructor, I agree, they should be public: I am integrating this.
I would much appreciate to see the modifications you made to your local templates, as well as the XML addition you integrated ... :)
Enjoy your day,
Florent.
Florent,
Glad to see the beans are serializable now (I thought I got the latest source from CVS but maybe not). Is the serialVesionUID generated?
We have been using the XML with a couple of Web Services based applications. The changes are still a bit of a hack (I have not had time to refine them) but they suit our needs at the moment.
I just last night noticed the XML generated for loadByWhere() methods with field lists needs to be fixed.
Carl
Hi carl,
even with bugs, I would be very interessted in your addition.
maybe i could help you to fix it ? :)
enjoy your day !
Florent.