looking for jar files
where can I find jar files for these three imports? import org.apache.ws.axis2.mtomsample.AttachmentResponse; import org.apache.ws.axis2.mtomsample.AttachmentType; import org.w3.www._2005._05.xmlmime.Base64Binary;
Re: Creating a async web sercice
2009/9/16 Håkon Sagehaug > Hi > > > I wanted to try out to make a web service async, does anyone know of a > cookbook how to do that? I found this link[1] explaning how I want my > service to work. is it the AsyncMessageReceiver from the integration module > in axis2 svn I should use? Basically I need som help and guide how to enable > async behavior on the server side, I know how to do it on the client side, > for getting a non-blocking using two transport channels. > > any tips or hint on this topic? > you need to set this parameter messageReceiver.invokeOnSeparateThread to true in your service. ie. true if the request contains a replyTo header service invocation happens in a separate thread. thanks, Amila. > cheers, Håkon > > > [1] http://www.ibm.com/developerworks/webservices/library/ws-axis2/ > > -- > Håkon Sagehaug, Scientific Programmer > Parallab, Bergen Center for Computational Science (BCCS) > UNIFOB AS (University of Bergen Research Company) > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: specifying that the operation parameter should be base64Binary encoded string
On Wed, Sep 16, 2009 at 4:54 PM, ghader wrote:
> I have an operation in my service which is like:
>
> public DataHandler loadData(String key)
> {...}
>
> I want to specify that the input parameter of the operation should be a
> base64Binary encoded string. How can I do this? I think that I should add
> something to my service.xml but I don't know what to add.
> could anyone help?
>
try false
if you have not enable mtom then it only takes base64binary.
thanks,
Amila
>
> Thanks
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Axis2 timeouts configuration
On Wed, Sep 16, 2009 at 6:35 PM, Moley Harey wrote: > Hi, yes here is the error trace in the server side: > org.apache.axis2.AxisFault > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) > at > org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83) > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:337) > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:214) > at > org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530) > at > org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:416) > at > org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:379) > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:167) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) > Caused by: com.ctc.wstx.exc.WstxIOException: null > at > com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313) > at > org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:146) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:472) > at > org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79) > ... 20 more > Caused by: ClientAbortException: java.net.SocketException: Broken pipe > at > org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319) > at > org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288) > at > org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98) > at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99) > at > com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214) > at > com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:311) this happens due to time out in client side. So increase the client side time you using the above mentioned option. thanks, Amila. > > > > 2009/9/16 Chinmoy Chakraborty > >> do you have any exception in the server side? send me the complete stack >> trace...you can also put a breakpoint and debug... >> >> >> >> >> >> On Wed, Sep 16, 2009 at 3:24 PM, Moley Harey wrote: >> >>> Hi again, >>> I am getting the following exception: "org.apache.axis2.AxisFault: Read >>> timed out" >>> >>> I have generated the Client-side stub classes to connect with my web >>> service using the wsdl2java Tool, in which class of the Client-side stub >>> should i set this "options.setTimeOutInMilliSeconds(60);" code? In the >>> Skeleton one? >>> >>> Also, is possible to configure the timeout in the server side using the >>> axsi2.xml paremeter "ConfigContextTimeoutInterval"? >>> >>> The default value for Axis2 web services timeout is 60 seconds, isn't it? >>> >>> thank you, >>> >>> Mh >>> >>> 2009/9/16 Chinmoy Chakraborty >>> >>> what exception you are getting? can you share your log? yes you can configure timeout in the client side..like options.setTimeOutInMilliSeconds(60); On Wed, Sep 16, 2009 at 2:12 PM, Moley Harey wrote: > Hi folks! > > I have implemented an Axis2 web service to retrieve some publication > data stored remotely in a web server. > I have done some tests and everything runs well but I have noticed that > if I do several consecutive calls to the web service I receive "Timeouts" > responses in the client side and I see that Axis exception in my log > files. > > Is there any way to configure the timeout response in my web service? > Or that timeout sho
Re: array with no elements
On Wed, Sep 16, 2009 at 7:14 PM, Mauro Molinari wrote: > Pär Malmqvist ha scritto: > >> When my adb Axis2 service should return an array with no elements to my >> client it looks like the client >> receives null instead of an array with zero elements. >> > > I also noticed that an Axis2 client "decodes" an "empty" array as null and > I don't know of any way to configure this. If you are working with other > clients (.NET ones?), maybe the convention adopted is the same. > > I think that the main reason of the ambiguity between "empty array" and > "null array" in web services is that it is not clear how to distinguish the > two cases given a SOAP message (that carries such an array) structured > following the XML Schema definition of a document/literal WSDL. > yes this is the reason. The only solution is to check both conditions at the client side when writing the business logic. eg. if ((array == null) or (array[0] == null) ) thanks, Amila. > > -- > Mauro Molinari > Software Designer & Developer > E-mail: mauro.molin...@cardinis.com > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL URL is Changing
what is the axis2 version you use? there is a commented parameter in axis2.xml. try changing that. thanks, Amila. On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera wrote: > My Application is deployed on JBOSS Application server (SSL enabled) and > WSDL access URL is https://localhost:9002/web/services/PayfoneWS?wsdl > > For some reason its going to redirect to > https://localhost:9002/axis2/services/PayfoneWS?wsdl > > > > I haven’t specify /axis2/ any were and also my filter in web.xml is as > follows, > > > > > > AxisServlet > > > org.apache.axis2.transport.http.AxisServlet > > 1 > > > > > > > > AxisServlet > > /services/* > > > > > > > > Also, in the later time some home client end point change to > https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this > end point is not working > > > > Thanks in advance. > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Axis2 1.5/Rampart 1.4 - XML Signatures - forwarding but not checking
I forgot to mention, Axis2 1.5, I am using the stand alone server under Windows 2003 server. I am not using Tomcat or some other container. ...Lyall -- View this message in context: http://www.nabble.com/Axis2-1.5-Rampart-1.4---XML-Signatures---forwarding-but-not-checking-tp25485520p25485544.html Sent from the Axis - User mailing list archive at Nabble.com.
Axis2 1.5/Rampart 1.4 - XML Signatures - forwarding but not checking
Hi. I have a request which has been signed by Oracle Web Services Manager (OWSM 10g) and forwarded to my Axis2 service (Java). I don't want Axis to verify the signatures, I simply want to forward the message on, in this case, by placing the message on a JMS queue. The signatures will be validated by OWSM, elsewhere. I am having problems getting Axis to simply accept the requests so I can write them to a JMS Queue (ActiveMQ in this case), xml signatures and all. At the moment, Axis is failing to understand the headers that are being supplied by OWSM. See further down for sample input/output I have installed rampart 1.4 in Axis2-1.5 but done no further configuration. Can anyone point me in the right direction to be able to configure/setup such a service? I already have a service which receives the envelope body and writes the body contents to JMS. ie. 1. Receive request which is signed 2. forward the request, signature headers and all, to JMS What I have at the other end is a java program to read the JMS message and then invoke the OWSM end point, which validates the signature and forwards it on. I need to figure out how to build the new request from the JMS message and forward it on. I already have a program which reads the body and simply forwards the body - the header stuff is new. I would not normally write the web service and program but OWSM does not support any JMS but Tibco and we are not using Tibco. Of course, if there are any better suggestions, I am all ears. Any assistance would be greatly appreciated. ...Lyall Sample input/output follows Supplied with (sorry about the length) http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; env:mustUnderstand="1"> http://www.w3.org/2000/09/xmldsig#"; xmlns:dsig="http://www.w3.org/2000/09/xmldsig#";> http://www.w3.org/2001/10/xml-exc-c14n#"/> http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> http://www.w3.org/2001/10/xml-exc-c14n#"/> http://www.w3.org/2000/09/xmldsig#sha1"/> Qe4IMCi2M9PFRCVKai0H+kXdRYU= http://www.w3.org/2001/10/xml-exc-c14n#"/> http://www.w3.org/2000/09/xmldsig#sha1"/> pG8ORuahQNUiqFU4IIJ+9Azap1E= ...deleted... http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"; EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"; wsu:Id="BST-g06EW1tza1vgdPbWqj7b7g22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>...deleted... http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="_JjRa246UcxFHtYJLGoYG5g22"> 2009-09-17T06:54:48Z http://namespace/jmsmessage";> 42f74ff13911efbd:-c9d11:123c5b13aca:-7121 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";> Users deleted SOMEWHERE Axis responds with http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/";> axis2ns4:MustUnderstand Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security null Stack trace of the Axis2 server is [INFO] Listening on port 8080 [ERROR] Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security at org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:97) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:267) at org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281) at org.apache.axis2.transport.http.server.AxisHttpSer
Re: Problems encountered when upgrading from 1.4.1 to 1.5
On Tue, Sep 15, 2009 at 14:49, GOOSSENS Wim wrote: > Hi all, > > Got 2 problems when upgrading to 1.5 (deployed in tomcat 6.0.18) > > 1. In 1.5 , only in the war distribution, the > geronimo-jta_1.1_spec-1.1.jar is included in the lib > This gives me problems when getting a UserTransation (class cast exception) > This problem is solved by removing geronimo-jta_1.1_spec-1.1.jar (correct > javaee.jar is in the tomcat/lib) > > > 2. Version 1.5 goes back from xerces 2.8.1 to xerces 2.6.2 > > - Why is this ? I get problems with the reset method not being know by > 2.6.2 Is this method used by your code or is it used by Axis2? > - Is it save to put xerces 2.8.1 in the lib or should i use 2.9.1 > instead > (1.5 seems to work with xerces 2.8.1 and 2.9.1) > > Regards > Wim > > >
WSDL URL is Changing
My Application is deployed on JBOSS Application server (SSL enabled) and WSDL access URL is https://localhost:9002/web/services/PayfoneWS?wsdl For some reason its going to redirect to https://localhost:9002/axis2/services/PayfoneWS?wsdl I haven't specify /axis2/ any were and also my filter in web.xml is as follows, AxisServlet org.apache.axis2.transport.http.AxisServlet 1 AxisServlet /services/* Also, in the later time some home client end point change to https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this end point is not working Thanks in advance.
Re: array with no elements
Pär Malmqvist ha scritto: When my adb Axis2 service should return an array with no elements to my client it looks like the client receives null instead of an array with zero elements. I also noticed that an Axis2 client "decodes" an "empty" array as null and I don't know of any way to configure this. If you are working with other clients (.NET ones?), maybe the convention adopted is the same. I think that the main reason of the ambiguity between "empty array" and "null array" in web services is that it is not clear how to distinguish the two cases given a SOAP message (that carries such an array) structured following the XML Schema definition of a document/literal WSDL. -- Mauro Molinari Software Designer & Developer E-mail: mauro.molin...@cardinis.com
Re: Wrong response when authentication fails with Rampart (not SOAP but HTML)
hi nandana, I also tried it with axis2 1.5 and rampart 1.5 RC1 -> same result 0 [JHttp-3] 2009-09-16 15:02:14.459 AxisEngine - The security token could not be authenticated or authorized; nested exception is: javax.security.auth.callback.UnsupportedCallbackException: Auth check failed org.apache.axis2.AxisFault: The security token could not be authenticated or authorized; nested exception is: javax.security.auth.callback.UnsupportedCallbackException: Auth check failed at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:172) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95) at org.apache.axis2.engine.Phase.invoke(Phase.java:318) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:142) at javax.servlet.http.HttpServlet.service(HttpServlet.java:738) at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) at org.mortbay.jetty.handler.HandlerList.handle(HandlerList.java:49) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403) at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228) at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:635) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522) Caused by: org.apache.ws.security.WSSecurityException: The security token could not be authenticated or authorized; nested exception is: javax.security.auth.callback.UnsupportedCallbackException: Auth check failed at org.apache.ws.security.processor.UsernameTokenProcessor.handleUsernameToken(UsernameTokenProcessor.java:172) at org.apache.ws.security.processor.UsernameTokenProcessor.handleToken(UsernameTokenProcessor.java:56) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:326) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:243) at org.apache.rampart.RampartEngine.process(RampartEngine.java:154) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92) ... 24 more Caused by: javax.security.auth.callback.UnsupportedCallbackException: Auth check failed at com.groiss.ws.security.UserNameTokenAuthHandler.handle(UserNameTokenAuthHandler.java:39) at org.apache.rampart.TokenCallbackHandler.handle(TokenCallbackHandler.java:90) at org.apache.ws.security.processor.UsernameTokenProcessor.handleUsernameToken(UsernameTokenProcessor.java:160) ... 29 more 0 [JHttp-3] 2009-09-16 15:02:14.469 log - /wf/services.axis2/SecureTokenService java.lang.NullPointerException at org.apache.rampart.RampartMessageData.(RampartMessageData.java:372) at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61) at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64) at org.apache.axis2.engine.Phase.invoke(Phase.java:318) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251) at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:508) at org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:423) at org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:386) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:176) at javax.servlet.http.HttpServlet.service(HttpServlet.java:738) at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at org.mortbay.jetty.se
Re: Axis2 timeouts configuration
Hi, yes here is the error trace in the server side: org.apache.axis2.AxisFault at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:337) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:214) at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530) at org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:416) at org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:379) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:167) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: com.ctc.wstx.exc.WstxIOException: null at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313) at org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:146) at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:472) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79) ... 20 more Caused by: ClientAbortException: java.net.SocketException: Broken pipe at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288) at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98) at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99) at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214) at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:311) 2009/9/16 Chinmoy Chakraborty > do you have any exception in the server side? send me the complete stack > trace...you can also put a breakpoint and debug... > > > > > > On Wed, Sep 16, 2009 at 3:24 PM, Moley Harey wrote: > >> Hi again, >> I am getting the following exception: "org.apache.axis2.AxisFault: Read >> timed out" >> >> I have generated the Client-side stub classes to connect with my web >> service using the wsdl2java Tool, in which class of the Client-side stub >> should i set this "options.setTimeOutInMilliSeconds(60);" code? In the >> Skeleton one? >> >> Also, is possible to configure the timeout in the server side using the >> axsi2.xml paremeter "ConfigContextTimeoutInterval"? >> >> The default value for Axis2 web services timeout is 60 seconds, isn't it? >> >> thank you, >> >> Mh >> >> 2009/9/16 Chinmoy Chakraborty >> >> what exception you are getting? can you share your log? >>> >>> yes you can configure timeout in the client side..like >>> options.setTimeOutInMilliSeconds(60); >>> >>> On Wed, Sep 16, 2009 at 2:12 PM, Moley Harey wrote: >>> Hi folks! I have implemented an Axis2 web service to retrieve some publication data stored remotely in a web server. I have done some tests and everything runs well but I have noticed that if I do several consecutive calls to the web service I receive "Timeouts" responses in the client side and I see that Axis exception in my log files. Is there any way to configure the timeout response in my web service? Or that timeout should be configured in the Client-side? thank you, Mh >>> >>> >> >
Re: [ANNOUNCE] Rampart1.5 Release Candidate ready for testing
Hi, Why are there two different versions of opensaml included in the dist-package? Are there any obsolete jars if I'm using axis2 with java 1.5? regards, gerhard Nunny wrote: > > Hi All, > Apache Rampart 1.5 (Rampart version for Axis2 1.5) Release Candidate > is > available here. > > http://people.apache.org/~nandana/rampart-1.5/RC1/dist/ > > And the M2 repository can be found here. > http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/ > > Please test and report any issues you may find. > > regards, > Nandana > > -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25471798.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Wrong response when authentication fails with Rampart (not SOAP but HTML)
Hi!
I'm using Axis2 1.5 and Rampart 1.4 --> same problem :-(
regards,
Gerhard
Nunny wrote:
>
> Hi Giuseppe,
> Are you using Axis2 1.4.1 and Rampart 1.3 ? Can you try
> with
> Rampart 1.4 ?
>
> regards,
> Nandana
>
> On Fri, Jul 3, 2009 at 4:51 PM, Giuseppe Gortan
> wrote:
>
>> Hi everybody.
>>
>> I have a problem with axis2 (1.4.1) and rampart (1.3).
>> I put a simple policy in services.xml [1] and I wrote a
>> PasswordHandler [2]. Everything works fine if user and password are
>> correct. When the user doesn't exist (getUser returns
>> UserNotFoundException), the authentication process (correctly) fails,
>> but returning a HTML error page [5] instead of a SOAP response
>> message. The servlet engine logs an error message coming from the Axis
>> Servlet [4], and the SOAP client, that uses a library generated by
>> WSDL2Java, logs the error "First Element must contain the local name,
>> Envelope , but found html" [3].
>>
>> I want to return to the client a custom SOAP error message if
>> authentication process fails. How can I do it?
>>
>> Thanks,
>>
>> Giuseppe
>>
>>
>> [1] Policy
>>
>>
>>UsernameToken
>>
>>mypackage.myapp.PasswordHandler
>>
>>
>>
>>
>> [2] PasswordHandler
>> public class PasswordHandler implements CallbackHandler {
>>public void handle(Callback[] callbacks) throws IOException,
>> UnsupportedCallbackException {
>>for (int i = 0; i < callbacks.length; i++) {
>>if (callbacks[i] instanceof WSPasswordCallback) {
>>try{
>>WSPasswordCallback pwcb =
>> (WSPasswordCallback) callbacks[i];
>>String username =
>> pwcb.getIdentifer();
>>String user = getUser(username);
>>String password =
>> getPlainPassword(user);
>>
>>int passwordType =
>> pwcb.getUsage();
>>if (passwordType ==
>> WSPasswordCallback.USERNAME_TOKEN) {
>>
>> pwcb.setPassword(password);
>>} else {
>>throw new
>> UnsupportedCallbackException(callbacks[i],
>> "Unrecognized Callback");
>>}
>>} catch (UserNotFoundException e){
>> throw new AxisFault("No user found",
>> e.getCause());
>> }
>>}
>>}
>> }
>>
>> [3] First Element must contain the local name, Envelope , but found html
>> org.apache.axis2.AxisFault: First Element must contain the local name,
>> Envelope , but found html
>>at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>>at
>> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)
>>at
>> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
>>at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
>>at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
>>at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>>at
>> mypackage.myapp.WebservicesStub.myRemoteWS(WebservicesStub.java:6642)
>>at mypackage.myapp.client.Client.main(Client.java:63)
>> Caused by: org.apache.axiom.soap.SOAPProcessingException: First
>> Element must contain the local name, Envelope , but found html
>>at
>> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:251)
>>at
>> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209)
>>at
>> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191)
>>at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172)
>>at
>> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
>>at
>> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:105)
>>at
>> org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
>>at
>> org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
>>at
>> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
>>at
>> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
>>... 6 more
>>
>> [4] Error log
>> GRAVE: Servlet.serv
Re: array with no elements
I think the answer to this is to ensure you schema for the array is marked with the soapenc:array restriction. See the jax-rpc spec for details. jon. On 16/09/2009, at 22:29, Pär Malmqvist wrote: Hello! When my adb Axis2 service should return an array with no elements to my client it looks like the client receives null instead of an array with zero elements. Is this the way it should be or is it configurable? Regards Pär Malmqvist Share your memories online with anyone you want anyone you want.
array with no elements
Hello! When my adb Axis2 service should return an array with no elements to my client it looks like the client receives null instead of an array with zero elements. Is this the way it should be or is it configurable? Regards Pär Malmqvist _ Share your memories online with anyone you want. http://www.microsoft.com/middleeast/windows/windowslive/products/photos-share.aspx?tab=1
Re: Axis2 timeouts configuration
do you have any exception in the server side? send me the complete stack trace...you can also put a breakpoint and debug... On Wed, Sep 16, 2009 at 3:24 PM, Moley Harey wrote: > Hi again, > I am getting the following exception: "org.apache.axis2.AxisFault: Read > timed out" > > I have generated the Client-side stub classes to connect with my web > service using the wsdl2java Tool, in which class of the Client-side stub > should i set this "options.setTimeOutInMilliSeconds(60);" code? In the > Skeleton one? > > Also, is possible to configure the timeout in the server side using the > axsi2.xml paremeter "ConfigContextTimeoutInterval"? > > The default value for Axis2 web services timeout is 60 seconds, isn't it? > > thank you, > > Mh > > 2009/9/16 Chinmoy Chakraborty > > what exception you are getting? can you share your log? >> >> yes you can configure timeout in the client side..like >> options.setTimeOutInMilliSeconds(60); >> >> On Wed, Sep 16, 2009 at 2:12 PM, Moley Harey wrote: >> >>> Hi folks! >>> >>> I have implemented an Axis2 web service to retrieve some publication data >>> stored remotely in a web server. >>> I have done some tests and everything runs well but I have noticed that >>> if I do several consecutive calls to the web service I receive "Timeouts" >>> responses in the client side and I see that Axis exception in my log files. >>> >>> Is there any way to configure the timeout response in my web service? Or >>> that timeout should be configured in the Client-side? >>> >>> thank you, >>> >>> Mh >>> >> >> >
specifying that the operation parameter should be base64Binary encoded string
I have an operation in my service which is like:
public DataHandler loadData(String key)
{...}
I want to specify that the input parameter of the operation should be a
base64Binary encoded string. How can I do this? I think that I should add
something to my service.xml but I don't know what to add.
could anyone help?
Thanks
Creating a async web sercice
Hi I wanted to try out to make a web service async, does anyone know of a cookbook how to do that? I found this link[1] explaning how I want my service to work. is it the AsyncMessageReceiver from the integration module in axis2 svn I should use? Basically I need som help and guide how to enable async behavior on the server side, I know how to do it on the client side, for getting a non-blocking using two transport channels. any tips or hint on this topic? cheers, Håkon [1] http://www.ibm.com/developerworks/webservices/library/ws-axis2/ -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
Re: Axis2 timeouts configuration
Hi again, I am getting the following exception: "org.apache.axis2.AxisFault: Read timed out" I have generated the Client-side stub classes to connect with my web service using the wsdl2java Tool, in which class of the Client-side stub should i set this "options.setTimeOutInMilliSeconds(60);" code? In the Skeleton one? Also, is possible to configure the timeout in the server side using the axsi2.xml paremeter "ConfigContextTimeoutInterval"? The default value for Axis2 web services timeout is 60 seconds, isn't it? thank you, Mh 2009/9/16 Chinmoy Chakraborty > what exception you are getting? can you share your log? > > yes you can configure timeout in the client side..like > options.setTimeOutInMilliSeconds(60); > > On Wed, Sep 16, 2009 at 2:12 PM, Moley Harey wrote: > >> Hi folks! >> >> I have implemented an Axis2 web service to retrieve some publication data >> stored remotely in a web server. >> I have done some tests and everything runs well but I have noticed that if >> I do several consecutive calls to the web service I receive "Timeouts" >> responses in the client side and I see that Axis exception in my log files. >> >> Is there any way to configure the timeout response in my web service? Or >> that timeout should be configured in the Client-side? >> >> thank you, >> >> Mh >> > >
Re: Axis2 timeouts configuration
what exception you are getting? can you share your log? yes you can configure timeout in the client side..like options.setTimeOutInMilliSeconds(60); On Wed, Sep 16, 2009 at 2:12 PM, Moley Harey wrote: > Hi folks! > > I have implemented an Axis2 web service to retrieve some publication data > stored remotely in a web server. > I have done some tests and everything runs well but I have noticed that if > I do several consecutive calls to the web service I receive "Timeouts" > responses in the client side and I see that Axis exception in my log files. > > Is there any way to configure the timeout response in my web service? Or > that timeout should be configured in the Client-side? > > thank you, > > Mh >
Axis2 timeouts configuration
Hi folks! I have implemented an Axis2 web service to retrieve some publication data stored remotely in a web server. I have done some tests and everything runs well but I have noticed that if I do several consecutive calls to the web service I receive "Timeouts" responses in the client side and I see that Axis exception in my log files. Is there any way to configure the timeout response in my web service? Or that timeout should be configured in the Client-side? thank you, Mh
