当前位置:   article > 正文

初次使用IDEA连接sql server并建立Web项目遇到的疑难问题和解决_idea中添加sql server依赖

idea中添加sql server依赖

1.sql server设置和Jar包

若是连接Sql server,对应服务器实例的登录方式必须为SQL Server 和 Windows 身份验证模式并设置sa登录名和密码,若初始为Windows 身份验证模式的,请根据更改服务器身份验证模式 - SQL Server | Microsoft Learn 加入sa登录名和密码。

对应Sql server的jar包在 Download - JDBC Driver for SQL Server | Microsoft Learn

对应的依赖为

  1. <dependency>
  2. <groupId>com.microsoft.sqlserver</groupId>
  3. <artifactId>mssql-jdbc</artifactId>
  4. <version>12.6.0.jre11</version>
  5. </dependency>

2.MAVEN配置错误 —— Unable to import maven project: See logs for details

错误代码log:

  1. at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:576)
  2. at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:163)
  3. at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:110)
  4. at com.google.inject.Guice.createInjector(Guice.java:87)
  5. at com.google.inject.Guice.createInjector(Guice.java:69)
  6. at com.google.inject.Guice.createInjector(Guice.java:59)
  7. at org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:344)
  8. at org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:333)
  9. at org.jetbrains.idea.maven.server.Maven3ServerEmbedderImpl.customizeComponents(Maven3ServerEmbedderImpl.java:561)
  10. at org.jetbrains.idea.maven.server.Maven3ServerEmbedderImpl.customize(Maven3ServerEmbedderImpl.java:532)
  11. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  12. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  13. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  14. at java.lang.reflect.Method.invoke(Method.java:498)
  15. at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:346)
  16. at sun.rmi.transport.Transport$1.run(Transport.java:200)
  17. at sun.rmi.transport.Transport$1.run(Transport.java:197)
  18. at java.security.AccessController.doPrivileged(Native Method)
  19. at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
  20. at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
  21. at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
  22. at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
  23. at java.security.AccessController.doPrivileged(Native Method)
  24. at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
  25. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  26. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  27. at java.lang.Thread.run(Thread.java:745)
  28. at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)
  29. at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253)
  30. at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:162)
  31. at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227)
  32. at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179)
  33. at com.sun.proxy.$Proxy204.customize(Unknown Source)
  34. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  35. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  36. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  37. at java.lang.reflect.Method.invoke(Method.java:498)
  38. at com.intellij.execution.rmi.RemoteUtil.invokeRemote(RemoteUtil.java:179)
  39. at com.intellij.execution.rmi.RemoteUtil.access$300(RemoteUtil.java:39)
  40. at com.intellij.execution.rmi.RemoteUtil$2$1$1.compute(RemoteUtil.java:160)
  41. at com.intellij.openapi.util.ClassLoaderUtil.runWithClassLoader(ClassLoaderUtil.java:66)
  42. at com.intellij.execution.rmi.RemoteUtil.executeWithClassLoader(RemoteUtil.java:231)
  43. at com.intellij.execution.rmi.RemoteUtil$2$1.invoke(RemoteUtil.java:157)
  44. at com.sun.proxy.$Proxy204.customize(Unknown Source)
  45. at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.doCustomize(MavenEmbedderWrapper.java:96)
  46. at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.onWrappeeCreated(MavenEmbedderWrapper.java:49)
  47. at org.jetbrains.idea.maven.server.RemoteObjectWrapper.getOrCreateWrappee(RemoteObjectWrapper.java:42)
  48. at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.doCustomize(MavenEmbedderWrapper.java:96)
  49. at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.lambda$customizeForResolve$1(MavenEmbedderWrapper.java:69)
  50. at org.jetbrains.idea.maven.server.RemoteObjectWrapper.perform(RemoteObjectWrapper.java:76)
  51. at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.customizeForResolve(MavenEmbedderWrapper.java:68)
  52. at org.jetbrains.idea.maven.project.MavenProjectsTree.resolve(MavenProjectsTree.java:1249)
  53. at org.jetbrains.idea.maven.project.MavenProjectsProcessorResolvingTask.perform(MavenProjectsProcessorResolvingTask.java:44)
  54. at org.jetbrains.idea.maven.project.MavenProjectsProcessor.doProcessPendingTasks(MavenProjectsProcessor.java:132)
  55. at org.jetbrains.idea.maven.project.MavenProjectsProcessor.access$000(MavenProjectsProcessor.java:32)
  56. at org.jetbrains.idea.maven.project.MavenProjectsProcessor$2.run(MavenProjectsProcessor.java:107)
  57. at org.jetbrains.idea.maven.utils.MavenUtil.lambda$runInBackground$5(MavenUtil.java:446)
  58. at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:305)
  59. at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
  60. at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  61. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  62. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  63. at java.lang.Thread.run(Thread.java:745)
  64. 2024-04-01 13:10:20,177 [341339760] ERROR - #org.jetbrains.idea.maven - IntelliJ IDEA 2018.1 Build #IU-181.4203.550
  65. 2024-04-01 13:10:20,177 [341339760] ERROR - #org.jetbrains.idea.maven - JDK: 1.8.0_152-release
  66. 2024-04-01 13:10:20,177 [341339760] ERROR - #org.jetbrains.idea.maven - VM: OpenJDK 64-Bit Server VM
  67. 2024-04-01 13:10:20,177 [341339760] ERROR - #org.jetbrains.idea.maven - Vendor: JetBrains s.r.o
  68. 2024-04-01 13:10:20,177 [341339760] ERROR - #org.jetbrains.idea.maven - OS: Windows 10
  69. 2024-04-01 13:10:20,177 [341339760] ERROR - #org.jetbrains.idea.maven - Last Action: Maven.ReimportProject
  70. 2024-04-01 13:10:53,202 [341372785] INFO - ide.actions.ShowFilePathAction -
  71. Exit code 1

