商城項目隨記

時間 2019-12-19

標籤商城項目简体版

原文原文鏈接

1.項目初始化啓動時，報錯 java

[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.zfsoft:shoping-web:0.0.1-SNAPSHOT: Could not find artifact com.zfsoft:shoping-parent:pom:0.0.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 3, column 11
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project com.zfsoft:shoping-web:0.0.1-SNAPSHOT (E:\eclipseWorkspace\shoping-web\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.zfsoft:shoping-web:0.0.1-SNAPSHOT: Could not find artifact com.zfsoft:shoping-parent:pom:0.0.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

解決辦法： web

Non-resolvable parent POM for com.zfsoft:shoping-web:0.0.1-SNAPSHOT: Could not find artifact com.zfsoft:shoping-parent:pom:0.0.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2]

本地倉庫中沒有shoping-parent，右鍵parent---maven installredis

2.運行繼續報錯spring

[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building shoping-web 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for com.zfsoft:shoping-interface:jar:0.0.1-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.524 s
[INFO] Finished at: 2019-07-08T23:45:55+08:00
[INFO] Final Memory: 8M/154M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project shoping-web: Could not resolve dependencies for project com.zfsoft:shoping-web:war:0.0.1-SNAPSHOT: Could not find artifact com.zfsoft:shoping-interface:jar:0.0.1-SNAPSHOT -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

解決：多添加了interface的依賴apache

3.使用maven tomcat7插件運行報錯：The ServletContentInitializer [org.springframework.web.SpringServletContainerInitializer] could not be createdjson

[INFO] --- tomcat7-maven-plugin:2.2:run (default-cli) @ taotao-manager-web ---
[INFO] Running war on http://localhost:8080/
[INFO] Creating Tomcat server configuration at F:\eclipse-workspace-7-24\taotao-manager\taotao-manager-web\target\tomcat
[INFO] create webapp with contextPath: 
八月 11, 2017 4:14:41 下午 org.apache.coyote.AbstractProtocol init
信息: Initializing ProtocolHandler ["http-bio-8080"]
八月 11, 2017 4:14:41 下午 org.apache.catalina.core.StandardService startInternal
信息: Starting service Tomcat
八月 11, 2017 4:14:41 下午 org.apache.catalina.core.StandardEngine startInternal
信息: Starting Servlet Engine: Apache Tomcat/7.0.47
八月 11, 2017 4:14:42 下午 org.apache.catalina.startup.ContextConfig getServletContainerInitializer
嚴重: The ServletContentInitializer [org.springframework.web.SpringServletContainerInitializer] could not be created
java.lang.ClassNotFoundException: org.springframework.web.SpringServletContainerInitializer
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1702)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1547)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.apache.catalina.startup.ContextConfig.getServletContainerInitializer(ContextConfig.java:1668)
at org.apache.catalina.startup.ContextConfig.getServletContainerInitializers(ContextConfig.java:1652)
at org.apache.catalina.startup.ContextConfig.processServletContainerInitializers(ContextConfig.java:1562)

解決：tomcat

jar包不完整，刪除倉庫中的jar包，而後重啓項目，右鍵項目---maven---maven update服務器

4.由於使用soa架構，在service層的web.xml配置完初始化spring容器後，在web層還須要再配一個嗎？不用。restful

通常咱們在父容器applicationcontext這種配置掃描包dao、service，子容器中配置掃描controller/actionsession

即使配置只掃描到shoping，父容器中有controller，可是依舊沒有意義；子容器中也就會有dao、service那他就不會再去父容器中找了，可是事務是在父容器中配的，子容器中使用的service是沒有事務加強的

父子容器他們功能徹底相同，可是DispatcherServlet畢竟是一個表現層框架，使用父容器還能夠和別的框架整合，擴展性更好（好比父容器中再使用Struts2）

4.RestFul

webservice一遍（使用cxf能夠發佈restful服務），本質是http請求（get或者post）。springmvc從路徑中取值：@pathVariable

5.Dubbo只能是java和java之間通訊，和其餘通訊使用其餘兩種方式：webservice（基於soap）、resful形式（http+json）

什麼是Dubbo：服務治理中間件

Cluster：集羣節點

傳統的單一系統能夠佈置1-10個節點。tomcat集羣，session共享，以後配置session廣播。1-10個，再多性能降低

Dubbo架構

註冊中心：

