RE: Axis 1.2FINAL support for HTTP1.1 and Keep-Alive
Hi John, I have already tried your suggestion ans it is working. I now have a persistent connection with the target web server. Now after making my last SOAP call to the web server, how do I tell CommonsHTTPSender to close its connection? Because when I do a netstat, I see all my connections in established state. Thanks! ChrisJohn Babbidge <[EMAIL PROTECTED]> wrote: Hi Chris, You'll need the following line in your client-side wsdd as follows: The wsdd should be placed in the clients classpath. Can someone confirm this behavior has not change for 1.2 final? John -Original Message-From: Chris Averia [mailto:[EMAIL PROTECTED]Sent: Monday, May 30, 2005 7:18 PMTo: axis-user@ws.apache.org; [EMAIL PROTECTED]; Carolina MoraisSubject: Re: Axis 1.2FINAL support for HTTP1.1 and Keep-Alive Hello Davanum, How do I set Axis to use CommonsHTTPSender instead of the default HTTPSender? Which java source file I need to modify for that? The reason I want a keep-alive support is that I make a sequence of SOAP calls to a Web Server (I use the stub classes generated by WSDL2Java for that). So for thoughput to be faster, I want my HTTP connection to be persistent. But lets say after I make my last SOAP call, I want the HTTPSender to close the connection. How do I do that? Thanks a lot! ChrisDavanum Srinivas <[EMAIL PROTECTED]> wrote: You can use CommonsHTTPSender with Jakarta commons HTTPClient library.-- dimsOn 5/30/05, Carolina Morais <[EMAIL PROTECTED]>wrote:> Hi Chris,> > The Axis implementation don't support Keep-Alive. Axis always closes> the connection.> See the HttpSender class.> > Ana Carolina.> > On 5/29/05, Chris Averia <[EMAIL PROTECTED]>wrote:> > Hi,> >> > How do I use HTTP 1.1 and Keep-Alive in my axis client? Im using the> > classes compiled by wsdl2java. Im using Axis1.2final.> >> > Thanks!> > Chris> >> > __> > Do You Yahoo!?> > Tired of spam? Yahoo! Mail has the best spam protection around> > http://mail.yahoo.com> -- Davanum Srinivas - http://webservices.apache.org/~dims/ Do You Yahoo!?Yahoo! Small Business - Try our new Resources site!__Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: multiple ws clients in one application
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Srinath Perera wrote: > Hi Nathaniel; > >>one question... does axis cache the file at startup, or does it >>reference it over and over for each call to a method on the web service? >> basically, should the system property be set before each call to the >>webservice, or would it be ok just to set it once in the constructor of >>the service? > > I am positive it is cached at the start up of Axis (e.g. creating the > call) even though I do > not remeber the exact code. If it does per each call .. that would be > a huge perforamnce overhead. i just ran a few tests and i believe you are correct. i created two clients and only set the system property before creating the clients. then called multiple methods on both clients and all were successful. you've been a great help! thank you! nate ps: my next goal is to figure out how to get the crypto.properties out of the classpath, as our system admins do not like passwords in the classpath. and then, for some reason, my signatures are working (at least the requestFlows) but the encryption is failing... not sure why yet, but i'm digging into that one too... keeps saying it can't find the alias in the keystore. > Thanks > Srinath -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCnRXVgj8ksIjnb2wRAmleAJ47rg1er0E/nzlXPYMlIVUzct/zvwCfd0si iFgpddna0opKbmSANHKeO5Y= =VcVt -END PGP SIGNATURE-
Re: multiple ws clients in one application
Hi Nathaniel; > one question... does axis cache the file at startup, or does it > reference it over and over for each call to a method on the web service? > basically, should the system property be set before each call to the > webservice, or would it be ok just to set it once in the constructor of > the service? I am positive it is cached at the start up of Axis (e.g. creating the call) even though I do not remeber the exact code. If it does per each call .. that would be a huge perforamnce overhead. Thanks Srinath
Re: multiple ws clients in one application
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi srinath, thanks for the advice! threads are not being created on purpose, but the applications are webapps, so i guess by default the serlvets are multithreaded. one question... does axis cache the file at startup, or does it reference it over and over for each call to a method on the web service? basically, should the system property be set before each call to the webservice, or would it be ok just to set it once in the constructor of the service? thanks! nate Srinath Perera wrote: > Hi Nathaniel; > > Before loading the client config file Axis look at this poperty, do > this to before each clinet before doing other things. Are u running > the Client in differnat thread, in that case this might be tricky > ..otherwise this should works > > System.setProperty( > EngineConfigurationFactoryDefault.OPTION_CLIENT_CONFIG_FILE, > client-config-file-path ) > > Thanks > Srinath > > Thanks > Srinath > > On 6/1/05, Nathaniel A. Johnson <[EMAIL PROTECTED]> wrote: > > hello everyone, > > we are building applications that use multiple axis web service clients > to talk to multiple services. because of this, we can not set a system > property or have a client-config.wsdd on the classpath, since there will > be more than one. is there a way to programmatically load the > properties for the client-config.wsdd into the client for each ws client > piece? > > if not, can someone point me to code that does this loading so that i > can try to re-write it a bit to meet our needs? > > maybe i am just going about this the wrong way? does anyone have any > better ideas or advice for me? > > many thanks! > nate > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCnRASgj8ksIjnb2wRAlxoAJ9ij2wUr3NJ+rEBv87OoN2i0RnfsACfZl5R tOHLlxu79/1/v58rSxs/X3o= =IMfO -END PGP SIGNATURE-
Re: multiple ws clients in one application
Hi Nathaniel; Before loading the client config file Axis look at this poperty, do this to before each clinet before doing other things. Are u running the Client in differnat thread, in that case this might be tricky ..otherwise this should works System.setProperty( EngineConfigurationFactoryDefault.OPTION_CLIENT_CONFIG_FILE, client-config-file-path ) Thanks Srinath Thanks Srinath On 6/1/05, Nathaniel A. Johnson <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > hello everyone, > > we are building applications that use multiple axis web service clients > to talk to multiple services. because of this, we can not set a system > property or have a client-config.wsdd on the classpath, since there will > be more than one. is there a way to programmatically load the > properties for the client-config.wsdd into the client for each ws client > piece? > > if not, can someone point me to code that does this loading so that i > can try to re-write it a bit to meet our needs? > > maybe i am just going about this the wrong way? does anyone have any > better ideas or advice for me? > > many thanks! > nate > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.0 (MingW32) > > iD8DBQFCnQQfgj8ksIjnb2wRAsaeAJ9/7tOfD57LGP0+0NOrc4iiLjahJgCggkRa > M1utac68ug0/U0rAsh+V3bE= > =8hLO > -END PGP SIGNATURE- >
two-dimensional array
I'm trying to use WSDL with SOAP when i use java2wsdl to generate a java file my two-dimensional array of an complex type was not generated in my wsdl file so how I should express two-dimensional array in a wsdl file? someone has an example? thanx _ Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vidéos ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com
multiple ws clients in one application
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hello everyone, we are building applications that use multiple axis web service clients to talk to multiple services. because of this, we can not set a system property or have a client-config.wsdd on the classpath, since there will be more than one. is there a way to programmatically load the properties for the client-config.wsdd into the client for each ws client piece? if not, can someone point me to code that does this loading so that i can try to re-write it a bit to meet our needs? maybe i am just going about this the wrong way? does anyone have any better ideas or advice for me? many thanks! nate -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCnQQfgj8ksIjnb2wRAsaeAJ9/7tOfD57LGP0+0NOrc4iiLjahJgCggkRa M1utac68ug0/U0rAsh+V3bE= =8hLO -END PGP SIGNATURE-
RE: Axis 1.2FINAL support for HTTP1.1 and Keep-Alive
Hi John, Do you have any sample for a client-side wsdd file? What are the elements I need to define there? I have now a server-config.wsdd but I dont what elements I need to define in a client-side.wsdd... Thanks Chris John Babbidge <[EMAIL PROTECTED]> wrote: Hi Chris, You'll need the following line in your client-side wsdd as follows: The wsdd should be placed in the clients classpath. Can someone confirm this behavior has not change for 1.2 final? John -Original Message-From: Chris Averia [mailto:[EMAIL PROTECTED]Sent: Monday, May 30, 2005 7:18 PMTo: axis-user@ws.apache.org; [EMAIL PROTECTED]; Carolina MoraisSubject: Re: Axis 1.2FINAL support for HTTP1.1 and Keep-Alive Hello Davanum, How do I set Axis to use CommonsHTTPSender instead of the default HTTPSender? Which java source file I need to modify for that? The reason I want a keep-alive support is that I make a sequence of SOAP calls to a Web Server (I use the stub classes generated by WSDL2Java for that). So for thoughput to be faster, I want my HTTP connection to be persistent. But lets say after I make my last SOAP call, I want the HTTPSender to close the connection. How do I do that? Thanks a lot! ChrisDavanum Srinivas <[EMAIL PROTECTED]> wrote: You can use CommonsHTTPSender with Jakarta commons HTTPClient library.-- dimsOn 5/30/05, Carolina Morais <[EMAIL PROTECTED]>wrote:> Hi Chris,> > The Axis implementation don't support Keep-Alive. Axis always closes> the connection.> See the HttpSender class.> > Ana Carolina.> > On 5/29/05, Chris Averia <[EMAIL PROTECTED]>wrote:> > Hi,> >> > How do I use HTTP 1.1 and Keep-Alive in my axis client? Im using the> > classes compiled by wsdl2java. Im using Axis1.2final.> >> > Thanks!> > Chris> >> > __> > Do You Yahoo!?> > Tired of spam? Yahoo! Mail has the best spam protection around> > http://mail.yahoo.com> -- Davanum Srinivas - http://webservices.apache.org/~dims/ Do You Yahoo!?Yahoo! Small Business - Try our new Resources site! Do You Yahoo!? Yahoo! Small Business - Try our new Resources site!
Re: UserGuide Calculator example broken in Axis 1.2?
Apologies. I realized it was a problem with the server - I was using
Tomcat 5.0.27. Have just updated to 5.5.9 and it works fine.
Madeleine
MKW wrote:
Just trying out the 1.2 Axis. Deployed the userguide Calculator class
as a service (not jws) inside a "calc" package. Found the client didn't
work any more - but it did in the last version. It now produces the
error message given at the end.
Also experimented capturing the generated wsdl - used a very basic wsdd
file for deployment:
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
Generated SOAP requests in both XMLSpy and Oxygen. They both generated
basically the same:
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
http://calc";
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
INT
INT
I added values and sent them but the response came back from each:
org.apache.commons.httpclient.HttpException :
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>soapenv:Server.generalExceptionjava.lang.IncompatibleClassChangeError;
nested exception is:
java.lang.IncompatibleClassChangeErrorxmlns:ns1="http://xml.apache.org/axis/";>Mad
Is something broken - or am I missing something??
Madeleine
(exception from Client)
Exception in thread "main" AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: java.lang.IncompatibleClassChangeError; nested exception is:
java.lang.IncompatibleClassChangeError
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:Mad
java.lang.IncompatibleClassChangeError; nested exception is:
java.lang.IncompatibleClassChangeError
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:784)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at CalcClient.main(CalcClient.java:47)
RE: dynamic web service location?
Looks like there is something in the Axis docs but is not completed yet on how to accomplish this: "Dynamically Discovering and Binding to a Web Service When Axis generates client proxy classes code from WSDL, it binds the code to the endpoint URL specified in the WSDL -this is usually a URL generated from the URL of the inbound request. Using a http://localhost URL to fetch a WSDL page will result in client code also bound to a service served up on the localhost, which is not what you want in a redistributable. Similarly, even if you use the hostname when fetching the WSDL, you need the fully qualified domain name, not any short name -http://s1.example.org/ and not http://s1/ -otherwise only callers in your own domain or subnet will be able to find the server. Hand-written WSDL does not exhibit this problem; the endpoint in the WSDL is the one the author typed in. It is almost essential that you provide some way to update the URL on the clients. The simplest is some command line override option, as used in the Axis command line tools. More advanced is a dialog box for entering URLs, and more advanced yet is some automated discovery mechanism. Axis does not provide any discovery mechanism in the JAR. There is a sibling project, jUDDI, that provides access to UDDI registries. There is also a multicast discovery jar that works with Axis in the Axis CVS tree; this is a proof-of-concept mechanism that uses XML messages but is not compatible with any existing standard. It works OK over LAN networks, but is not designed to be used over wider area. TODO: how to set the URL in a service" Anyone have any ideas on how to accomplish this? Thanks! -Original Message- From: James Taylor [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 31, 2005 6:03 PM To: axis-user@ws.apache.org Subject: Re: dynamic web service location? Think you may have to configure tomcat or your webapp to listen on a port and access your service through there. Not sure how to do this!! Quoting Carolyn Vo <[EMAIL PROTECTED]>: > Hello, > > > > Is it possible to specify the server and port number for a web service > during runtime? The default in my wsdl file is hardcoded to localhost:8080 > but I want the user to be able to specify it during runtime. How is this > possible? > > > > Thanks, > > Carolyn > > -- Between the question and the answer lies free will
Re: dynamic web service location?
Think you may have to configure tomcat or your webapp to listen on a port and access your service through there. Not sure how to do this!! Quoting Carolyn Vo <[EMAIL PROTECTED]>: > Hello, > > > > Is it possible to specify the server and port number for a web service > during runtime? The default in my wsdl file is hardcoded to localhost:8080 > but I want the user to be able to specify it during runtime. How is this > possible? > > > > Thanks, > > Carolyn > > -- Between the question and the answer lies free will
RE: Axis 1.2FINAL support for HTTP1.1 and Keep-Alive
Hi Chris, You'll need the following line in your client-side wsdd as follows: The wsdd should be placed in the clients classpath. Can someone confirm this behavior has not change for 1.2 final? John -Original Message-From: Chris Averia [mailto:[EMAIL PROTECTED]Sent: Monday, May 30, 2005 7:18 PMTo: axis-user@ws.apache.org; [EMAIL PROTECTED]; Carolina MoraisSubject: Re: Axis 1.2FINAL support for HTTP1.1 and Keep-Alive Hello Davanum, How do I set Axis to use CommonsHTTPSender instead of the default HTTPSender? Which java source file I need to modify for that? The reason I want a keep-alive support is that I make a sequence of SOAP calls to a Web Server (I use the stub classes generated by WSDL2Java for that). So for thoughput to be faster, I want my HTTP connection to be persistent. But lets say after I make my last SOAP call, I want the HTTPSender to close the connection. How do I do that? Thanks a lot! ChrisDavanum Srinivas <[EMAIL PROTECTED]> wrote: You can use CommonsHTTPSender with Jakarta commons HTTPClient library.-- dimsOn 5/30/05, Carolina Morais <[EMAIL PROTECTED]>wrote:> Hi Chris,> > The Axis implementation don't support Keep-Alive. Axis always closes> the connection.> See the HttpSender class.> > Ana Carolina.> > On 5/29/05, Chris Averia <[EMAIL PROTECTED]>wrote:> > Hi,> >> > How do I use HTTP 1.1 and Keep-Alive in my axis client? Im using the> > classes compiled by wsdl2java. Im using Axis1.2final.> >> > Thanks!> > Chris> >> > __> > Do You Yahoo!?> > Tired of spam? Yahoo! Mail has the best spam protection around> > http://mail.yahoo.com> -- Davanum Srinivas - http://webservices.apache.org/~dims/ Do You Yahoo!?Yahoo! Small Business - Try our new Resources site!
dynamic web service location?
Hello, Is it possible to specify the server and port number for a web service during runtime? The default in my wsdl file is hardcoded to localhost:8080 but I want the user to be able to specify it during runtime. How is this possible? Thanks, Carolyn
weird error when I try to invoke service
Hey folks, I've this ant build file that I use to deploy a axis web service but I get the following error - > [java] Exception in thread "main" java.lang.IncompatibleClassChangeError > [java] at > arg.apache.axis.message.MessageElement.addTextNode(MessageElement.java:13= > 87) > [java] at > org.apache.axis.message.SOAPHandler.endElement(SOAPHandler.java:118) > followed by lots more errors and... > BUILD FAILED ...which i get when I try to run the axis admin deploy tool using this task: > s server. depends =3D deploy"> > > failonerror=3D"true"> > > > > > > > I know there is an ant task for this but I find this easier. I know that axis.jar is in the classpath. But the problem is that even though I get this error the service is deployed on axis. I get no error when I run the admin client of the command line with the following command: > java -cp "C:\Program Files\Apache\axis-1_2\lib\axis.jar;C:\Program > Files\Apache\axis-1_2\lib\jaxrpc.jar;C:\Program > Files\Apache\axis-1_2\lib\commons-logging.jar;C:\Program > Files\Apache\axis-1_2\lib\commons-discovery.jar;%CATALINA_HOME%\webapps\a= > xis\WEB-INF\lib\saaj-api.jar;%CATALINA_HOME%\common\lib\activation.jar;%C= > ATALINA_HOME%\common\lib\mail.jar;." > org.apache.axis.client.AdminClient -p 7070../src/flightCompany/rpcservice/deploy.wsdd ... and this ant task worked for me before. This really bugs me because it fails the build and I can't understand why??!! Here's a link to the problem that I posted to sun when looking for help that has the wsdl for the service - http://forum.java.sun.com/thread.jspa?threadID=3D631449&tstart=3D0 I used java2wsdl and wsdl2java tools to generate stubs for the service but when I use the client to invoke the service tcp monitor shows me this error,(any help to resolve this greatly appreciated) >HTTP/1.1 500 Internal Server Error >Content-Type: text/html;charset=ISO-8859-1 >Content-Language: en-IE >Date: Tue, 31 May 2005 21:44:50 GMT >Server: Apache-Coyote/1.1 >Connection: close >description > The server encountered an internal error () that prevented >it from fulfilling this request. > > > exception >massive error list...blah blah... > > > root cause > java.lang.IncompatibleClassChangeErrorat > org.apache.axis.message.MessageElement.addTextNode(MessageElement.java:13= > 87)at > org.apache.axis.message.SOAPHandler.endElement(SOAPHandler.java:118)at > org.apache.axis.encoding.DeserializationContext.endElement(Deserializatio= > nContext.java:1083)at > org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown > Source)at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDisp= > atcher.dispatch(Unknown > Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un= > known > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at javax.xml.parsers.SAXParser.parse(Unknown Source) > at > org.apache.axis.encoding.DeserializationContext.parse(DeserializationCont= > ext.java:226) > at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645) > at org.apache.axis.Message.getSOAPEnvelope(Message.java:424) > at org.apache.axis.server.AxisServer.invoke(AxisServer.java:279) > at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:65= > 3) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:716) > at > org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.ja= > va:301) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat= > ionFilterChain.java:200) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte= > rChain.java:146) > Blah Blah BlahCan post the rest of the error if it helps -- Between the question and the answer lies free will -- Between the question and the answer lies free will
UserGuide Calculator example broken in Axis 1.2?
Just trying out the 1.2 Axis. Deployed the userguide Calculator class
as a service (not jws) inside a "calc" package. Found the client didn't
work any more - but it did in the last version. It now produces the
error message given at the end.
Also experimented capturing the generated wsdl - used a very basic wsdd
file for deployment:
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
Generated SOAP requests in both XMLSpy and Oxygen. They both generated
basically the same:
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
http://calc";
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
INT
INT
I added values and sent them but the response came back from each:
org.apache.commons.httpclient.HttpException :
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>soapenv:Server.generalExceptionjava.lang.IncompatibleClassChangeError;
nested exception is:
java.lang.IncompatibleClassChangeErrorxmlns:ns1="http://xml.apache.org/axis/";>Mad
Is something broken - or am I missing something??
Madeleine
(exception from Client)
Exception in thread "main" AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: java.lang.IncompatibleClassChangeError; nested exception is:
java.lang.IncompatibleClassChangeError
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:Mad
java.lang.IncompatibleClassChangeError; nested exception is:
java.lang.IncompatibleClassChangeError
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:784)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at CalcClient.main(CalcClient.java:47)
isOnlyLiteralReferenced question
Using this WSDL: http://207.142.131.5/testwsdl/population.xml I am creating a SymbolTable object and playing around with the Axis API. Upon examining the "getPopulation" operation, I retrieve its parameters and iterate through them. The problem that I am having is that I would expect the "getPopulation" TypeEntry object to have the isOnlyLiteralReferenced flag set to true. I've experimented with WSDLs that have a similar layout where the flag is set to true. Can anyone enlighten me as to why it would be false in this case? __ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/ __ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/
RE: Client authenticaion using certificates
If your server application is a J2EE web application, just configure your application server security service (the realm in Tomcat for example), to handle your client certificates, and just use the principal and roles in your web service server code. For the client code, i suppose you have to set up your HTTPS connection with the right keystore and ssl factory... In my opinion, your web service client code should not be aware of this security aspects, as it just use the endpoint URL to address requests, with no security or network knowledge... -- Ephemeris Lappis >>> -Original Message- >>> From: Christian Kunert [mailto:[EMAIL PROTECTED] >>> Sent: Tuesday, May 31, 2005 4:56 PM >>> To: axis-user@ws.apache.org >>> Subject: Client authenticaion using certificates >>> >>> >>> Hello everybody, >>> >>> I'm trying to create a client which uses certificate authentication. I >>> have a cert-file but I really don't know how the use it. Sorry, but I'm >>> a axis-newbie :-) >>> Should anybody show me a little workaround how to authenticate with this >>> certificate? >>> >>> Christian >>> Thanks! >>>
RE: Question about handlers
Be carefull, the MessageContext is an interface in JAXP-RPC standard API, not a class, and i don't know any class that provides a static access to the current call context. The class you mention is probably an axis specific class, and you may lose portability... >>> -Original Message- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>> Sent: Tuesday, May 31, 2005 4:08 PM >>> To: axis-user@ws.apache.org >>> Subject: RE: Question about handlers >>> >>> >>> You are right on target, from your XXXBindingImpl class you can >>> access the >>> current request's MessageContext by calling the static method >>> MessageContext.getCurrentContext(). From there all information that the >>> handlers have added into the MessageContext will be available. >>> >>> Underneath the hood, MessageContext.getCurrentContext() refererences a >>> ThreadLocal instance of MessageContext that is maintained by >>> the AxisEngine. >>> >>> Hope this helps, >>> Al >>> >>> Quoting Mark Ford <[EMAIL PROTECTED]>: >>> >>> > You can pass information between handlers in the chain using the >>> > MessageContext, but I don't see how you could pass >>> information directly to >>> > the service endpoint class. A workaround would be to install a custom >>> > handler in the chain and have this handler set the >>> credentials or other >>> > information on a static class with a ThreadLocal that you >>> could then read >>> > from your endpoint. >>> > >>> > -Original Message- >>> > From: Garzon Maldonado, Jesus Javier [mailto:[EMAIL PROTECTED] >>> > Sent: Tuesday, May 31, 2005 6:14 AM >>> > To: axis-user@ws.apache.org >>> > Subject: Question about handlers >>> > >>> > Hello all, >>> > >>> > Is there any way to pass data from handlers to service >>> implementations?, >>> > (that is, XXXBindingImpl classes) >>> > >>> > For example, a handler perform user authentication and service >>> > implementation needs that user to login a database. >>> > >>> > Thanks. >>> > >>> > Javi Garzón >>> > >>> > >>> >>>
RE: Question about handlers
I have not read all the passed messages of this thread, so excuse my idea if it doesn't match your needs and context : if the endpoint class is a J2EE endpoint ejb implementation, the session context provide a message context for this purpose... -- Ephemeris Lappis >>> -Original Message- >>> From: Mark Ford [mailto:[EMAIL PROTECTED] >>> Sent: Tuesday, May 31, 2005 3:49 PM >>> To: axis-user@ws.apache.org >>> Subject: RE: Question about handlers >>> >>> >>> You can pass information between handlers in the chain using the >>> MessageContext, but I don't see how you could pass information >>> directly to >>> the service endpoint class. A workaround would be to install a custom >>> handler in the chain and have this handler set the credentials or other >>> information on a static class with a ThreadLocal that you could >>> then read >>> from your endpoint. >>> >>> -Original Message- >>> From: Garzon Maldonado, Jesus Javier [mailto:[EMAIL PROTECTED] >>> Sent: Tuesday, May 31, 2005 6:14 AM >>> To: axis-user@ws.apache.org >>> Subject: Question about handlers >>> >>> Hello all, >>> >>> Is there any way to pass data from handlers to service implementations?, >>> (that is, XXXBindingImpl classes) >>> >>> For example, a handler perform user authentication and service >>> implementation needs that user to login a database. >>> >>> Thanks. >>> >>> Javi Garzón >>>
RE: missing derived types from the auto generated wsdl
Yes, it appears to be the same problem. The 1.2.1 interim drop contained the fix! Thank you, - Kris Original Message Follows From: "Dovholuk, Clint" <[EMAIL PROTECTED]> Reply-To: axis-user@ws.apache.org To: Subject: RE: missing derived types from the auto generated wsdl Date: Tue, 31 May 2005 12:02:53 -0400 Hi Kris, I've not tested the scenario myself, but I had a similar issue with a concrete class containing an abstract class... I posted a bug and your fix might be the same as the one posted for this bug: http://issues.apache.org/jira/browse/AXIS-1955?page=all I've not tested the latest patch release to see if it is fixed in the latest build, I am assuming it's fixed... Take a look at the latest build, it might be fixed by now. -Clint -Original Message- From: Kris Bradley [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 31, 2005 11:51 AM To: axis-user@ws.apache.org Subject: missing derived types from the auto generated wsdl Hi, I began with a WSDL file that contained complex types that extended other types (derived classes). The problem is that when I deploy this web service, Axis only includes the type information for the base types in the WSDL. So, the concrete types are not present in the WSDL, which makes the service unusable to clients. Is there a way to force Axis to include what was originally present in the WSDL and include these derived types? FYI, I'm using the release version of Axis 1.2. I wrote the WSDL by hand, then used to generate the Java classes, etc. I'm attempting to access this from a .NET client. I tried returning the original WSDL file, using in the .wsdd, but that doesn't work, either. - Kris
RE: missing derived types from the auto generated wsdl
Hi Kris, I've not tested the scenario myself, but I had a similar issue with a concrete class containing an abstract class... I posted a bug and your fix might be the same as the one posted for this bug: http://issues.apache.org/jira/browse/AXIS-1955?page=all I've not tested the latest patch release to see if it is fixed in the latest build, I am assuming it's fixed... Take a look at the latest build, it might be fixed by now. -Clint -Original Message- From: Kris Bradley [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 31, 2005 11:51 AM To: axis-user@ws.apache.org Subject: missing derived types from the auto generated wsdl Hi, I began with a WSDL file that contained complex types that extended other types (derived classes). The problem is that when I deploy this web service, Axis only includes the type information for the base types in the WSDL. So, the concrete types are not present in the WSDL, which makes the service unusable to clients. Is there a way to force Axis to include what was originally present in the WSDL and include these derived types? FYI, I'm using the release version of Axis 1.2. I wrote the WSDL by hand, then used to generate the Java classes, etc. I'm attempting to access this from a .NET client. I tried returning the original WSDL file, using in the .wsdd, but that doesn't work, either. - Kris
missing derived types from the auto generated wsdl
Hi, I began with a WSDL file that contained complex types that extended other types (derived classes). The problem is that when I deploy this web service, Axis only includes the type information for the base types in the WSDL. So, the concrete types are not present in the WSDL, which makes the service unusable to clients. Is there a way to force Axis to include what was originally present in the WSDL and include these derived types? FYI, I'm using the release version of Axis 1.2. I wrote the WSDL by hand, then used to generate the Java classes, etc. I'm attempting to access this from a .NET client. I tried returning the original WSDL file, using in the .wsdd, but that doesn't work, either. - Kris
Second stub call returns Connection Reset
I've searched this mailing list and haven't found this mentioned the way it's happening to me. Sorry if it's redundant. I have a standard Java class (not a servlet) sitting on the Tomcat v5.5.9 server. I'm using Java 1.5. I used the Installation Guide, User's Guide, and WSDL2Java to generate the client-side stubs for that class. The stub classes work fine for one call only. The second call across the stub returns a "java.net.SocketException: Connection Reset" and Tomcat shuts down. I get one good call with a correct value returned and then I get the exception. I've tried changing the scope (request, session, or application) in the server- config.wsdd file but it behaves the same. It also doesn't matter whether I make two calls within the client program or if I make a single call within the client program but run the client program twice. The second call fails. The Tomcat logs show no errors or exceptions or any explaination for why it shuts down. The second call doesn't get to my server-side class but fails somewhere within Tomcat or Axis. Thank you.
Client authenticaion using certificates
Hello everybody, I'm trying to create a client which uses certificate authentication. I have a cert-file but I really don't know how the use it. Sorry, but I'm a axis-newbie :-) Should anybody show me a little workaround how to authenticate with this certificate? Christian Thanks!
Re: Error in deserialization
Hi Anne, I've created stubs as you have suggested and I have 4 packages with several java in each There one java file EndUserIdentifier.java I've then looked at the method i'm trying to call (makeACall) that look like this : public String makeACall(EndUserIdentifier callingParty, EndUserIdentifier calledParty, String charging) The parameters i'm trying to pass are : callingParty = "tel:+44123456789;vnd.bt.cli-presentation=available";; calledParty = "tel:+44123456789;vnd.bt.cli-presentation=available";; String charging ="9F" By looking at the method callingParty and calledParty must be of type EndUserIdentifier, I think this is my problem, I am passing these values in as Strings but I must pass them in as EndUserIdentifier types but i'm not sure how i convert to this Am i looking in the right direction? Can you help me convert my callingParty and calledParty to type EndUserIdentifier? Thanks very much for your help From: Anne Thomas Manes <[EMAIL PROTECTED]> Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Subject: Re: Error in deserialization Date: Tue, 31 May 2005 08:34:38 -0400 Kumar, This WSDL imports another WSDL and two schemas. Can you send us those also? Also, can you tell us how you built and configured your client? I noticed that you're using the call interface. Have you tryied creating a stub client and invoking operations on the stub? Anne On 5/31/05, Plorks mail <[EMAIL PROTECTED]> wrote: > Hello again > > Sorry clicked send too soon > > In the 2nd WSDL there's another reference to a WSDL, heres that WSDL > > Thanks for any help you can ofer, much apreciated > > P > > > > - > - targetNamespace="http://www.csapi.org/wsdl/parlayx/common_faults/v1_0"; > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > - > > > - > > > - > > > - > > > - > > > - > > > > > > > >From: Anne Thomas Manes <[EMAIL PROTECTED]> > >Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]> > >To: axis-user@ws.apache.org > >Subject: Re: Error in deserialization > >Date: Sat, 28 May 2005 17:36:15 -0400 > > > >Kumar, > > > >The WSDL you sent me contains this import: > > > >> >namespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; > >location="parlayx_third_party_calling_service_port.wsdl" /> > > > >This imported WSDL contains the , , and > >definitions. I need to see this WSDL to answer your questions. > > > >Anne > > > >On 5/28/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > > > > > > > Sorry about the sending, i just clicked reply, didn't notice it wasn't > >the > > > axis-user > > > > > > What do you mean by the imported WSDL document? > > > > > > Many thanks for nay help > > > > > > > > > > > > > > > > > > > > > > > > >We also need the imported WSDL document. > > > > > > > >One problem I noticed with this WSDL is that it uses "rpc" style, but > > > >it doesn't specify a namespace attribute in the > > > >descriptions. > > > > > > > >Thanks, > > > >Anne > > > > > > > >On 5/27/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Here is the WSDL > > > > > > > > > > Thanks for any help > > > > > > > > > > > > > > > > > > > > - > > > > > - > > > > > > > > > >targetNamespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service"; > > > > > xmlns="http://schemas.xmlsoap.org/wsdl/"; > > > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > > > > > > > > >xmlns:tns="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service"; > > > > > > > > > > >xmlns:port="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port";> > > > > >> > > > > > > > > >namespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; > > > > > location="parlayx_third_party_calling_service_port.wsdl" /> > > > > > - > > >type="port:ThirdPartyCallPort"> > > > > >> > >transport="http://schemas.xmlsoap.org/soap/http"; > > > > > /> > > > > > - > > > > > style="rpc" > >/> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > >> > >style="rpc" > > > > > /> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > > style="rpc" /> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > >> > >style="rpc" > > > > > /> > > > > > - > > > > > > > >
RE: Question about handlers
I think this is what I'm looking for. Thanks. De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Enviado el: mar 31/05/2005 16:07 Para: axis-user@ws.apache.org Asunto: RE: Question about handlers You are right on target, from your XXXBindingImpl class you can access the current request's MessageContext by calling the static method MessageContext.getCurrentContext(). From there all information that the handlers have added into the MessageContext will be available. Underneath the hood, MessageContext.getCurrentContext() refererences a ThreadLocal instance of MessageContext that is maintained by the AxisEngine. Hope this helps, Al Quoting Mark Ford <[EMAIL PROTECTED]>: > You can pass information between handlers in the chain using the > MessageContext, but I don't see how you could pass information directly to > the service endpoint class. A workaround would be to install a custom > handler in the chain and have this handler set the credentials or other > information on a static class with a ThreadLocal that you could then read > from your endpoint. > > -Original Message- > From: Garzon Maldonado, Jesus Javier [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 31, 2005 6:14 AM > To: axis-user@ws.apache.org > Subject: Question about handlers > > Hello all, > > Is there any way to pass data from handlers to service implementations?, > (that is, XXXBindingImpl classes) > > For example, a handler perform user authentication and service > implementation needs that user to login a database. > > Thanks. > > Javi Garzón > > <>
RE: Question about handlers
You are right on target, from your XXXBindingImpl class you can access the current request's MessageContext by calling the static method MessageContext.getCurrentContext(). From there all information that the handlers have added into the MessageContext will be available. Underneath the hood, MessageContext.getCurrentContext() refererences a ThreadLocal instance of MessageContext that is maintained by the AxisEngine. Hope this helps, Al Quoting Mark Ford <[EMAIL PROTECTED]>: > You can pass information between handlers in the chain using the > MessageContext, but I don't see how you could pass information directly to > the service endpoint class. A workaround would be to install a custom > handler in the chain and have this handler set the credentials or other > information on a static class with a ThreadLocal that you could then read > from your endpoint. > > -Original Message- > From: Garzon Maldonado, Jesus Javier [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 31, 2005 6:14 AM > To: axis-user@ws.apache.org > Subject: Question about handlers > > Hello all, > > Is there any way to pass data from handlers to service implementations?, > (that is, XXXBindingImpl classes) > > For example, a handler perform user authentication and service > implementation needs that user to login a database. > > Thanks. > > Javi Garzón > >
RE: Cannot install Axis 1.2 in BEA WebLogic Workshop 8.1.2
Just skip using .jws files. -- Tom Jordahl Macromedia Server Development > -Original Message- > From: Jason Liu [mailto:[EMAIL PROTECTED] > Sent: Friday, May 27, 2005 4:24 PM > To: axis-dev@ws.apache.org > Cc: axis-user@ws.apache.org > Subject: Cannot install Axis 1.2 in BEA WebLogic Workshop 8.1.2 > > Hi there, > >I am trying to install axis 1.2 in WebLogic Workshop 8.1.2. I > followed the instructions on http://ws.apache.org/axis/java/install.html. > The problem is, WebLogic interprets .jws file as its own format (which > should contain annotations specific to WebLogic), so the out-of-box Axis > .jws file does not fit into Workshop. > > Anyone has suggestions on how to fix it? > > > Thanks, > > Jason >
Re: Error in deserialization
Hi Anne, Here are the 3 links to the WSDL files http://uddi.bt.com/WSDL/parlayx/thirdpartycallservice/rpc-lit/parlayx_third_party_calling_service.wsdl http://uddi.bt.com/WSDL/parlayx/thirdpartycallservice/rpc-lit/parlayx_third_party_calling_service_port.wsdl http://uddi.bt.com/WSDL/parlayx/thirdpartycallservice/rpc-lit/parlayx_common_faults.wsdl I can't see the reference to the schemas. Are they in the parlayx_common_faults.wsdl file? I have created a stub client but i'm unsure how to call it. I'm familiar with the Call interface and know how to use it. I've inc. my java file to invoke their uddi regesrty and call the method passing the parameters Thanks for your help From: Anne Thomas Manes <[EMAIL PROTECTED]> Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Subject: Re: Error in deserialization Date: Tue, 31 May 2005 08:34:38 -0400 Kumar, This WSDL imports another WSDL and two schemas. Can you send us those also? Also, can you tell us how you built and configured your client? I noticed that you're using the call interface. Have you tryied creating a stub client and invoking operations on the stub? Anne On 5/31/05, Plorks mail <[EMAIL PROTECTED]> wrote: > Hello again > > Sorry clicked send too soon > > In the 2nd WSDL there's another reference to a WSDL, heres that WSDL > > Thanks for any help you can ofer, much apreciated > > P > > > > - > - targetNamespace="http://www.csapi.org/wsdl/parlayx/common_faults/v1_0"; > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > - > > > - > > > - > > > - > > > - > > > - > > > > > > > >From: Anne Thomas Manes <[EMAIL PROTECTED]> > >Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]> > >To: axis-user@ws.apache.org > >Subject: Re: Error in deserialization > >Date: Sat, 28 May 2005 17:36:15 -0400 > > > >Kumar, > > > >The WSDL you sent me contains this import: > > > >> >namespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; > >location="parlayx_third_party_calling_service_port.wsdl" /> > > > >This imported WSDL contains the , , and > >definitions. I need to see this WSDL to answer your questions. > > > >Anne > > > >On 5/28/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > > > > > > > Sorry about the sending, i just clicked reply, didn't notice it wasn't > >the > > > axis-user > > > > > > What do you mean by the imported WSDL document? > > > > > > Many thanks for nay help > > > > > > > > > > > > > > > > > > > > > > > > >We also need the imported WSDL document. > > > > > > > >One problem I noticed with this WSDL is that it uses "rpc" style, but > > > >it doesn't specify a namespace attribute in the > > > >descriptions. > > > > > > > >Thanks, > > > >Anne > > > > > > > >On 5/27/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Here is the WSDL > > > > > > > > > > Thanks for any help > > > > > > > > > > > > > > > > > > > > - > > > > > - > > > > > > > > > >targetNamespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service"; > > > > > xmlns="http://schemas.xmlsoap.org/wsdl/"; > > > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > > > > > > > > >xmlns:tns="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service"; > > > > > > > > > > >xmlns:port="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port";> > > > > >> > > > > > > > > >namespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; > > > > > location="parlayx_third_party_calling_service_port.wsdl" /> > > > > > - > > >type="port:ThirdPartyCallPort"> > > > > >> > >transport="http://schemas.xmlsoap.org/soap/http"; > > > > > /> > > > > > - > > > > > style="rpc" > >/> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > >> > >style="rpc" > > > > > /> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > > style="rpc" /> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > >> > >style="rpc" > > > > > /> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > - > > >binding="tns:ThirdPartyCallBinding">
RE: Question about handlers
You can pass information between handlers in the chain using the MessageContext, but I don't see how you could pass information directly to the service endpoint class. A workaround would be to install a custom handler in the chain and have this handler set the credentials or other information on a static class with a ThreadLocal that you could then read from your endpoint. -Original Message- From: Garzon Maldonado, Jesus Javier [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 31, 2005 6:14 AM To: axis-user@ws.apache.org Subject: Question about handlers Hello all, Is there any way to pass data from handlers to service implementations?, (that is, XXXBindingImpl classes) For example, a handler perform user authentication and service implementation needs that user to login a database. Thanks. Javi Garzón
duplicate header elements
I'm having a problem with a WS client. Occassionally the client will put two duplicate elements in the header instead of just the required one. We pass in the request header object into the port's method call and two show up in the XML. This doesn't happen all the time, in fact quite rarely and it's random, we don't know when it will happen. I've been searching the old mail and Issue Navigator but haven't found anything so I thought I'd see if anyone had had this problem... Thanks in advance, Mike
Re: how to unsubscribe?
See instructions here: http://ws.apache.org/axis/mail. You must unsubscribe using the same email address that you subscribed with, and you must respond to the unsubscribe message that the mail server sends you. On 5/30/05, Yao Xu <[EMAIL PROTECTED]> wrote: > Hi, > > Please let me know how to unsubscribe this email list. > > Thanks > > Yao > > > > __ > Yahoo! Mail Mobile > Take Yahoo! Mail with you! Check email on your mobile phone. > http://mobile.yahoo.com/learn/mail >
Re: Question about handlers
Don't know if this is the best way, but I've done it through setting and
getting properties.
Handler
ctx.setProperty("USER", "SOME USER");
Implementation
String user = (String) ctx.getProperty("USER");
You can also setProperty in the implementation and have a post handler pick
it up with the getProperty.
Mark Malinoski
Consultant
AES/PHEAA
"Garzon
Maldonado, Jesus
Javier"To
<[EMAIL PROTECTED]
> cc
05/31/2005 06:14 Subject
AMQuestion about handlers
Please respond to
[EMAIL PROTECTED]
he.org
Hello all,
Is there any way to pass data from handlers to service implementations?,
(that is, XXXBindingImpl classes)
For example, a handler perform user authentication and service
implementation needs that user to login a database.
Thanks.
Javi Garzón
Re: Error in deserialization
Kumar, This WSDL imports another WSDL and two schemas. Can you send us those also? Also, can you tell us how you built and configured your client? I noticed that you're using the call interface. Have you tryied creating a stub client and invoking operations on the stub? Anne On 5/31/05, Plorks mail <[EMAIL PROTECTED]> wrote: > Hello again > > Sorry clicked send too soon > > In the 2nd WSDL there's another reference to a WSDL, heres that WSDL > > Thanks for any help you can ofer, much apreciated > > P > > > > - > - targetNamespace="http://www.csapi.org/wsdl/parlayx/common_faults/v1_0"; > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > - > > > - > > > - > > > - > > > - > > > - > > > > > > > >From: Anne Thomas Manes <[EMAIL PROTECTED]> > >Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]> > >To: axis-user@ws.apache.org > >Subject: Re: Error in deserialization > >Date: Sat, 28 May 2005 17:36:15 -0400 > > > >Kumar, > > > >The WSDL you sent me contains this import: > > > > >namespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; > >location="parlayx_third_party_calling_service_port.wsdl" /> > > > >This imported WSDL contains the , , and > >definitions. I need to see this WSDL to answer your questions. > > > >Anne > > > >On 5/28/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > > > > > > > Sorry about the sending, i just clicked reply, didn't notice it wasn't > >the > > > axis-user > > > > > > What do you mean by the imported WSDL document? > > > > > > Many thanks for nay help > > > > > > > > > > > > > > > > > > > > > > > > >We also need the imported WSDL document. > > > > > > > >One problem I noticed with this WSDL is that it uses "rpc" style, but > > > >it doesn't specify a namespace attribute in the > > > >descriptions. > > > > > > > >Thanks, > > > >Anne > > > > > > > >On 5/27/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Here is the WSDL > > > > > > > > > > Thanks for any help > > > > > > > > > > > > > > > > > > > > - > > > > > - > > > > > > > > > >targetNamespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service"; > > > > > xmlns="http://schemas.xmlsoap.org/wsdl/"; > > > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > > > > > > > > >xmlns:tns="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service"; > > > > > > > > > > >xmlns:port="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port";> > > > > >> > > > > > > > > >namespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; > > > > > location="parlayx_third_party_calling_service_port.wsdl" /> > > > > > - > > >type="port:ThirdPartyCallPort"> > > > > >> > >transport="http://schemas.xmlsoap.org/soap/http"; > > > > > /> > > > > > - > > > > >>/> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > >> > >style="rpc" > > > > > /> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > - > > > > >> > >style="rpc" > > > > > /> > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > - > > >binding="tns:ThirdPartyCallBinding"> > > > > >> > > > > > > > > >location="http://www.wwcc.bt.com:9000/ccx/parlayx_third_party_calling_service"; > > > > > /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >From: Anne Thomas Manes <[EMAIL PROTECTED]> > > > > > >Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]> > > > > > >To: axis-user@ws.apache.org > > > > > >Subject: Re: Error in deserialization > > > > > >Date: Fri, 27 May 2005 08:43:59 -0400 > > > > > > > > > > > >Can you provide us with the WSDL? > > > > > > > > > > > >Somewhere in either the request or response message there is an > > > > > >element of type EndUserIdentifier, and it appears that this element > > > > > >isn't mapping properly. > > > > > > > > > > > >Anne > > > > > > > > > > > >On 5/27/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > > Hi all > > > > > > > > > > > > > > I'm trying to access an external
FW: Weblogic8.1 and Axis 1.2 (Final) :: NullPointerException
Friends, I also tried to force weblogic to use xerces with the following VM argument, but I am still getting the same error. Please let me know if you have any thoughts. -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl Thanks ~Kiran From: Kiran Kumar [mailto:[EMAIL PROTECTED]Sent: Mon 5/30/2005 7:16 PMTo: axis-user@ws.apache.orgSubject: Weblogic8.1 and Axis 1.2 (Final) :: NullPointerException Hello, I wanted to use document style webservices so I moved to Axis 1.2 (Final). I built a simple webservice (RPC style) to see how Axis 1.2 works.. It did go well with Tomcat 4.1. I deployed the same war file in weblogic8.1 SP4. It was deployed successfully but when I try to call from the client it was giving the following error. org.apache.axis.utils.XMLUtils - Failed to set EntityResolver to null on DocumentBuilderjava.lang.NullPointerException at weblogic.xml.jaxp.ChainingEntityResolver.popEntityResolver(ChainingEntityResolver.java:61) at weblogic.xml.jaxp.RegistryDocumentBuilder.setEntityResolver(RegistryDocumentBuilder.java:168) I attached the detailed stack trace in the attached txt file. I did following thing to resolve this but could not get through this.. 1. I kept the jar files saaj.jar, xercesImpl.jar, xml-apis.jar, jax-rpc.jar in the weblogic classpath before webservices.jar Based on stack trace, apache.utils.XMLUtils is probably sending some XML which is not being able to get through the weblogic document builder. If you guys have any idea please throw some light on this.. Thanks for your time Kiran - Ph: 312 742 9630 Email: [EMAIL PROTECTED] This e-mail, and any attachments thereto, is confidential and is intended only for the individual(s) named. If you are not the intended recipient, please let us know by e-mail reply and delete it from your system; do not copy/save this e-mail or disclose its contents to anyone. E-mail transmissions cannot be guaranteed to be secure or error-free as the transmission could be interrupted, corrupted, lost, destroyed, altered, arrive late or contain viruses. ObjectWave does not accept liability for any errors or omissions in the contents of this e-mail which arise as a result of e-mail transmission. The views expressed in this e-mail do not necessarily reflect those of ObjectWave or its affiliates. This e-mail, and any attachments thereto, is confidential and is intended only for the individual(s) named. If you are not the intended recipient, please let us know by e-mail reply and delete it from your system; do not copy/save this e-mail or disclose its contents to anyone. E-mail transmissions cannot be guaranteed to be secure or error-free as the transmission could be interrupted, corrupted, lost, destroyed, altered, arrive late or contain viruses. ObjectWave does not accept liability for any errors or omissions in the contents of this e-mail which arise as a result of e-mail transmission. The views expressed in this e-mail do not necessarily reflect those of ObjectWave or its affiliates. http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://schemas.xmlsoap.org/soap/encoding/";>50 w washington sthttp://schemas.xmlsoap.org/soap/encoding/"; xsi:type="xsd:int" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>1http://schemas.xmlsoap.org/soap/encoding/"; xsi:type="xsd:boolean" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>true 2005-05-30 18:43:44,328 [DEBUG] org.apache.axis.transport.http.HTTPSender - HTTP/1.1 500 Internal Server Error 2005-05-30 18:43:44,343 [DEBUG] org.apache.axis.transport.http.HTTPSender - Date Mon, 30 May 2005 23:43:43 GMT 2005-05-30 18:43:44,343 [DEBUG] org.apache.axis.transport.http.HTTPSender - Content-Type text/xml; charset=utf-8 2005-05-30 18:43:44,343 [DEBUG] org.apache.axis.transport.http.HTTPSender - Connection Close * HERE IS THE ERROR * === 2005-05-30 18:43:44,343 [DEBUG] org.apache.axis.utils.XMLUtils - Failed to set EntityResolver to null on DocumentBuilder java.lang.NullPointerException at weblogic.xml.jaxp.ChainingEntityResolver.popEntityResolver(ChainingEntityResolver.java:61) at weblogic.xml.jaxp.RegistryDocumentBuilder.setEntityResolver(RegistryDocumentBuilder.java:168) at org.apache.axis.utils.XMLUtils.releaseDocumentBuilder(XMLUtils.java:252) at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:342) at org.apache.axis.message.SOAPDocumentImpl.(SOAPDocumentImpl.java:70) at org.apache.axis.SOAPPart.(SOAPPart.java:1013) at org.apache.a
RE: WSDL2JAVA
In http://www.carm.es/ctyc/jsps/jsp/wsdl/ObtenerEc.wsdl
wsdl2java (axis 1.2) generate only any types that wsdl2java(axis 1.1). I need
all the type to invoke web service.
java -cp %AXISCLASSPATH%
org.apache.axis.wsdl.WSDL2Java -oCliente -W http://www.carm.es/ctyc/jsps/jsp/wsdl/ObtenerEc.wsdl
(axis 1.2)
this generate
EXPEDIENTE_CONTABLEType.java
EXPEDIENTE_CONTABLETypeCAB.java
EXPEDIENTE_CONTABLETypeLINEAS.java
EX_OBTENEREC.java
ID_EXPType.java
IM_OBTENEREC.java
IM_ObtenerECBindingStub.java
IM_ObtenerECService.java
IM_ObtenerECServiceLocator.java
INTERVENCIONType.java
LINEA_CONTABLEType.java
LISTA_EXP_CONTABLEType.java
RESULTADOType.java
/**
* IM_ObtenerEC.java
*
* This file was auto-generated from WSDL
* by the Apache Axis 1.2 May 03, 2005 (02:20:24 EDT)
WSDL2Java emitter.
*/
package es.carm.ws.ec;
public interface IM_ObtenerEC extends java.rmi.Remote
{
public es.carm.ws.ec.EX_OBTENEREC
IM_ObtenerEC(es.carm.ws.ec.IM_OBTENEREC IM_OBTENEREC) throws
java.rmi.RemoteException;
}
wsdl2java (axis 1.1) generate
ACTIVO_FIJOType.java
CEN_GESType.java
CLASE_DOCType.java
COD_TERType.java
DOC_FIType.java
EXPEDIENTE_CONTABLEType.java
EXPEDIENTE_CONTABLEType_CAB.java
EXPEDIENTE_CONTABLEType_LINEAS.java
FASE_DOCType.java
FASE_INTERVType.java
FECHAType.java
ID_EXPType.java
IMPORTEType.java
IM_ObtenerEC.java
IM_ObtenerECBindingImpl.java
IM_ObtenerECBindingSkeleton.java
IM_ObtenerECBindingStub.java
IM_ObtenerECService.java
IM_ObtenerECServiceLocator.java
INTERVENCIONType.java
LINEA_CONTABLEType.java
LINEA_CONTABLEType_DESC_LIN.java
LISTA_EXP_CONTABLEType.java
MONEDAType.java
NIFType.java
POS_EXPType.java
POS_PREType.java
PROYECTOType.java
RESULTADOType.java
SOCIEDADType.java
TIPO_INTERVType.java
_EX_OBTENEREC.java
_IM_OBTENEREC.java
_IM_OBTENEREC_CEN_GES.java
/**
* IM_ObtenerEC.java
*
* This file was auto-generated from WSDL
* by the Apache Axis WSDL2Java emitter.
*/
package es.carm.ctyc.wc.CSigepal;
public interface IM_ObtenerEC extends java.rmi.Remote
{
public es.carm.ctyc.wc.CSigepal._EX_OBTENEREC
IM_ObtenerEC(es.carm.ctyc.wc.CSigepal._IM_OBTENEREC IM_OBTENEREC) throws
java.rmi.RemoteException;
}
Axis 1.1 generate the
class _IM_OBTENEREC and I use this class to pass the
parameter to web service, but axis 1.2 not generate this class and I don’t
know how I can pass the parameter to web service.
Manuel N.
De: I.Venuti
[mailto:[EMAIL PROTECTED]
Enviado el: martes, 31 de mayo de
2005 13:54
Para: axis-user@ws.apache.org;
[EMAIL PROTECTED]
Asunto: R: WSDL2JAVA
wrong WSDL?
-- Ivan
-Messaggio originale-
Da: Manuel Nicolas Ortuño
[mailto:[EMAIL PROTECTED]
Inviato: martedì 31 maggio 2005
12.48
A: axis-user@ws.apache.org
Oggetto: RE: WSDL2JAVA
In this url of wsdl. The wsdl2java not generate all
the types, and I not invoke the web service If I don’t have the class
type
Any idea because axis not generate the types.
http://www.carm.es/ctyc/jsps/jsp/wsdl/ObtenerEc.wsdl
R: WSDL2JAVA
wrong WSDL? -- Ivan -Messaggio originale-Da: Manuel Nicolas Ortuño [mailto:[EMAIL PROTECTED]Inviato: martedì 31 maggio 2005 12.48A: axis-user@ws.apache.orgOggetto: RE: WSDL2JAVA In this url of wsdl. The wsdl2java not generate all the types, and I not invoke the web service If I don’t have the class type Any idea because axis not generate the types. http://www.carm.es/ctyc/jsps/jsp/wsdl/ObtenerEc.wsdl
String gets wrapped
Hi all I'm passing a string value to a remote web service method. I've noticed in the SOAP request the string gets wrapped e.g. String a = "string;12345678;presentation=available"; the SOAP looks like this string;12345678; presentation=available Is there any way i can send this strng through so it doesn't get wrapped ? So it looks like this in the SOAP string;12345678;presentation=available Does it matter the string is wrapped? When it ges passed to the remote method would the remote method treat it is as one line, or wrapped? Thanks for any help _ Use MSN Messenger to send music and pics to your friends http://messenger.msn.co.uk
RE: WSDL2JAVA
In this url of wsdl. The wsdl2java not generate all the types, and I not invoke the web service If I don’t have the class type Any idea because axis not generate the types. http://www.carm.es/ctyc/jsps/jsp/wsdl/ObtenerEc.wsdl
Question about handlers
Hello all, Is there any way to pass data from handlers to service implementations?, (that is, XXXBindingImpl classes) For example, a handler perform user authentication and service implementation needs that user to login a database. Thanks. Javi Garzón
Returning a SOAP Fault
We are currently in the testing phase of a document style web services application. The application is required to return a soap fault when certain conditions are not met e.g. failure on XML schema validation of attached XML document. What we currently do in a fault situation is that we throw an AxisFault, setting the fault code, fault string etc. What we expected was the Fault element would be returned in the body of the SOAP response message. This is not the case, there is no SOAP response message when a fault occurs, we can only get access to the fault code, fault string etc. set in the web services at point of failure by catching the exception on the client and extracting the relevant fields. Is there anyway of sending back the fault element in the body of the SOAP response message, without your client crashing out with an exception that you would have to trap? Regards, SAM AMARTEIFIO [EMAIL PROTECTED] +44 (0)20 7780 5955 ec3 solutions / 1st floor 9-13 fenchurch buildings london ec3m 5hr / +44 (0)20 7780 5955 / http://www.ec3.com / Confidentiality Notice This communication is strictly confidential. If you are not the intended recipient, you must not copy, distribute or take any action in reliance of it and destroy this email. Please immediately notify the sender or contact EC3 on telephone +44 (0)845 330 4396 or email '[EMAIL PROTECTED]'. The views represented in this email are not necessarily those of EC3.
java.lang.IncompatibleClassChangeError after dumping SOAPRequest in Sender
Hi there, I wrote my own Sender. When I dump the SOAPResponse by "responseMsg.getSOAPPartAsString()" in my sender, I get a "java.lang.IncompatibleClassChangeError" later in the response-processing. Why? java.lang.IncompatibleClassChangeError at org.apache.axis.message.MessageElement.addTextNode(MessageElement.java:1387) at org.apache.axis.message.SOAPHandler.addTextNode(SOAPHandler.java:148) at org.apache.axis.message.SOAPHandler.endElement(SOAPHandler.java:112) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1712) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope(Message.java:424) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at org.apache.axis.client.Call.invokeEngine(Call.java:2765) at org.apache.axis.client.Call.invoke(Call.java:2748) at org.apache.axis.client.Call.invoke(Call.java:2424) at org.apache.axis.client.Call.invoke(Call.java:2347) at org.apache.axis.client.Call.invoke(Call.java:1804) Thanks, Markus Sozialwahl 2005 Richtig. Wichtig. Schon gewaehlt? Noch bis 1. Juni!
how to get the HTTP response code to avoid AxisFault "401 (Unauthorized)" Messages?
Hello everybody,
I’m using Axis 1.2 in a little Web Service
project. The web service requires authentication with a username and a
password.
The client set the values as follows:
ServiceLocator locator =
new ServiceLocator();
BindingStub binding
= (BindingStub)locator.getPort();
binding.setUsername("username");
binding.setPassword("password");
and the client calls the service with:
binding.mehtodToCall();
This works really fine. But Sometimes it is possible
that username and password has changed. In this case i got an AxisFault Message
“401 (Unauthorized)”.
And now my question. Is it possible to get the http
response code before any exception is thrown on the client side?
May be:
ServiceLocator locator =
new ServiceLocator();
BindingStub binding = (BindingStub)locator.getPort();
binding.setUsername("username");
binding.setPassword("password");
if ( methodToGetHTTPResponseCode() != 200
){ // OK
// new authentication
}
Thanks for your help!
Christian Kunert
___
Produktion und Entwicklung
NEXNET GmbH
Am Borsigturm 12
13507 Berlin
Tel.:
+49 30 726297 411
Mail: [EMAIL PROTECTED]
Re: Error in deserialization
Hello again
Sorry clicked send too soon
In the 2nd WSDL there's another reference to a WSDL, heres that WSDL
Thanks for any help you can ofer, much apreciated
P
-
- targetNamespace="http://www.csapi.org/wsdl/parlayx/common_faults/v1_0";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
-
-
-
-
-
-
From: Anne Thomas Manes <[EMAIL PROTECTED]>
Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Subject: Re: Error in deserialization
Date: Sat, 28 May 2005 17:36:15 -0400
Kumar,
The WSDL you sent me contains this import:
http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port";
location="parlayx_third_party_calling_service_port.wsdl" />
This imported WSDL contains the , , and
definitions. I need to see this WSDL to answer your questions.
Anne
On 5/28/05, Plorks mail <[EMAIL PROTECTED]> wrote:
>
>
> Sorry about the sending, i just clicked reply, didn't notice it wasn't
the
> axis-user
>
> What do you mean by the imported WSDL document?
>
> Many thanks for nay help
>
>
>
>
>
>
>
> >We also need the imported WSDL document.
> >
> >One problem I noticed with this WSDL is that it uses "rpc" style, but
> >it doesn't specify a namespace attribute in the
> >descriptions.
> >
> >Thanks,
> >Anne
> >
> >On 5/27/05, Plorks mail <[EMAIL PROTECTED]> wrote:
> > >
> > > Here is the WSDL
> > >
> > > Thanks for any help
> > >
> > >
> > >
> > > -
> > > - > >
>
>targetNamespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service";
> > > xmlns="http://schemas.xmlsoap.org/wsdl/";
> > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > >
>
>xmlns:tns="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service";
> > >
>
>xmlns:port="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port";>
> > >> >
>
>namespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port";
> > > location="parlayx_third_party_calling_service_port.wsdl" />
> > > - >type="port:ThirdPartyCallPort">
> > >>transport="http://schemas.xmlsoap.org/soap/http";
> > > />
> > > -
> > > />
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > >
> > > -
> > >>style="rpc"
> > > />
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > >
> > > -
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > >
> > > -
> > >>style="rpc"
> > > />
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > > -
> > >
> > >
> > >
> > >
> > > -
> > > - >binding="tns:ThirdPartyCallBinding">
> > >> >
>
>location="http://www.wwcc.bt.com:9000/ccx/parlayx_third_party_calling_service";
> > > />
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > >From: Anne Thomas Manes <[EMAIL PROTECTED]>
> > > >Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]>
> > > >To: axis-user@ws.apache.org
> > > >Subject: Re: Error in deserialization
> > > >Date: Fri, 27 May 2005 08:43:59 -0400
> > > >
> > > >Can you provide us with the WSDL?
> > > >
> > > >Somewhere in either the request or response message there is an
> > > >element of type EndUserIdentifier, and it appears that this element
> > > >isn't mapping properly.
> > > >
> > > >Anne
> > > >
> > > >On 5/27/05, Plorks mail <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > >
> > > > > Hi all
> > > > >
> > > > > I'm trying to access an external web service and get this error
when
> >it
> > > >gets
> > > > > to this line
> > > > >
> > > > > String result = (String)call.invoke(new Object[] {param1,
param2,
> > > >param3});
> > > > >
> > > > > Error in deserialization : failed deserializing value of type
> > > > > {http://www.api.org/schema/par/common/v1_0}
> > > > > EndUserIdentifier into class
> >org.api.www.par.common.EndUserIdentifier
> > > > >
> > > > >
> > > > >
> > > > > I'm been back to the supplier of the web service but i'm not
getting
> > > >much
> > > > > help from them. Does anyone know what this error means. I have
to
> >pass
> > > >up
> > > > > username and password in the http header and using the
> >passweord/usernme
> > > > > they gave me
> > > > >
> > > > > This is my code
> > > > >
> > > > > Can anyone see anything outstandingly wrong in my code
> > > > >
> > > > > Thanks for any help
> > > > >
> > > > >
> > > > >
> > > > > URL endpoint = new URL
> > > > >
> > >
> >
>("http://www.domain.com:9000/ccx/par_third_party_calling_service/encoded";);
> > > > >
> > > > > Service service = new Service();
> > > > >
> > > > > Call call = (Call)service.
Re: Error in deserialization
Hi Anne, Here's the WSDL file referenced in the original WSDL - - targetNamespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:tns="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; xmlns:parlayx_third_party_calling_xsd="http://www.csapi.org/schema/parlayx/third_party_calling/v1_0"; xmlns:parlayx_common_faults="http://www.csapi.org/wsdl/parlayx/common_faults/v1_0"; xmlns:parlayx_common_xsd="http://www.csapi.org/schema/parlayx/common/v1_0";> namespace="http://www.csapi.org/wsdl/parlayx/common_faults/v1_0"; location="parlayx_common_faults.wsdl" /> - - http://www.csapi.org/schema/parlayx/common/v1_0"; schemaLocation="parlayx_common_types.xsd" /> namespace="http://www.csapi.org/schema/parlayx/third_party_calling/v1_0"; schemaLocation="parlayx_third_party_calling_types.xsd" /> - - - - /> /> - - - type="parlayx_third_party_calling_xsd:CallInformationType" /> - - - - message="parlayx_common_faults:UnknownEndUserException" /> message="parlayx_common_faults:InvalidArgumentException" /> message="parlayx_common_faults:ServiceException" /> - message="tns:UnknownCallIdentifierException" /> message="parlayx_common_faults:ServiceException" /> - message="tns:CallTerminatedException" /> message="tns:UnknownCallIdentifierException" /> message="parlayx_common_faults:ServiceException" /> - message="tns:CallConnectedException" /> message="tns:UnknownCallIdentifierException" /> message="parlayx_common_faults:ServiceException" /> From: Anne Thomas Manes <[EMAIL PROTECTED]> Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Subject: Re: Error in deserialization Date: Sat, 28 May 2005 17:36:15 -0400 Kumar, The WSDL you sent me contains this import: http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; location="parlayx_third_party_calling_service_port.wsdl" /> This imported WSDL contains the , , and definitions. I need to see this WSDL to answer your questions. Anne On 5/28/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > Sorry about the sending, i just clicked reply, didn't notice it wasn't the > axis-user > > What do you mean by the imported WSDL document? > > Many thanks for nay help > > > > > > > > >We also need the imported WSDL document. > > > >One problem I noticed with this WSDL is that it uses "rpc" style, but > >it doesn't specify a namespace attribute in the > >descriptions. > > > >Thanks, > >Anne > > > >On 5/27/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > > > > Here is the WSDL > > > > > > Thanks for any help > > > > > > > > > > > > - > > > - > > > >targetNamespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service"; > > > xmlns="http://schemas.xmlsoap.org/wsdl/"; > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > > >xmlns:tns="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service"; > > > > >xmlns:port="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port";> > > >> > > >namespace="http://www.csapi.org/wsdl/parlayx/third_party_calling/v1_0/service_port"; > > > location="parlayx_third_party_calling_service_port.wsdl" /> > > > - >type="port:ThirdPartyCallPort"> > > >>transport="http://schemas.xmlsoap.org/soap/http"; > > > /> > > > - > > > /> > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > > > > - > > >>style="rpc" > > > /> > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > > > > - > > > > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > > > > - > > >>style="rpc" > > > /> > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > - > > > > > > > > > > > > > > > - > > > - >binding="tns:ThirdPartyCallBinding"> > > >> > > >location="http://www.wwcc.bt.com:9000/ccx/parlayx_third_party_calling_service"; > > > /> > > > > > > > > > > > > > > > > > > > > > > > > > > > >From: Anne Thomas Manes <[EMAIL PROTECTED]> > > > >Reply-To: Anne Thomas Manes <[EMAIL PROTECTED]> > > > >To: axis-user@ws.apache.org > > > >Subject: Re: Error in deserialization > > > >Date: Fri, 27 May 2005 08:43:59 -0400 > > > > > > > >Can you provide us with the WSDL? > > > > > > > >Somewhere in either the request or response message there is an > > > >element of type EndUserIdentifier, and it a