错误原因解析:

1、maven配置的本地仓库地址与项目中使用的不一致

2、项目目录内的.idea目录存在不明配置

错误修正:

使用IDEA自带的MAVEN

3.Maven的setting.xml

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
  3. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  4. xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">
  5. <!-- 本地仓库地址-->
  6. <localRepository>D:\jar_dll_tomcat\MavenRepository</localRepository>
  7. <pluginGroups>
  8. <!-- pluginGroup
  9. | Specifies a further group identifier to use for plugin lookup.
  10. <pluginGroup>com.your.plugins</pluginGroup>
  11. -->
  12. </pluginGroups>
  13. <proxies>
  14. <!-- proxy
  15. | Specification for one proxy, to be used in connecting to the network.
  16. |
  17. <proxy>
  18. <id>optional</id>
  19. <active>true</active>
  20. <protocol>http</protocol>
  21. <username>proxyuser</username>
  22. <password>proxypass</password>
  23. <host>proxy.host.net</host>
  24. <port>80</port>
  25. <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
  26. </proxy>
  27. -->
  28. </proxies>
  29. <servers>
  30. </servers>
  31. <mirrors>
  32. <mirror>
  33. <id>alimaven</id>
  34. <mirrorOf>central</mirrorOf>
  35. <name>aliyun maven</name>
  36. <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
  37. </mirror>
  38. </mirrors>
  39. <profiles>
  40. <profile>
  41.   <!-- profile的唯一标识 -->
  42. <id>jdk</id>
  43. <!-- 自动触发profile的条件逻辑 -->
  44. <activation>
  45. <activeByDefault>false</activeByDefault>
  46. <jdk>1.8</jdk>
  47. </activation>
  48. <!-- 扩展属性列表 -->
  49. <properties>
  50. <maven.compiler.source>1.8</maven.compiler.source>
  51. <maven.compiler.target>1.8</maven.compiler.target>
  52. <maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
  53. </properties>
  54. <!-- 远程仓库列表 -->
  55. <repositories />
  56. <!-- 插件仓库列表 -->
  57. <pluginRepositories />
  58. </profile>
  59. </profiles>
  60. <!-- activeProfiles
  61. | List of profiles that are active for all builds.
  62. |
  63. <activeProfiles>
  64. <activeProfile>alwaysActiveProfile</activeProfile>
  65. <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  66. </activeProfiles>
  67. -->
  68. </settings>

3.Maven的ssm改为Spring boot,启动tomact报错

关于【Factory method 'formContentFilter' threw exception】类似类型的错误

1.Spring boot不需要web.xml

解决方案:将web.xml文件删去

2.formContentFilter是springboot的内部包抛出的异常,异常的指向却是一个jackson的包内异常,说明是一个引用错误依赖,跟踪源码发现却是存在依赖冲突

解决方案:使用jackson:2.11.2
1、删除jackson的包,替换其他类json框架。
2、升级jackson的版本,jackson最好使用2.11.0及以上版本

①jackson-databind < 2.9.10.8,存在反序列化远程代码执行漏洞(CVE-2020-35490/CVE-2020-35491),远程攻击者可通过精心构造的恶意载荷利用该漏洞在系统执行任意代码;
②jackson-databind 2.11.0及以上版本与spring-boot版本兼容。

4.layui试图在前台输出数据,报错:Uncaught TypeError: s.parents is not a function 

试图输出的数据不是个合规的变量,换到后台输出,如果换成后台还是不行,就清一下浏览器缓存。

5.关于lodop免费版的打印问题

Lodop(6.111及之后版本)按域名的高级注册号和使用方式(域名为:snailpet.cn,localhost):
在页面装载之后,调用Lodop普通函数之前执行一次如下语句:
LODOP.SET_LICENSES("","EE0887D00FCC7D29375A695F728489A6","C94CEE276DB2187AE6B65D56B3FC2848","");
假如您采用了LodopFuncs.js文件(6.0之后),简单办法是把该语句放到此文件内那个注明“空白位置”的地方。

本注册号语句成功生效之后会有如下表现:
1:打印维护界面不再有“关于”按钮;
2:直接打印时输出结果的左下角不再有试用版字样;
3:导出的Excel文件里也不再有试用版字样;
5:打印设计界面也不再有“关于”按钮;
(更多注册功效参考价格表相关说明)

如果注册号测试无效,可用以下简单步骤排查:
一、在SET_LICENSES语句前后加alert提示语句,例如:
LODOP.SET_LICENSES("","EE0887D00FCC7D29375A695F728489A6","C94CEE276DB2187AE6B65D56B3FC2848","");
alert("SET_LICENSES执行了");
二、执行时若无以上提示,说明未调用到这里,此时重点排查是否调用了getlodop过程;
三、不想使用getlodop时可以把SET_LICENSES放到每个具体打印过程中,例如PRINT_INIT前面;
四、更简单的测试办法是把注册语句放在Lodop样例2里试试;
五、注册后有资格加入QQ的VIP群:144894000 或 205332300 入群时说明域名或Email,也可咨询QQ:932131686
最新版本及其技术手册可从如下地址下载:
http://www.c-lodop.com/download.html
http://www.mtsoftware.cn/download.html

谢谢您的注册,感谢对Lodop的支持!

声明:本文内容由网友自发贡献,不代表【wpsshop博客】立场,版权归原作者所有,本站不承担相应法律责任。如您发现有侵权的内容,请联系我们。转载请注明出处:https://www.wpsshop.cn/w/繁依Fanyi0/article/detail/866039
推荐阅读
相关标签
  

闽ICP备14008679号