S
Sean Clarke
Hi,
I am implementing a server that processes data supplied from clients
using SOAP (RPC) and am not sure on the best way to implement the server.
I am using JBoss/Tomcat and so was planning to use a JAXMServlet to act as
the listener etc. however unless i am really stupid (which it could
be ) I can't find an implementation of JAXMServlet etc.
My first preference was Axis (as one of the clients are using it - the other
is X++/gSOAP based), but I could not find JAXM, but the documentation does
mention JAXM->SAAJ - alas I cannot find any classes in SAAJ that do what I
want - ie sit as a server and receive client requests.
I downloaded SUNS WSDP and couldn't see the JAXMServlet in the docs.
What would be the best solution for this problem? as typical in Java there
are many possibilities, as mentioned my preference is Axis. One of the
other teams had used a completely separate web service, connecting to an
Axis web service etc. that just sounds overkill and complicated.. in
essence I just need something that sits there, receives a message and
passes it on to some cleverer classes... The main business logic here is
processing the data, SOAP is purely a method of transferring the data (ie
it is not a dedicated SOAP message processor, it does lots of other
things).
I even though of using a normal servlet and building my functionality in
that...
Any suggestions?
I am implementing a server that processes data supplied from clients
using SOAP (RPC) and am not sure on the best way to implement the server.
I am using JBoss/Tomcat and so was planning to use a JAXMServlet to act as
the listener etc. however unless i am really stupid (which it could
be ) I can't find an implementation of JAXMServlet etc.
My first preference was Axis (as one of the clients are using it - the other
is X++/gSOAP based), but I could not find JAXM, but the documentation does
mention JAXM->SAAJ - alas I cannot find any classes in SAAJ that do what I
want - ie sit as a server and receive client requests.
I downloaded SUNS WSDP and couldn't see the JAXMServlet in the docs.
What would be the best solution for this problem? as typical in Java there
are many possibilities, as mentioned my preference is Axis. One of the
other teams had used a completely separate web service, connecting to an
Axis web service etc. that just sounds overkill and complicated.. in
essence I just need something that sits there, receives a message and
passes it on to some cleverer classes... The main business logic here is
processing the data, SOAP is purely a method of transferring the data (ie
it is not a dedicated SOAP message processor, it does lots of other
things).
I even though of using a normal servlet and building my functionality in
that...
Any suggestions?