1 thought on “How to release WebService in WebSphere in WebSphere”
Raymond
First of all, the environment is WebSphere embedded in RAD7, and AXIS2 uses the latest version of 1.6.2.
The reason for the above problem is that the JAR supported by WebSphere itself should have conflicts with Axis2. Although the conflict of the problem I encountered is not the same as others. No method found, but I checked the source code to find the method exist. This solution was found from this URL, but it was not particularly detailed, and it was completely changed after groping for a long time. The solution is relatively common for the package conflict. 1, set the parameters in Axis2.xml to True (AXIS2 1.5.5 or higher version) 2, and the class loading level of the application is Classes loaded with local class loader first (Parent Last ) 3, set the custom parameter of the WAS Server JVM: com.ibmcom.iBm.websphere .. For True
Is when I did the second step, I encountered a problem. After opening Console, I set up the wrong path. The correct setting path should be selected for the application. After clicking to enter Class installation and update detection, ineffective after modification), click the corresponding module to enter, you can see the class load level to be modified at the bottom. The third step, the application server-"-> Java and process definition under process management ---> Java virtual machines under other attributes-> customized attributes under other attributes, if there is no attribute, if there is no attribute, if there is no attribute, if there is no attribute, if there is no attribute, if there is no attribute, Newly built. It should be restarted. problem solved. Compare the rookie, hoping to help people who are as confused as me.
First of all, the environment is WebSphere embedded in RAD7, and AXIS2 uses the latest version of 1.6.2.
The reason for the above problem is that the JAR supported by WebSphere itself should have conflicts with Axis2. Although the conflict of the problem I encountered is not the same as others. No method found, but I checked the source code to find the method exist.
This solution was found from this URL, but it was not particularly detailed, and it was completely changed after groping for a long time. The solution is relatively common for the package conflict.
1, set the parameters in Axis2.xml to True (AXIS2 1.5.5 or higher version)
2, and the class loading level of the application is Classes loaded with local class loader first (Parent Last )
3, set the custom parameter of the WAS Server JVM: com.ibmcom.iBm.websphere .. For True
Is when I did the second step, I encountered a problem. After opening Console, I set up the wrong path. The correct setting path should be selected for the application. After clicking to enter Class installation and update detection, ineffective after modification), click the corresponding module to enter, you can see the class load level to be modified at the bottom.
The third step, the application server-"-> Java and process definition under process management ---> Java virtual machines under other attributes-> customized attributes under other attributes, if there is no attribute, if there is no attribute, if there is no attribute, if there is no attribute, if there is no attribute, if there is no attribute, Newly built.
It should be restarted. problem solved. Compare the rookie, hoping to help people who are as confused as me.