You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Davanum Srinivas <da...@gmail.com> on 2005/06/05 05:27:20 UTC
Re: Some problem with Axis and JAX-RPC
Venkat,
Problem is with the HandlerChainImpl's kludge for jaxrpc in axis. if
you set the optimize flag to true in doReceiver and clear the
JAXRPC_METHOD_INFO from messagecontext then the message is sent fine,
but there is problem in receiving...can you please look into this
ASAP? We need to get the latest CVS if both wss4j and axis working
with each other.
thanks,
dims
On 6/3/05, Werner Dittmann <We...@t-online.de> wrote:
> Venkat,
>
> sorry for the late replay - was not online on my home computer the last
> days.
>
> No, I haven't seen such a behaviour. Checked my Jars here, I'm using the
> RC3 jars from Axis. Never saw such an error as far as I can remember.
> Also checked the deploy.wsdd - that wasn't changed since a long time ago.
>
> Regards,
> Werner
>
> Venkat Reddy schrieb:
> > When i replace 1.2-Rc3 jars with the ones from 1.2 final, i get
> > SAXParseExceptions while running interopTests. Seems that deployment of
> > build\work\org\apache\ws\axis\oasis\ping\deploy.wsdd results in
> > AxisFault. with the following exception. But it works fine if i use RC3
> > axis jars. Still looking into this. Werner, did you face this before?
> > I'm using latest CVS for WSS4J.
> >
> > interopTests:
> > [echo] Running system tests - BEGIN...
> > [java] <?xml version="1.0" encoding="UTF-8"?>
> > [java] <Admin>Done processing</Admin>
> >
> >
> > [java] Processing file
> > C:\APACHE\ws-fx\wss4j\build\work\org\apache\ws\axis\oasis\ping\deploy.wsdd
> > [java] Exception: AxisFault
> > [java] faultCode: {
> > http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > [java] faultSubcode:
> > [java] faultString: org.xml.sax.SAXParseException: Content is not
> > allowed in prolog.
> > [java] faultActor:
> > [java] faultNode:
> > [java] faultDetail:
> > [java]
> > {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException :
> > Content is not allowed in prolog.
> >
> > [java] at
> > org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> > Source)
> > [java] at
> > org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
> > [java] at org.apache.xerces.impl.XMLErrorReporter.reportError
> > (Unknown Source)
> > [java] at
> > org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> > [java] at
> > org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
> > [java] at
> > org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch
> > (Unknown Source)
> > [java] at
> > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> > Source)
> > [java] at
> > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> > [java] at
> > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> > [java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> > [java] at
> > org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> > [java] at javax.xml.parsers.SAXParser.parse(Unknown Source)
> > [java] at
> > org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
> > [java] at org.apache.axis.SOAPPart.getAsSOAPEnvelope
> > (SOAPPart.java:696)
> > [java] at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
> > [java] at
> > org.apache.axis.server.AxisServer.initSOAPConstants(AxisServer.java:345)
> > [java] at org.apache.axis.server.AxisServer.invoke
> > (AxisServer.java:279)
> > [java] at
> > org.apache.axis.transport.http.SimpleAxisWorker.execute(SimpleAxisWorker.java:428)
> > [java] at
> > org.apache.axis.transport.http.SimpleAxisWorker.run(SimpleAxisWorker.java
> > :155)
> > [java] at
> > org.apache.axis.transport.http.SimpleAxisServer.run(SimpleAxisServer.java:245)
> > [java] at
> > org.apache.axis.transport.http.SimpleAxisServer.start(SimpleAxisServer.java:296)
> > [java] at
> > org.apache.axis.transport.http.SimpleAxisServer.start(SimpleAxisServer.java:304)
> > [java] at
> > org.apache.axis.transport.http.SimpleAxisServer.main(SimpleAxisServer.java:385)
> >
> >
> >
> >
> >
> > On 5/27/05, *Davanum Srinivas* <davanum@gmail.com
> > <ma...@gmail.com>> wrote:
> >
> > Venkat,
> >
> > Can you please figure out a way to fix this problem ASAP! (some work
> > around for setting the property for Axis 1.2 final AND a code fix for
> > latest CVS)
> >
> > thanks,
> > dims
> >
> > ---------- Forwarded message ----------
> > From: Werner Dittmann <Werner.Dittmann@t-online.de
> > <ma...@t-online.de>>
> > Date: May 27, 2005 7:35 AM
> > Subject: Some problem with Axis and JAX-RPC
> > To: davanum@gmail.com <ma...@gmail.com>
> >
> >
> > Dims,
> >
> > instead of bothering the whole list, just a report about a problem
> > I found during WSS4J tests:
> >
> > During the tests of the JAX-RPC compliant handler I've seen that the
> > original SOAP request is not replaced by the security enhanced
> > SOAP request. WSS4JHandler uses the following code to set
> > a new SOAPPart content:
> > ....
> > sPart.setContent(new StreamSource(new
> > ByteArrayInputStream(os.toByteArray())));
> > ....
> >
> > I digged a little bit into the Axis sources and found (in
> > SOAPPart.java )
> > that
> > the setting of new content only works if a property called
> >
> > *public* *static* *final* String ALLOW_FORM_OPTIMIZATION =
> > *"axis.form.optimization"*;
> >
> > is either not set or is defined as "true".
> >
> > When using the interop testcase for the WSS4JHandler this property is
> > set to "false", thus
> > preventing the handler to replace the SOAPPart content. This causes
> > errors in the tests.
> >
> > The main difference between the mentioned interop testcase and our
> > other
> > interop testcases is, that only this specific testcase uses a fully
> > dynamic setup of the handler, i.e
> > does not use a client side deployment file. Pls refer to
> > TestJAXRPCHandler.java in test/interop.
> >
> > I haven't looked into the Axis sources in more detail, but it seems
> > that
> > there are
> > some differences between deployment file and dynamic handler setup.
> >
> > Can you check that?
> >
> > Regards
> > Werner
> >
> > BTW, I've checked the ant target to generate a binary distributin, works
> > so far.
> > Also modified to use the enhanced timestamps, tests ok so far. Now I'm
> > doing some upgrades/remove of warings during Javadoc generation to get
> > a more clean distri. I'll checking during the weekend.
> >
> > Werner
> >
> >
> > --
> > Davanum Srinivas - http://webservices.apache.org/~dims/
> >
> >
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Some problem with Axis and JAX-RPC
Posted by Werner Dittmann <We...@t-online.de>.
Dims,
thanks for the fast keystore fix.
The ant target for the distribution is ready in my local copy.
just need to incoporate the latest changes about the "legal"
directory, but this is a small matter. Otherwise I would like
to wait for the Axis fix. Doing so we could get all test and
interops up and running.
I'll synchronize my local copy during the week, hoping that
the Axis problemg get solved somehow.
If that is ok we can produce a Beta fairly quick IMHO.
Regards,
Werner
Davanum Srinivas schrieb:
> Venkat,
>
> Problem is with the HandlerChainImpl's kludge for jaxrpc in axis. if
> you set the optimize flag to true in doReceiver and clear the
> JAXRPC_METHOD_INFO from messagecontext then the message is sent fine,
> but there is problem in receiving...can you please look into this
> ASAP? We need to get the latest CVS if both wss4j and axis working
> with each other.
>
> thanks,
> dims
>
> On 6/3/05, Werner Dittmann <We...@t-online.de> wrote:
>
>>Venkat,
>>
>>sorry for the late replay - was not online on my home computer the last
>>days.
>>
>>No, I haven't seen such a behaviour. Checked my Jars here, I'm using the
>>RC3 jars from Axis. Never saw such an error as far as I can remember.
>>Also checked the deploy.wsdd - that wasn't changed since a long time ago.
>>
>>Regards,
>>Werner
>>
>>Venkat Reddy schrieb:
>>
>>>When i replace 1.2-Rc3 jars with the ones from 1.2 final, i get
>>>SAXParseExceptions while running interopTests. Seems that deployment of
>>>build\work\org\apache\ws\axis\oasis\ping\deploy.wsdd results in
>>>AxisFault. with the following exception. But it works fine if i use RC3
>>>axis jars. Still looking into this. Werner, did you face this before?
>>>I'm using latest CVS for WSS4J.
>>>
>>>interopTests:
>>> [echo] Running system tests - BEGIN...
>>> [java] <?xml version="1.0" encoding="UTF-8"?>
>>> [java] <Admin>Done processing</Admin>
>>>
>>>
>>> [java] Processing file
>>>C:\APACHE\ws-fx\wss4j\build\work\org\apache\ws\axis\oasis\ping\deploy.wsdd
>>> [java] Exception: AxisFault
>>> [java] faultCode: {
>>>http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>>> [java] faultSubcode:
>>> [java] faultString: org.xml.sax.SAXParseException: Content is not
>>>allowed in prolog.
>>> [java] faultActor:
>>> [java] faultNode:
>>> [java] faultDetail:
>>> [java]
>>>{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException :
>>>Content is not allowed in prolog.
>>>
>>> [java] at
>>>org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>>>Source)
>>> [java] at
>>>org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
>>> [java] at org.apache.xerces.impl.XMLErrorReporter.reportError
>>>(Unknown Source)
>>> [java] at
>>>org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>>> [java] at
>>>org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
>>> [java] at
>>>org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch
>>>(Unknown Source)
>>> [java] at
>>>org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>>Source)
>>> [java] at
>>>org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>> [java] at
>>>org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>> [java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>> [java] at
>>>org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>>> [java] at javax.xml.parsers.SAXParser.parse(Unknown Source)
>>> [java] at
>>>org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>>> [java] at org.apache.axis.SOAPPart.getAsSOAPEnvelope
>>>(SOAPPart.java:696)
>>> [java] at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
>>> [java] at
>>>org.apache.axis.server.AxisServer.initSOAPConstants(AxisServer.java:345)
>>> [java] at org.apache.axis.server.AxisServer.invoke
>>>(AxisServer.java:279)
>>> [java] at
>>>org.apache.axis.transport.http.SimpleAxisWorker.execute(SimpleAxisWorker.java:428)
>>> [java] at
>>>org.apache.axis.transport.http.SimpleAxisWorker.run(SimpleAxisWorker.java
>>>:155)
>>> [java] at
>>>org.apache.axis.transport.http.SimpleAxisServer.run(SimpleAxisServer.java:245)
>>> [java] at
>>>org.apache.axis.transport.http.SimpleAxisServer.start(SimpleAxisServer.java:296)
>>> [java] at
>>>org.apache.axis.transport.http.SimpleAxisServer.start(SimpleAxisServer.java:304)
>>> [java] at
>>>org.apache.axis.transport.http.SimpleAxisServer.main(SimpleAxisServer.java:385)
>>>
>>>
>>>
>>>
>>>
>>>On 5/27/05, *Davanum Srinivas* <davanum@gmail.com
>>><ma...@gmail.com>> wrote:
>>>
>>> Venkat,
>>>
>>> Can you please figure out a way to fix this problem ASAP! (some work
>>> around for setting the property for Axis 1.2 final AND a code fix for
>>> latest CVS)
>>>
>>> thanks,
>>> dims
>>>
>>> ---------- Forwarded message ----------
>>> From: Werner Dittmann <Werner.Dittmann@t-online.de
>>> <ma...@t-online.de>>
>>> Date: May 27, 2005 7:35 AM
>>> Subject: Some problem with Axis and JAX-RPC
>>> To: davanum@gmail.com <ma...@gmail.com>
>>>
>>>
>>> Dims,
>>>
>>> instead of bothering the whole list, just a report about a problem
>>> I found during WSS4J tests:
>>>
>>> During the tests of the JAX-RPC compliant handler I've seen that the
>>> original SOAP request is not replaced by the security enhanced
>>> SOAP request. WSS4JHandler uses the following code to set
>>> a new SOAPPart content:
>>> ....
>>> sPart.setContent(new StreamSource(new
>>> ByteArrayInputStream(os.toByteArray())));
>>> ....
>>>
>>> I digged a little bit into the Axis sources and found (in
>>> SOAPPart.java )
>>> that
>>> the setting of new content only works if a property called
>>>
>>> *public* *static* *final* String ALLOW_FORM_OPTIMIZATION =
>>> *"axis.form.optimization"*;
>>>
>>> is either not set or is defined as "true".
>>>
>>> When using the interop testcase for the WSS4JHandler this property is
>>> set to "false", thus
>>> preventing the handler to replace the SOAPPart content. This causes
>>> errors in the tests.
>>>
>>> The main difference between the mentioned interop testcase and our
>>> other
>>> interop testcases is, that only this specific testcase uses a fully
>>> dynamic setup of the handler, i.e
>>> does not use a client side deployment file. Pls refer to
>>> TestJAXRPCHandler.java in test/interop.
>>>
>>> I haven't looked into the Axis sources in more detail, but it seems
>>> that
>>> there are
>>> some differences between deployment file and dynamic handler setup.
>>>
>>> Can you check that?
>>>
>>> Regards
>>> Werner
>>>
>>> BTW, I've checked the ant target to generate a binary distributin, works
>>> so far.
>>> Also modified to use the enhanced timestamps, tests ok so far. Now I'm
>>> doing some upgrades/remove of warings during Javadoc generation to get
>>> a more clean distri. I'll checking during the weekend.
>>>
>>> Werner
>>>
>>>
>>> --
>>> Davanum Srinivas - http://webservices.apache.org/~dims/
>>>
>>>
>>
>>
>
>