axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alistair Young <alist...@smo.uhi.ac.uk>
Subject Re: [AXIS2] Best practices - RawXMLINOutMessageReceiver?
Date Thu, 10 Aug 2006 08:50:29 GMT
I think what I need is a extension to  
AbstractInOutSyncMessageReceiver that does the xmlbeans Document to  
Type mapping and calls the service class with those types instead of  
the default of calling the service class with one xmlbeans Document.

Alistair


On 10 Aug 2006, at 09:33, Alistair Young wrote:

> Would the folks on the list have any recommendations for best  
> practices?
>
> If I have a service operation:
>
> public TestObject doSomething(TestObject testObject1,  
> OtherTestObject testObject2) {
>   return testIObject1.something(testObject2);
> }
>
> Would it be best to work with RawXMLINOutMessageReceiver  +  
> OMElement + xmlbeans instead of the actual xmlbeans objects  
> themselves and have the method do the mapping from OMElement to  
> TestObject and OtherTestObject via xmlbeans?
>
> Seems no matter what I try I can't get the service skeleton to be  
> generated with two parameters anyway. It always has one xmlbean  
> parameter that wraps the two params as xmlbeans inside it.
> i.e.  
> TestObjectMessageDocument.getTestObjectMessage.getTestObjectType();
> TestObjectMessageDocument.getTestObjectMessage.getOtherTestObjectType( 
> );
>
> thanks,
>
> Alistair
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Mime
View raw message