养成好的习惯 随时记录解决方案
好记性不如烂笔头,以前在WebSphere上部署过axis2 今天又折腾了一晚上
决定还是写在这做备案
WebSphere6+axis2 1.3
发布webservice服务的时候出现下面的异常
java.lang.NoSuchMethodError: javax/wsdl/Operation.getExtensibilityElements()Ljava/util/List; at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOperations(WSDL11ToAxisServiceBuilder.java:1010) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortType(WSDL11ToAxisServiceBuilder.java:399) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpoints(WSDL11ToAxisServiceBuilder.java:318) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:288) at ...
解决方案:
1、
引用
Apache Muse - Conflicting Version of WSDL4J in WebSphere Deployments
When deploying your Muse-based applications on IBM WebSphere Application Server (WAS) 6.0 or 6.1, you need to be aware that Muse relies on WSDL4J 1.6.1 while the server's core libraries include WSDL4J 1.4. If you install your application using the default class loading system, it will fail to start because the Muse framework depends on WSDL4J APIs that are only available in WSDL4J 1.5 and above. To work around this issue, you can configure the server to use the application's class loader before the container or system class loaders; this will ensure that the WSDL4J classes that are in your application's /WEB-INF/lib directory will be loaded before those in $WAS_HOME/lib.
If you are developing and deploying your application through IBM Rational Application Developer (RAD), you can make the required changes by setting the class loader mode to PARENT_LAST and the class loader policy to SINGLE.
If you are installing your application through the WAS admin console, select Enterprise Applications > Your Application > Class loading and update detection. You should then check the boxes labeled as follows:
* Classes loaded with application class loader first
* Single class loader for application
Making these changes should not affect your other (non-Muse) applications because, having no WSDL4J JAR files of their own, the server will continue up the chain of class loaders until the container's class loader discovers WSDL4J 1.4 in $WAS_HOME/lib.
就是先加载应用自己的类库 最后在加载父类 不用WebSphere自带的wsdl类
2、更改之后 抛出struts标签不能解析 什么的
这个时候 把应用里面的servlet.jar删除 这个时候用WebSphere自带的
3、再抛出
RAD 6.0.1, DataSource ClassCastException
这个异常
的时候 删除这个jar包jdbc2_0-stdext.jar(hibernate带的),可以查询下DataSource这个类在哪些包中 没用的都删掉
4、重启 发布成功ok
分享到:
相关推荐
Websphere6.0安装手册Websphere6.0安装手册Websphere6.0安装手册Websphere6.0安装手册Websphere6.0安装手册Websphere6.0安装手册
Websphere6.0应用部署文档
Websphere 6.0集群文档 大家可以作下参考
websphere 6.0 for linux安装
websphere 6.0 for linux.doc
websphere6.0如何配置ldap安全性并应用于项目.doc
WebSphere Portal 6.0数据库迁移到Oracle参考手册 资料共享:WebSphere Portal 6.0数据库迁移到Oracle参考手册 主要描述在WebSphere Portal 6.0 下,如何将数据库迁移到oracle的参考手册,记录迁移过程,解决迁移...
09[1].12-使用websphere6.0搭建高可靠性系统.ppt
安装过程,如何配置数据源链接,配置数据源,测试数据源连接。如何将工程部署到服务器上。
IBM WebSphere Portal 6.0 安装手册,繁体中文
webshpere使用自定义的驱动程序连接数据库
websphere本地部署手顺websphere本地部署手顺
Install, Config WebSphere Portal 6.0 with DB2 8.2.5详解 ……
websphere java 部署websphere java 部署
WebSphere安装部署手册十分详细,屡试不爽。kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk
WebSphere_MQ_V6.0,支持03 08 非常好用,一手珍藏。好东西。
NULL 博文链接:https://wxu.iteye.com/blog/268981
在websphere8.5 下部署含有CXFwebservice的war包无法正常启动,而相应的war包在tomcat上是可以正常启动的,通过后台的日志分析大致可以定位为相关的cxf类无法找到,其实这些类在项目的lib目录下都是存在的,莫名其妙...
这两天装WAS,第一次装的时候有些小问题,装了2,3次就觉得其实很...2. WebSphere 6.0.2.0 升级维护包; 3. WebSphere 6.0.2.23 升级维护包;6.0.2.23只能升级6.0.2.0及以上版本,不支持从6.0.0.1直接升到6.0.2.23。