Closed ewolff closed 10 years ago
I can look into that, but AFAIK the jdbc command is native to CRaSH. Maybe we're doing something to break it. IIRC though, it's uses JNDI to look up a DataSource, so I'm surprised it works at all in a standalone app. Is that what you have?
I am using it in a Spring Boot application with an embedded Tomcat i.e. a standalone JAR. As it uses the JDBC URL to connect to database I don't think it uses a JNDI lookup for a DataSource. However, generally speaking CRaSH seems to rely on a Java EE environment - see my other bug report. So I guess a specific CRaSH version for Spring Boot will be needed... :(
I can take a look at that together with #588. I can work with the guys behind CRaSH to get solved I hope.
Great, thanks. We could remove the jdbc and jpa support in the short term I guess. Or maybe add them only if there is a JNDI registry available (there must be on be in Tomcat?).
After some investigation it looks like our only chance is to disable the commands in our env.
@cdupuis Can you elaborate? Looking at the code of the CRaSH command I don't see why it shouldn't work in Spring Boot - it is just plain JDBC Groovy code.
I am using an embedded HSQL database. Here is what CRaSH does:
I'd expect jdbc table and jdbc tables to give a sensible output - i.e. list the CUSTOMER table that obviously exists...