You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Deepal Jayasinghe <de...@opensource.lk> on 2008/02/01 05:32:05 UTC
Re: "Pass through" Web Service
> Hello,
> I am curious about how to create a web-service when the payloads it
> delivers could have un-anticipated elements. That is, the xsd for the
> payloads would have to leave open the possibility of potentially
> random elements being included. In this case, only the outermost tag
> would be known as well as a few other elements. However, its
> complexType declaration would also have an xsd:any element. Because
> of the unknown elements, there seems to be no good way to characterize
> such messages in a corresponding Java class. So, I don't expect the
> code generation tools to be of any use here. The alternative would be
> to design the web-service so that it is able to put an arbitrary XML
> message into a payload. Could you help me start researching how to
> implement such a service? This is a more general question than this
> message about RDF
>
In Axis2 you can write your service impl class with Axiom and get this
working. I mean you can write your service impl class as below
class MyService {
public OMElement getData(OMElement value){
// do the processing here
}
}
Thanks
Deepal
"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: "Pass through" Web Service
Posted by John Cabral <jo...@gmail.com>.
Thank you very much for your help.
JC
On Jan 31, 2008 11:32 PM, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
> > Hello,
> > I am curious about how to create a web-service when the payloads it
> > delivers could have un-anticipated elements. That is, the xsd for the
> > payloads would have to leave open the possibility of potentially
> > random elements being included. In this case, only the outermost tag
> > would be known as well as a few other elements. However, its
> > complexType declaration would also have an xsd:any element. Because
> > of the unknown elements, there seems to be no good way to characterize
> > such messages in a corresponding Java class. So, I don't expect the
> > code generation tools to be of any use here. The alternative would be
> > to design the web-service so that it is able to put an arbitrary XML
> > message into a payload. Could you help me start researching how to
> > implement such a service? This is a more general question than this
> > message about RDF
> >
> In Axis2 you can write your service impl class with Axiom and get this
> working. I mean you can write your service impl class as below
>
> class MyService {
> public OMElement getData(OMElement value){
> // do the processing here
> }
> }
>
> Thanks
> Deepal
>
> "
>
>
>
> ---------------------------------------------------------------------
> 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