Geez! I can't believe that was it! A simple transposition of sqlserver and
jdbc. I had it correct in the DTP configuration and the properties file, but
not the data source file (or vice-versa, I don't remember now). Thanks, Max.
View the original post :
Seems like my comments only make it through half of the time.
The problem is that the class name of the jdbc driver is wrong (exactly as the
error message actually says).
When I look at the latest sql driver from MS it contains
com.microsoft.sqlserver.jdbc.SQLServerDriver which is the new name
I got your file and I can see that the console configuration refers to a
hibernate.cfg.xml that does not exist.
Is that intentional ? And if it is, any reason why you got that in there and
expect it to be able to load without errors ? :)
View the original post :
That was actually a relatively recent change. I've been playing with different
options trying to get this to work. I did have a hibernate.cfg.xml. It wasn't
clear initially (after deleting the file) how to get rid of the reference in
the console configuration since the field is disabled, but
Double click the console configuration, go to the Common tab and tell it to
save the config into the project in the workspace - then zip that up and ship
it.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4256614#4256614
Reply to the post :
Max, is there any way I could package up and send you my project and console
configuration so you can directly see what I've got and tell me what I'm doing
wrong? Packaging up the project is easy, but I have no idea where the console
configuration is actually stored.
View the original post :
But the error is pretty clear here - the class you are referencing is not be
found.
Either it is not in the build dir (which should be on the classpath), spelled
incorrectly or referenced incorrectly (i.e. inner classes need a $ instead of .
to be referenced)
View the original post :
Yes, the class is clearly missing from the bin folder as one would expect when
seeing compilation errors for the class (The 'Column XXX cannot be resolved'
errors I referred to before). So how do I get rid of those errors? What do I
have configured incorrectly?
View the original post :
Those errors are not compilation errors; its Dali not being able to find the
matching column/tables.
They do not prevent generation of the .class.
There must be something else wrong beyond Dali/JPA warnings/errors ?
View the original post :
Here's an image of my errors. I don't see any other reason that the classes
wouldn't be generated:
http://screencast.com/t/aJJgvwU7
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4251873#4251873
Reply to the post :
No, I'm not working with DTP at all. I've added the sqljdbc.jar to the
Hibernate Console configuration classpath, the same type of configuration
referenced in the video you pointed me to. I'm guessing there's probably
something fundamentally wrong with my project due to the way I built it.
care to use jing or screenr to record what you are actually doing ? Might get
us there faster than our current comment ping-pong ? :)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4251597#4251597
Reply to the post :
The screencast you sent to me in private email have the same error again and
again on creating the console configuraiton:
Some class/package is missing and that is 99% because the project is not
actually built. It also seems like there is no Entity class on the classpath.
Have you disabled
No, automatic build is turned on. Not to mention, I've tried manually building
several times also with no change. Wrt the missing entity class, I show the
Inner class in the screencast with the @Entity annotation, and I believe that
is the class that can't be found for some reason. This is a
Sounds to me you are still focusing on the classpath for the DTP connection and
not for the configuration Hibernate Tools uses.
Pre-JBoss Tools 3.1.x you need to add the classpath to the console
configuration or the related project.
Have you tried following the movies here:
Okay, added the SQL Server jar to the Hibernate configuration, but still
doesn't work. Now I don't even get the error log entry. But I think I
stumbled onto an earlier indication that there's a classpath issue. In the
Hibernate Configuration view, when I try to expand my configuration entry,
I was sure I answered this issue already, but apparently that got lost somehow.
You need to add the driver to the classpath of the project or console
configuration in releases before JBT 3.1.x.
After that (current nightly buiilds) we add the DTP connection classpath to the
classpath
What database are you running against ?
Are the database actually online/connected ?
Anything in the Error Log View ?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4249640#4249640
Reply to the post :
As I indicated in my initial question, I'm trying to generate DDL for SQL
Server. The database is online and accessible via the Data Source Explorer,
but not otherwise sure what you mean by connected. I'm just trying to generate
DDL; why would I need to be connected to the database?
Guess I should also mention that the ClassNotFoundException was embedded within
a HibernateConsoleRuntimeException.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4249657#4249657
Reply to the post :
20 matches
Mail list logo
