Hi,
I am new to Axis and would like to ask for your help.
Is there a way I can let the Axis Server Engine bypass
the invocation of the service after its request
handlers have been executed, but I don't want to reply
with fault message, instead, the reply message is
pre-generated beforehand and re
The code for server and client is largely the same. So you merely ignore the
fact that you are gettting both, and the classloader will do the same. The
only overhead is space on your harddisk. Axis does not expect to be talking
on Axis on the other side, but anyone that adheres to the transport
pro
Hi,
I would like to validate incoming messages against XML Schema
definition, but unfortunately I don't know to do it.
Could you tell me how to do it?
Thanks in advance.
Marcin Okraszewski
Hi danch, Pablo
yah, if it can fulfil the requirements writing XSLT is the much
attractive than try to write bunch of code.
Danch Thank for the lesson :)
Srinath
On Fri, 2003-09-19 at 22:42, Dan Christopherson wrote:
> Alternatively, you could just write an XSLT stylesheet to generate it,
>
This isn't really an axis question, but i think that this should get you
on the way:
SAXParserFactory spf = new SAXParserFactory();
spf.setValidating(true);
SAXParser saxp = spf.newInstance();
saxp.parse(WHATEVER);
For further help read the Xerces API docs:
http://xml.apache.org/xerces2-j/api.
Hi Marcin,
I guess you manually want to validate. I point out two ways of doing it.
1) You can write a handler. Get the SOAPBody from the MessageContext. Then
you can parse it with xerces.
2) You can write a message style service with below signature.
public Element [] method(Element [] bodies
Hi Richard
I am strongly belive that doing so . changing the execution flow
by the handlers is against axis semantics.
what u need to do is sounds like caching..(the context of the
caching is "n this case, only when the reply message is not ready, the
service will be ca
