From 5dd657e82d7ebd14de9f6c0922762208bb952b4b Mon Sep 17 00:00:00 2001 From: Arjen Poutsma Date: Tue, 15 May 2007 16:28:09 +0000 Subject: [PATCH] More Docs. --- src/docbkx/server.xml | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/src/docbkx/server.xml b/src/docbkx/server.xml index 7203e4d6..7a123a02 100644 --- a/src/docbkx/server.xml +++ b/src/docbkx/server.xml @@ -195,7 +195,8 @@ method, implement your logic, and return an Element. Here is a short example consisting of a class and a declaration in the application context. - - + ]]> The above class and the declaration in the application context is all you need besides setting up a @@ -230,11 +231,19 @@ public class SampleEndpoint extends AbstractDomPayloadEndpoint { AbstractJDomPayloadEndpoint allows you to use JDOM, and the AbstractXomPayloadEndpoint uses XOM to handle the XML. All endpoints have an invokeInternal method similar to above. - +
<classname>AbstractMarshallingPayloadEndpoint</classname> - + + Rather than handling XML directly using DOM, you can use marshalling to convert the payload of the XML + message into a Java Object. Spring Web Services offers the + AbstractMarshallingPayloadEndpoint for this purpose, which is built on the + marshalling abstraction described in . The + AbstractMarshallingPayloadEndpoint has two properties: + marshaller and unmarshaller, in which you can inject + +
<literal>@Endpoint</literal>