zookeeper（集羣管理工具），能夠管理hodoop集羣等等。可是dubbo中zookeeper是用來作註冊中心的，不用來管理集羣。

固然也可使用redis做爲註冊中心

使用步驟（Linux版）

解壓縮---》目錄下新建data文件夾

切換到conf目錄，將zoo_sample.cfg更名爲zoo.cfg

編輯zzoo.cfg,將dataDir改成剛纔新建的data目錄

回到bin目錄啓動zookeeper

查看是否啓動成功

7，問題：spring明明定義的是4.2可是裏面依賴進來了2.6的jar包

解決：

右鍵exclusion，而後回到pom文件處查看

已經被排除，保存pom文件便可

繼續排除衝突jar包，方法同上

dubbo的配置文件

在service模塊中

在web模塊中

8.問題：406錯誤

若是有時候出現406錯誤，多是沒有吧jackson包加進來

9.問題：測試dubbo的時候，控制檯卡主，看不到錯誤信息，添加log4j.properties後，發現報錯

Opening socket connection to server 10.70.42.99/10.70.42.99:2181. Will not attempt to authenticate using SASL （沒法定位登陸配置)

緣由：服務器端口開放2181或者關閉防火牆，同時阿里雲服務器開放2181端口

10.dubbo配置完成後，啓動項目

11.啓動項目後輸入web層的mapping：http://localhost:8081/item/679532

報錯

[DUBBO] Got unchecked and undeclared exception which called by 192.168.1.109. service: com.shoping.service.ItemService, method: findById, exception: org.apache.ibatis.binding.BindingException: Invalid bound statement (not found): com.shoping.mapper.TbItemMapper.selectByPrimaryKey, dubbo version: 2.5.3, current host: 127.0.0.1
org.apache.ibatis.binding.BindingException: Invalid bound statement (not found): com.shoping.mapper.TbItemMapper.selectByPrimaryKey

找不到對應的實現，可是這個是經過mybatis逆向工程生成的

也就是xml文件就是實現類了，去編譯後的目錄查看

只有dao模塊接口類的class文件，並無xml文件。mapping映射文件未發佈的問題。

配置的做用：吧src/main/java目錄下的xml文件也配置到編譯後的目錄下

重啓manage模塊，並查看編譯後的目錄

從新輸入地址，又報錯

後臺報錯內容

[DUBBO] Fail to encode response: Response [id=6, version=2.0.0, status=20, event=false, error=null, result=RpcResult [result=com.shoping.pojo.TbItem@7d82ecd5, exception=null]], send bad_response info instead, cause: Serialized class com.shoping.pojo.TbItem must implement java.io.Serializable, dubbo version: 2.5.3, current host: 127.0.0.1
java.lang.IllegalStateException: Serialized class com.shoping.pojo.TbItem must implement java.io.Serializable
	at com.alibaba.com.caucho.hessian.io.SerializerFactory.getDefaultSerializer(SerializerFactory.java:261)
	at com.alibaba.com.caucho.hessian.io.SerializerFactory.getSerializer(SerializerFactory.java:233)
	at com.alibaba.com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:406)
	at com.alibaba.dubbo.common.serialize.support.hessian.Hessian2ObjectOutput.writeObject(Hessian2ObjectOutput.java:92)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.encodeResponseData(DubboCodec.java:200)
	at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.encodeResponse(ExchangeCodec.java:276)
	at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.encode(ExchangeCodec.java:77)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCountCodec.encode(DubboCountCodec.java:39)
	at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalEncoder.encode(NettyCodecAdapter.java:81)
	at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:66)
	at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
	at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:292)
	at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.writeRequested(NettyHandler.java:99)
	at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:254)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
	at org.jboss.netty.channel.Channels.write(Channels.java:704)
	at org.jboss.netty.channel.Channels.write(Channels.java:671)
	at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248)
	at com.alibaba.dubbo.remoting.transport.netty.NettyChannel.send(NettyChannel.java:98)
	at com.alibaba.dubbo.remoting.transport.AbstractPeer.send(AbstractPeer.java:51)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:171)
	at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:52)
	at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:82)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)

實體對象沒有序列化，加上序列化接口便可

10.dubbo監控中心

前面已經安裝了zookeeper註冊中心，生產者，消費者，還有個監控中心

把dubbo-admin.war放到tomcat的webapps下面

啓動tomcat，輸入網址：http://47.97.125.139:8080/dubbo-admin

點進去，能夠看到生產者服務的ip和端口號

切換到消費者