This content has been marked as final. There is an answer in SO that asserts that it’s possible to define datasources in a standard container-agnostic way, but when I tried to implement that solution I failed. I am trying to move from JBoss 6 to JBoss 7 and am running into a few difficulties. I tried changing the JDBC driver as you recommended, but discovered that it still does not work. By the way, I don’t want to use Windows Authentication for the datasource but I tried also that way, unsuccessfully.
|Date Added:||9 February 2012|
|File Size:||14.7 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The JBoss server is a piece of excrement as attested by the fact that if you decided to comment out a section in the standalone.
Driver … which spells out the class name of the driver, in our case: This will be my next try. See Question with no answers, but issue solved in the comments or extended in chat. Correct Answers – 4 points. Hoping it helps to give you a clear idea of what is happening. ntds
Setup MSSQL datasource on Jboss AS 7 using jTDS | hs2n Blog
Rasmus was correct in his assessment that I had the jar and module. Email Required, but never shown. That will help isolate the issue. By the way, I don’t want to use Windows Authentication for the datasource but I tried also that way, unsuccessfully.
Setup MSSQL datasource on Jboss AS 7 using jTDS
Thank you for your advice. I agree with you that in this case the error is misleading. Apparently the JDBC driver in JBoss has to be installed as a “module” in the server which is unfortunate as it decreases my options in terms of scripting and cannot be captured in source control.
More properly you are using utds driver which work out of the box with your setting since it is jdbc 4 compliant.
It is the module name net. The correct config in your case should be: Go to original post.
Please type your message and try again. Sign up or log in Sign up using Google.
Sign up using Facebook. I finally got back to working on this.
JBoss – SQL Server – Datasource configuration (JTDS) – Stack Overflow
There is an answer in SO that asserts that it’s possible to define datasources in a standard container-agnostic way, but when I tried to implement that solution I failed.
I’m fighting with this problem for several days and I has not been able to solve it. After the above steps, I restarted the server and when I visited the JBoss EAP administrative interface to define a new datasource I saw that the driver was already recognized and available as an option. Thank you all, Luca.