简体   繁体   English

是否可以用org.apache.axis2构件替换org.apache.axis2.wso2构件?

[英]Is it possible to replace org.apache.axis2.wso2 artifacts with org.apache.axis2 artifacts?

folks! 乡亲们!

I need to update artifacts in a project that is running on wso2 server. 我需要更新在wso2服务器上运行的项目中的工件。 There were used wso2 specific artifacts like org.apache.axis2.wso2 or org.apache.ws.commons.axiom.wso2. 使用了wso2特定工件,例如org.apache.axis2.wso2或org.apache.ws.commons.axiom.wso2。

If I want to replace these wso2 specific artifacts with more up-to-date regular org.apache.axis2 artifacts could it lead to errors or I can use non specific artifacts freely? 如果我想用更多最新的常规org.apache.axis2工件替换这些wso2特定工件,是否可能导致错误或我可以自由使用非特定工件?

WSO2 creates its own versions of such 3rd party libraries in 2 cases. WSO2在2种情况下创建了自己的第三方库版本。

  1. When the original jar is not OSGi 当原始jar不是OSGi时
  2. When WSO2 needs to add new fixes and improvement which are not there is the original jar 当WSO2需要添加新的修复程序和改进时,则没有原始的jar

In either case, changing a jar to its original version can break the server. 无论哪种情况,将jar更改为其原始版本都可能导致服务器损坏。

On the other hand, new versions of those 3rd party jars can have API (signature) changes too. 另一方面,这些第3方jar的新版本也可以进行API(签名)更改。 So it can also break the server. 因此它也可能破坏服务器。

So the bottom line is it won't be possible to do such jar upgrades without internal code changes. 因此,最重要的是,如果不更改内部代码,将无法进行此类jar升级。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 org.apache.axis2.wso2 依赖项中的 maven 构建问题 - A maven build issue in org.apache.axis2.wso2 dependency WSO2 ESB-java.lang.ClassNotFoundException:org.apache.synapse.core.axis2.Axis2MessageContext - WSO2 ESB - java.lang.ClassNotFoundException: org.apache.synapse.core.axis2.Axis2MessageContext org.apache.axis2.AxisFault:传输错误:201错误:已创建? - org.apache.axis2.AxisFault: Transport error: 201 Error: Created? 迭代中介器中的错误:Axis2Sender将消息发回org.apache.axis2.AxisFault发生意外错误 - Error in iterate mediator:Axis2Sender Unexpected error sending message back org.apache.axis2.AxisFault axis + android错误:org.apache.axis2.engine.DispatchPhase.checkPostConditions - axis+android error : org.apache.axis2.engine.DispatchPhase.checkPostConditions 找不到或加载主类org.apache.axis2.wsdl.WSDL2CPP - Could not find or load main class org.apache.axis2.wsdl.WSDL2CPP org.apache.axis2.AxisFault:传输错误:415错误:不支持的媒体类型 - org.apache.axis2.AxisFault: Transport error: 415 Error: Unsupported Media Type wso2获取org.apache.rampart.RampartException:不支持的SignedSupportingToken - wso2 getting org.apache.rampart.RampartException: Unsupported SignedSupportingToken API管理器 - 发送调解器:“未捕获的异常{org.apache.axis2.transport.base.threads.NativeWorkerPool} java.lang.NumberFormatException:null” - API Manager - Send Mediator: “Uncaught exception {org.apache.axis2.transport.base.threads.NativeWorkerPool} java.lang.NumberFormatException: null” WS02ESB代理服务返回<axis2ns2:binary xmlns:axis2ns2=“http://ws.apache.org/commons/ns/payload”> - WS02ESB proxy service returns <axis2ns2:binary xmlns:axis2ns2=“http://ws.apache.org/commons/ns/payload”>
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM