RE: Hopefully a simple problem...
Thank you for the suggestion. I have downloaded a recent version (November 18) but it still fails to compile under VC7. I tried the ANT build but it also got into a tangle. Rather than boring everyone with the details, can I ask first whether this is the right forum? Also I noticed that the following line needs changing (one reason for me trying to recompile): src\platforms\windows\PlatformSpecificWindows.hpp(44): #define PLATFORM_CONFIG_PATH "/axiscpp.conf" On windows platforms /axixcpp.conf does not resolve to anything. It should either be "./axiscpp.conf" or simply "axiscpp.conf" Thank you Juan From: John Hawkins [mailto:[EMAIL PROTECTED] Sent: 03 November 2005 10:13To: Apache AXIS C User ListSubject: Re: Hopefully a simple problem... Hi, I was wrong (although ANT is still our preferred build system) apparently, you are breaking because there are function signature changes between vc6 and vc 7 that we did not know about until post 1.5. You need to upgrade to a more recent build. cheers, John. John Hawkins/UK/[EMAIL PROTECTED] 03/11/2005 09:03 Please respond to"Apache AXIS C User List" To "Apache AXIS C User List" axis-c-user@ws.apache.org cc Subject Re: Hopefully a simple problem... Please could you try the ant instructions here - http://ws.apache.org/axis/cpp/antbuild-guide.html I suspect the project files are out of date. Notice to recipient:The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority.
Remote call failure due to stream errors ?
I have a very simple service (implemented in Java) with two methods:
String echo(String message)
and
Future getFuture()
I have tested both through a browser and they are both known to work.
I have used the binary version of Axis C++ 1.5 to generate stubs and
wrote a very simple client that invokes echo() twice followed by
getFuture()
echo works without any problems but getFuture systematically fails with
the following error message returned by the what() method of
SoapFaultException
HTTPTransportException:Output streaming error on Channel while writing
data Channel error 0 while writing data: 'The operation completed
successfully.
'
The only warning I see when I start my client is
Warning - The configuration file was not found (/axiscpp.conf).
Using default values
Could anyone please give me a good hint as to what may be going wrong
here (given that I am a Java programmer and struggle with C++) ?
Here is my client code:
#include stdafx.h
#include SimpleServicePort.hpp
#include Future.hpp
#include axis/GDefine.hpp
int main(int argc, _TCHAR* argv[])
{
char uri[] = http://localhost:7001/webservice/SimpleService;;
SimpleServicePort *ssp = new SimpleServicePort(uri,APTHTTP1_1);
char *response = ssp-echo(Hello World!);
printf(\n%s %s\n\n, response, ssp-echo(And hello again.));
Future *aFuture;
try {
aFuture = ssp-getFuture();
}
catch(SoapFaultException sfe) {
printf(Remote call failed: %s\n, sfe.what());
}
return 0;
}
Thank you in advance
Juan
Notice to recipient:
The information in this internet e-mail and any attachments is confidential and
may be privileged. It is intended solely for the addressee. If you are not the
intended addressee please notify the sender immediately by telephone. If you
are not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful.
When addressed to external clients any opinions or advice contained in this
internet e-mail are subject to the terms and conditions expressed in any
applicable governing terms of business or client engagement letter issued by
the pertinent Bank of America group entity.
If this email originates from the U.K. please note that Bank of America, N.A.,
London Branch and Banc of America Securities Limited are authorised and
regulated by the Financial Services Authority.
Re: [Axis2] Jira for Axis2C
The Jira for Axis2C is here: http://issues.apache.org/jira/browse/AXIS2C Please report bugs and improvements in this Jira. Thanks, Samisa... Lilantha Darshana wrote: I'm copying Dims here in case he has not seen this since as I remember Dims helps us setting that up for Axis1 C++. Thanks -Lilantha -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Sunday, November 13, 2005 11:37 AM To: Apache AXIS C Developers List Subject: Re: [Axis2] Jira for Axis2C What is the procedure for creating a Jira space for Axis2C? Do we have to have a vote, or can we directly request it from infrastructure? Thanks, Samisa... Paul Fremantle wrote: Henrik With Axis/Java we kept the mailing list the same with a [Axis2] marker in the subject line. It did help because people had often already coded things in Axis1 that came up in Axis2 and so there was the opportunity for sharing of ideas/experience and code. Paul On 11/10/05, *Henrik Nordberg* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: From: Samisa Abeysinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org mailto:axis-c-dev@ws.apache.org Sent: Thursday, November 10, 2005 2:24 AM Subject: [Axis2] Jira for Axis2C Hi All, I feels like it is time that we setup Jira for Axis2C, given that we have OM working. I think it is best to have an independant Jira for Axis2C as we have to minimize mix-ups with Axis C++ 1.x issues. Thoughts please... Thanks, Samisa... Would it make sense to have a separate mailing list too? Thanks - Henrik ___ Siebel IT'S ALL ABOUT THE CUSTOMER Visit www.siebel.com This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation.
Axis2C Milestone Release M0.1 Released
Hi All, The first milestone release of Axis2C, M0.1 has been released and could be downloaded at http://www.apache.org/dist/ws/axis2c/ This release includes the C implementation of AXIOM, an important part of Axis2C web service stack. Following features are included 1. OM module 2. Guththila pull parser support 3. libxml2 parser support(only reader is supported as of now) 4. doxygen documentation support 5. A sample demonstrating how to use OM We welcome your early feedback on this implementation. Best Regards Damitha
Re: FW: [Axis2] Deployment packaging
This is well answered in the followingthread in the dev list. An issue caused due tocross posting.. http://www.opensubscriber.com/message/axis-dev@ws.apache.org/2642402.html ~Thilina On 11/24/05, Ajith Ranabahu [EMAIL PROTECTED] wrote: hi all, Well I'm not sure why nobody seems to answer (probably the guys were pretty busy :() but the answer is actually pretty simple. include a lib folder into the archive and put all the jars that you need in there. The service has a seperate classloader so none of the jars you put in the service lib folder will show up in the other applications On 11/24/05, Routis Babis [EMAIL PROTECTED] wrote: Tony Dean wrote:Forwarding to axis-user listserve. -Original Message- From: Tony Dean [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 22, 2005 8:16 AM To: axis-dev@ws.apache.org Subject: [Axis2] Deployment packaging What is the Axis2 best practice for packaging a complex web service application that spans multiple jars?Essentially, to create an Axis2 web service endpoint, you must create a single jar with the following contents: meta-inf/services.xml meta-inf/services.wsdl MyWebServicePortTypeSkeleton.class My concern is making other dependent jars available on the classpath and doing so without affecting other applications. Thanks. Tony Dean SAS Institute Inc. 919.531.6704 [EMAIL PROTECTED] SAS... The Power to Know http://www.sas.comIt is strange that although many people keep asking the same question (including myself), no one in this list has given an answer-- Ajith Ranabahu -- May the SourcE be with u http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
How can I cancel a web service call?
Hi, I’m currently working on a simple web service working with Axis 1.2.1 and Tomcat 5. This web service is working perfectly but I have a problem with long running calls. In fact I would like to know how I can cancel a call which is taking to much time? Did anybody have this problem before or know how to do this? Thanks, Camille
RE: How can I cancel a web service call?
Hi! My approach would be to have a second service that is provided with some unique parameters of the first (long running) call, that internally aborts the first call with traditional thread communication means. Another approach would be to decompose the long running WS into smaller fractions if that is possible and feasible. Best regards, -- DI Günter Grossberger Consultant Tel: +43 1 329 50 161 Software AG Österreich Fax: +43 1 329 50 171 Guglgasse 7-9 GSM: +43 676 833 29 261 1030 Wien http://www.softwareag.com/austria -Original Message- From: HOFFMANN Camille [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 11:21 AM To: axis-user@ws.apache.org Subject: How can I cancel a web service call? Hi, I'm currently working on a simple web service working with Axis 1.2.1 and Tomcat 5. This web service is working perfectly but I have a problem with long running calls. In fact I would like to know how I can cancel a call which is taking to much time? Did anybody have this problem before or know how to do this? Thanks, Camille
Re: How can I cancel a web service call?
Hi, That's seems a good idea but how can I know which thread I should abort. I mean if I running my first web service and it is too long I want to abort and call a second web service doing that. But how can I give the second one an unique parameter on the first one as the first is still running and did give me back anything? I don't know if I 'm clear ... do you have any idea of this ? Thanks Camille ## Hi! My approach would be to have a second service that is provided with some unique parameters of the first (long running) call, that internally aborts the first call with traditional thread communication means. Another approach would be to decompose the long running WS into smaller fractions if that is possible and feasible. Best regards, -- DI Günter Grossberger Consultant Tel: +43 1 329 50 161 Software AG Österreich Fax: +43 1 329 50 171 Guglgasse 7-9 GSM: +43 676 833 29 261 1030 Wien http://www.softwareag.com/austria -Original Message- From: HOFFMANN Camille [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 11:21 AM To: axis-user@ws.apache.org Subject: How can I cancel a web service call? Hi, I'm currently working on a simple web service working with Axis 1.2.1 and Tomcat 5. This web service is working perfectly but I have a problem with long running calls. In fact I would like to know how I can cancel a call which is taking to much time? Did anybody have this problem before or know how to do this? Thanks, Camille
using handlers to identify who is requesting service
Hi I have a small problem with my ws. I'm exposing an api on a framework I'm using and would like to know if a custom handler can get the instance of the backend service, before the request is made, in order to set a parameter in the service class? Basicly I'm trying to get a param from an URL and set it as a private variable in a session bean , because I don't want to add this as a parameter to every soap call. Regards Arnaldur
Defining faults in the WSDD
Title: Nachricht Hi all, does anyone here have knowledge of how to add a fault to a service in a WSDD file that is serializable by AXIS and therefore appears in the auto-generated WSDL file? Since now I have tried to add this: faultclass="my.package.MyException/ where 'MyException' extends java.rmi.RemoteException. When deploying I get a server-site error that the class'java.lang.Throwable' can not be serialized. My web service method throws a 'MyException'. Am I on the right path or is there a better way??? Please advise! Thanks, Denis
RE: How can I cancel a web service call?
Hi, In the simplest case you can send a unique id as an additional parameter to the first call. If you want to abort the call you send the id to the abortion service. You have to register the thread servicing the first call in a central map with the id. Then you can lookup the thread in the second service and call Thread.interrupt(). Best regards, Günter -Original Message- From: HOFFMANN Camille [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 11:46 AM To: axis-user@ws.apache.org Subject: Re: How can I cancel a web service call? Hi, That's seems a good idea but how can I know which thread I should abort. I mean if I running my first web service and it is too long I want to abort and call a second web service doing that. But how can I give the second one an unique parameter on the first one as the first is still running and did give me back anything? I don't know if I 'm clear ... do you have any idea of this ? Thanks Camille ## Hi! My approach would be to have a second service that is provided with some unique parameters of the first (long running) call, that internally aborts the first call with traditional thread communication means. Another approach would be to decompose the long running WS into smaller fractions if that is possible and feasible. Best regards, -- DI Günter Grossberger Consultant Tel: +43 1 329 50 161 Software AG Österreich Fax: +43 1 329 50 171 Guglgasse 7-9 GSM: +43 676 833 29 261 1030 Wien http://www.softwareag.com/austria -Original Message- From: HOFFMANN Camille [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 11:21 AM To: axis-user@ws.apache.org Subject: How can I cancel a web service call? Hi, I'm currently working on a simple web service working with Axis 1.2.1 and Tomcat 5. This web service is working perfectly but I have a problem with long running calls. In fact I would like to know how I can cancel a call which is taking to much time? Did anybody have this problem before or know how to do this? Thanks, Camille
RE: using handlers to identify who is requesting service
Hi, I guess you want your service to access some parameter made available by the handler. You don't need to get the instance of the backend service in the handler. Besides, the service's implementation can access the instance of MessageContext being manipulated by the request chain using MessageContext's static method getCurrentContext(). Add your parameters to the properties of the message context than retrieve those properties in your backend service. Regards, Tony -Message d'origine- De : Arnaldur Hilmisson [mailto:[EMAIL PROTECTED] Envoyé : jeudi 24 novembre 2005 12:00 À : axis-user@ws.apache.org Objet : using handlers to identify who is requesting service Hi I have a small problem with my ws. I'm exposing an api on a framework I'm using and would like to know if a custom handler can get the instance of the backend service, before the request is made, in order to set a parameter in the service class? Basicly I'm trying to get a param from an URL and set it as a private variable in a session bean , because I don't want to add this as a parameter to every soap call. Regards Arnaldur
Re: using handlers to identify who is requesting service
Hi, The problem is that the service bean is in another package (both packages are in jboss), does that work with the static method getCurrentContext()? And just to be sure... is there no way for the handler to call a method in the backend service before the actual call is made? Regards Arnaldur On 11/24/05, zze-ELSOKHON Tony RD-BIZZ-ISS [EMAIL PROTECTED] wrote: Hi, I guess you want your service to access some parameter made available by the handler. You don't need to get the instance of the backend service in the handler. Besides, the service's implementation can access the instance of MessageContext being manipulated by the request chain using MessageContext's static method getCurrentContext(). Add your parameters to the properties of the message context than retrieve those properties in your backend service. Regards, Tony -Message d'origine- De: Arnaldur Hilmisson [mailto:[EMAIL PROTECTED] Envoyé: jeudi 24 novembre 2005 12:00 À: axis-user@ws.apache.org Objet: using handlers to identify who is requesting service Hi I have a small problem with my ws. I'm exposing an api on a framework I'm using and would like to know if a custom handler can get the instance of the backend service, before the request is made, in order to set a parameter in the service class? Basicly I'm trying to get a param from an URL and set it as a private variable in a session bean , because I don't want to add this as a parameter to every soap call. Regards Arnaldur
RE: Defining faults in the WSDD
Title: Nachricht MyExtension should extend AxisFault. Best regards,--DI Günter GrossbergerConsultant Tel: +43 1 329 50 161Software AG Österreich Fax: +43 1 329 50 171Guglgasse 7-9 GSM: +43 676 833 29 2611030 Wien http://www.softwareag.com/austria From: Denis Schlesinger [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 12:00 PMTo: axis-user@ws.apache.orgSubject: Defining faults in the WSDD Hi all, does anyone here have knowledge of how to add a fault to a service in a WSDD file that is serializable by AXIS and therefore appears in the auto-generated WSDL file? Since now I have tried to add this: faultclass="my.package.MyException/ where 'MyException' extends java.rmi.RemoteException. When deploying I get a server-site error that the class'java.lang.Throwable' can not be serialized. My web service method throws a 'MyException'. Am I on the right path or is there a better way??? Please advise! Thanks, Denis
RE: using handlers to identify who is requesting service
I haven't tried using getCurrentContext() with EJB's deployed in other packages. It may work, because the current instance of MessageContext must stay in scope until the full treatment of the response message is completed. It is normally not possible for the handler to access the backend service. According to the Axis Architecture Guide, the LAST handler in the server's request chain dispatches the request to the backend implementation after all the preceding handlers have been invoked. Besides, if you're dispatching to a session stateless EJB, you're not even sure about the way JBoss is creating instances of your EJB classes. I think that working things out with message contexts is much more straightforward. -Message d'origine- De : Arnaldur Hilmisson [mailto:[EMAIL PROTECTED] Envoyé : jeudi 24 novembre 2005 14:04 À : axis-user@ws.apache.org Objet : Re: using handlers to identify who is requesting service Hi, The problem is that the service bean is in another package (both packages are in jboss), does that work with the static method getCurrentContext()? And just to be sure... is there no way for the handler to call a method in the backend service before the actual call is made? Regards Arnaldur
Re: serializing the Map datatype
Hi, I was looking at the DataDeser in examples/encoding and I'm still at a loss. If someone has written a deserializer for a map/hashmap (especially for nested maps), could you please help? Thanks, Don Tam wrote: Hi, Thank you for the response. Do you have a complete example of how to do this? Thanks, Anne Thomas Manes wrote: You will need to write a custom deserializer. On 11/3/05, *Don Tam* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I realize this was quite the newb question, but could please someone point me in the right direction? WSDL2Java is returning a MapEntry[] and making its own MapEntry stuff, but I really want it to use java.util.Map. Thanks, Don Tam wrote: Hi, I had deployed some web services using JWSDP about a year ago, and now I'm trying to get an Axis client to work with it. The problem I'm having is that I'm using WSDL2Java and I'm not quite sure how to tell it that I want things that return map to serialize into java.util.Map. What are the steps I need to take? Is there an example? Here is a snippet of the WSDL that was generated by JWSDP (it's deserialized java.util.Map like this): complexType name=map - complexContent - restriction base=soap11-enc:Array attribute ref=soap11-enc:arrayType wsdl:arrayType=tns:mapEntry[]/ /restriction /complexContent /complexType - complexType name=mapEntry - sequence element name=key type=anyType/ element name=value type=anyType/ /sequence /complexType Thanks,
Dealing with sessions
Hi, i've just started to build my first app using web services and Axis. My business interface has a simple logon method that (if successful) returns a token. This token is to be used for subsequent method calls (it essentially allows me to have a timed session). The question I have is that i now need to add an additional parameter for this token to each business method call. Is there a way around this? I'd much prefer to keep my business methods ignorant of the token. In a typical web app I have used filters for interception. I'm not sure how i could do that with web services. Thanks Rakesh
RE: Dealing with sessions
Hi, Axis lets you define and deploy HANDLERS in order to customize the SOAP processing chain. Handlers are similar in many ways to the filters used for interception in webapps. The use case you described could be easily implemented using handlers. For more information on this, please refer to the Axis Architecture Guide and the Axis API documentation. Regards, Tony -Message d'origine- De : Rakesh Patel [mailto:[EMAIL PROTECTED] Envoyé : jeudi 24 novembre 2005 17:39 À : axis Objet : Dealing with sessions Hi, i've just started to build my first app using web services and Axis. My business interface has a simple logon method that (if successful) returns a token. This token is to be used for subsequent method calls (it essentially allows me to have a timed session). The question I have is that i now need to add an additional parameter for this token to each business method call. Is there a way around this? I'd much prefer to keep my business methods ignorant of the token. In a typical web app I have used filters for interception. I'm not sure how i could do that with web services. Thanks Rakesh
Dynamic typeMapping deserializers
Hi, I already have an old web service running JWSDP. So if I write a deserializer for a datatype, how would I register it with my client so that Axis knows I need to use it for said datatype? Is there a way I can declare this in the code once I have the stub (because I have nothing to deploy)? Thanks, -- Don Tam Manager, Software Development (416)493-6111x143 [EMAIL PROTECTED]
Re: Dynamic typeMapping deserializers
Em Quinta 24 Novembro 2005 15:16, o Don Tam escreveu: Hi, I already have an old web service running JWSDP. So if I write a deserializer for a datatype, how would I register it with my client so that Axis knows I need to use it for said datatype? Is there a way I can declare this in the code once I have the stub (because I have nothing to deploy)? Thanks, I solved seemingly this same problem a while back. With JWSDP and wscompile, you can generate a mapping file, like... wscompile.sh -import -mapping resources/CallCentreWeb_Mapping.xml resources/config-wsdl.xml Now with an axis client, the code is like: String wsdl_loc = http://localhost:8080/CallCentreWebServiceJAR?wsdl;; URL mappinglocation = ClassLoader.getSystemResource(CallCentreWeb_Mapping.xml); URL ws4eeMetaData = ClassLoader.getSystemResource(ws4ee-deploy.xml); QName qname = new QName(http://localhost/callcentreweb;, CallCentreWebService); URL url = new URL(wsdl_loc); org.jboss.webservice.client.ServiceFactoryImpl factory= (org.jboss.webservice.client.ServiceFactoryImpl) ServiceFactoryImpl.newInstance(); javax.xml.rpc.Service service = factory.createService(url, mappinglocation, ws4eeMetaData, qname, null); endpoint = (CallCentreWebEndpoint) service.getPort(CallCentreWebEndpoint.class); ReturnWeb_Login rwl = endpoint.web_Login(1,user,password); ReturnWeb_UserList ul = endpoint.web_user_List(1,sessionStr); The idea here is that you load the mappinglocation from JWSDP into an Axis library. JBoss uses Axis internally, and I picked it because I thought I also needed ws4eeMetaData with the axis descriptor, shown here: deployment xmlns='http://xml.apache.org/axis/wsdd/' xmlns:java='http://xml.apache.org/axis/wsdd/providers/java' xmlns:soap='http://schemas.xmlsoap.org/soap/encoding/' xmlns:xsi='http://www.w3.org/2000/10/XMLSchema-instance' xmlns:xsd='http://www.w3.org/2001/XMLSchema' typeMapping qname=ns2:SimpleStaffEntry xmlns:ns2=urn:BeanService serializer='org.apache.axis.encoding.ser.BeanSerializerFactory' deserializer='org.apache.axis.encoding.ser.BeanDeserializerFactory' type=java:hostedtelecom.callcentreweb.endpoint.ReturnWeb_UserList_Item encodingStyle='' / /deployment In retrospect I ended up calling a lot more than ReturnWeb_UserList_Item, and never changed this file. Bottom line, IIRC you need to find a ServiceFactoryImpl that supports importing a mapping location. HTH, iksrazal
Re: How can I cancel a web service call?
If you want to cancel the call from the client side, do call.setTimeout(mSecToWait) before making the call. -K --- HOFFMANN Camille [EMAIL PROTECTED] wrote: Hi, Im currently working on a simple web service working with Axis 1.2.1 and Tomcat 5. This web service is working perfectly but I have a problem with long running calls. In fact I would like to know how I can cancel a call which is taking to much time? Did anybody have this problem before or know how to do this? Thanks, Camille Ketan Deshpande [EMAIL PROTECTED] __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
fault message type is not being serialized
Title: Nachricht Hallo, I have a declared a fault message type in the WSDD file as follows: operation name="create" returnQName="resultValue" returnType="ns:ServerLogEntry" parameter name="material" type="ns:Material"/ fault name="RIACOMFault" qname="ns:RIACOMFault" type="ns:RIACOMFaultType" xmlns:ns="http://localhost:18080/RIACOM_WS/services/CreateTCMatService" class="com.riacom.standardws.commands.RIACOMFault"/ /operation
fault message type is not being serialized in Axis 1.3
Title: Nachricht Hallo, I have a declared a fault message type in the WSDD file as follows: operation name="create" returnQName="resultValue" returnType="ns:ServerLogEntry" parameter name="material" type="ns:Material"/ fault name="MyFault" qname="ns:MyFault" type="ns:MyFaultType" xmlns:ns="http://myws/services/CreateTCMatService" class="myws.commands.MyFault"/ /operation with the beanmapping: beanMapping xmlns:ns="http://myws/services/CreateTCMatService" qname="ns:MyFaultType" type="java:myws.commands.MyFault" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" / The class myFault extends java.rmi.RemoteException and implements java.io.Serializable I took the example from samples\faults and changed it to my needs. Now I am having the problem that MyFault is not being serialized in the generated WSDL. I only get wsdl:message name="MyFault" /wsdl:message without any part elements. Can anyone tell me what I have done wrong? Thanks! Denis
Resolved: fault message type is not being serialized in Axis 1.3
Title: Nachricht Don't worry, I did notthrow 'MyFault' in my web service method... sorry, my fault ;) -Ursprüngliche Nachricht-Von: Denis Schlesinger Gesendet: Donnerstag, 24. November 2005 19:33An: axis-user@ws.apache.orgBetreff: fault message type is not being serialized in Axis 1.3 Hallo, I have a declared a fault message type in the WSDD file as follows: operation name="create" returnQName="resultValue" returnType="ns:ServerLogEntry" parameter name="material" type="ns:Material"/ fault name="MyFault" qname="ns:MyFault" type="ns:MyFaultType" xmlns:ns="http://myws/services/CreateTCMatService" class="myws.commands.MyFault"/ /operation with the beanmapping: beanMapping xmlns:ns="http://myws/services/CreateTCMatService" qname="ns:MyFaultType" type="java:myws.commands.MyFault" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" / The class myFault extends java.rmi.RemoteException and implements java.io.Serializable I took the example from samples\faults and changed it to my needs. Now I am having the problem that MyFault is not being serialized in the generated WSDL. I only get wsdl:message name="MyFault" /wsdl:message without any part elements. Can anyone tell me what I have done wrong? Thanks! Denis
RE: SOAP Monotor applet
Let me answer my own posting here again. If we support a signed applet that allows us to ask question to allow this SOAPMonitor applet to run in browser. When user gives permission to run the applet has access to system clip board. That way we can cut and paste the text from soap monitor to desired validator including notepad ..;D http://java.sun.com/developer/technicalArticles/Security/Signed/ -Venky -Original Message- From: Jayaraman, Venkatesh [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 10:28 PM To: axis-user@ws.apache.org Subject: RE: SOAP Monotor applet I can do ctrl-C /V on soap monitor also. Just needed a explicit button like CopyRequest and CopyResonse (It is easy to add to the applet code) -Venky -Original Message- From: Toshiyuki Kimura [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 8:01 PM To: axis-user@ws.apache.org Subject: Re: SOAP Monotor applet Hi Venky, I am looking for copy button that will help me to copy the request or responses from the soap monitor to xml spy or other validators. If you use tcpmon (org.apache.axis.utils.tcpmon), you can copy selected messages by pushing 'CTL+C'. Thanks, Toshi On Tue, 15 Nov 2005, Jayaraman, Venkatesh wrote: What kind of GUI enhancement is going on with soap monitor applet? I am looking for copy button that will help me to copy the request or responses from the soap monitor to xml spy or other validators. Any help would be greatly appreciated -Venky
How do I stop WSDL2Java from unwrapping my arrays?
Title: SEC:U How do I stop WSDL2Java from unwrapping my arrays? Hi, I have a couple of Wrapped style services. When defining these services in WSDL, I wrapped all the arrays I defined. However, it appears that WSDL2Java is unwrapping these arrays. The published WSDL files (name?WSDL) differ from the originals. I don't understand why the original definition element name=setUserRequest/ complexType sequence element name=groups type=impl:Arrayofstring/ sequence /complexType /element becomes element name=setUserRequest/ complexType sequence element name=groups maxOccurs=unbounded type=xsd:string/ sequence /complexType /element In the published definition. How do I prevent this? Thanks Russell Thamm
Axis2C Milestone Release M0.1 Released
Hi All, The first milestone release of Axis2C, M0.1 has been released and could be downloaded at http://www.apache.org/dist/ws/axis2c/ This release includes the C implementation of AXIOM, an important part of Axis2C web service stack. Following features are included 1. OM module 2. Guththila pull parser support 3. libxml2 parser support(only reader is supported as of now) 4. doxygen documentation support 5. A sample demonstrating how to use OM We welcome your early feedback on this implementation. Best Regards Damitha
