Re: AXIS 1.x to AXIS2 Migration Roadmap
Eran, That page seem to have good content for comparing between 1.x v2.0, useful for new users. But the existing users of Axis 1.x would need migration plan that has sections to show how to migrate handler code, deployment code, clients, and service implementations. I think we need to provide elaborate documentation on this, for the benefit of 1.x users. - venkat On 9/15/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > http://ws.apache.org/axis2/migration.html > > > Kr wrote: > > >Hi All, > > > >I have fair experience with AXIS 1.x and now planning to switch to AXIS2. > >Does anybody have AXIS 1.x to AXIS2 migration roadmap. What are the > >various differences between the two based on parameters like > >performance, ease-of-use, ws-security, support for various > >java-xml-data-binding-frameworks etc. > > > >When should be look for migrating our exisiting web services providers > >and consumer built using AXIS 1.X to AXIS2. Any issues that we can > >forecast ? > > > >Please suggest ? > > > >Thanks & Regards, > >Kr. > > > > > > > >
Re: problem building Axis 1.2.1 from source
This must be because of using JRE 5.0, which uses DOM-3. You can fix this either simply using a 1.4.2 JRE or ensuring Xerces 2.6.2 is in classpath. How does your classpath looks like as emitted by ant while running "ant clean compile"? - venkat On 8/30/05, Mike Woinoski <[EMAIL PROTECTED]> wrote: > I'm trying to rebuild axis.jar from the Axis 1.2.1 source. "ant compile" > generates a number of errors like the following: > > C:\Home\Java\axis\src\org\apache\axis\SOAPPart.java:90: > org.apache.axis.SOAPPart is not abstract and does not override abstract > method renameNode(org.w3c.dom.Node,java.lang.String,java.lang.String) in > org.w3c.dom.Document > public class SOAPPart extends javax.xml.soap.SOAPPart implements Part > ^ > > I've tried it with Java 5.0 and Java 1.4.2 (using Ant 1.6.2), resetting > JAVA_HOME for the different compilers, but I get the same errors. Is the > compiler using the wrong version of the Xerces libraries? Should I be using an > older compiler (JDK 1.3?) > > Thanks, > Mike > >
Re: Download archives for Axis 1.1?
try http://archive.apache.org/dist/ws/axis/1_1/ The links on the news page seem to be broken. - venkat On 8/24/05, Guy Rixon <[EMAIL PROTECTED]> wrote: > What's happened to the archives of the Axis 1.1 jars? All the download sites > I've tried today claim to have them but the links don't work. > > Guy Rixon [EMAIL PROTECTED] > Institute of Astronomy Tel: +44-1223-337542 > Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523 >
Re: Problem with WSDL2Java
What is the error?? WSDL2Java doesn't need tomcat to be running unless you have any references to wsdl imports or the wsdl itself, fetched from a URL served by tomcat, which is not the case in your example. - venkat On 8/22/05, Arun Bhandari <[EMAIL PROTECTED]> wrote: > Hi Venkat, > > Thanks for your help. I made the correction, but I am still facing an issue. > > Here is the command line that I am using: > > java -classpath > .\webapps\axis\WEB-INF\lib\axis.jar;.\webapps\axis\WEB-INF\lib\log4j-1.2.8.jar;.\webapps\axis\WEB-INF\lib\commons-discovery-0.2.jar;.\webapps\axis\WEB-INF\lib\commons-logging-1.0.4.jar;.\webapps\axis\WEB-INF\lib\wsdl4j-1.5.1.jar;.\webapps\axis\WEB-INF\lib\saaj.jar;.\webapps\axis\WEB-INF\lib\axis-ant.jar;.\webapps\axis\WEB-INF\lib\jaxrpc.jar;"C:\Sun\jwsdp-1.6\jaxp\lib\jaxp-api.jar";"C:\Sun\jwsdp-1.6\jwsdp-shared\lib\mail.jar";"C:\Sun\jwsdp-1.6\jwsdp-shared\lib\activation.jar" > org.apache.axis.wsdl.WSDL2Java SaleOrder.wsdl > > I am executing this command line from my container (tomcat) home folder. > Please let me know if you have an idea for this error. > > Thanks, > Arun. > > > On 8/22/05, Venkat Reddy <[EMAIL PROTECTED]> wrote: > > Your WSDL has a element in binding section which doesn't > > correspond to the one defined in portType section. After correcting > > this error, I could run WSDL2Java without any issues. Here is the > > corrected version of inside binding section of your WSDL. > > > > > > > namespace="http://FaultMessageNamespace"; name="SaleError"/> > > > > > > - venkat > > > > > > On 8/22/05, Arun Bhandari <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > I have attached my WSDL. Thanks for your response > > > > > > On 8/22/05, Venkat Reddy <[EMAIL PROTECTED]> wrote: > > > > please post your WSDL. > > > > > > > > - venkat > > > > > > > > On 8/22/05, Arun Bhandari <[EMAIL PROTECTED]> wrote: > > > > > I am using Apache Axis 1.2 with java jdk 1.5, Tomcat as my web > > > > > container. > > > > > I have ensured that all the Axis jars in my classpath. > > > > > > > > > > I am trying to generate a client stub using a WSDL, but I get the > > > > > following error: > > > > > > > > > > > > > > > java.lang.NullPointerException > > > > > at javax.wsdl.OperationType.equals(Unknown Source) > > > > > at > > > > > org.apache.axis.wsdl.toJava.JavaGeneratorFactory.constructSignat= > > > > > ures( > > > > > JavaGeneratorFactory.java:1393) > > > > > at > > > > > org.apache.axis.wsdl.toJava.JavaGeneratorFactory.generatorPass(J= > > > > > avaGe > > > > > neratorFactory.java:213) > > > > > at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:424) > > > > > at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:44) > > > > > at > > > > > org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361= > > > > > ) > > > > > at java.lang.Thread.run(Unknown Source) > > > > > > > > > > Any help will be appreciated. > > > > > > > > > > -- > > > > > Thanks & Regards, > > > > > > > > > > Arun Bhandari > > > > > > > > > > > > > > > > > > -- > > > Thanks & Regards, > > > > > > Arun Bhandari > > > > > > > > > > > > > > -- > Thanks & Regards, > > Arun Bhandari >
Re: Axis 1.2.1 -> .NET interop problem
For me, it appears that your classpath might have a jaxrpc.jar in classpath other than the one built using axis code - venkat On 7/20/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > FYI, I downloaded the latest build and did Java2WSDL/WSDL2Java, the > WSDL2Java gave me this: > > java.lang.NoSuchMethodError: javax.xml.namespace.QName: method > getPrefix()Ljava/lang/String; not found > at > org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithDifferentLocal(BackslashUtil.java:47) > at > org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithBackslashlessLocal(BackslashUtil.java:32) > at > org.apache.axis.wsdl.symbolTable.SymbolTable.populateServices(SymbolTable.java:3070) > at > org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:745) > at > org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543) > at > org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518) > at > org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495) > at > org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) > at java.lang.Thread.run(Thread.java:568) > > It appears to be in the axis code? > > Thank you, > > Ken Katsma > J.P. Morgan Chase > Application Architect > Wholesale CRM/Core Services > 312-954-8634 > > > > Kenneth R Katsma > Venkat Reddy <[EMAIL PROTECTED]> > > 07/20/2005 08:42 AM > Please respond to axis-user > To:axis-user@ws.apache.org > cc: > Subject:Re: Axis 1.2.1 -> .NET interop problem > > > > FYI - I have already tested your wsdl againist latest Axis, and i > don't see any extra testArray wrapper in response. Using latest Axis - > is that a feasible option for you? > > - venkat > > On 7/20/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > > > > I submitted another article on this subject where I found that it was > > related to multiple namespaces. You asked me to submit a bug report, > which > > I will do later today. > > > > Thank you, > > > > Ken Katsma > > J.P. Morgan Chase > > Application Architect > > Wholesale CRM/Core Services > > > > > > > > Kenneth R Katsma > > Anne Thomas Manes <[EMAIL PROTECTED]> > > > > 07/19/2005 07:20 PM > > > > Please respond to axis-user > > To:axis-user@ws.apache.org > > cc: > > Subject:Re: Axis 1.2.1 -> .NET interop problem > > > > > > > > Quite possibly. What version of Axis are you using? We had a lot of > > bugs dealing with arrays. > > > > Anne > > > > On 7/11/05, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > > wrote: > > > > > > Anne, > > > > > > Thanks for your advice. Can you tell me what is causing the extra > > testArray > > > wrapper? It's not clear to me how Axis is generating the extra > wrapper > > if > > > I'm not asking it to do so in the WSDL. Is this a bug? > > > > > > Thank you, > > > > > > Ken Katsma > > > J.P. Morgan Chase > > > Senior Application Development Analyst > > > Wholesale CRM/Core Services > > > 312-954-8634 > > > > > > > > > > > > Kenneth R Katsma > > > Anne Thomas Manes <[EMAIL PROTECTED]> > > > > > > 07/11/2005 02:32 PM > > > Please respond to axis-user > > > To:axis-user@ws.apache.org > > > cc: > > > Subject:Re: Axis 1.2.1 -> .NET interop problem > > > > > > > > > > > > Ken, > > > > > > Your response is fully qualified. The problem is that your response > > > contains an extra "testArray" wrapper. According to your schema, the > > > response should look like this: > > > > > > > > >> > xmlns="http://test.ckc.services.crm.jpmorgan.com";> > > > > > > > > > George > > > Washington > > > > > > > > >
Re: Axis 1.2.1 -> .NET interop problem
FYI - I have already tested your wsdl againist latest Axis, and i don't see any extra testArray wrapper in response. Using latest Axis - is that a feasible option for you? - venkat On 7/20/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I submitted another article on this subject where I found that it was > related to multiple namespaces. You asked me to submit a bug report, which > I will do later today. > > Thank you, > > Ken Katsma > J.P. Morgan Chase > Application Architect > Wholesale CRM/Core Services > > > > Kenneth R Katsma > Anne Thomas Manes <[EMAIL PROTECTED]> > > 07/19/2005 07:20 PM > > Please respond to axis-user > To:axis-user@ws.apache.org > cc: > Subject:Re: Axis 1.2.1 -> .NET interop problem > > > > Quite possibly. What version of Axis are you using? We had a lot of > bugs dealing with arrays. > > Anne > > On 7/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > > > > Anne, > > > > Thanks for your advice. Can you tell me what is causing the extra > testArray > > wrapper? It's not clear to me how Axis is generating the extra wrapper > if > > I'm not asking it to do so in the WSDL. Is this a bug? > > > > Thank you, > > > > Ken Katsma > > J.P. Morgan Chase > > Senior Application Development Analyst > > Wholesale CRM/Core Services > > 312-954-8634 > > > > > > > > Kenneth R Katsma > > Anne Thomas Manes <[EMAIL PROTECTED]> > > > > 07/11/2005 02:32 PM > > Please respond to axis-user > > To:axis-user@ws.apache.org > > cc: > > Subject:Re: Axis 1.2.1 -> .NET interop problem > > > > > > > > Ken, > > > > Your response is fully qualified. The problem is that your response > > contains an extra "testArray" wrapper. According to your schema, the > > response should look like this: > > > > > >> xmlns="http://test.ckc.services.crm.jpmorgan.com";> > > > > > > George > > Washington > > > > > > Ben > > Franklin > > > > > > > > > > > > > > Anne > > > > On 7/11/05, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > > wrote: > > > > > > Hi, > > > > > > I've constructed a very simple test case in Java and am using > Java2WSDL > > > and WSDL2Java to create the wsdl and stubs. I'm using Axis 1.2.1 for > > > these tests and created the WSDL using document/wrapped. The service > > > works fine when using Axis as the client, but when connecting from > .NET > > > the response is not deserialized correctly. > > > > > > Microsoft has indicated that this is because Axis is not including > the > > > qualified namespace on the return elements. Is this a bug/weakness > in > > > Axis? Is there a work-around? Am I doing something else wrong? > > > > > > Here is the wsdl, genereated from Java2WSDL and retrieved from the > > server > > > with ?wsdl with the request and response below: > > > > > > > > > > > > > > targetNamespace="http://test.ckc.services.crm.jpmorgan.com"; > > > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > > > > xmlns:impl="http://test.ckc.services.crm.jpmorgan.com"; > > > > xmlns:intf="http://test.ckc.services.crm.jpmorgan.com"; > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > > > > > targetNamespace="http://test.ckc.services.crm.jpmorgan.com"; > > > xmlns="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > type="impl:TestTO"/> > > > > > > > > > > > > > > > > > >> type="impl:ArrayOfTestTO"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > name="testResponse"/> > > > > > > > > > > > > > > > > > > type="impl:TestService"> > > > > > > > > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > > > > >
Re: Axis 1.2.1 -> .NET interop problem
AFAICT, you shouldn't see the extra Array wrapper with latest Axis CVS. - venkat On 7/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Anne, > > Thanks for your advice. Can you tell me what is causing the extra testArray > wrapper? It's not clear to me how Axis is generating the extra wrapper if > I'm not asking it to do so in the WSDL. Is this a bug? > > Thank you, > > Ken Katsma > J.P. Morgan Chase > Senior Application Development Analyst > Wholesale CRM/Core Services > 312-954-8634 > > > > Kenneth R Katsma > Anne Thomas Manes <[EMAIL PROTECTED]> > > 07/11/2005 02:32 PM > Please respond to axis-user > To:axis-user@ws.apache.org > cc: > Subject:Re: Axis 1.2.1 -> .NET interop problem > > > > Ken, > > Your response is fully qualified. The problem is that your response > contains an extra "testArray" wrapper. According to your schema, the > response should look like this: > > > xmlns="http://test.ckc.services.crm.jpmorgan.com";> > > > George > Washington > > > Ben > Franklin > > > > > > > Anne > > On 7/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > > > > Hi, > > > > I've constructed a very simple test case in Java and am using Java2WSDL > > and WSDL2Java to create the wsdl and stubs. I'm using Axis 1.2.1 for > > these tests and created the WSDL using document/wrapped. The service > > works fine when using Axis as the client, but when connecting from .NET > > the response is not deserialized correctly. > > > > Microsoft has indicated that this is because Axis is not including the > > qualified namespace on the return elements. Is this a bug/weakness in > > Axis? Is there a work-around? Am I doing something else wrong? > > > > Here is the wsdl, genereated from Java2WSDL and retrieved from the > server > > with ?wsdl with the request and response below: > > > > > > > > targetNamespace="http://test.ckc.services.crm.jpmorgan.com"; > > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > > xmlns:impl="http://test.ckc.services.crm.jpmorgan.com"; > > xmlns:intf="http://test.ckc.services.crm.jpmorgan.com"; > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > > > > targetNamespace="http://test.ckc.services.crm.jpmorgan.com"; > > xmlns="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> type="impl:TestTO"/> > > > > > > > > > > > > type="impl:ArrayOfTestTO"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > name="TestService"> > > > >> > location="http://localhost:9080/CKCServicesWEB/services/TestService"/> > > > > > > > > > > > > > > > > Here is the request: > > > > POST /CKCServicesWEB/services/TestService HTTP/1.0 > > Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, > > application/dime, multipart/related, text/* User-Agent: Axis/1.2.1 Host: > > localhost:2000 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" > > Content-Length: 367 > > > > 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";> > > > >> xmlns="http://test.ckc.services.crm.jpmorgan.com";> > > > > > > > > > > > > > > > > > > Here is the response: > > > > HTTP/1.1 200 OK Server: WebSphere Application Server/5.1 Expires: Thu, 01 > > Dec 1994 16:00:00 GMT Set-Cookie: > > JSESSIONID=_AVVKTC5yzeGJJTLWDPn2n8:-1;Path=/ > > Cache-Control: no-cache="set-cookie,set-cookie2" > > Content-Type: text/xml
Re: Document root element is missing
Kumar, Can you post your handler code, which is trying to "monitor" the request? - venkat On 7/19/05, Kumar <[EMAIL PROTECTED]> wrote: > Hi All, > > When I deployed to the remote .net service on my local environment and > try to consume it with a axis client I am see the xml declaration for > the request soap message in axis tcpmonitor. However if I try to > monitor the the same request soap message using a handler then the xml > declaration is getting stripped of. > > Since I am unable to monitor the actual remote .net web serivce using > axis tcpmon, I have used a handler to log the request soap message (to > the .net service) which shows the soap message stripping down xml > declaration. > > So in conclusion I presume that the request soap message has xml declaration. > > Any more thoughts Anne ? > > > Thanks & Regards, > Kumar. >
Re: How to configure and deploy JAX-RPC handler in Axis?
You need to specify the handler in deploy.wsdd, something like the following You can refer to the samples/jaxrpc --venkat On 7/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Thank your reply.I have try that with making use of Axis's own Handler > interface,it's ok! > But now,I alse want to try the JAX-RPC handler implementing > javax.xml.rpc.handler.Handler interface, > Who does this?I'm very appreciate with your help! > > Best Regards, > > Robert Zhang > Email:[EMAIL PROTECTED] > Tel:86-010-62014411-2437 > > - 原邮件 - > 从: Dong Liu <[EMAIL PROTECTED]> > 日期: 星期二, 七月 12日, 2005 上午9:13 > 主题: Re: How to configure and deploy JAX-RPC handler in Axis? > > > Axis has its own Handler interface. No idea about the difference > > between axis handler and javax handler. Anyway, you can first try to > > deploy the handler like axis handler, and then see if it work, and > > what is the error. > > > > Cheers, > > > > Don > > > > On 7/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Hi all > > > I have wrote a handler class implement the > > javax.xml.rpc.handler.Handler interface.But I don't know how to > > > configure and deploy it at the server side in Axis.I know the > > Axis is compliant with JAX-RPC specification and should be surport it. > > > > > > Thanks in advance:) > > > > > > > > > Best Regards, > > > > > > Robert Zhang > > > Email:[EMAIL PROTECTED] > > > Tel:86-010-62014411-2437 > > > > > > > > > >
Re: Return Type of XML
> How can I include an external schema in the WSDL generated by Axis?
In the WSDD file, specify a location for wsdl file which inturn may
import an external schema.
example:
/srv/webapps/axis/order-message.wsdl
- - - - - - - -
> What is the proper return type so the retrieved XML shows up in the SOAP
> message properly
What kind of problem did you face while using java.lang.String as the
return type for your service method?
- venkat
On 6/1/05, Marc Rabil <[EMAIL PROTECTED]> wrote:
>
>
> We are designing a web service that will connect to a back-end system and
> retrieve a chunk of XML and will simply return that XML. The .JWS definition
> may look something like this:
>
>
>
> public class CallBackendSystem {
>
> public String invoke(String arg1, String arg2) {
>
> String xmlString = // contact another system and retrieve XML
>
> return xmlString;
>
> }
>
> }
>
>
>
> We want the returned XML to be part of the SOAP body in the normal way (not
> escaped, or in a CDATA, etc.). We also want to include the XML schema
> (which we have from the back-end system) in the WSDL for this service. In
> short, we would like this web service to look to the outside world like it
> was all generated from the same system.
>
>
>
> Here are my questions:
>
>
> How can I include an external schema in the WSDL generated by Axis?
> What is the proper return type so the retrieved XML shows up in the SOAP
> message properly
>
>
>
> Any help or advice will be greatly appreciated.
>
>
>
> Marc
Re: Asynchronous Web Services
Axis2 (http://ws.apache.org/axis2/) will support asynch messaging, and Axis 1.2 doesn't. - Venkat On 23 May 2005 07:10:21 -, Ramanthan RV <[EMAIL PROTECTED]> wrote: hi,As far as, I know Axis provides a feeble support to Asynchronous web services.And I could not find any tutorial for the same.If any of had implemented it earlier or had any good references, plz forward the same to me. As I am very new to aysnc, a step by step guide will be preferable.Any help is welcomed.Since, my inbox is flooding with subscription mails, plz take pain to reply to [EMAIL PROTECTED]ThanksRamanathan
Re: very urgent - SAXException
Surendar, Could you post your complete WSDL content obtained using "?WSDL" and the WSDD you have used for deploying the service? -- venkat On 5/10/05, Surendar Suram <[EMAIL PROTECTED]> wrote: > Here is my WSDL Looks like > > > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > base="soapenc:Array"> > http://schemas.xmlsoap.org/wsdl/"; > ref="soapenc:arrayType" > wsdl:arrayType="stns:TroubleTicketSummaryList[]"> > > > > > > I have generated Client stubs by using WSDL2JAVA tool. > > But when i'm trying to access the WebService by writing Apache client. > I'm > getting the SAX Exception. But with WebLogic Client it is not > happening. > > May 9, 2005 1:29:04 PM org.apache.axis.client.Call invoke > SEVERE: Exception: > org.xml.sax.SAXException: Invalid element in > org.bls.bst.erepair.client.QryTroubleTicketDetail - statusHistList >at > org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:260) >at > org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:963) >at > org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:198) >at > org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:722) >at > org.apache.axis.message.RPCElement.deserialize(RPCElement.java:233) >at > org.apache.axis.message.RPCElement.getParams(RPCElement.java:347) >at org.apache.axis.client.Call.invoke(Call.java:2272) >at org.apache.axis.client.Call.invoke(Call.java:2171) >at org.apache.axis.client.Call.invoke(Call.java:1691) >at > org.bls.bst.erepair.client.ErepairtrblmgmtPortStub.queryTicketDetail(ErepairtrblmgmtPortStub.java:700) >at > com.bls.bst.erepair.client.WebServiceHandler.execute(WebServiceHandler.java:230) >at > com.bls.bst.erepair.webservice.EgateTestClient.processQueryTicketDetail(EgateTestClient.java:1272) >at > com.bls.bst.erepair.webservice.EgateTestClient.main(EgateTestClient.java:1668) > > I will be very great full if any body can show me the path. > > PS: I was wondering like can't we use Array Type for Apache Axis or > some thing wrong with my WSDL. > > Thanks in Adavance, > Surendar. > > Senior Developer. >
Re: [1.2RC2] Two instances of AxisServlet using different wsdd files?
Each servlet can use its own AxisEngine. But i'm not sure if you can force AxisProperties, through the servlet code, to load different config files each time. - venkat On 4/20/05, Ralph Pöllath <[EMAIL PROTECTED]> wrote: > In Axis 1.2RC2, is it possible to have 2 instances of AxisServlet (in > the same webapp) use different deployment descriptors (e.g. > server-config-one.wsdd and server-config-two.wsdd)? > > Thanks, > -Ralph. > >
Re: License for wsdl2java output?
I'm not sure if it is good idea for axis to impose licensing on generated code. For example, if a dataEclispe generates some bootstrap java code from its templates for a POJO or web app, which you later modify for your needs, which licence applies to the code? IMO, Same should hold good for wsdl2java, except that the amount and complexity of gerated code is more here. I think its upto the user of the wsdl2java to apply their own license. - venkat On 4/19/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > I don't think we impose any license on the generated code. Do you want > us to make this explicit in our docs? (Please open a JIRA issue if you > think we should) > > thanks, > dims > > On 4/19/05, David Kaelbling <[EMAIL PROTECTED]> wrote: > > Hi, > > > > What license is code generated by wsdl2java under? Apache 2.0? Public > > domain? I couldn't find an explicit reference in the docs. > > > > Thanks, > > David > > > > -- > > David KAELBLING 100 Beaver St., Waltham MA 02453-8425 > > <[EMAIL PROTECTED]> 781-891-5100 ext 121, fax -5145 > > > > > > > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/ >
Re: boolean type
It works in my test case - generates "boolean" if nillable is false and Boolean for nillable=true. Can you provide the sample code to reproduce the issue. - venkat On 4/19/05, Joe Plautz <[EMAIL PROTECTED]> wrote: > Hello, > > In using wsdl2java to create our services we're running into some > issues. When nillable is set to true we are expecting the Wrapper java > types to be used, but it's not. We run into this issue particularly when > we use booleans. Is this a known issue? Has anyone else had to deal with > this? Or, are we not understanding what's supposed to happen with > wsdl2java correctly? Any help would be appreciated. > > Thanks, > Joe Plautz >
Re: Timeouts
Default is 60 seconds, i guess. The value should be an integer in milliseconds. See the javadoc for Call interface in the apidocs that shipped with Axis distributable for more details. - venkat On 4/19/05, Jyrki Saarinen <[EMAIL PROTECTED]> wrote: > Venkat Reddy wrote: > > >You can try changing the default behaviour using a property > >axis.connection.timeout while starting up the client. This will set > >the timeout on the Stub. > > > Thanks. > > What might be the default value and where can I find documentation about this > property and other properties? > > Jyrki > >
Re: Timeouts
You can try changing the default behaviour using a property
axis.connection.timeout while starting up the client. This will set
the timeout on the Stub.
- venkat
On 4/19/05, Jyrki Saarinen <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I have a web service that is quite long running before the response is
> sent to the
> SOAP client. I'm getting the following AxisFault:
>
> AxisFault
> faultCode: {http://xml.apache.org/axis/}HTTP
> faultSubcode:
> faultString: (0)null
> faultActor:
> faultNode:
> faultDetail:
>{}:return code: 0
>
>{http://xml.apache.org/axis/}HttpErrorCode:0
>
> (0)null
>at
> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:693)
>at
> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:141)
>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:2754)
>at org.apache.axis.client.Call.invoke(Call.java:2737)
>at org.apache.axis.client.Call.invoke(Call.java:2413)
>at org.apache.axis.client.Call.invoke(Call.java:2336)
>at org.apache.axis.client.Call.invoke(Call.java:1793)
>
> Does this timeout come from the server or the client, and how do I
> increase this timeout?
>
> Jyrki
>
>
Re: Encoding request as iso8859_1
Do you have a test case that demostrates the issue? thanks venkat On 4/18/05, Kim Thrysøe <[EMAIL PROTECTED]> wrote: > Is it possible to configure Axis to post requests using a charset other > that UTF8, eg. iso8859_1? > > This question has been posted a while ago > (http://marc.theaimsgroup.com/?l=axis-user&m=104617666812022&w=2), but I > failed to find a response. > > thanks > kim >
Re: Server Selection
Tomcat 5 is better choice, but seems you got some basic issues with installating axis on Tomcat. Please refere to user guide and post the stack trace if any. - venkat On Apr 12, 2005 3:58 AM, Nikolaos Diakos <[EMAIL PROTECTED]> wrote: > > > Hello. > > > > I am trying to deploy a single sample web service and for sometime now I was > using Tomcat 5.0.28 sever for windows. > > I managed to deploy the sample services but I was getting all kinds of > errors when I was trying to test them.I didn't tested > > Successfully not a single sample file. I tried everything an finally I > decided to change server version. I installed Tomcat 4.1.31 and > > Now I can't even get the server running.(500 server internal error).Do you > think that the 5 version of Tomcat is better choice for axis? > > > >
Re: Newbie:server-config.wsdd:Persisting the deployment of services on weblogic 7.0
It does persist on Tomcat. Do you have any file I/O permission issues to write to the config file in weblogic? - venkat On Apr 12, 2005 3:31 AM, A K <[EMAIL PROTECTED]> wrote: > Hi All, > I am deploying some EJBs as webservices using Axis on Weblogic 7.I have > to redepoly the services using AdminClient everytime weblogic is > restarted. Once I restart the weblogic only the services that were a part of > the server-config.wsdd when I deploy the application for the first time > are available. > > Any pointers to persisting the changes to the server-config.wsdd after > the deployment of the services through AdminClient would be helpful. > > Editing the weblogic start script to call AdminClient is not sounding > an appealing idea to me ;-) > > Thanks and Regards, > Amit > > > > Do you Yahoo!? > Yahoo! Small Business - Try our new resources site! > >
Re: .NET cred (I think I am so much closer...) Unbuffered entity enclosing request can not be repeated.
just to give a data point - i also faced the same error 2 months back
(feb 7). The NTLM challenge from proxy requires the request to be
re-sent, and i didnt know how to set the PostMethod to buffer it for
sending it again.
- venkat
On Apr 12, 2005 1:48 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Can u send a stack trace?
>
> On 4/11/05, John Windberg <[EMAIL PROTECTED]> wrote:
> > No change with "corp\\Administrator"
> > Still the unbuffered entity error.
> >
> > -J
> >
> > --- Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> >
> > > It's the opposite "Domain\Administator"
> > >
> > > On 4/11/05, John Windberg <[EMAIL PROTECTED]>
> > > wrote:
> > > > no, it was just "Administrator"
> > > > I just tried "Administrator\\Domain" and got the
> > > same
> > > > error.
> > > > The machine is domain for "corp", within
> > > > productsight.com, so I tried various values...
> > > >
> > > > "Administrator\\corp"
> > > > "Administrator\\productsight"
> > > > "Administrator\\corp.productsight.com"
> > > > "Administrator\\productsight.com"
> > > >
> > > >
> > > > -J
> > > > --- Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> > > > > my bad...Actually the nightly has this patch
> > > already
> > > > > in it. next
> > > > > question, is your username is in the form
> > > > > "user\domain"
> > > > >
> > > > > -- dims
> > > > >
> > > > > On 4/11/05, John Windberg <[EMAIL PROTECTED]>
> > > > > wrote:
> > > > > > Patch?
> > > > > > It says to change this, but it doesn't say
> > > where
> > > > > this
> > > > > > is...
> > > > > > (I have the nightly build jar file of axis,
> > > not
> > > > > the
> > > > > > source.)
> > > > > >
> > > > >
> > > ---
> > > > > > the anwser is to change :
> > > > > > ((PostMethod)method).setRequestBody(new
> > > > > > ByteArrayInputStream(baos.toByteArray()));
> > > > > >
> > > > > > into
> > > > > >
> > > > > > RequestEntity rq = new
> > > > > > ByteArrayRequestEntity(baos.toByteArray());
> > > > > > ((PostMethod)method).setRequestEntity(rq);
> > > > > >
> > > > >
> > > ---
> > > > > >
> > > > > >
> > > > > > --- Davanum Srinivas <[EMAIL PROTECTED]>
> > > wrote:
> > > > > > > Hmm...looks like this bug still exists. try
> > > the
> > > > > > > patch mentioned here:
> > > > > > >
> > > http://issues.apache.org/jira/browse/AXIS-1850
> > > > > > >
> > > > > > > If that fixes your problem, then i will
> > > check it
> > > > > in
> > > > > > > ASAP :)
> > > > > > >
> > > > > > > -- dims
> > > > > > >
> > > > > > > On 4/11/05, John Windberg
> > > <[EMAIL PROTECTED]>
> > > > > > > wrote:
> > > > > > > > How do I create/set/use credentials?
> > > > > > > >
> > > > > > > > Steps so far...
> > > > > > > >
> > > > > > > > 1. downloaded nightly build of axis
> > > > > > > > 2. create eclipse project
> > > > > > > > 3. added all axis libs to project
> > > > > > > > 4. added xerces-2_5_0 libs to project
> > > > > > > > 5. added junit libs to project
> > > > > > > > 6. created ant task to generate via
> > > wsdl2java
> > > > > > > > (server is win2003/Sharepoint with MS
> > > > > sharepoint
> > > > > > > > services)
> > > > > > > > 7. generated client classes
> > > > > > > > 8. extracted client-config.wsdd
> > > > > > > > 9. modified such with
> > > > > > > >
> > > > > org.apache.axis.transport.http.CommonsHTTPSender
> > > > > > > > as transport
> > > > > > > > 10. run simplest method from test class
> > > > > > > > test1ListsSoapGetListCollection()
> > > > > > > >
> > > > > > > > Console shows:
> > > > > > > > - Unable to find required classes
> > > > > > > > (javax.activation.DataHandler and
> > > > > > > > javax.mail.internet.MimeMultipart).
> > > Attachment
> > > > > > > support
> > > > > > > > is disabled.
> > > > > > > > - ntlm authentication scheme selected
> > > > > > > > - No credentials available for NTLM > > > > > > > realm>@iceland:80
> > > > > > > >
> > > > > > > > junit error:
> > > > > > > > AxisFault
> > > > > > > > faultCode:
> > > {http://xml.apache.org/axis/}HTTP
> > > > > > > > faultSubcode:
> > > > > > > > faultString: (401)Unauthorized
> > > > > > > >
> > > > > > > > 11. in test added lines before client
> > > call:
> > > > > > > >
> > > binding.setUsername("Administrator");
> > > > > > > > binding.setPassword("Password");
> > > > > > > > value =
> > > binding.getListCollection();
> > > > > > > >
> > > > > > > > Now I see:
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > {http://xml.apache.org/axis/}stackTrace:org.apache.commons.httpclient.ProtocolException:
> > > > > > > > Unbuffered entity enclosing request can
> > > not be
> > > > > > > > repeated.
> > > > > > > > at
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:483)
> > > > > > > >
> > > > > > > > and no errors in the console...
> > > > > > > >
> > > > > > > > oh, so
Axis 1.x and [Axis2]
I have a bunch of questions related to Axis releases in general for both 1.x and 2.0 1.Its nice to hear 1.2 release is round the corner (or the weekend). What's after that? Are we going to start working for 1.3? What are the major changes / features to expect in 1.3? I think we should have 1.3, may be to fix the remaining bugs, if any, and for continued support for 1.x. Has the Axis 1 ship already "sailed and reached its destination"? (as Tom said once). 2.What's the timeline for Axis2.0? Is June-2006 is a good guess for the first version go GA? 3.Until 2.0 comes out stable and complete, I think we should also keep good support for 1.x. But I see most of us focusing on 2.0. 4.What's the migration plan from 1.x to 2.0? Looks like 2.0 doesn't guarantee backward compatibility with 1.x code. And may be we are not too keen on support for JAX-RPC support. 5.Currently if I have code running Axis 1.2, what are the things I should consider or be aware of while switching over to 2.0? – stubs need to be re-generated, change in programming model etc. thanks Venkat
Re: How to dump the raw SOAP Envelope?
You can write a tiny logging handler to do something like - Transformer transformer = TransformerFactory.newInstance().newTransformer(); StringWriter stringWriter = new StringWriter(128); transformer.transform(new DOMSource(env), new StreamResult(stringWriter)); StringBuffer buffer = stringWriter.getBuffer(); - venkat On Apr 8, 2005 3:55 PM, Jin-Ha Tchoe <[EMAIL PROTECTED]> wrote: > Hi, > > we use Axis 1.2 Alpha with Tomcat 4.0.3 and Castor 0.95 for a > SOAP-Service. Sometimes we have customers you are not accustomed to SOAP > and have lots of problems using our Service. The problems range from > simple typos and wrong namespaces to forgetting the SOAP-Envelope. > > Whenever Axis and Castor are unable to determine the right Service or > (Un-)marshal the message, the most the customers can see (and therefore > us) is a simple AxisFault. Unfortunately that does not help us see what > exactly is going wrong. So, is there a way for Axis to dump the complete > raw SOAP Envelope _before_ doing its work, so that we can something? > > Many thanks in advance, > > Jin-Ha Tchoe > -- > Jin-Ha Tchoe <[EMAIL PROTECTED]> > >
Re: Null Pointer Exception
try setting the TypeMappingRegistry before calling emitToString, if you can get hold of msgContext - emitter.setTypeMappingRegistry(msgContext.getTypeMappingRegistry()); - venkat On Apr 6, 2005 8:17 PM, Virginie Legrand <[EMAIL PROTECTED]> wrote: > Here is the Stack trace : > > Exception in thread "main" java.lang.NullPointerException >at org.apache.axis.wsdl.fromJava.Emitter.init(Emitter.java:574) >at org.apache.axis.wsdl.fromJava.Emitter.getWSDL(Emitter.java:465) >at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:326) >at > org.apache.axis.wsdl.fromJava.Emitter.emitToString(Emitter.java:399) > > Venkat Reddy wrote: > > > Can you provide the full exception stacktrace? > > > > - venkat > > > > > > On Apr 6, 2005 2:39 PM, *Virginie Legrand* > > <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Does anybody never encounter this issue ?? > > > > Virginie Legrand wrote: > > > > > Hello, > > > > > > I use axis axis-1_2RC3 and wsdl4j in order to generate a WSDL file. > > > Here is a sample of my code : > > > Emitter emitter = new Emitter(); > > > emitter.setDisallowedMethods(disallowedMethods); > > > emitter.setAllowedMethods(allowedMethods); > > > emitter.setLocationUrl(urlRouter); > > > emitter.setIntfNamespace(namespace); > > > emitter.setImplNamespace(namespace); > > > emitter.setCls(c); > > > emitter.setServiceElementName(serviceName); > > > String wsdl = emitter.emitToString(Emitter.MODE_ALL); > > > > > > > > > when calling the emitToString() method, I get a > > NullPointerException. > > > I worked when I was using previous version of axis. > > > What do I do wrong here ? > > > > > > Thanks for your help > > > > > > Regards, > > > > > > Virginie > > > > > > > > >
Re: Programmatic Service Deployment
Instead of a handler, a servlet filter for AxisServlet could be a better place to do this ? - venkat On Apr 5, 2005 9:09 PM, Bradley Mazurek <[EMAIL PROTECTED]> wrote: Hi,I'm writing some infrastructure that is expected to take a Class and aservice name (String), and deploy a service with the provided name,dispatching requests to instances of the given class.I know the way I'd like to accomplish this, but I'm running into somedifficulties.What I'd like to do is use a handler to look at the request when itarrives. If it is a request to a service I am aware of, but has notbeen deployed, I deploy it using the AdminClient/AxisServlet, similar towhat I would expect JWS files are doing, and the request is serviced.The problem is that the handlers (even transport handlers?) are onlybeing invoked on requests for services that are already deployed.Is there any way for Axis users to accomplish something similar to whatJWS handlers do?--Brad
Re: Null Pointer Exception
Can you provide the full exception stacktrace? - venkat On Apr 6, 2005 2:39 PM, Virginie Legrand <[EMAIL PROTECTED]> wrote: Does anybody never encounter this issue ??Virginie Legrand wrote:> Hello,>> I use axis axis-1_2RC3 and wsdl4j in order to generate a WSDL file.> Here is a sample of my code :> Emitter emitter = new Emitter();> emitter.setDisallowedMethods(disallowedMethods);> emitter.setAllowedMethods(allowedMethods);> emitter.setLocationUrl(urlRouter);> emitter.setIntfNamespace(namespace);> emitter.setImplNamespace(namespace);> emitter.setCls(c);> emitter.setServiceElementName(serviceName);> String wsdl = emitter.emitToString(Emitter.MODE_ALL);>>> when calling the emitToString() method, I get a NullPointerException.> I worked when I was using previous version of axis.> What do I do wrong here ?>> Thanks for your help>> Regards,>> Virginie>
Re: string arrays as input parameters in in doc/literal services
On Apr 6, 2005 5:07 AM, MKW <[EMAIL PROTECTED]> wrote: > plus I've tried adding (is this read when there is a ref to a wsdl file?): > xmlns:ns="http://dct"; >qname="ns:ArrayOf_xsd_string" >type="java:string[]" >serializer="org.apache.axis.encoding.ser.ArraySerializerFactory" > deserializer="org.apache.axis.encoding.ser.ArrayDeserializerFactory" >encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > try changing the type to type="java:java.lang.String[]" - venkat
Re: List of Possible Exception Messages?
how about the messages in ws-axis\java\build\classes\org\apache\axis\i18n\resource.properties? - venkat On Apr 5, 2005 7:18 PM, Mark Leone <[EMAIL PROTECTED]> wrote: > My project is consuming services from an Axis server, and we'd like to > compile a list of the possible faultstring values we could get returned > in a SOAP fault message, so we can design an auditing service that > properly accounts for all known error conditions that fit certain > criteria. I thought I might get this info from the Axis source code, but > it looks like I'd have to go through every class that invokes an > Exception, and note the message string that it passes to the exception > object, as the message strings with which exceptions are invoked usually > make their way into the faultstring element of the SOAP fault message. > The info is not important enough to justify that sort of effort, but I > was wondering if there might be documented somewhere already a list of > the exception messages/faultstring values generated by the Axis code. > Even a partial list would be of some value. > >
Re: gSOAP 2.7 (client)<-> Axis Java 1.2rc3 Interoperability problem
You need to copy the wsdl file to WEB-INF directory, or wherever the URL points to as specified in your wsdd file. Redeploy the service and point your browser to ?WSDL. The wsdl displayed in browser should identify the message parts according to the wsdl file definitions. - venkat On Apr 5, 2005 4:28 PM, Bruno LEDOUX <[EMAIL PROTECTED]> wrote: > I tried it but it didn't work. Is the wsdl file required by Axis only when > deploying the service ? Do I also need to copy it in the WEB-INF directory. > > Anyway I "googled" and found I was not the only one having > troubles: cf http://java2.5341.com/msg/99739.html > > Thanks for your help. > > Bruno > > Got it. Axis server side doesn't have access to your wsdl file. > > you can specify something like this in wsdd file while deploying - > > > > > > . .. .. .. .. .. . > > /srv/tomcat/webapps/axis/wsdl/GetQuote.wsdl > > > > > > hope that helps > > - venkat > > > > > > On Apr 5, 2005 2:27 PM, Bruno LEDOUX <[EMAIL PROTECTED]> wrote: > >> Yes it does, but the part name should be "result" instead of > >> "getQuoteReturn" or am I misinterpreting the WSDL file ? > >> > >> Bruno > >>> But, doesn't the operation defintion inside portType indicate > >>> "GetQuoteResponse"? > >>> > >>> > >>> > >>> > >>> > >>> > >>> - venkat > >>> > >>> > >>> On Apr 5, 2005 11:46 AM, Bruno LEDOUX <[EMAIL PROTECTED]> wrote: > Hi , > > I have a problem with the latest version of Axis Java axis-1.2rc3 and > gSOAP > C++. When running the sample "stock" service on Axis and calling the > getQuote method with gSOAP, the low level SOAP Response returned is the > following: > > ... > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:ns1="urn:xmltoday-delayed-quotes"> > > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xsi:type="xsd:float" > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>90.32 > > ... > > PROBLEM: gSOAP doesn't manage to read the return value because it should > be > stored in a tag named "result" as stated in the WSDL file > (GetQuote.wsdl): > > ... > > > > ... > > Any Ideas ? > > Bruno > > > >> > >> > >
Re: gSOAP 2.7 (client)<-> Axis Java 1.2rc3 Interoperability problem
Got it. Axis server side doesn't have access to your wsdl file. you can specify something like this in wsdd file while deploying - . .. .. .. .. .. . /srv/tomcat/webapps/axis/wsdl/GetQuote.wsdl hope that helps - venkat On Apr 5, 2005 2:27 PM, Bruno LEDOUX <[EMAIL PROTECTED]> wrote: > Yes it does, but the part name should be "result" instead of > "getQuoteReturn" or am I misinterpreting the WSDL file ? > > Bruno > > But, doesn't the operation defintion inside portType indicate > > "GetQuoteResponse"? > > > > > > > > > > > > > > - venkat > > > > > > On Apr 5, 2005 11:46 AM, Bruno LEDOUX <[EMAIL PROTECTED]> wrote: > >> Hi , > >> > >> I have a problem with the latest version of Axis Java axis-1.2rc3 and gSOAP > >> C++. When running the sample "stock" service on Axis and calling the > >> getQuote method with gSOAP, the low level SOAP Response returned is the > >> following: > >> > >> ... > >> > >> >> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > >> xmlns:ns1="urn:xmltoday-delayed-quotes"> > >> > >> > >> >> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > >> xsi:type="xsd:float" > >> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>90.32 > >> > >> ... > >> > >> PROBLEM: gSOAP doesn't manage to read the return value because it should be > >> stored in a tag named "result" as stated in the WSDL file (GetQuote.wsdl): > >> > >> ... > >> > >> > >> > >> ... > >> > >> Any Ideas ? > >> > >> Bruno > >> > >> > >
Re: gSOAP 2.7 (client)<-> Axis Java 1.2rc3 Interoperability problem
But, doesn't the operation defintion inside portType indicate "GetQuoteResponse"? - venkat On Apr 5, 2005 11:46 AM, Bruno LEDOUX <[EMAIL PROTECTED]> wrote: > Hi , > > I have a problem with the latest version of Axis Java axis-1.2rc3 and gSOAP > C++. When running the sample "stock" service on Axis and calling the > getQuote method with gSOAP, the low level SOAP Response returned is the > following: > > ... > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:ns1="urn:xmltoday-delayed-quotes"> > > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xsi:type="xsd:float" > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>90.32 > > ... > > PROBLEM: gSOAP doesn't manage to read the return value because it should be > stored in a tag named "result" as stated in the WSDL file (GetQuote.wsdl): > > ... > > > > ... > > Any Ideas ? > > Bruno > >
Re: How does one extract the key (say Symmetric Key) from the Key Info?
may be you can get more help in fx-dev or xml security forums ... On Apr 5, 2005 12:38 PM, anshuk pal chaudhuri <[EMAIL PROTECTED]> wrote: > How does one extract the value of the symmetric key > from the KeyInfo Element from the Encrypted XML > Document? > That I am trying to use In XML Decryption. > And i am trying to do that using XML Security APIS. > Looking forward for ur reply. > > > __ > Do you Yahoo!? > Make Yahoo! your home page > http://www.yahoo.com/r/hs >
Re: what is the different between org.apache.axis.hander.Handler and javax.xml.rpc.handler.Handler ?
The javax.xml.rpc.handler.Handler is provided for compatibilty with JAX-RPC programming model. The org.apache.axis.handler.Handler is the central piece in Axis arctitecutre for message processing. Naturally the same is used for message handlers. It is recommended to use org.apache.axis.handler.Handler, unless you really want the handlers to be JAX-RPC compliant. Please refer to axis documentation for further details on axis handler architecture. - venkat On Apr 5, 2005 1:04 PM, Pham Hoai Van <[EMAIL PROTECTED]> wrote: > Dear all, > I used both Handler of org.apache and javax.xml.rpc. > Why do AXIS define a new Handler when using > javax.xml.rpc.handler.Handler is sufficent I think ? > In which case should we use axis's Handler or Java' Handler ? > Thanks for reading. > Best Regards, > - > Pham Hoai Van > Y!: hoaivanpham > Tel: 7.220.105 > Mobile: 0915.116.202 > Website: http://hoaivan.info > >
Re: possible ways of creating WSDL file
Regarding errors due to manual creation of WSDL, use graphical WSDL editors instead. I also think that the text version of a WSDL document is analogous to serialized form of a database schema, or a use case or a class diagram. Create and manipulate, and generate code from all these the same way. I agree with you that Java2WSDL is good for prototyping. I also think it is useful where web service facade is an after-thought for existing systems, and another use is to update WSDL document to reflect changes in the code any time. However, if we consider iterative development, then the question is the same as - do we do the class diagrams to start with or write the code first, assuming we have tools to generate one from the other. I would say we need minimal design artefacts to start with, to express end-to-end working of a system, then fill in the details as the implementation goes on. But the overall integrity of the system is the reponsibilty of the design and not the implementation. So the design tends to dictate implementation, though it builds up from fedback. -venkat On Thu, 24 Mar 2005 09:58:23 -0500, Ayers, Sam <[EMAIL PROTECTED]> wrote: > Then, are you saying java2wsdl should not even exist as a tool? > > Again, take the analogy of round-trip software engineering (model driven > architecture). You change your system by modifying the diagrams, generating > the code, or, conversely, by modifying your code, generating the diagrams. > > For a new model-driven project, up-front you start with diagrams - i.e. the > "forward-engineering path". Then, at some point later, you modify the code > and regenerate the diagrams from the code. > > Another analogy is iterative development. With iterative development, it > really doesn't matter how you get to your requirements, so long as you do get > to them within the time and cost constraints of your project. Sometimes in > order to produce good requirements quickly, you must do some rapid > prototyping. > > This same idea applies to WSDL. Sometimes, in order to get good WSDL > quickly, you must do some rapid prototyping. The wsdl generation from code > helps greatly in this process. You just have to make sure that before the > project is deeply into coding, and before outside vendors or partners have > been asked to develop to your wsdl, that everyone agrees to the wsdl, and > that the wsdl meets the interoperability requirements of your project. > > Sam > > -Original Message- > From: Venkat Reddy [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 24, 2005 8:08 AM > To: axis-user@ws.apache.org > Subject: Re: possible ways of creating WSDL file > > I agree with Anne. At design level, stuff like WSDL, database schema, > interfaces with existing systems and workflow constitute the overall > system design. And all of them are participants and pieces in the > pipeine in ensuring the integrity of the overall system. Java > interfaces are just one kind of implementation that follow the design. > They should not dictate the WSDL, unless the design is being reverse > engineered from java code. Iterative approach for WSDL is just as good > as it is for designing a database - i mean, we need it in right > amount. > > jmho, > -- venkat > > On Thu, 24 Mar 2005 07:37:02 -0500, Ayers, Sam <[EMAIL PROTECTED]> wrote: > > I believe you are all correct, from different perspectives. But, I believe > > one must take into account the same lessons learned from "round-trip" > > engineering in software development. > > > > 1) If it is a new system, starting from scratch, and involving > > heterogeneous systems integration, yes, it is best to focus on the > > interface early in the lifecycle, and perhaps design the WSDL before > > coding. After the WSDL is "roughed-in", use the round trip tools > > (wsdl2java) to maintain. > > > > 2) If the system involves extension of an existing legacy code base it is > > practical to "reverse engineer" the interface from the code, starting with > > code and generating the wsdl. Then, you can maintain the wsdl by editing > > the wsdl, or by editing the code, and using the round-trip tools to keep > > them in synch. > > > > 3) For expert developers who are relatively new to web services and SOAP > > (i.e. exactly the audience we are trying to bring up to get on board) I > > believe writing WSDL from the get-go is impossible. You must start from > > code, generate the wsdl, then hopefully learn-by-doing by examining the > > output wsdl, and maintaining it moving forward. Insisting that expert > > developers start by creating wsdl is somewhat akin to the round-trip > > eng
Re: possible ways of creating WSDL file
I agree with Anne. At design level, stuff like WSDL, database schema, interfaces with existing systems and workflow constitute the overall system design. And all of them are participants and pieces in the pipeine in ensuring the integrity of the overall system. Java interfaces are just one kind of implementation that follow the design. They should not dictate the WSDL, unless the design is being reverse engineered from java code. Iterative approach for WSDL is just as good as it is for designing a database - i mean, we need it in right amount. jmho, -- venkat On Thu, 24 Mar 2005 07:37:02 -0500, Ayers, Sam <[EMAIL PROTECTED]> wrote: > I believe you are all correct, from different perspectives. But, I believe > one must take into account the same lessons learned from "round-trip" > engineering in software development. > > 1) If it is a new system, starting from scratch, and involving heterogeneous > systems integration, yes, it is best to focus on the interface early in the > lifecycle, and perhaps design the WSDL before coding. After the WSDL is > "roughed-in", use the round trip tools (wsdl2java) to maintain. > > 2) If the system involves extension of an existing legacy code base it is > practical to "reverse engineer" the interface from the code, starting with > code and generating the wsdl. Then, you can maintain the wsdl by editing the > wsdl, or by editing the code, and using the round-trip tools to keep them in > synch. > > 3) For expert developers who are relatively new to web services and SOAP > (i.e. exactly the audience we are trying to bring up to get on board) I > believe writing WSDL from the get-go is impossible. You must start from > code, generate the wsdl, then hopefully learn-by-doing by examining the > output wsdl, and maintaining it moving forward. Insisting that expert > developers start by creating wsdl is somewhat akin to the round-trip > engineering "paralysis by analysis". You'll end up spending large amounts of > time trying to create and perfect the WSDL, while in the end the project > fails because you took too long analyzing and creating the interface. > > So, I believe the answer is in "rapid iteration", i.e. successive > approximation utilizing both techniques, and choosing the right one at the > right moment. To insist on working WSDL before a project begins, especially > for legacy systems integration, is somewhat akin to following the "waterfall > model" of software development. Instead, we need to be flexible, rapidly > iterate, and judiciously use all tools at our disposal. > > Sam > > -Original Message- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 23, 2005 6:02 PM > To: axis-user@ws.apache.org > Subject: Re: possible ways of creating WSDL file > > In a better world, you have a XML Schema administration team (similar > to your DBA team) that is responsible for developing the schemas that > applications will communicate with. (Do your developers define their > own database schemas???) > > When developers build services, they should be handed the schemas they > are supposed to use, and then map those schems to their code. > > Developers should not generate WSDL from code. > > Anne > > On Wed, 23 Mar 2005 14:55:38 -0800, Tim K. (Gmane) <[EMAIL PROTECTED]> wrote: > > In an ideal world I would agree with Anne. However, consider this > > scenario: you have a team of 10+ developers working on a server side API > > that follows the rules to allow it to be easily exposed as web services. > > The API has over 200+ methods total, distributed over 20+ modules. Each > > module would be exposed as a web service, hence 20+ WSDL files. The goal > > is to have the API on the server side look exactly the same as the API > > on the client side, so in theory an application built against the API > > could be run in process on the server or remotely via web services. > > > > Now, only a couple of these developers know anything about web services > > and even those developers are just getting their feet wet with web services. > > > > During the development cycle the API's can (slightly) change many times > > a day and everything needs to be recompiled/regenerated. I think it's > > unreasonable in this case to edit any generated WSDL files by hand. It's > > much more reasonable to just fire an ant task that starts with the > > server side java classes, generates the WSDL's and from those the client > > side stubs. This improves the development process a lot. > > > > I hope I'll live to see the day when the tools are good enough to > > achieve this task end to end. Obviously we are not there yet, but we are > > getting close. > > > > Btw, this is not an imaginary scenario, it's the cruel reality I live in > > every day. > > > > Tim > > > > Anne Thomas Manes wrote: > > > I strongly disagree with Sunil. WSDL First (TM) is the way to go. > > > > > > I think it's okay to use java2wsdl to generate a WSDL template to
Re: WSS4J for download in apache
you can download the sources as a bundle at http://cvs.apache.org/snapshots/ws-fx/ On Mon, 7 Mar 2005 12:16:55 +0530, Shahi, Ashutosh <[EMAIL PROTECTED]> wrote: > > http://ws.apache.org/ws-fx/wss4j/cvs-usage.html > > You can get the latest source from the above cvs link and build it using > maven. I don't think WSS4J provides the binaries. > > Ashutosh > > -Original Message- > From: Krthekeyan Suriyanarayanan [mailto:[EMAIL PROTECTED] > Sent: Monday, March 07, 2005 12:05 PM > To: axis-user@ws.apache.org > Subject: WSS4J for download in apache > > HI all, > Could not find WSS4J for download in apache . can any one give me the > url for download. > thanks, > krthekeyan.s > >
