|
|
Endpoints and soap responses...
Using an AbstractJDomPayloadEndpoint, this snippet:Code:
protected Element invokeInternal(Element applySanctionRequest) throws Exception {
//Do Stuff
Element returnVal = new Element(quot;ServiceResponsequot;);
returnVal.setNamespace(commonNamespace);
returnVal.setText(quot;OK!quot;);
logger.debug(quot;Returning Fake Responsequot;);
return returnVal;
}
Results in this exception:
Code:
Envelope namespace must be: soap/envelope/ is soa/schema/sf
Which says to me Spring-WS is trying to return returnVal as the *entire* return response, rather than the Soap Payload.
Am I right, and is there an easier way to doing this than constructing the entire soap envelope/header/body myself?
Have same problem using OC4J 10.1.3, other posts suggest to get this working for request/response (from sample one-way) requires changing the XML Parser ?
Site wont let me post link on this forum ? html page is t-42386
Not a realistic option for a real server deploying apps...
mons.loggingquot; /gt;
lt;import-shared-library name=quot;oracle.toplinkquot; /gt;
lt;/imported-shared-librariesgt;
lt;/orion-applicationgt;
And to emphasise the point: Simply deploying a war and asking for the libs to be left out didn't work for me. I actually had to provide my own descriptor.
*edit* PS. I have since then actually started using the Jaxb2Marshallers for my endpoints. Less hassle that way.
Hi, have indeed changed tack and am fair way down the JAXB route now having generated classes via xjc in usual way, deploying spring-ws 1.5.0 and JAXB2.0 over OC4J1 0.1.3 and am finding the same kinds of classpath problems u were describing in your quot;XML APIs, OC4J, and BeanDefinitionsquot; thread. Since u have overcome the various issues and custom oracle parts of the OC4J 10.1.3 web services environment with spring-ws, (something i am yet to do!) what version of JAXB did u use to compile ? did u deploy the same JAXB jars from the Spring-ws dist to the OC4J classpath, and/or use the Oracle jars ? thanks ...
You are using the xjc2 maven plugin aren't you? (just to be sure).
I'll post a list of dependencies later I'm using later in the day. I'm shipping them in WEB-INF/lib atm, but I intend to change them over to shared libraries soon.
Hi, nope unfortunately not using mvn at all right now since have to integrate into standing build environment here, that list of dependences would be great ! I had a look at the changing the xml parser for the application to get the XM api endpoints going and it looks ok, am keen to resolve the jaxb side as well, thanks for your help...
What I meant to say was, you're using the jaxb2 xjc plugin, as opposed to the jaxb1 plugin. (Hey, it happens )
Here are the dependencies I have. The 'provided' ones already exist on the server, and including them in your distribution will lead to classpath problems.
Code:
lt;dependencygt;
lt;groupIdgt;org.lt;/groupIdgt;
lt;artifactIdgt;springlt;/artifactIdgt;
lt;versiongt;2.5.4lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;org..wslt;/groupIdgt;
lt;artifactIdgt;spring-ws-core-tigerlt;/artifactIdgt;
lt;versiongt;1.5.1lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;org..wslt;/groupIdgt;
lt;artifactIdgt;spring-oxm-tigerlt;/artifactIdgt;
lt;versiongt;1.5.1lt;/versiongt;
lt;scopegt;runtimelt;/scopegt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;log4jlt;/groupIdgt;
lt;artifactIdgt;log4jlt;/artifactIdgt;
lt;versiongt;1.2.15lt;/versiongt;
lt;exclusionsgt;
lt;exclusiongt;
lt;artifactIdgt;maillt;/artifactIdgt;
lt;groupIdgt;javax.maillt;/groupIdgt;
lt;/exclusiongt;
lt;exclusiongt;
lt;artifactIdgt;jmslt;/artifactIdgt;
lt;groupIdgt;javax.jmslt;/groupIdgt;
lt;/exclusiongt;
lt;exclusiongt;
lt;artifactIdgt;jmxtoolslt;/artifactIdgt;
lt;groupIdgt;com.sun.jdmklt;/groupIdgt;
lt;/exclusiongt;
lt;exclusiongt;
lt;artifactIdgt;jmxrilt;/artifactIdgt;
lt;groupIdgt;com.sun.jmxlt;/groupIdgt;
lt;/exclusiongt;
lt;/exclusionsgt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;jdomlt;/groupIdgt;
lt;artifactIdgt;jdomlt;/artifactIdgt;
lt;versiongt;1.0lt;/versiongt;
lt;scopegt;providedlt;/scopegt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;jaxenlt;/groupIdgt;
lt;artifactIdgt;jaxenlt;/artifactIdgt;
lt;versiongt;1.1-beta-4lt;/versiongt;
lt;scopegt;providedlt;/scopegt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;javax.xml.bindlt;/groupIdgt;
lt;artifactIdgt;jaxb-apilt;/artifactIdgt;
lt;versiongt;2.1lt;/versiongt;
lt;exclusionsgt;
lt;exclusiongt;
lt;artifactIdgt;stax-apilt;/artifactIdgt;
lt;groupIdgt;javax.xml.streamlt;/groupIdgt;
lt;/exclusiongt;
lt;exclusiongt;
lt;artifactIdgt;activationlt;/artifactIdgt;
lt;groupIdgt;javax.activationlt;/groupIdgt;
lt;/exclusiongt;
lt;/exclusionsgt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;com.sun.xml.bindlt;/groupIdgt;
lt;artifactIdgt;jaxb-impllt;/artifactIdgt;
lt;versiongt;2.0.5lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;javax.xml.soaplt;/groupIdgt;
lt;artifactIdgt;saaj-apilt;/artifactIdgt;
lt;versiongt;1.3lt;/versiongt;
lt;scopegt;providedlt;/scopegt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;xerceslt;/groupIdgt;
lt;artifactIdgt;xercesImpllt;/artifactIdgt;
lt;versiongt;2.8.1lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;xalanlt;/groupIdgt;
lt;artifactIdgt;xalanlt;/artifactIdgt;
lt;versiongt;2.7.0lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;commons-logginglt;/groupIdgt;
lt;artifactIdgt;commons-logginglt;/artifactIdgt;
lt;versiongt;1.1.1lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;com.oraclelt;/groupIdgt;
lt;artifactIdgt;ojdbc14lt;/artifactIdgt;
lt;versiongt;10.2.0.3.0lt;/versiongt;
lt;scopegt;providedlt;/scopegt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;javax.activationlt;/groupIdgt;
lt;artifactIdgt;activationlt;/artifactIdgt;
lt;versiongt;1.1.1lt;/versiongt;
lt;scopegt;providedlt;/scopegt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;com.sun.xml.messaging.saajlt;/groupIdgt;
lt;artifactIdgt;saaj-impllt;/artifactIdgt;
lt;versiongt;1.3lt;/versiongt;
lt;scopegt;providedlt;/scopegt;
lt;exclusionsgt;
lt;exclusiongt;
lt;artifactIdgt;activationlt;/artifactIdgt;
lt;groupIdgt;javax.activationlt;/groupIdgt;
lt;/exclusiongt;
lt;/exclusionsgt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;staxlt;/groupIdgt;
lt;artifactIdgt;stax-apilt;/artifactIdgt;
lt;versiongt;1.0.1lt;/versiongt;
lt;scopegt;providedlt;/scopegt;
lt;/dependencygt;Great, good stuff !, thanks for this...
I have the XML API endpoints (JDOM amp; DOM4J) working with the oracle shared library quot;oracle.xmlquot; excluded in orion-application.xml. Just to confirm, to get the JABX endpoints working did u have to exclude any other oracle shard libs ? |
|