Forum Discussion
BA_Service_Haus
13 years agoRegular Contributor
Hi Ole,
this issue is some months ago, but finaly I solved it today.
At the end you were right: it was a classloading problem.
I used the cat-tool of the WLS (http://wls-host:port/wls-cat) and it suggested how to fill the <prefer-application-packages> part of the weblogic-application.xml.
So I just had to insert the suggested XML into a weblogic-application.xml and build an ear-archive out of this file and the soapUI-Mock (war-file).
That's it.
Now all dispatching-methods are running problem-free. And also FAULTs are returned. And last but not least the XmlHolder can be used again (I had to switch to XmlSlurper in the past).
Best regards
this issue is some months ago, but finaly I solved it today.
At the end you were right: it was a classloading problem.
I used the cat-tool of the WLS (http://wls-host:port/wls-cat) and it suggested how to fill the <prefer-application-packages> part of the weblogic-application.xml.
So I just had to insert the suggested XML into a weblogic-application.xml and build an ear-archive out of this file and the soapUI-Mock (war-file).
That's it.
Now all dispatching-methods are running problem-free. And also FAULTs are returned. And last but not least the XmlHolder can be used again (I had to switch to XmlSlurper in the past).
Best regards