Re: Sanity Check
Hi, why don't you simply use a base64binary field instead of an attachment? As the attachment is encoded the same way, I can't see any advantage. On top of it, attachments are notoriously tricky, especially in interop scenarios. Cheers Wolfgang --- On Tue, 2/2/10, mhuffman michael.mhuff...@gmail.com wrote: From: mhuffman michael.mhuff...@gmail.com Subject: Sanity Check To: axis-dev@ws.apache.org Date: Tuesday, February 2, 2010, 8:58 PM I've written a web-service in Axis2/C based on an Echo example. Based on this this page: http://wso2.org/library/3618 I've got the echo service working with attachments. However, I ran into a problem using axutil_base64_decode(); it would only decode the first 50 some characters of the message. After some trial and error, I figured out it was having problems with '\r' and '\n' characters in the char *data; and after stripping out all whitespace from the character string, I was able to decode the attachment completely... I'm making a few assumptions, (1) the Pear::Soap implementation that I'm using to test my server is inserting the '\r\n' characters into the mime attachment, despite the client server both run in a UNIX environment (I would imagine this is per the mime spec?); (2) AXIS2/C doesn't contain a function that I'm missing to strip out the line-endings from the encoded attachment before passing off to the decoder? Is this a standard way of going about decoding attachments, or is there a more AXIS2/C preferred (easier) way? And will/would this work differently with streaming? Thanks, --Mike. -- View this message in context: http://old.nabble.com/Sanity-Check-tp27426468p27426468.html Sent from the Axis - Dev mailing list archive at Nabble.com.
Re: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation
Dear ppl, I think this leads us nowhere. Webservices is neither JAVA nor DOTNET nor PHP nor PERL-specific nor should it be. Webservices is expected to interoperate with all of them. How is this to be accomplished? By adhering to the standards laid down for WSDL. So PLEASE restrain yourself to using language constructs which can be clearly defined within the reach of WSDL/XML-Schema, and keep it simple on top of that. It is the JAVA-Programmers or DOTNET-Programmers duty to guarantee that unproper values are not put into WS-clients or WS-Server-stubs!! Cheers, Wolfgang --- On Thu, 1/7/10, Mauro Molinari (JIRA) j...@apache.org wrote: From: Mauro Molinari (JIRA) j...@apache.org Subject: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation To: axis-dev@ws.apache.org Date: Thursday, January 7, 2010, 11:24 AM [ https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797580#action_12797580 ] Mauro Molinari commented on AXIS2-3300: --- I fear I am not really understanding your last intervention. Looking at the source code of org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator and your last patch quickly, it seems that nillable=true is actually specified whenever a type is not a primitive one. So this would actually mean that, after your patch, the behaviour would be the one you mentioned in your comment of 05/Jan/10 05:46 AM. If this is so, feel free to solve again this bug and sorry. I just understood that you opted for removing minOccurs=0 without adding nillable=true for object type parameters. This is ok for me, however keep in mind that .NET 1.1 compatibility will stay compromised. minOccurs=0 always generated by Java2WSDL - problems with .NET client generation -- Key: AXIS2-3300 URL: https://issues.apache.org/jira/browse/AXIS2-3300 Project: Axis2 Issue Type: Bug Components: Tools Affects Versions: 1.3 Reporter: Mauro Molinari Assignee: Deepal Jayasinghe Attachments: axis2-1.4.1.diff When you try to expose a POJO as a webservice, suppose you have two Java methods with the following signatures: public Integer a(String, Integer) public String b(Integer, String) Java2WSDL adds the minOccurs=0 for each element of each complex type, both for the input parameters and for the output parameters. When generating clients using .NET WebService Studio 2.0, the result is the following: - all the generated C# methods input parameters are doubled, except for the string ones: the doubled parameters are booleans whose meaning is: is the previous parameter specified or not? - all the generated C# methods return parameters are void, except for the string ones The actual result are clients with methods like these: public void a(string, int, bool); public string b(int, bool, string); This is obviously a problem, particularly for the void return type. If I remove minOccurs=0, clients are generated correctly by .NET WebService Studio 2.0. The issue is this: why does Java2WSDL always adds minOccurs=0? If its meaning were it can be null, I think nillable=true attribute should be more appropriate... Moreover, if I substitute Integer with int in the original Java class methods, minOccurs=0 is still added by Java2WSDL, even if an int cannot be null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation
Dear ppl, I think this leads us nowhere. Webservices is neither JAVA nor DOTNET nor PHP nor PERL-specific nor should it be. Webservices is expected to interoperate with all of them. How is this to be accomplished? By adhering to the standards laid down for WSDL. So PLEASE restrain yourself to using language constructs which can be clearly defined within the reach of WSDL/XML-Schema, and keep it simple on top of that. It is the JAVA-Programmers or DOTNET-Programmers duty to guarantee that unproper values are not put into WS-clients or WS-Server-stubs!! Cheers, Wolfgang --- On Thu, 1/7/10, Mauro Molinari (JIRA) j...@apache.org wrote: From: Mauro Molinari (JIRA) j...@apache.org Subject: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation To: axis-dev@ws.apache.org Date: Thursday, January 7, 2010, 11:24 AM [ https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797580#action_12797580 ] Mauro Molinari commented on AXIS2-3300: --- I fear I am not really understanding your last intervention. Looking at the source code of org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator and your last patch quickly, it seems that nillable=true is actually specified whenever a type is not a primitive one. So this would actually mean that, after your patch, the behaviour would be the one you mentioned in your comment of 05/Jan/10 05:46 AM. If this is so, feel free to solve again this bug and sorry. I just understood that you opted for removing minOccurs=0 without adding nillable=true for object type parameters. This is ok for me, however keep in mind that .NET 1.1 compatibility will stay compromised. minOccurs=0 always generated by Java2WSDL - problems with .NET client generation -- Key: AXIS2-3300 URL: https://issues.apache.org/jira/browse/AXIS2-3300 Project: Axis2 Issue Type: Bug Components: Tools Affects Versions: 1.3 Reporter: Mauro Molinari Assignee: Deepal Jayasinghe Attachments: axis2-1.4.1.diff When you try to expose a POJO as a webservice, suppose you have two Java methods with the following signatures: public Integer a(String, Integer) public String b(Integer, String) Java2WSDL adds the minOccurs=0 for each element of each complex type, both for the input parameters and for the output parameters. When generating clients using .NET WebService Studio 2.0, the result is the following: - all the generated C# methods input parameters are doubled, except for the string ones: the doubled parameters are booleans whose meaning is: is the previous parameter specified or not? - all the generated C# methods return parameters are void, except for the string ones The actual result are clients with methods like these: public void a(string, int, bool); public string b(int, bool, string); This is obviously a problem, particularly for the void return type. If I remove minOccurs=0, clients are generated correctly by .NET WebService Studio 2.0. The issue is this: why does Java2WSDL always adds minOccurs=0? If its meaning were it can be null, I think nillable=true attribute should be more appropriate... Moreover, if I substitute Integer with int in the original Java class methods, minOccurs=0 is still added by Java2WSDL, even if an int cannot be null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation
Mauro, Of course I understand your practical point exactly and I would very much appreciate easier DOTNET-compatibility too- however: interoperability can realistically only be achieved in areas where standards have been established already (in our real world) For better or worse, there are no official WS-standards for expressing Null-Values of programming languages, DB-Nulls, and much more. (Nor will the two of us be able to establish it now, let alone enforce it - so again: outside of standards its up to the programmer methinks) The central piece of a Web Service is, conceptually, a WSDL-definition (description of interface/contract) I am sure a Web Service based on a WS-I conforming WSDL-definition can be called by DOTNET-Clients with no problem, same as by all other WS-I-conforming Clients. (Otherwise twould be a Microsoft-bug) Ask Microsoft about it. WS-I was after all co-founded by Microsoft. So pls demonstrate where exactly an AXIS-generated WSDL is not conforming to these standards. This really would be an AXIS-bug to attend to then. Some new pseudostandard JAVA2DOTNET (which versions of each anyway, what about future developments?) is looking like a dead horse to me. Many of the webservices out there, and in fact, all public ones, have to be reachable by non DOTNET-clients. Maybe even yours - someday! Cheers Wolfgang --- On Thu, 1/7/10, Mauro Molinari mauro.molin...@cardinis.com wrote: From: Mauro Molinari mauro.molin...@cardinis.com Subject: Re: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation To: axis-dev@ws.apache.org Date: Thursday, January 7, 2010, 12:16 PM WJ Krpelan ha scritto: Dear ppl, I think this leads us nowhere. Webservices is neither JAVA nor DOTNET nor PHP nor PERL-specific nor should it be. Webservices is expected to interoperate with all of them. How is this to be accomplished? By adhering to the standards laid down for WSDL. So PLEASE restrain yourself to using language constructs which can be clearly defined within the reach of WSDL/XML-Schema, and keep it simple on top of that. It is the JAVA-Programmers or DOTNET-Programmers duty to guarantee that unproper values are not put into WS-clients or WS-Server-stubs!! Cheers, Wolfgang In an ideal world, I would perfectly agree with you. In a real world, given the importance and market share of .NET, if tools provided by Axis2 don't let me write web services that are correctly callable by .NET clients, I would consider them to be completely useless. Moreover, please notice that the discussion is all about adhering to the standards, but in the way that grants interoperation the most in real-world common scenarios. -- Mauro Molinari Software Designer Developer E-mail: mauro.molin...@cardinis.com
Re: Webservice and javascript calling
Hi, use the same wsdl to create stubs on both sides dont use any proprietory namespaces like *mircosoft* etc Cheers Wolfgang --- On Tue, 12/22/09, abhishah abhishah4...@gmail.com wrote: From: abhishah abhishah4...@gmail.com Subject: Webservice and javascript calling To: axis-dev@ws.apache.org Date: Tuesday, December 22, 2009, 10:15 PM Hi I have a simple webservice which returns Array of Strings. When I try to call same webservice using .htc file of Microsoft, its only taking first value of webservice returned value. If I use .Net webservice then its getting all values. It seems like WSDL file difference between AXis2 generated and .Net generated is causing this thing. Is there anyway I can call webservice using javascript. I tried SOAP javascript client but could not succeed as I am getting access deined error message in IE7 as I try to call remotely deployed webservice. Is there anyway to generate WSDL which looks like .Net created wsdl. Thanks Abhi -- View this message in context: http://old.nabble.com/Webservice-and-javascript-calling-tp2689p2689.html Sent from the Axis - Dev mailing list archive at Nabble.com.
Re: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation
Hi its no bug, at most its a missing (interoperability-) feature - cause if you adapt java2wsdl to some specific microsoft behaviour it gets incompatible with other platforms which makes no sense you could make a interoperability feature request - either here or with mircosoft :) anyway wsdl first is the correct interop approach. consider it. Cheers, Wolfgang --- On Tue, 12/22/09, Gilly Morg (JIRA) j...@apache.org wrote: From: Gilly Morg (JIRA) j...@apache.org Subject: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation To: axis-dev@ws.apache.org Date: Tuesday, December 22, 2009, 1:24 PM [ https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12793598#action_12793598 ] Gilly Morg commented on AXIS2-3300: --- Can anyone tell me the status of this bug?... any solution for this?:S THKS gilly minOccurs=0 always generated by Java2WSDL - problems with .NET client generation -- Key: AXIS2-3300 URL: https://issues.apache.org/jira/browse/AXIS2-3300 Project: Axis2 Issue Type: Bug Components: Tools Affects Versions: 1.3 Reporter: Mauro Molinari Assignee: Deepal Jayasinghe Attachments: axis2-1.4.1.diff When you try to expose a POJO as a webservice, suppose you have two Java methods with the following signatures: public Integer a(String, Integer) public String b(Integer, String) Java2WSDL adds the minOccurs=0 for each element of each complex type, both for the input parameters and for the output parameters. When generating clients using .NET WebService Studio 2.0, the result is the following: - all the generated C# methods input parameters are doubled, except for the string ones: the doubled parameters are booleans whose meaning is: is the previous parameter specified or not? - all the generated C# methods return parameters are void, except for the string ones The actual result are clients with methods like these: public void a(string, int, bool); public string b(int, bool, string); This is obviously a problem, particularly for the void return type. If I remove minOccurs=0, clients are generated correctly by .NET WebService Studio 2.0. The issue is this: why does Java2WSDL always adds minOccurs=0? If its meaning were it can be null, I think nillable=true attribute should be more appropriate... Moreover, if I substitute Integer with int in the original Java class methods, minOccurs=0 is still added by Java2WSDL, even if an int cannot be null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation
Hi, well, dont expect anything but WSDL-first to work reliably in interoperability scenarious - ever! i dont think adopting java2wsdl to some micro* style would be a good idea, because it would break interoperability elsewhere! Cheers, Wolfgang --- On Mon, 11/2/09, Charles Galpin (JIRA) j...@apache.org wrote: From: Charles Galpin (JIRA) j...@apache.org Subject: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation To: axis-dev@ws.apache.org Date: Monday, November 2, 2009, 9:12 PM [ https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772637#action_12772637 ] Charles Galpin commented on AXIS2-3300: --- Well it turns out there is a bug when serving the static copy of my WSDL so I have no work around for this bug. Can you give us an idea of when this might be included Deepal? thanks, charles minOccurs=0 always generated by Java2WSDL - problems with .NET client generation -- Key: AXIS2-3300 URL: https://issues.apache.org/jira/browse/AXIS2-3300 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.3 Reporter: Mauro Molinari Assignee: Deepal Jayasinghe Attachments: axis2-1.4.1.diff When you try to expose a POJO as a webservice, suppose you have two Java methods with the following signatures: public Integer a(String, Integer) public String b(Integer, String) Java2WSDL adds the minOccurs=0 for each element of each complex type, both for the input parameters and for the output parameters. When generating clients using .NET WebService Studio 2.0, the result is the following: - all the generated C# methods input parameters are doubled, except for the string ones: the doubled parameters are booleans whose meaning is: is the previous parameter specified or not? - all the generated C# methods return parameters are void, except for the string ones The actual result are clients with methods like these: public void a(string, int, bool); public string b(int, bool, string); This is obviously a problem, particularly for the void return type. If I remove minOccurs=0, clients are generated correctly by .NET WebService Studio 2.0. The issue is this: why does Java2WSDL always adds minOccurs=0? If its meaning were it can be null, I think nillable=true attribute should be more appropriate... Moreover, if I substitute Integer with int in the original Java class methods, minOccurs=0 is still added by Java2WSDL, even if an int cannot be null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: SOAP styles
Hi, small wonder. One possibility is of course given by the saying every IT-Problem can be solved by another indirection create new webservices out of the description of the old ones and let the new ones call the old ones - performance-issues to the side kind of usual IT-madness, dont cite me Cheers, Wolfgang --- On Mon, 8/31/09, Demetris demet...@ece.neu.edu wrote: From: Demetris demet...@ece.neu.edu Subject: Re: SOAP styles To: axis-dev@ws.apache.org Date: Monday, August 31, 2009, 6:48 PM Hi Wolfgang, thanks for the good info - I did see some of these links and I will go over them. We have an underlying p2p infrastructure that intercepts the SOAP messages from clients to servers without distrupting the operation of the upper layers ( so the soap enginers and the WS implementations remain as is) and routes them across peers. Now that we are adding mobile peers in the mix, including CXF-based ones, Axis2 ones etc. we are seeing some incompatability issues - for ex. CXF does not handle rcp/encoded styles. So how do you suggest we avoid the migration and manage to handle these issues? Thanks again WJ Krpelan wrote: Hi http://ws.apache.org/axis/java/reference.html hopefully answers your last question, dont expect bugfixes any more ;-) there is a migration guide for axis1 to axis2 webservices, http://ws.apache.org/axis2/1_5/migration.html dont think there is any special attention to preserving soap-styles however. its really not in the spirit nowadays, see http://ws-i.org/ you didnt mention why you would want to migrate good luck, Wolfgang --- On Fri, 8/28/09, Demetris demet...@ece.neu.edu wrote: From: Demetris demet...@ece.neu.edu Subject: Re: SOAP styles To: axis-dev@ws.apache.org Date: Friday, August 28, 2009, 7:41 PM Well I will certainly push the notion of upgrading the target servers but there are cases where the customer does not want to do that. So we NEED to deal with deprecated styles - so the question will remain if Axis 1.4 can generate one and only or multiple (even if deprecated) styles programmatically? Cheers WJ Krpelan wrote: Hi, all SOAP styles except doc/lit are kind of deprecated by now and are no longer fully supported by most frameworks, if at all. You better migrate everything to doc/lit, resp. doc/lit wrapped I suppose Cheers, Wolfgang --- On Thu, 8/27/09, Demetris demet...@ece.neu.edu wrote: From: Demetris demet...@ece.neu.edu Subject: SOAP styles To: axis-dev@ws.apache.org Date: Thursday, August 27, 2009, 10:10 PM Hi all, we have some legacy systems still using Axis 1.4 and we need clients from them to generate SOAP rpc/lit or doc/lit instead of rpc/enc - does anyone know if the latter is the default for Axis 1.4 and how it can be manipulated programmatically? Thanks Ruwan Linton wrote: On Thu, Aug 27, 2009 at 11:21 PM, Deepal jayasinghe deep...@gmail.com mailto:deep...@gmail.com wrote: No I can't, I guess I have explained why I can't use it as well, because I cannot differentiate the undeployment call for the hot update and real undeployment. Well, what Amila suggested will work though :-) Of course you can if the file is there then that is hot-update else it is un deployment. I propose adding a update method to the Deployer interface or passing the state as an argument, I would consider undeploy as the update method you can do whatever you want there, and you can just ignore at when it call deploy method. (I know in undeploy method you only get the filename, but since your deployer is domain specific you know what to do with the file name) No, the issue is we need to invoke a different code in the case
Re: SOAP styles
Hi http://ws.apache.org/axis/java/reference.html hopefully answers your last question, dont expect bugfixes any more ;-) there is a migration guide for axis1 to axis2 webservices, http://ws.apache.org/axis2/1_5/migration.html dont think there is any special attention to preserving soap-styles however. its really not in the spirit nowadays, see http://ws-i.org/ you didnt mention why you would want to migrate good luck, Wolfgang --- On Fri, 8/28/09, Demetris demet...@ece.neu.edu wrote: From: Demetris demet...@ece.neu.edu Subject: Re: SOAP styles To: axis-dev@ws.apache.org Date: Friday, August 28, 2009, 7:41 PM Well I will certainly push the notion of upgrading the target servers but there are cases where the customer does not want to do that. So we NEED to deal with deprecated styles - so the question will remain if Axis 1.4 can generate one and only or multiple (even if deprecated) styles programmatically? Cheers WJ Krpelan wrote: Hi, all SOAP styles except doc/lit are kind of deprecated by now and are no longer fully supported by most frameworks, if at all. You better migrate everything to doc/lit, resp. doc/lit wrapped I suppose Cheers, Wolfgang --- On Thu, 8/27/09, Demetris demet...@ece.neu.edu wrote: From: Demetris demet...@ece.neu.edu Subject: SOAP styles To: axis-dev@ws.apache.org Date: Thursday, August 27, 2009, 10:10 PM Hi all, we have some legacy systems still using Axis 1.4 and we need clients from them to generate SOAP rpc/lit or doc/lit instead of rpc/enc - does anyone know if the latter is the default for Axis 1.4 and how it can be manipulated programmatically? Thanks Ruwan Linton wrote: On Thu, Aug 27, 2009 at 11:21 PM, Deepal jayasinghe deep...@gmail.com mailto:deep...@gmail.com wrote: No I can't, I guess I have explained why I can't use it as well, because I cannot differentiate the undeployment call for the hot update and real undeployment. Well, what Amila suggested will work though :-) Of course you can if the file is there then that is hot-update else it is un deployment. I propose adding a update method to the Deployer interface or passing the state as an argument, I would consider undeploy as the update method you can do whatever you want there, and you can just ignore at when it call deploy method. (I know in undeploy method you only get the filename, but since your deployer is domain specific you know what to do with the file name) No, the issue is we need to invoke a different code in the case of hot update. Yes, as I mentioned earlier if the file is there then that is hot-update, else un-deployment. So it should not be a big issues. Anyway I feel I should go for a synapse deployer :-) I though you already have deployer for synapse. I mean a new deployer framework implementation, not an deployer.. anyway synapse doesn't have a deployer yet. Thanks, Ruwan -- Ruwan Linton Technical Lead Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com mailto:ru...@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
Re: SOAP styles
Hi, all SOAP styles except doc/lit are kind of deprecated by now and are no longer fully supported by most frameworks, if at all. You better migrate everything to doc/lit, resp. doc/lit wrapped I suppose Cheers, Wolfgang --- On Thu, 8/27/09, Demetris demet...@ece.neu.edu wrote: From: Demetris demet...@ece.neu.edu Subject: SOAP styles To: axis-dev@ws.apache.org Date: Thursday, August 27, 2009, 10:10 PM Hi all, we have some legacy systems still using Axis 1.4 and we need clients from them to generate SOAP rpc/lit or doc/lit instead of rpc/enc - does anyone know if the latter is the default for Axis 1.4 and how it can be manipulated programmatically? Thanks Ruwan Linton wrote: On Thu, Aug 27, 2009 at 11:21 PM, Deepal jayasinghe deep...@gmail.com mailto:deep...@gmail.com wrote: No I can't, I guess I have explained why I can't use it as well, because I cannot differentiate the undeployment call for the hot update and real undeployment. Well, what Amila suggested will work though :-) Of course you can if the file is there then that is hot-update else it is un deployment. I propose adding a update method to the Deployer interface or passing the state as an argument, I would consider undeploy as the update method you can do whatever you want there, and you can just ignore at when it call deploy method. (I know in undeploy method you only get the filename, but since your deployer is domain specific you know what to do with the file name) No, the issue is we need to invoke a different code in the case of hot update. Yes, as I mentioned earlier if the file is there then that is hot-update, else un-deployment. So it should not be a big issues. Anyway I feel I should go for a synapse deployer :-) I though you already have deployer for synapse. I mean a new deployer framework implementation, not an deployer.. anyway synapse doesn't have a deployer yet. Thanks, Ruwan -- Ruwan Linton Technical Lead Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com mailto:ru...@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
Re: SOAP message structure
Hi, Webservice Engines dont create Standards but try to implement them - as good as it gets anyhow - I'd say developers of Web Services should not need to bother with SOAP at all - apart from extreme cases of interoperability problems. Using a WSDL first approach you should have no problems exchanging your Web Service Engine on one ore both sides - that is, theoretically To answer your question literally - no, I dont think so! Cheers, Wolfgang --- On Thu, 8/27/09, Demetris demet...@ece.neu.edu wrote: From: Demetris demet...@ece.neu.edu Subject: SOAP message structure To: axis-dev@ws.apache.org Date: Thursday, August 27, 2009, 10:17 PM In our migration from the Axis 1.x to Axis2 and beyond, one question that came up was how the SOAP message structure emitted by the client stubs generated by Axis2 is exactly the same as the one that would have been created for the same Web Service from an Axis 1.x stub (considering the same encoding styles). I know the Axis project implements a standard so I am expecting that it still follows that standard across versions - if it offers async invocations or all the other goodies that is a separate layer, but the emitted SOAP messages I am not expecting to change. Is that a correct assumption? Thanks
Re: Axis 1.4 strange characters lt; #13;....
Hi, your strange characters is standard xml-escaped characters obviously are you doing soap-processing by hand? Cheers Wolfgang --- On Mon, 8/24/09, David Vir virch...@gmail.com wrote: From: David Vir virch...@gmail.com Subject: Axis 1.4 strange characters lt; #13; To: axis-dev@ws.apache.org Date: Monday, August 24, 2009, 5:06 PM Hello, My name is David and i have seen that you are an experienced user of axis. I need to connect to one Web Service that have a wsdl that i can't change.=20 I am receiving strange characters in their response: For example: You must present a photo ID when checking in. Your credit card is charged at the time you book. Bed type and smoking preferences are not guaranteed.Your reservation is prepaid and is guaranteed for late arrival. The total charge includes all room charges and taxes, as well as fees for access and booking. Any incidental charges such as parking, phone calls, and room service will be handled directly between you and the property. The wsdl is RPC encoded and i can only use Axis 1.4 because Axis 2 doesn't allow RPC encoded.=20 I don't know how to solve this problem because i receive many strange characters Do you know how to solve, including some header in the stub? The stub of axis have one method setHeader. I have tried the following:=20 stub.setHeader(urn:thisNamespace, charset, ISO-8859-1); or stub.setHeader(urn:thisNamespace, charset, UTF-8); And the result is the same. Do you know how to solve? Regards -- View this message in context: http://www.nabble.com/Axis-1.4-strange-characters--lt13--tp25117707p25117707.html Sent from the Axis - Dev mailing list archive at Nabble.com.
Re: [jira] Commented: (AXIS2-4468) Failure to ISO-8559-1 encode server response message body
Hi all, without claiming knowledge of details here, let me state the obvious: of course utf-8 cannot be cleanly mapped to 8-bit character sets. --- On Wed, 8/19/09, Michael Fryars (JIRA) j...@apache.org wrote: From: Michael Fryars (JIRA) j...@apache.org Subject: [jira] Commented: (AXIS2-4468) Failure to ISO-8559-1 encode server response message body To: axis-dev@ws.apache.org Date: Wednesday, August 19, 2009, 9:38 AM [ https://issues.apache.org/jira/browse/AXIS2-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744939#action_12744939 ] Michael Fryars commented on AXIS2-4468: --- Andreas implies that the problem may be specific to XmlBeans databinding. So I did a quick trial with ADB instead = conversion to ISO-8859-1works correctly with ADB. Failure to ISO-8559-1 encode server response message body - Key: AXIS2-4468 URL: https://issues.apache.org/jira/browse/AXIS2-4468 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.5 Environment: Axis2-1.5 / Tomcat 6.0 / XmlBeans Reporter: Michael Fryars Attachments: exp01_utf8.txt, exp02_iso-8859-1.txt, MfrTestService.aar When request has Content-Type: text/xml;charset=UTF-8, the response is labelled as UTF-8 and any special characters are correctly encoded in UTF-8. But when request has Content-Type: text/xml;charset=iso-8859-1, the response is labelled as ISO-8859-1 but the message body is still encoded as UTF-8. See thread at http://marc.info/?l=axis-userm=125062671421564w=2 for more details. -- List: axis-user Subject: Re: [AXIS2] Control character encoding used by axis2 server for From: Andreas Veithen andreas.veithen () gmail ! com Date: 2009-08-18 20:17:40 Message-ID: b67458760908181317v352bd106wd8fc9ae171728cc3 () mail ! gmail ! com [Download message RAW] Michael, The following log message is interesting: org.apache.axiom.om.impl.MTOMXMLStreamWriter - Returning access to the original output stream: java.io.bufferedoutputstr...@14181418 It means that the xmlbeans databinding bypasses the normal StAX XMLStreamWriter and writes part of the output directly to the underlying byte stream. It is probably at that moment that things go wrong. Can you please open a JIRA [1] and attach a sample AAR (or WAR) that allows us to reproduce this problem? Andreas -- -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: AW: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation
Hi folks, Right - by pure doctrine. However, the need to master xml-schema and wsdl doesnt make life so much easier for web service developers, does it? Cheers Wolfgang --- On Thu, 7/30/09, Ajith Ranabahu ajith.ranab...@gmail.com wrote: From: Ajith Ranabahu ajith.ranab...@gmail.com Subject: Re: AW: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation To: axis-dev@ws.apache.org Date: Thursday, July 30, 2009, 11:06 PM Well said Andreas :) On Thu, Jul 30, 2009 at 11:00 AM, Andreas Veithen andreas.veit...@gmail.com wrote: What this example really shows is that to achieve interoperability and to make everybody's life easier (in an environment where different platforms are used), you should not use a code first approach, but a contract first. Andreas On Thu, Jul 30, 2009 at 11:26, WJ Krpelankrpelan...@yahoo.com wrote: Hi Matthias, in my personal view you are asking to much. to achieve interoperability, its not unusual that one has to adjust automatically generated wsdls/schemes manually. if you try to do webservices fully dynamically you'd better make sure the same webservice-engine is present on both sides Seen from the java side, how could the generator tell from the code whether a variable is meant to be optional or obligatory or even nullable? Usually it can't so it generates the most general approach, which is optional and nullable obviously. Cheers, Wolfgang --- On Wed, 7/29/09, matthias.gai...@t-systems.com matthias.gai...@t-systems.com wrote: From: matthias.gai...@t-systems.com matthias.gai...@t-systems.com Subject: AW: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation To: axis-dev@ws.apache.org Date: Wednesday, July 29, 2009, 2:10 PM Hi Chris (or someone else), maybe it is just a misunderstanding on my side. I am generating a wsdl from a java class via java2wsdl. I am using a simple method like public String login(String user, String password); java2wsdl now generates a wsdl where the parameters are marked with minOccurs=0, which should not be the case for my webservice. Is there a possibility to set the standard behavior to minOccurs=1? As far as I have seen in the DefaultSchemaGenerator the minOccurs=0 is hardcoded. Generated wsdl fragment: xs:element name=login xs:complexType xs:sequence xs:element minOccurs=0 name=user nillable=true type=xs:string/ xs:element minOccurs=0 name=password nillable=true type=xs:string/ /xs:sequence /xs:complexType /xs:element Please help me in clarfying this issue. Thank you, Matthias. -Ursprüngliche Nachricht- Von: Chris van Es (JIRA) [mailto:j...@apache.org] Gesendet: Dienstag, 28. Juli 2009 14:49 An: axis-dev@ws.apache.org Betreff: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation [ https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12736053#action_12736053 ] Chris van Es commented on AXIS2-3300: - I patched the DefaultSchemaGenerator in that fashion and we haven't had any problems to date. Chris. minOccurs=0 always generated by Java2WSDL - problems with .NET client generation -- Key: AXIS2-3300 URL: https://issues.apache.org/jira/browse/AXIS2-3300 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.3 Reporter: Mauro Molinari Assignee: Deepal Jayasinghe Attachments: axis2-1.4.1.diff When you try to expose a POJO as a webservice, suppose you have two Java methods with the following signatures: public Integer a(String, Integer) public String b(Integer, String) Java2WSDL adds the minOccurs=0 for each element of each complex type, both for the input parameters and for the output parameters. When generating clients using .NET WebService Studio 2.0, the result is the following: - all the generated C# methods input parameters are doubled, except for the string ones: the doubled parameters are booleans whose meaning is: is the previous parameter specified or not? - all the generated C# methods return parameters are void, except for the string ones The actual result are clients with methods like these: public void a(string,
Re: AW: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation
Hi Matthias, in my personal view you are asking to much. to achieve interoperability, its not unusual that one has to adjust automatically generated wsdls/schemes manually. if you try to do webservices fully dynamically you'd better make sure the same webservice-engine is present on both sides Seen from the java side, how could the generator tell from the code whether a variable is meant to be optional or obligatory or even nullable? Usually it can't so it generates the most general approach, which is optional and nullable obviously. Cheers, Wolfgang --- On Wed, 7/29/09, matthias.gai...@t-systems.com matthias.gai...@t-systems.com wrote: From: matthias.gai...@t-systems.com matthias.gai...@t-systems.com Subject: AW: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation To: axis-dev@ws.apache.org Date: Wednesday, July 29, 2009, 2:10 PM Hi Chris (or someone else), maybe it is just a misunderstanding on my side. I am generating a wsdl from a java class via java2wsdl. I am using a simple method like public String login(String user, String password); java2wsdl now generates a wsdl where the parameters are marked with minOccurs=0, which should not be the case for my webservice. Is there a possibility to set the standard behavior to minOccurs=1? As far as I have seen in the DefaultSchemaGenerator the minOccurs=0 is hardcoded. Generated wsdl fragment: xs:element name=login xs:complexType xs:sequence xs:element minOccurs=0 name=user nillable=true type=xs:string/ xs:element minOccurs=0 name=password nillable=true type=xs:string/ /xs:sequence /xs:complexType /xs:element Please help me in clarfying this issue. Thank you, Matthias. -Ursprüngliche Nachricht- Von: Chris van Es (JIRA) [mailto:j...@apache.org] Gesendet: Dienstag, 28. Juli 2009 14:49 An: axis-dev@ws.apache.org Betreff: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation [ https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12736053#action_12736053 ] Chris van Es commented on AXIS2-3300: - I patched the DefaultSchemaGenerator in that fashion and we haven't had any problems to date. Chris. minOccurs=0 always generated by Java2WSDL - problems with .NET client generation -- Key: AXIS2-3300 URL: https://issues.apache.org/jira/browse/AXIS2-3300 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.3 Reporter: Mauro Molinari Assignee: Deepal Jayasinghe Attachments: axis2-1.4.1.diff When you try to expose a POJO as a webservice, suppose you have two Java methods with the following signatures: public Integer a(String, Integer) public String b(Integer, String) Java2WSDL adds the minOccurs=0 for each element of each complex type, both for the input parameters and for the output parameters. When generating clients using .NET WebService Studio 2.0, the result is the following: - all the generated C# methods input parameters are doubled, except for the string ones: the doubled parameters are booleans whose meaning is: is the previous parameter specified or not? - all the generated C# methods return parameters are void, except for the string ones The actual result are clients with methods like these: public void a(string, int, bool); public string b(int, bool, string); This is obviously a problem, particularly for the void return type. If I remove minOccurs=0, clients are generated correctly by .NET WebService Studio 2.0. The issue is this: why does Java2WSDL always adds minOccurs=0? If its meaning were it can be null, I think nillable=true attribute should be more appropriate... Moreover, if I substitute Integer with int in the original Java class methods, minOccurs=0 is still added by Java2WSDL, even if an int cannot be null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (AXIS-2795) Axis 1.4 support for complex type in SOAP request
Hi, your wsdl includes an unmatched any/? Cheers Wolfgang --- On Mon, 7/6/09, Sneha (JIRA) axis-dev@ws.apache.org wrote: From: Sneha (JIRA) axis-dev@ws.apache.org Subject: [jira] Created: (AXIS-2795) Axis 1.4 support for complex type in SOAP request To: axis-dev@ws.apache.org Date: Monday, July 6, 2009, 11:46 AM Axis 1.4 support for complex type in SOAP request - Key: AXIS-2795 URL: https://issues.apache.org/jira/browse/AXIS-2795 Project: Axis Issue Type: Bug Components: Serialization/Deserialization Affects Versions: 1.4 Environment: Eclipse Ganymede Reporter: Sneha Hi, I am using Axis 1.4. Onlines to the example samples/client/DynamicInvoker.java, I am creating a SOAP request stub from a given WSDL url and populating it with the argument s and then giving a call to invoke the function. I have observed that if my request has an element of complex type, code throws a run time exception while trying to populate the parameters for the request, at its unable to fill in the complex type. e.g. if part of my wsdl looks as below: xsd:schema targetNamespace=http://www.example.org/NewWSDLFile/; − xsd:element name=NewOperation − xsd:complexType − xsd:sequence xsd:element name=in type=xsd:string/ xsd:element name=NewElement type=xsd:int/ xsd:element name=NewElement1 type=xsd:int/ xsd:element name=NewElement2 type=xsd:boolean/ xsd:any/ xsd:element name=NewElement3 type=xsd:string/ xsd:element name=NewElement4 type=xsd:string/ xsd:element name=NewElement5 type=xsd:string/ xsd:element name=NewElement6 type=xsd:string/ xsd:element name=NewElement7 type=xsd:string/ xsd:element name=NewElement8 type=xsd:int/ xsd:element name=NewElement9 type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element − xsd:element name=NewOperationResponse − xsd:complexType − xsd:sequence xsd:element name=out type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element /xsd:schema /wsdl:types − wsdl:message name=NewOperationRequest wsdl:part element=tns:NewOperation name=parameters/ /wsdl:message − wsdl:message name=NewOperationResponse wsdl:part element=tns:NewOperationResponse name=parameters/ /wsdl:message If you observe the highlighted portion, NewOperationRequest, it has element, parameters, of type NewOPeration, which is of complex type. My code give s a run time exception when I try to execute my code using this WSDL file, as java.lang.RuntimeException: not know how to convert 'abc' into org.apache.axis.client.c...@b45130 Please help me find a solution on this problem, as most of my WSDL files include complex types for the requests. Thanks in advance. -- Sneha -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Problem with Polymorphic data types with ADB stubs on client side and RPC*MessageReceiver on Server side.
Hi, it goes against the philosophy of web services to become dependent on java packages or .net assemblies or whatever. it is essential that a classname within a soap-message is NOT relied upon for communication purposes to have a special meaning within a certain framework. you would kill interoperability this way Cheers, Wolfgang --- On Thu, 4/23/09, Rahul Miglani rmigl...@quark.com wrote: From: Rahul Miglani rmigl...@quark.com Subject: Problem with Polymorphic data types with ADB stubs on client side and RPC*MessageReceiver on Server side. To: axis-dev@ws.apache.org Date: Thursday, April 23, 2009, 9:50 AM Hi, I have an existing spring framework based Java application where-in the services were exposed as web services using Axis 1.3. Now we are migrating the same to Axis2 1.4.1. I have used the RPC*MessageReceiver classes for my MEPs and instead of service implementation class parameter “SeviceClass” I am using the “ServiceObjectSupplier” and the “SpringBeanName” parameters in the services.xml file to describe my service. On the client side I am using the ADB stubs. When I encounter any polymorphic data here i.e. if the client is sending a polymorphic data type as a parameter, the RPC*MessageReceiver class is not able to de-serialize the exact derived object instead it creates an object of the base class, resulting in data loss. Actually the problem comes in the BeanUtil class’s deserailize() method. A fix is already mentioned there for issues AXIS2-2055 and AXIS2-1899 to support polymorphism in POJO approach. The code expects that a “type” attribute should be mentioned with a value as the fully qualified class name of the actual type object whereas if we are using ADB stubs on the client side then the request XML contains the “type” attribute with a namespace as http://www.w3.org/2001/XMLSchema-instance and the value as just the class name, the package name is not sent. So the code mentioned here fails. I have added a workaround for the problem and am attaching the file modified along with the mail. Changes are in the BeanUtil.java file. Also a new file has been added by name BeanClassMapper.java which expects a “Namespace2PackageMapping.properties” file in the classpath that contains the mapping between the fully qualified java classes and the namespace qualified object name as is received in the SOAP request. Example properties file is also attached. Please suggest if the code is correct or if there is some other way of achieving the desired result. Thanks and Regards, Rahul Miglani Quark Media House.
Re: First Element must contain the local name, Envelope , but found definitions
Hi
you are right inasfar as that wsdl is not correct (invalid)
sorry no way to to dynamic webservices without valid wsdl-document
you could contact the source very well IMHO cause all other consumers will have
the same problem -
Cheers, Wolfgang
--- On Thu, 4/2/09, Clifton B. Sothoron Jr. clifton.sothoro...@logixml.com
wrote:
From: Clifton B. Sothoron Jr. clifton.sothoro...@logixml.com
Subject: First Element must contain the local name, Envelope , but found
definitions
To: axis-dev@ws.apache.org
Date: Thursday, April 2, 2009, 3:34 AM
I’m
testing a dynamic client Axis 2 application. It works fine except that one web
service I’m testing with is giving me a problem. The ServiceClient.sendReceive
invocation generates the message “First Element must contain the local
name, Envelope , but found definitions”. The URL is
http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl.
I’ve looked at the returned XML via a sniffer and it indeed has
definitions in it. Obviously I can’t change the server side. Is there
a way around this using Axis 2 in a dynamic client? The following code
illustrates the problem.
import
org.apache.axiom.om.OMAbstractFactory;
import
org.apache.axiom.om.OMElement;
import
org.apache.axiom.om.OMFactory;
import
org.apache.axis2.Constants;
import
org.apache.axiom.om.OMNamespace;
import
org.apache.axis2.AxisFault;
import
org.apache.axis2.addressing.EndpointReference;
import
org.apache.axis2.client.Options;
import
org.apache.axis2.client.ServiceClient;
public
class Forecasts{
private static EndpointReference targetEPR = new EndpointReference(
http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl;);
public static void main(String[] args) {
try {
ServiceClient client = new ServiceClient();
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace ns =
fac.createOMNamespace(http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl;,
tns);
OMElement
payload = fac.createOMElement(LatLonListZipCode, ns);
OMElement value = fac.createOMElement(ZipCode, ns);
value.setText(22102);
payload.addChild(value);
Options options = new Options();
options.setTimeOutInMilliSeconds(6);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setTo(targetEPR);
options.setAction(http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl/LatLonListZipCode;);
client.setOptions(options);
//Blocking invocation
OMElement result = client.sendReceive(payload);
System.out.println(result.toString());
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
}
}
}
Thanks
in advance,
Clifton
Sothoron
LogiXML,
Development Department
7900 Westpark Drive, Suite T107 | McLean, VA 22102
(703) 752-9700 Ext. 162 | fax: (703) 773-6903
clifton.sothoro...@logixml.com
| http://www.logixml.com
Re: Is there any workaround over invalid character in responses?
Hi, having looked around a bit I guess the encoding of the SOAP-response is not UTF-8 at all, but plain old ascii. Still the fault would be on the server side and there is little you can do about it on the client side. Mind you the encoding=UTF-8 tag does not force anything but is meant as a hint only Wolfgang --- On Mon, 12/1/08, Wesley Mesquita [EMAIL PROTECTED] wrote: From: Wesley Mesquita [EMAIL PROTECTED] Subject: Is there any workaround over invalid character in responses? To: axis-dev@ws.apache.org Date: Monday, December 1, 2008, 6:09 PM Hi all, I am having troubles with the the exception: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x64 (at char #538, byte #127) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.jav a:239) at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.j ava:552) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElement Impl.java:563) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstElement(OMElement Impl.java:823) at org.apache.axiom.soap.impl.llom.SOAPBodyImpl.hasFault(SOAPBodyImpl.ja va:89) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse( OutInAxisOperation.java:340) Using axis2-1.3 with stubs generated by eclipse wtp. So, we think there is just one character in the responses that is not UTF-8 (ã, very commom in portuguese), but we don´t have much to do on the server side (just send reports). This is breaking other tests with the application, so would very intersting to workaround this for now. I tried a lot of things, read a lot of mailing lists, but nothing has worked. I have been trying to convert non-UTF-8 chars to some kind of garbage just do complete the trasaction, but did not word. We only can see the data in the SOAP envelope using sniffers; Thanks in advance for any help. -- Wesley Mesquita Computer Engineering Student Institute of Computing University of Campinas (UNICAMP) Mobile: +55 19 93455420 LinkedIn: http://www.linkedin.com/in/wesleymesquita - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is there any workaround over invalid character in responses?
Hi, short of rewriting AXIS2 on the client side, I see no method to come to terms with invalid UTF-8 sequences coming with the SOAP-response. Invalid UTF-8 is not meant to work of course. Perhaps the server side can change the encoding to UTF-16? Wolfgang --- On Mon, 12/1/08, Wesley Mesquita [EMAIL PROTECTED] wrote: From: Wesley Mesquita [EMAIL PROTECTED] Subject: Is there any workaround over invalid character in responses? To: axis-dev@ws.apache.org Date: Monday, December 1, 2008, 6:09 PM Hi all, I am having troubles with the the exception: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x64 (at char #538, byte #127) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.jav a:239) at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.j ava:552) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElement Impl.java:563) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstElement(OMElement Impl.java:823) at org.apache.axiom.soap.impl.llom.SOAPBodyImpl.hasFault(SOAPBodyImpl.ja va:89) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse( OutInAxisOperation.java:340) Using axis2-1.3 with stubs generated by eclipse wtp. So, we think there is just one character in the responses that is not UTF-8 (ã, very commom in portuguese), but we don´t have much to do on the server side (just send reports). This is breaking other tests with the application, so would very intersting to workaround this for now. I tried a lot of things, read a lot of mailing lists, but nothing has worked. I have been trying to convert non-UTF-8 chars to some kind of garbage just do complete the trasaction, but did not word. We only can see the data in the SOAP envelope using sniffers; Thanks in advance for any help. -- Wesley Mesquita Computer Engineering Student Institute of Computing University of Campinas (UNICAMP) Mobile: +55 19 93455420 LinkedIn: http://www.linkedin.com/in/wesleymesquita - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unexpected subelement Exception
Hi, according to your info you are receiving an element which relates to a different wsdl resp. a different schema. to verify the location of that element, monitor the SOAP-messages you send and receive is your wsdl importing some schemas? watch out for an import tag Wolfgang --- On Thu, 11/27/08, Wesley Mesquita [EMAIL PROTECTED] wrote: From: Wesley Mesquita [EMAIL PROTECTED] Subject: Unexpected subelement Exception To: axis-dev@ws.apache.org Date: Thursday, November 27, 2008, 1:59 PM Hi all, I am getting problems in generating calls to a third part Web Service which I have only the WSDL and no access to the server side implementation (I neither know what they are using to implement that). The fact is that I am getting the following exception: org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement obterChamadoPC For some reason I didn´t get permission from the project manager to post the WSDL file. The only thing I realized is that I didn´t find any reference to obterChamadoPC in the WSDL. Is this the cause? I am in doubt because the staff on the server side is telling everything is fine, but I am telling that the WSDL in not compatible with the service so I can´t generate the right clients. My suspect is that I am sending the right data, they are producing the right response but the interface to receive the answer is not compatible with the WSDL that I have.. I am using Axis2-1.3 and Eclipse Ganymede WTP to generate the stubs code. I really appreciate any opinions. Thanks in advance. -- Wesley Mesquita Computer Engineering Student Institute of Computing University of Campinas (UNICAMP) Mobile: +55 19 93455420 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: getting exceptions while calling .Net web-services with Axis client
Virgil, pls provide the wsdl Cheers, Wolfgang --- On Wed, 10/1/08, Trasca Virgil [EMAIL PROTECTED] wrote: From: Trasca Virgil [EMAIL PROTECTED] Subject: getting exceptions while calling .Net web-services with Axis client To: axis-dev@ws.apache.org Date: Wednesday, October 1, 2008, 8:15 PM Hi, I am trying to call some .Net server web-services using Axis1.x client and I am getting the attached exceptions. Can you please give me some inputs on when such exceptions are appearing and what could be the problem? Thank you, Virgil DocumentBurster , http://java-hobby.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 1.4 and MTOM
Hi, I'd say dont do it this way AXIS 1.4 is no longer being maintained you could use base64 encoding with axis 1.4 Cheers, Wolfgang --- On Thu, 8/14/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: From: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Axis 1.4 and MTOM To: axis-dev@ws.apache.org Date: Thursday, August 14, 2008, 3:18 PM Hi group, I am currently trying to implement an axis 1.4 web service (with a client) with attachments using MTOM. Somewhere it was said, that this is also possible with axis 1.4. But unfortunately I don't get it working. I'm sending the attachments from the server side via MTOM, but I can't receive them on the client. The problem seems to be on the client side. On the client I get this error: [#text: Error in parsing mime data stream: null I included the stacktrace and the response message as attachments. My questions: * Is it possible to implement a Web Service with Attachments using MTOM and Axis 1.4? * Do I have to tell the client somehow that MTOM is being used? * Can you provide some help to my issue? The future plan is to migrate to axis2, but this would take too long for my current issue. Hopefully waiting for your answers. Matthias. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding problem
Hi, as to how to do this I'd say take one of your breaking russian characters and look it up by using for example some windows-build-in character utility i cant recollect its name right now In principle I dont doubt this codepoints are correct. There are even some axis-emails about a similar problem with chinese characters. you could try to google for it. If you can verify that eclipse is able to display russian characters i would agree a bug is likely. Proving it is another matter but you only have to show that any one single character is being translated wrongly giving the exact numeric value Cheeers, Wolfgang --- On Mon, 8/11/08, Carsten Burghardt [EMAIL PROTECTED] wrote: From: Carsten Burghardt [EMAIL PROTECTED] Subject: Re: Encoding problem To: axis-dev@ws.apache.org Date: Monday, August 11, 2008, 4:40 PM Quoting WJ Krpelan [EMAIL PROTECTED]: Hi, hope I got this right. The encoding with #hex; looks perfect to me. You should check wether the actual hex-values correspond to the UNICODE-CODEPONTS of you Russian Characters. Hmm, how do I do this? If this is the case, how did you verify the characters were broken inside the DOM-tree. Is your tool capable of showing Russiaan characters? Yes, I debugged it with Eclipse therefore I could see that the characters were not displayed correctly. Broken would mean that the numeric values in your UTF-8 XML do not correspond to the UTF-8-values of your Russian Characters, which are quite different from the UNICODE-Codepoints. HTH, Wolfgang --- On Fri, 8/8/08, Carsten Burghardt [EMAIL PROTECTED] wrote: From: Carsten Burghardt [EMAIL PROTECTED] Subject: Encoding problem To: axis-dev@ws.apache.org Date: Friday, August 8, 2008, 1:51 PM Hi, first of all I know that this is more a question for the user list but nobody could help me there - so apologies but I'll try as I don't know how to continue. I've a webservice (Axis 1.4) that connects to an Alfresco server and stores metadata from emails (like subject, sender, ...). This works fine with ISO-* or UTF-8 encoded emails. But once I have an email with more exotic character sets like KOI8-R (russian) I get an error on the server side because of invalid characters (like 0x1e). I know that no control characters are in the content so I watched the traffic with tcpmon and noticed that all characters were totally screwed up. So I traced the Axis code and saw that the characters were encoded with #hex; in the SoapBody. Afterwards the DOM tree is serialized in the DoAllSender class and then the characters are broken in the generated XML. When I switched the encoding of the Soap Message to KOI8-R instead of UTF-8 the characters showed up fine in the tcpmon but then the server reports an error about a different illegal character (0x1) which is probably because the message is converted to UTF-8 at a certain step. So I guess my questions is: what is the proposed way to transmit those characters to a webservice (apart from Base64 encoding them...)? Many thanks Carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding problem
Hi, hope I got this right. The encoding with #hex; looks perfect to me. You should check wether the actual hex-values correspond to the UNICODE-CODEPONTS of you Russian Characters. If this is the case, how did you verify the characters were broken inside the DOM-tree. Is your tool capable of showing Russiaan characters? Broken would mean that the numeric values in your UTF-8 XML do not correspond to the UTF-8-values of your Russian Characters, which are quite different from the UNICODE-Codepoints. HTH, Wolfgang --- On Fri, 8/8/08, Carsten Burghardt [EMAIL PROTECTED] wrote: From: Carsten Burghardt [EMAIL PROTECTED] Subject: Encoding problem To: axis-dev@ws.apache.org Date: Friday, August 8, 2008, 1:51 PM Hi, first of all I know that this is more a question for the user list but nobody could help me there - so apologies but I'll try as I don't know how to continue. I've a webservice (Axis 1.4) that connects to an Alfresco server and stores metadata from emails (like subject, sender, ...). This works fine with ISO-* or UTF-8 encoded emails. But once I have an email with more exotic character sets like KOI8-R (russian) I get an error on the server side because of invalid characters (like 0x1e). I know that no control characters are in the content so I watched the traffic with tcpmon and noticed that all characters were totally screwed up. So I traced the Axis code and saw that the characters were encoded with #hex; in the SoapBody. Afterwards the DOM tree is serialized in the DoAllSender class and then the characters are broken in the generated XML. When I switched the encoding of the Soap Message to KOI8-R instead of UTF-8 the characters showed up fine in the tcpmon but then the server reports an error about a different illegal character (0x1) which is probably because the message is converted to UTF-8 at a certain step. So I guess my questions is: what is the proposed way to transmit those characters to a webservice (apart from Base64 encoding them...)? Many thanks Carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding a CDATA element being converted to lt; and gt
Hi I know what happened ;-) you tried to serialize XML by hand my advice: use an appropriate tool Cheers --- On Fri, 7/25/08, Dini Omar [EMAIL PROTECTED] wrote: From: Dini Omar [EMAIL PROTECTED] Subject: Adding a CDATA element being converted to lt; and gt To: [EMAIL PROTECTED], axis-dev@ws.apache.org Date: Friday, July 25, 2008, 2:55 PM Hi all, I am trying to build the payload/messagebody for an element. According to the specific the payload has to be within a CDATA element. I tried to do this as shown below private static final String START_TAG=new String(![CDATA[); private static final String END_TAG= new String(]]); SadFileStub.IEEdifactString theString = new SadFileStub.IEEdifactString(); theString.setIEEdifactString(START_TAG.concat(MESSAGE CONTENT DATA).concat(END_TAG)); This does not seem to work as the message is coming out as shown below lt;![CDATA[MESSAGE CONTENT DATA]]gt; Does anyone know why this is happening? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I preserve the XML tags when invoking the web service?
Hi,
if you transport xml within xml-schema strings it is syntactically necessary to
escape certain characters as the embedded xml-strings are no official part of
the surrounding document and the xml-parser would behave unpredictably. This
got nothing to do with AXIS, however so maybe you should get in touch with an
xml-list.
Cheers,
Wolfgang
--- On Tue, 7/29/08, ktiongson [EMAIL PROTECTED] wrote:
From: ktiongson [EMAIL PROTECTED]
Subject: How do I preserve the XML tags when invoking the web service?
To: axis-dev@ws.apache.org
Date: Tuesday, July 29, 2008, 8:05 PM
Environment: Apache Axis 1.4, Java 1.5
Tools Used: Axis WSDL2Java, JAXB
Scenario: Java application sends an XML message via
SOAP/HTTP to SAP XI's
SOAP adapter
How do I invoke a web service from the application by
preserving the XML
tags and not transforming them to XML entities?
I intercepted the message using TCPMon and I saw that the
SOAP Body looks
like this:
soapenv:BodyPePCPricinglt;Headergt;lt;JMSDestinationgt;PcPricinglt;/JMSDestinationgt;
But I want it to look like this when I intercept the
message:
soapenv:Body
PePCPricingHeaderJMSDestinationPcPricing/JMSDestination
I marshal the XML message into a String (pePCPricing)
before invoking the
web service. Here is the code I use to invoke the web
service:
This is the Java code on the application side that invokes
the web service:
public void oa_PBA_PCP(java.lang.String pePCPricing)
throws
java.rmi.RemoteException {
if (super.cachedEndpoint == null) {
throw new
org.apache.axis.NoEndPointException();
}
org.apache.axis.client.Call _call =
createCall();
_call.setOperation(_operations[0]);
_call.setUseSOAPAction(true);
_call.setSOAPActionURI(http://sap.com/xi/WebService/soap1.1;);
_call.setEncodingStyle(_call.CHARACTER_SET_ENCODING);
_call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR,
Boolean.FALSE);
_call.setProperty(org.apache.axis.AxisEngine.PROP_DOMULTIREFS,
Boolean.FALSE);
_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
_call.setOperationName(new
javax.xml.namespace.QName(,
oa_PBA_PCP));
setRequestHeaders(_call);
setAttachments(_call);
_call.invokeOneWay(new java.lang.Object[] {
pePCPricing
});
}
How do I preserve the XML tags when invoking the web
service?
--
View this message in context:
http://www.nabble.com/How-do-I-preserve-the-XML-tags-when-invoking-the-web-service--tp18718113p18718113.html
Sent from the Axis - Dev mailing list archive at
Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Character Set Encoding problem
Hi,
I'm sure the client wont do a charset-conversion just because of setting this
property. So in my view the problem is rather on the server side.
Mind that XML-Standards default to UTF-8 or UTF-16 and you probably will lose
some interoperability by using a different charset encoding.
Why dont you read in your data in UTF-8 and do the charset-conversion
afterwards?
Cheers,
Wolfgang
--- On Fri, 7/25/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: [Axis2] Character Set Encoding problem
To: axis-dev@ws.apache.org
Date: Friday, July 25, 2008, 6:35 AM
Hi
I am using Axis2 v1.4 to consume a webservice. I have
generated the stubs using WSDL2Java with jdk1.6.0_06
While running the client, I am getting the following
exception:
org.apache.axis2.AxisFault: Character Set Encoding from
transport information [ISO-8859-1] does not match with
character set encoding in the received SOAP message [UTF-8]
at
org.apache.axis2.builder.BuilderUtil.validateCharSetEncoding(BuilderUtil.java:786)
at
org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:57)
at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:164)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at ymws.yahoo.YmwsStub.GetUserData(YmwsStub.java:1587)
I am explicitly setting charset encoding in my code as
below:
stub._getServiceClient().getOptions().setProperty(org.apache.axis2.Constants.Configuration.CHARACTER_SET_ENCODING,iso-8859-1);
However that does not seem help the exception pasted above.
When tracing using the Axis2 1.4 source, I found a possible
issue at the following line
streamReader = StAXUtils.createXMLStreamReader(pis,
actualCharSetEncoding);
of the SOAPBuilder class (see source below):
package org.apache.axis2.builder;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.impl.builder.StAXBuilder;
import org.apache.axiom.om.util.StAXUtils;
import org.apache.axiom.soap.SOAPEnvelope;
import
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder;
import org.apache.axis2.AxisFault;
import org.apache.axis2.Constants;
import org.apache.axis2.context.MessageContext;
import javax.xml.stream.XMLStreamException;
import javax.xml.stream.XMLStreamReader;
import java.io.IOException;
import java.io.InputStream;
import java.io.PushbackInputStream;
public class SOAPBuilder implements Builder {
public OMElement processDocument(InputStream
inputStream, String contentType,
MessageContext
messageContext) throws AxisFault {
XMLStreamReader streamReader;
try {
String charSetEncoding = (String)
messageContext
.getProperty(Constants.Configuration.CHARACTER_SET_ENCODING);
// Get the actual encoding by looking at
the BOM of the InputStream
PushbackInputStream pis =
BuilderUtil.getPushbackInputStream(inputStream);
String actualCharSetEncoding =
BuilderUtil.getCharSetEncoding(pis, charSetEncoding);
// Get the XMLStreamReader for this input
stream
streamReader =
StAXUtils.createXMLStreamReader(pis,
actualCharSetEncoding);
StAXBuilder builder = new
StAXSOAPModelBuilder(streamReader);
SOAPEnvelope envelope = (SOAPEnvelope)
builder.getDocumentElement();
BuilderUtil
.validateSOAPVersion(BuilderUtil.getEnvelopeNamespace(contentType),
envelope);
BuilderUtil.validateCharSetEncoding(charSetEncoding,
builder.getDocument()
.getCharsetEncoding(),
envelope.getNamespace().getNamespaceURI());
return envelope;
} catch (IOException e) {
throw AxisFault.makeFault(e);
} catch (XMLStreamException e) {
throw AxisFault.makeFault(e);
}
}
}
The issue seems like, the streamReader always reads in
UTF-8 instead of the specified encoding. And hence the
following statement of the above class fails
BuilderUtil.validateCharSetEncoding(charSetEncoding,
builder.getDocument()
.getCharsetEncoding(),
Re: Questions regarding Axis1.4
Hi Ahmed, this (part of an) wsdl is not well suited to communicate with dotnet-C#. your wsdl should use soap-style document/literal which is not very well supported by AXIS 1.4-wsdl-generator. Either you should rewrite your wsdl to this soap-style or maybe you should try the wsdl-generator of AXIS 2. dont expect interoperability to be easy. Still I think a ReadResponse-Error means the client cant read the response. The server cant possibly write out such an error-message on the client side. As I said small surprise. Cheers, Wolfgang --- On Tue, 7/1/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Tuesday, July 1, 2008, 8:03 PM Hi Wolfgang, Yes - it is using Axis 1.4. I have attached the wsdl file for you to review. The server sends error message to the client if something is wrong. That is the error message I sent you. The client I am using is a C# client. So the error was not generated on the client. I think the error is happening during the marshaling process on the server side. Please let me know what you think. Thanks again for all the help. Best Regards! Raihan --- On Tue, 7/1/08, WJ Krpelan [EMAIL PROTECTED] wrote: From: WJ Krpelan [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Tuesday, July 1, 2008, 6:41 AM ok, The errors you are getting are caused by the client java app trying to deserialize the soap/xml-response and getting something unexpected I.E. the SERVER is sending some response the CLIENT cant make sense of. Notice the various instances of response within these error-messages. the next step would be to have a look at the actual SOAP-XML-Response on the wire, which could be done e.g. by using the microsoft-tool fiddler or some soap-monitor like tcpmon which is being shipped with AXIS 1.4 My guess at this moment would be the Webservice-Implementation on the SERVER side doesnt do what you would expect. Is the server built on AXIS 1.4? What does the WSDL-document look like? I dont think the responsibility lies with the code you sent me, maybe with the code which reassembles the image out of the base64-data (improbable) HTH Wolfgang --- On Mon, 6/30/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 5:27 PM Hi, Yes, this document causes the error. But dumping it into a string, you might not be able to reproduce the error since the image data won't be base64 string dynamically generated from inside the code. But please try for me! Also, if you can't reproduce the error, could you write a small WS to send a small xml document where one node will have base64 data generated by reading an image file to see if you can reproduce error? I know I am asking too much! But I need your expertise/knowledge badly to shed some lights on this issue. I have attached the code to generate base64 from an image file to save you time in case you decide to try the second approach. And here is the error we are getting - ERROR: System.Web.Services.Protocols.SoapException: java.lang.reflect.InvocationTargetException at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at GuruWebServiceImpService.getArrestBookingReport(String in0, String in1) in C:\TestCourtWS\TestCourtWS\TestCourtWS\GuruWebServiceImpService.cs:line 334 at TestCourtWS.Form1.btnAB_Click(Object sender, EventArgs e) in C:\TestCourtWS\TestCourtWS\TestCourtWS\Form1.cs:line 269 Thanks so much! Raihan --- On Mon, 6/30/08, WJ Krpelan [EMAIL PROTECTED] wrote: From: WJ Krpelan [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 10:35 AM Ahmed, this xml document is looking alright could you verify that exactly this example document causes an error too so that I could try to reproduce it by putting it into a string. pls give me the exact error message if applicable Cheers, Wolfgang --- On Mon, 6/30/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 3:09 PM Hi Wolfgang, I am sending you an attachment with an example xml document
Re: Questions regarding Axis1.4
ok, The errors you are getting are caused by the client java app trying to deserialize the soap/xml-response and getting something unexpected I.E. the SERVER is sending some response the CLIENT cant make sense of. Notice the various instances of response within these error-messages. the next step would be to have a look at the actual SOAP-XML-Response on the wire, which could be done e.g. by using the microsoft-tool fiddler or some soap-monitor like tcpmon which is being shipped with AXIS 1.4 My guess at this moment would be the Webservice-Implementation on the SERVER side doesnt do what you would expect. Is the server built on AXIS 1.4? What does the WSDL-document look like? I dont think the responsibility lies with the code you sent me, maybe with the code which reassembles the image out of the base64-data (improbable) HTH Wolfgang --- On Mon, 6/30/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 5:27 PM Hi, Yes, this document causes the error. But dumping it into a string, you might not be able to reproduce the error since the image data won't be base64 string dynamically generated from inside the code. But please try for me! Also, if you can't reproduce the error, could you write a small WS to send a small xml document where one node will have base64 data generated by reading an image file to see if you can reproduce error? I know I am asking too much! But I need your expertise/knowledge badly to shed some lights on this issue. I have attached the code to generate base64 from an image file to save you time in case you decide to try the second approach. And here is the error we are getting - ERROR: System.Web.Services.Protocols.SoapException: java.lang.reflect.InvocationTargetException at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at GuruWebServiceImpService.getArrestBookingReport(String in0, String in1) in C:\TestCourtWS\TestCourtWS\TestCourtWS\GuruWebServiceImpService.cs:line 334 at TestCourtWS.Form1.btnAB_Click(Object sender, EventArgs e) in C:\TestCourtWS\TestCourtWS\TestCourtWS\Form1.cs:line 269 Thanks so much! Raihan --- On Mon, 6/30/08, WJ Krpelan [EMAIL PROTECTED] wrote: From: WJ Krpelan [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 10:35 AM Ahmed, this xml document is looking alright could you verify that exactly this example document causes an error too so that I could try to reproduce it by putting it into a string. pls give me the exact error message if applicable Cheers, Wolfgang --- On Mon, 6/30/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 3:09 PM Hi Wolfgang, I am sending you an attachment with an example xml document that we output to the client. I will send you the attachment to your personal account in Apache has any restrictions on attachments. I hope this will help you see what I am doing wrong. I again thank you sincerely for taking the time out to look at this issue. Raihan --- On Mon, 6/30/08, WJ Krpelan [EMAIL PROTECTED] wrote: From: WJ Krpelan [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 5:17 AM Ahmed, its difficult to follow because I cant tell when are you speaking of the overall xml-document and when of an included xml-document. btw the xml-schema-datatype is named base64Binary and not base64. so whereever you use base64 data you should discover a base64Binary datatype within your xml-schema-document for your xml-instance-document. I assume here that your xml-documents are all xml-schema-based? Still I think an (anonymized) example document would say more than a thousand words, Wolfgang --- On Mon, 6/30/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 1:36 AM Hi Wolfgang, Thanks a bunch for your email. I know it is very unusual having xml document inside xml document. It was one of the requirement of the client that the output has to be in xml document. It has data from multiple different sources and uses Justice xml for law enforcement
Re: Questions regarding Axis1.4
Ahmed, its difficult to follow because I cant tell when are you speaking of the overall xml-document and when of an included xml-document. btw the xml-schema-datatype is named base64Binary and not base64. so whereever you use base64 data you should discover a base64Binary datatype within your xml-schema-document for your xml-instance-document. I assume here that your xml-documents are all xml-schema-based? Still I think an (anonymized) example document would say more than a thousand words, Wolfgang --- On Mon, 6/30/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 1:36 AM Hi Wolfgang, Thanks a bunch for your email. I know it is very unusual having xml document inside xml document. It was one of the requirement of the client that the output has to be in xml document. It has data from multiple different sources and uses Justice xml for law enforcement agencies as its standard. So far we have not run into any issues (as long as we didn't use base64 data) with this even though it seems weird considering that SOAP response itself is an xml document. Can you think of any other way we could do this? As far as the hard-coded base64 string goes, this is what is happening - after a client request, I query database with input data, and parse the query result and put them in the xml document. During this process, I have to check if the record has an image associated with it. If it does, then I get the image file, convert it into base64 and stick that base64 string into the image tag. And it fails. I also print this xml document out for debugging purposes. From this output, if I copy and paste the base64 string into the image tag (that is I am sending a hard-coded output), then it works. That is, my output sent to client always has the same image data. I am not sure if I was able to explain this at all. Please let me know if you need any more info to help me out with this problem. Thanks again! Raihan --- On Sun, 6/29/08, WJ Krpelan [EMAIL PROTECTED] wrote: From: WJ Krpelan [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Sunday, June 29, 2008, 5:32 PM Hi what you are doing (putting xml documents within xml documents as strings) is not considered usual practice. I'm not surprised that you are running into problems with AXIS 1 using this approach. I dont understand exactly what you mean by putting it hardcoded vs generated into the response. could you provide an example? Cheers, Wolfgang --- On Sun, 6/29/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Sunday, June 29, 2008, 6:00 AM Hello, I am sorry to email in this manner. But I have run into an issue that I just can't figure out. I have searched the Internet without any luck. I have a web service running under Axis1.4. One of the methods returns an array of string to the client. Each string in the array is actually an XML document with data from database tables. And each of these XML documents has a node that has image data in Base64 string. Now the problem is this - Without the Base64, it works fine. But soon I add the base64 data in the node, I get the SoapException on the server side. If I copy the base64 string and hard-code it in the response, it works. But when the base64 is generated, it does not work. I can't figure out the reason - base64 is simple ascii characters. Why can't I put a string like that in the response? I am desperate. Please help! If I am in the wrong place, please point to the right people so that I can get an answer. Best Regards! Raihan U. Ahmed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] I18N problem
Hi ppl, what I can contribute: the binary representation of utf-8, utf-16, . and the actual UNICODE-values specified by U+ have no direct relation at all but are completely different binary representations (hopefully of the same characters) Cheers, Wolfgang --- On Mon, 6/30/08, Deepal jayasinghe [EMAIL PROTECTED] wrote: From: Deepal jayasinghe [EMAIL PROTECTED] Subject: Re: [Axis2] I18N problem To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 7:20 AM Hi Tony, I am sorry that I can not give you the full answer (because I do not know everything happening here) , however as i can see this problem is due to the parser that Axis2 uses. I think we need to set the character encoding when we crate the parser. Any way I will looking to that and let you know Hi, I have narrowed down an I18N problem when using Simplified Chinese characters in payload to Axis2 client side. I have an Axis2 client using ServiceClient to send a SOAP request to my service. For example a couple of characters in the payload are as follows: U+4e2d U+6587 U+6d4b U+8bd5 When the service receives these characters, they appear as follows: U+002d U+6587 U+004b U+8bd5 The high-order byte of the 1st and 3rd characters are incorrect. When the Axis2 ServiceClient converts the payload to UTF-8 for sending across the wire, these bytes become (as seen in soapMonitor): 2de6 9687 4be8 af95 I think that they should be: e4b8 ade6 9687 e6b5 8be8 af95 Can anyone explain what's going on? Seems like an easy transformation of encodings for wire-format, but something is not quite right. To replicate try the following: ServiceClient client = new ServiceClient(ctx, null); ... String value = new String(Hello world: \u4e2d\u6587\u6d4b\u8bd5); OMElement response = client.sendReceive(getPayload(value)); The Asian characters are not sent as expected. Thanks for any insight. I'll enter a bug if it so warrants. Tony Dean SAS Institute Inc. 919.531.6704 [EMAIL PROTECTED] SAS... The Power to Know http://www.sas.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal http://blogs.deepal.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Questions regarding Axis1.4
Ahmed, this xml document is looking alright could you verify that exactly this example document causes an error too so that I could try to reproduce it by putting it into a string. pls give me the exact error message if applicable Cheers, Wolfgang --- On Mon, 6/30/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 3:09 PM Hi Wolfgang, I am sending you an attachment with an example xml document that we output to the client. I will send you the attachment to your personal account in Apache has any restrictions on attachments. I hope this will help you see what I am doing wrong. I again thank you sincerely for taking the time out to look at this issue. Raihan --- On Mon, 6/30/08, WJ Krpelan [EMAIL PROTECTED] wrote: From: WJ Krpelan [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 5:17 AM Ahmed, its difficult to follow because I cant tell when are you speaking of the overall xml-document and when of an included xml-document. btw the xml-schema-datatype is named base64Binary and not base64. so whereever you use base64 data you should discover a base64Binary datatype within your xml-schema-document for your xml-instance-document. I assume here that your xml-documents are all xml-schema-based? Still I think an (anonymized) example document would say more than a thousand words, Wolfgang --- On Mon, 6/30/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Monday, June 30, 2008, 1:36 AM Hi Wolfgang, Thanks a bunch for your email. I know it is very unusual having xml document inside xml document. It was one of the requirement of the client that the output has to be in xml document. It has data from multiple different sources and uses Justice xml for law enforcement agencies as its standard. So far we have not run into any issues (as long as we didn't use base64 data) with this even though it seems weird considering that SOAP response itself is an xml document. Can you think of any other way we could do this? As far as the hard-coded base64 string goes, this is what is happening - after a client request, I query database with input data, and parse the query result and put them in the xml document. During this process, I have to check if the record has an image associated with it. If it does, then I get the image file, convert it into base64 and stick that base64 string into the image tag. And it fails. I also print this xml document out for debugging purposes. From this output, if I copy and paste the base64 string into the image tag (that is I am sending a hard-coded output), then it works. That is, my output sent to client always has the same image data. I am not sure if I was able to explain this at all. Please let me know if you need any more info to help me out with this problem. Thanks again! Raihan --- On Sun, 6/29/08, WJ Krpelan [EMAIL PROTECTED] wrote: From: WJ Krpelan [EMAIL PROTECTED] Subject: Re: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Sunday, June 29, 2008, 5:32 PM Hi what you are doing (putting xml documents within xml documents as strings) is not considered usual practice. I'm not surprised that you are running into problems with AXIS 1 using this approach. I dont understand exactly what you mean by putting it hardcoded vs generated into the response. could you provide an example? Cheers, Wolfgang --- On Sun, 6/29/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Sunday, June 29, 2008, 6:00 AM Hello, I am sorry to email in this manner. But I have run into an issue that I just can't figure out. I have searched the Internet without any luck. I have a web service running under Axis1.4. One of the methods returns an array of string to the client. Each string in the array is actually an XML document with data from database tables. And each of these XML documents has a node that has image data in Base64 string. Now the problem is this - Without the Base64, it works fine. But soon I add the base64 data in the node, I get the SoapException on the server side. If I copy the base64 string and hard-code it in the response, it works. But when the base64
Re: Questions regarding Axis1.4
Hi what you are doing (putting xml documents within xml documents as strings) is not considered usual practice. I'm not surprised that you are running into problems with AXIS 1 using this approach. I dont understand exactly what you mean by putting it hardcoded vs generated into the response. could you provide an example? Cheers, Wolfgang --- On Sun, 6/29/08, Raihan Ahmed [EMAIL PROTECTED] wrote: From: Raihan Ahmed [EMAIL PROTECTED] Subject: Questions regarding Axis1.4 To: axis-dev@ws.apache.org Date: Sunday, June 29, 2008, 6:00 AM Hello, I am sorry to email in this manner. But I have run into an issue that I just can't figure out. I have searched the Internet without any luck. I have a web service running under Axis1.4. One of the methods returns an array of string to the client. Each string in the array is actually an XML document with data from database tables. And each of these XML documents has a node that has image data in Base64 string. Now the problem is this - Without the Base64, it works fine. But soon I add the base64 data in the node, I get the SoapException on the server side. If I copy the base64 string and hard-code it in the response, it works. But when the base64 is generated, it does not work. I can't figure out the reason - base64 is simple ascii characters. Why can't I put a string like that in the response? I am desperate. Please help! If I am in the wrong place, please point to the right people so that I can get an answer. Best Regards! Raihan U. Ahmed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can a web service be deployed on a server that is not an application server
Hi in principle you just need a http:-server which has access to a webservice-engine, that is a xml-serialization and deserialization-program which knows how to handle SOAP-messages. in practice you will have to use one of the standard solutions available, be it in java, dotnet or elsewhere. Cheers --- Yuling Chen [EMAIL PROTECTED] wrote: Hi Pudur, I think this article also requires a Tomcat...which we wouldn't really like to do. Thanks! YuLing Chen EEU SW EMS group Santa Clara, CA email: [EMAIL PROTECTED] Direct: 408-970-2145 -Original Message- From: Ramaswamy, Pudur [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 20, 2008 4:45 PM To: axis-dev@ws.apache.org Subject: RE: Can a web service be deployed on a server that is not an application server Can this answer your question? http://ws.apache.org/axis2/1_1_1/pojoguide.html Thanks, -pudur -Original Message- From: Yuling Chen [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 20, 2008 4:40 PM To: axis-dev@ws.apache.org Subject: Can a web service be deployed on a server that is not an application server Hi All, Does anyone know that if a web service can be deployed on a server that is not an application server? Thanks! YuLing Chen EEU SW EMS group Santa Clara, CA email: [EMAIL PROTECTED] Direct: 408-970-2145 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: Why this wsdl is not valid Wsdl
Hi, First point is your working WSDL is working fine only because you have all referenced XML-Schemas accessible. (doesnt work with me) Second point is the imported XML-Schema MUST have a different Namespace than the importing XML-Schema. Third point is you should qualify all referenced elements with their corresponding shortcut for the namespace they reside in All in all why dont you use JAVA2WSDL (at least as a starter) which would solve the problems for you. Namespace-Handling is notoriously difficult. Cheers, Wolfgang --- Dayalan, Ravikumar [EMAIL PROTECTED] wrote: -Original Message- From: Dayalan, Ravikumar Sent: Tuesday, April 01, 2008 7:45 PM To: 'axis-dev@ws.apache.org' Subject:Why this wsdl is not valid Wsdl When I try this wsdl and try to validate (I Use eclipse) it always gives this error. IWAB0380E Errors were encountered while validating XML schemas. XSD: The target namespace 'http://MedicalMitchel/interfaces/IMedMitPOC' of the resolved schema conflicts with '' XSD: Element reference '#MMFILE' is unresolved Can you please help me in understanding where iam wrong in this WSDL Whereis the otherwsdl is working fine.. working.wsdl Here I have element ref=MMFILE... in mywsdl.wsdl whereis in working.wsdl it has element name=.. Type= Will this be the reason.. Since this wsdl is given by some other team I don't have much control over changing it. Any help will be highly appreciated. Thanks Ravi. ravi.xsd mywsdl.wsdl = The information in this transmission is intended for official use only and may contain information from NJM Insurance Group that is privileged, confidential and exempt from disclosure under applicable law. It is intended for the exclusive use of the persons or entities to which it is addressed. If you are not an intended recipient or the employee or agent responsible for delivering this transmission to an intended recipient, be aware that any disclosure, dissemination, distribution or copying of this communication, or the use of its contents, is strictly prohibited. If you received this transmission in error, please notify the sender by return e-mail and delete the material from any computer. = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2: Invalid UTF-8 start byte 0xff (at char #1, byte #-1)
Hi, just guessing: could something have changed the actual encoding to utf-16 on the way (standard encoding with microsoft windows) ? of course an UTF-8-XML-Document is not expected to start with 0xFF. additionaly, using text/xml is not quite safe, application/xml would be preferrable Cheers --- Simon Steinacker [EMAIL PROTECTED] wrote: Hello, I already wrote this issue once to the mailing list. But for me nothing has changed with the problem. I still get this error (I checked all library versions). The complete Axis2 debug trace is: http://www.pastebin.org/23395 The message that causes the problem: http://www.pastebin.org/23396 I am very grateful for help! It is quite importat for me to solve this. Thank you very much in advance! best regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2: Invalid UTF-8 start byte 0xff (at char #1, byte #-1)
Hi, I'd suggest testing service and client on the same machine using AXIS2's WSDL2Java. Is this an AXIS2 service talking to an AXIS2 Client? What obviously is missing in your soap-message in an ?xml version=./? - tag in front of soapenv:Envelope .../ Compare this to other soap-message-samples. I'm not a member of the axis2 team btw so I cant give you a definite answer where the problem lies I'm afraid. Cheers --- Simon Steinacker [EMAIL PROTECTED] wrote: Thanks for you reply! Well, as I am not developing the client application and do not have the source code available, it might be the case that the message is UTF-16. How can I determine that? Or where can I tell axis2 that it should decode UTF-16 messages? Thanks, Simon WJ Krpelan wrote: Hi, just guessing: could something have changed the actual encoding to utf-16 on the way (standard encoding with microsoft windows) ? of course an UTF-8-XML-Document is not expected to start with 0xFF. additionaly, using text/xml is not quite safe, application/xml would be preferrable Cheers --- Simon Steinacker [EMAIL PROTECTED] wrote: Hello, I already wrote this issue once to the mailing list. But for me nothing has changed with the problem. I still get this error (I checked all library versions). The complete Axis2 debug trace is: http://www.pastebin.org/23395 The message that causes the problem: http://www.pastebin.org/23396 I am very grateful for help! It is quite importat for me to solve this. Thank you very much in advance! best regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MTOM Communication with .NET
Hi, in .net the corresponding program is wsdl.exe I'm very interested whether MTOM-communications is interoperable so pls tell us your experiences. Cheers, Wolfgang --- Thilina Gunarathne [EMAIL PROTECTED] wrote: Hi, Now, I'm trying to create an application to talk to a .NET web service and since .NET doesn't use WSDL, i cannot generate the required files necessary to do the bindings. Are you sure??... AFAIK .net use WSDL... According to following (which I found just now) .net even supports contract first development.. http://msdn2.microsoft.com/en-us/magazine/cc163800.aspx Wat exactly is your use case.. ?? thanks, Thilina Does anyone know how to talk to a .NET application with MTOM using Java ? Thanks, -- Thilina Gunarathne - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Urgent Help! AXIS 1.4 SoapEnvelope error
Hi, Its very clear that we have a technical problem when deserializing cause the second ns1: overwrites the first. My question is how this serialization comes about? AXIS 1.4 wasnt built with sending arbitrary XML-Messages around in mind. I'd suggest start anew with a WSDL-first approach. Cheers Wolfgang --- Ryan Champlin [EMAIL PROTECTED] wrote: All, I'm also running into the same exact issue as this prior post (below) to this mailing list. Are there any resolutions out there for this This issue is preventing Axis clients as well as others from properly consuming the response SOAP document. I need a resolution or proper workaround for this issue. Thanks, Ryan Hi All, I've been struggling with the following error that has to do with deserializing a soapEnvelope, can anyone help? Thanks much. Frank = I am using AXIS 1.4 for my web service needs. I try to send an XML message over HTTP, the XML message defines a namespace at the root element like this: xmlns:ns1=somthing Let me assume this xml string as xmltext, now I create a soap envelope with this XML message as body, the soapEnvelope object seems good to me in my debugger, but a problem occurs when I try to deserialize it using soapEnvelope.toString() or soapEnvelope.getAsString().I notice that for every local element in the original xml such as this: ns1:recxxx/ns1:rec, in the output string, I get the the following: ns1:rec xmlns:ns1=xxx/ns1:rec That is, there is an extra attribute with empty value. This causes problems for the receivers of the http response. Here is the soapEnvelope dump: soapenv:Envelope 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:Body ns1:RecordSet xmlns:ns1=http://.com/yyy_out; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; ns1:Record xmlns:ns1= ns1:PROSPECT_NUMBER xmlns:ns1=10/ns1:PROSPECT_NUMBER ns1:FIRM xmlns:ns1=Business Objects/ns1:FIRM ns1:FIRST_NAME xmlns:ns1=Ryan/ns1:FIRST_NAME ns1:MIDDLE_NAME xmlns:ns1=/ ns1:LAST_NAME xmlns:ns1=Champlin/ns1:LAST_NAME /ns1:Record /ns1:RecordSet /soapenv:Body /soapenv:Envelope Here are my code snappet: === SOAPEnvelope soapEnvelope = new SOAPEnvelope(); Element bodyElement = createDocument(xmltext).getDocumentElement(); org.apache.axis.message.SOAPBodyElement messageElement = new org.apache.axis.message.SOAPBodyElement(bodyElement); soapEnvelope.addBodyElement((SOAPBodyElement)messageElement); The createDocument(xmlText) calls the following APIs: InputSource source = new InputSource( new StringReader( xmlText ) ) ; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); factory.setIgnoringElementContentWhitespace(false); DocumentBuilder docBuilder = factory.newDocumentBuilder(); return docBuilder.parse(source); Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: call to web service is too slow
Hi Ajit, A typical Web Service with Axis 1.4 needs half a second only. What is the size of your payload? Cheers Wolfgang --- [EMAIL PROTECTED] wrote: Hi Group, I am using Axis 1.4 for my web service development. One thing I have observed is that the time taken for the return of the method call to the client is considerably high is sometimes to the tune of 7-8 seconds. I believe, this is the time taken by the axis engine to prepare a SOAP reply in return. This does not seem to be acceptable. Is there any way, I can improve the performance? Will moving to Axis 2 work in this regard? Has anyone of you observed any performance improvements when moved to Axis 2? Thanks, Ajit DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with VB as client of axis 1.4 web services
Hi, which Axis version ? Axis 2 1.4 or Axis 1 1.4? WSDL? SOAP-Trace? Cheers Wolfgang --- [EMAIL PROTECTED] wrote: Hi Group, I have an axis java client axis java server which works fine. When I use wsdl with a VB client, I am able to hit the server, but when I make the call, the return values are always nothing. I am using Document/Literal style for exposing my web services. Any help would be highly appreciated. Thanks, Ajit DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help! AXIS 1.4 SoapEnvelope deserialization error
Hi, could you provide the wsdl and a soap-trace? which style and encoding are u using? Cheers Wolfgang --- Frank Zhou [EMAIL PROTECTED] wrote: Hi All, I am re-posting this message, hoping to get some urgent help. I am using AXIS 1.4 for my web service needs. I am now encounting the following error when I try to send an XML over HTTP: I have a valid XML message as a string, the XML message defines a namespace at the root element like this: xmlns:ns1=somthing Let me assume this xml string as xmltext, now I create a soap envelope with this XML message as body, the soapEnvelope object seems good to me in my debugger, but a problem occurs when I try to deserialize it using soapEnvelope.toString() or soapEnvelope.getAsString(). I notice that for every local element in the original xml such as this: ns1:recxxx/ns1:rec, in the output string, I get the the following: ns1:rec xmlns:ns1=xxx/ns1:rec That is, there is an extra attribute with empty value. This causes problems for the receivers of the http response. Here are my code snappet: === SOAPEnvelope soapEnvelope = new SOAPEnvelope(); Element bodyElement = createDocument(xmltext).getDocumentElement(); org.apache.axis.message.SOAPBodyElement messageElement = new org.apache.axis.message.SOAPBodyElement(bodyElement); soapEnvelope.addBodyElement((SOAPBodyElement)messageElement); The createDocument(xmlText) calls the following APIs: InputSource source = new InputSource( new StringReader( xmlText ) ) ; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); factory.setIgnoringElementContentWhitespace(false); DocumentBuilder docBuilder = factory.newDocumentBuilder(); return docBuilder.parse(source); It seems to me that AXIS has a bug handling this case. Any help is very much appreciated! Thanks! Frank Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: code too large error
Hi, once upon a time there had been a size limit for classes of 64K Just wildly guessing. Cheers, --- Hemant Borole [EMAIL PROTECTED] wrote: Sorry, The binding we are using is rpc. On Dec 20, 2007 8:16 AM, Hemant Borole [EMAIL PROTECTED] wrote: Hi Amila, This is the same issue that I have reported about limitation on the number of operations in the WSDL. I am not using the -u option, will give it a try. I am using axis 1.4 I am using document encoded. Unfortunately due to privacy concerns I am not able to share the WSDL. P.S. The issue reported by Man Tat and me are the same. Basically we are talking about the same WSDL file. On Dec 20, 2007 5:13 AM, Amila Suriarachchi [EMAIL PROTECTED] wrote: what are the options you use to generate the code? do you use the -u option. is it possible you to send the wsdl? thanks, Amila. On Dec 20, 2007 1:33 AM, Man Tat Lam [EMAIL PROTECTED] wrote: Hi everyone, I am a webservices developer (just for a few months). I am using wsdl2java ant alot to build the stub, binding and stuff. Everything works fine (thanks for your effort). I went into some problem yesterday. I now have around 121 operations in my wsdl file, when I add one more operation and try to compile it. The BindingSkeleton.java generated by wsdl2java throw me an error 12: code too large [javac] private static java.util.Map _myOperations = new java.util.Hashtable(); It looks like there are too many operations and the Hashtable cannot hold it. Can anyone give me some suggestion what I should do. I know many of you are very good designer and think I should refactor out some methods. In this case, I don;t think I have the options. thanks alot, appreciated Merry X'mas mantat -- Amila Suriarachchi, WSO2 Inc. -- Thanks and Regards Hemant -- Thanks and Regards Hemant Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Namespace problem of Array element.
Hi you should generally use doc-lit-wrapped anyway, Cheers, Wolfgang --- Terry Zhou [EMAIL PROTECTED] wrote: Hey Anne, Sorry my typo the client message is wrong, should be env:Envelope xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; env:Header/ env:Body math:a xmlns:math=http://math.samples; math:item1/math:item math:item2/math:item math:item5/math:item math:item8/math:item math:item99/math:item /math:a /env:Body /env:Envelope I have started from a clean state and try the message on Axis2-1.3 and Axis1.4 again and found Axis1.4 did have namespace problem of Array elements as I have described. I used doc/literal bare style, for Axis2-1.3, it has no such problem with the same style. A workaround for Axis1.4 is to use doc/literal wrapped style, it's OK. Regards, Terry On Nov 28, 2007 12:19 AM, Anne Thomas Manes [EMAIL PROTECTED] wrote: As I said, I think it must be something wrong in your implementation. Please start from a clean slate by generating code from your WSDL file. Anne On Nov 27, 2007 9:28 AM, Terry Zhou [EMAIL PROTECTED] wrote: Thanks Anne for your reply! I have two question about you answer: 1.The same WSDL why axis2 behavior differs with Axis 1.4? 2.If it's qualified why not use http://math.samples; as its namespace instead of empty? Regards, Terry On Nov 27, 2007 10:23 PM, Anne Thomas Manes [EMAIL PROTECTED] wrote: You schema definition specifies elementFormDefault=qualified therefore Axis should qualify the item elements. Axis normally handles this just fine, so I assume there's a problem in the way you implemented your service. I suggest you start over by running wsdl2java. Anne On Nov 27, 2007 9:10 AM, Terry Zhou [EMAIL PROTECTED] wrote: Sorry, Anne, I just think this maybe an issue of Axis 1.4, developer may know more about it. Thanks, Terry On Nov 27, 2007 10:02 PM, Anne Thomas Manes [EMAIL PROTECTED] wrote: Please send questions related to using Axis and Axis2 to the axis-user list. The axis-dev list is for issues related to developing the Axis and Axis2 frameworks themselves. Anne On Nov 27, 2007 5:31 AM, Terry Zhou [EMAIL PROTECTED] wrote: Hi, all Is there any configuration to prevent the empty namespace generatation of array element for Axis1.4 when use basic type array with document/literal style? For example, The client soap request message is: soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/ soapenv:Body ns:echoIntArrayResponse xmlns:ns= http://quickstart.samples/xsd; ns:return1/ns:return ns:return2/ns:return ns:return5/ns:return ns:return8/ns:return ns:return99/ns:return /ns:echoIntArrayResponse /soapenv:Body /soapenv:Envelope and axis serve side response: soapenv:Envelope 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:Body aReturn xmlns= http://math.samples; item xmlns=1/item item xmlns=2/item item xmlns=5/item item xmlns=8/item item xmlns=99/item /aReturn /soapenv:Body /soapenv:Envelope This won't interop with some web service client for the element item has a empty namespace instead of the default one( http://math.samples;). I have also tested with Axis2-1.3, it responses OK with the following message: soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns:echoIntArrayResponse xmlns:ns= http://quickstart.samples/xsd ns:return1/ns:return ns:return2/ns:return ns:return5/ns:return ns:return8/ns:return ns:return99/ns:return /ns:echoIntArrayResponse /soapenv:Body /soapenv:Envelope So for Axis 1.4, is there any configuration to make the namespace of element item right? Thanks a lot! Terry FYI, WSDL file for the web service. ?xml version=1.0 encoding=UTF-8? wsdl:definitions === message truncated === Be a better pen pal. Text or chat with friends inside
Re: First Element must contain the local name, Envelope , but found HTML
Hello, mere guess: are you using xhtml in the error-case? pls send a soap-trace Cheers --- BJuma [EMAIL PROTECTED] wrote: Belal wrote: The strange thing is if it is OC4J alone, the auto-generated java client is working fine as expected. but on the Oracle AS it is not working. pzfreo wrote: WSDL2Java is pretty reliable. To debug the next step is to see a trace of your message. Paul On Nov 19, 2007 3:08 PM, BJuma [EMAIL PROTECTED] wrote: Belal wrote: using SOAPUI it is working perfectly. I can see the soap respnse as expected. but why using the generated java client (wsdl2java) i got such an exception. is axis2 wsdl2java not reliable or I am doing some thing wrong! pzfreo wrote: It seems like maybe the URL is incorrect. Basically the call is returning a HTML page instead of a SOAP document. The best way to trace this is to use TCPMON or another network sniffer to see what is happening. Another approach is to try SOAPUI to make a call and test the service is working properly. Paul On Nov 19, 2007 12:53 PM, BJuma [EMAIL PROTECTED] wrote: Hi, We have developed some webservices in OracleAS 10g. I can check from the axis2 web administration console that all of them are depoloyed successfully and I can view their WSDL. I auto-generated axis2 java client to access those webservices. when trying to run them, I got the following exception. I really appreciate your urgent help. Nov 19, 2007 4:09:30 PM org.apache.axis2.builder.BuilderUtilgetSOAPBuilder INFO: OMException in getSOAPBuilder org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found HTML at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode( StAXSOAPModelBuilder.java:219) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement ( StAXSOAPModelBuilder.java:177) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java :163) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope ( StAXSOAPModelBuilder.java:161) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init( StAXSOAPModelBuilder.java:110) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java :609) at org.apache.axis2.transport.TransportUtils.createDocumentElement( TransportUtils.java:178) at org.apache.axis2.transport.TransportUtils.createSOAPMessage( TransportUtils.java:111) at org.apache.axis2.transport.TransportUtils.createSOAPMessage( TransportUtils.java:87) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse( OutInAxisOperation.java:326) at org.apache.axis2.description.OutInAxisOperationClient.send( OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl( OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java :163) at ae.ead.egovernment.core.webservice.LookupDataServiceStub.getCountries( LookupDataServiceStub.java:385) at ae.ead.egovernment.core.webservice.TestClient.main(TestClient.java:19) Nov 19, 2007 4:09:30 PM org.apache.axis2.builder.BuilderUtilgetSOAPBuilder INFO: Remaining input stream :[] Exception in thread main org.apache.axis2.AxisFault: First Element must contain the local name, Envelope , but found HTML at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.TransportUtils.createSOAPMessage( TransportUtils.java:89) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse( OutInAxisOperation.java:326) at org.apache.axis2.description.OutInAxisOperationClient.send( OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl( OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java :163) at ae.ead.egovernment.core.webservice.LookupDataServiceStub.getCountries( LookupDataServiceStub.java:385) at ae.ead.egovernment.core.webservice.TestClient.main(TestClient.java:19) Caused by: org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found HTML at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode( StAXSOAPModelBuilder.java:219) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement ( StAXSOAPModelBuilder.java:177) === message truncated ===
Re: Problem with ConverterUtil convertTo* methods and empty XML tag
Hi
the problem with non-perfect XSD is that its no longer
XSD proper and the whole idea of a world-wide agreed
interface standard collapses.
An official XSD-tool must not support inofficial
XSD-modifications.
Your customer cant Schema-validate his non-perfect XML
with standard tools either
Cheers
--- Jozef Krssak [EMAIL PROTECTED] wrote:
Hi
ok, my customer hasn't absolutely perfect XSD and
sends to me empty elements
even if their type is int.
I think primary problem is that utility class
ConverterUtil and its methods
do not check input parameters for values null or
empty string to avoid
useless exceptions like:
java.lang.RuntimeException: In valid string to parse
in convertToDate(String) method
or
java.lang.NumberFormatException
in convertToDecimal(String) method
Is there any reason why robustness of common utility
class ConverterUtil
cannot be improved? In many cases if input parameter
is null of empty string
the valid return value is null, I think.
--
Jozef Krssak
On 10/8/07, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
you have to declare your element as nillable=true
if you want to have
xs:nil=true
xsd:element name=EndDate type=tns:WSTypeDate
nillable=true/
Amila.
On 10/8/07, Jozef Krssak [EMAIL PROTECTED]
wrote:
Hi
Element definition in schema:
xsd:element name=EndDate
type=wsct:WSTypeDate minOccurs=1/
Type wsct:WSTypeDate is in other schema as:
xsd:simpleType name=WSTypeDate
xsd:restriction base=xsd:date
xsd:pattern
value='[0-9]{4}-[0-9]{2}-[0-9]{2}'/
/xsd:restriction
/xsd:simpleType
Element in XML:
EndDate xsi:nil=true/
Another one example:
xsd:element name=SMS_Provider
type=wsct:WSTypeChar3 minOccurs=1/
xsd:simpleType
name=WSTypeChar3xsd:restriction
base=xsd:stringxsd:maxLength
value=3//xsd:restriction/xsd:simpleType
SMS_Provider xsi:nil=true/
Thanks and Regards
--
Jozef Krssak
On 10/5/07, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
Can you send a sample schema and sample xml
you get as well?
I guess you talk something like this.
xs:element name=test type=xs:int/
and you get an xml for this like this
test/test
My question is, is this a valid xml for this?
if the type is int there
must be an int inside it.
on the other hand you can have
xs:element nillable=true minOccurs=0
name=test type=xs:int/
to represent that is null. but above is an
invalid xml.
Amila.
--
Amila Suriarachchi,
WSO2 Inc.
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.
http://farechase.yahoo.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with pattern restriction in XSD and WDSL2Java generated code
Hi,
so there must be a way
to valide using the object
Using the original REGEXP: Only AFTER serializing the
object to XML and applying
the REGEXP afterwards. Checking the object would have
to be done on a logical level, the REGEXP could do
anything, e.g. exclude todays date only.
Cheers,
Wolfgang
--- Amila Suriarachchi [EMAIL PROTECTED]
wrote:
On 9/28/07, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
hi,
this should be a bug. we have to use the
connvertToString method
of the ConverterUtil class. which properly out put
the string values.
please have a look at with a nightly build.
On 9/27/07, WJ Krpelan [EMAIL PROTECTED] wrote:
Hi
from an XSD point of view, it is possible to
forbid certain kinds of date-formatting by using
patterns. of course, those patterns would have
to be
applied to the original xml-content.
ok from this we can only valid this at the parsing
time. i.e when getting
an xml.
how about the serilizing? i.e we have to produce
the xml from the object.
so there must be a way
to valide using the object.
Amila.
Cheers
Wolfgang
--- Jozef Krssak [EMAIL PROTECTED] wrote:
Hi
We have several wsdl and xsd files from
customer and
we are using
Axis2 v1.3WSDL2Java task to create client part
of
Java classes to call
Web Services.
One problematic part of generated code commes
from
XSD code:
xsd:simpleType name=WSTypeDate
xsd:restriction base=xsd:date
xsd:pattern
value='[0-9]{4}-[0-9]{2}-[0-9]{2}'/
/xsd:restriction
/xsd:simpleType
xsd:simpleType name=WSTypeTime8
xsd:restriction base=xsd:string
xsd:maxLength value=6/
xsd:pattern
value='[0-9]{2}:[0-9]{2}:[0-9]{2}'/
/xsd:restriction
/xsd:simpleType
xsd:simpleType name=WSTypeDateTime
xsd:restriction base=xsd:dateTime
xsd:pattern
value='[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}'/
/xsd:restriction
/xsd:simpleType
xsd:simpleType name=WSTypeUID38
xsd:restriction base=xsd:string
xsd:pattern
value='\{[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}\}'/
/xsd:restriction
/xsd:simpleType
Created classes WSTypeDate, WSTypeTime8,
WSTypeDateTime, WSTypeUID38 have
setter methods like:
public void setWSTypeDate( java.util.Date
param)
{
if
(java.lang.String.valueOf(param).matches([0-9]{4}-[0-9]{2}-[0-9]{2}))
{
this.localWSTypeDate = param;
} else {
throw new
java.lang.RuntimeException();
}
}
public void
setWSTypeTime8(java.lang.String
param) {
if
(java.lang.String.valueOf
(param).matches([0-9]{2}:[0-9]{2}:[0-9]{2}))
{
this.localWSTypeTime8 = param;
} else {
throw new
java.lang.RuntimeException();
}
}
public void
setWSTypeDateTime(java.util.Calendar
param) {
if (java.lang.String.valueOf(param)
.matches([0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}))
{
this.localWSTypeDateTime = param;
} else {
throw new
java.lang.RuntimeException();
}
}
public void setWSTypeUID38(
java.lang.String
param) {
if (java.lang.String.valueOf(param)
.matches(\\{[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}\\}))
{
this.localWSTypeUID38 = param;
} else {
throw new
java.lang.RuntimeException();
}
}
When given parameter is String, then the
matching of
pattern is OK, BUT if
it is Date or Calendar then it is problem due
to
used String.valueOf(param)
because Date.toString() and
Calendar.toString()
alaways use same String
pattern which never match given pattern and
furthermore in that case there
is no sense to check any pattern.
My question is: Is it a bug of WSDL2Java task
to
create this part of code
when XSD use restriction base xsd:date or
xsd:dateTime or is it a feature? I
think it is a bug.
Thank you
Regards
--
Jozef Krák
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
=== message truncated
Re: Problem with pattern restriction in XSD and WDSL2Java generated code
Hi
from an XSD point of view, it is possible to
forbid certain kinds of date-formatting by using
patterns. of course, those patterns would have to be
applied to the original xml-content.
Cheers
Wolfgang
--- Jozef Krssak [EMAIL PROTECTED] wrote:
Hi
We have several wsdl and xsd files from customer and
we are using
Axis2 v1.3WSDL2Java task to create client part of
Java classes to call
Web Services.
One problematic part of generated code commes from
XSD code:
xsd:simpleType name=WSTypeDate
xsd:restriction base=xsd:date
xsd:pattern
value='[0-9]{4}-[0-9]{2}-[0-9]{2}'/
/xsd:restriction
/xsd:simpleType
xsd:simpleType name=WSTypeTime8
xsd:restriction base=xsd:string
xsd:maxLength value=6/
xsd:pattern
value='[0-9]{2}:[0-9]{2}:[0-9]{2}'/
/xsd:restriction
/xsd:simpleType
xsd:simpleType name=WSTypeDateTime
xsd:restriction base=xsd:dateTime
xsd:pattern
value='[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}'/
/xsd:restriction
/xsd:simpleType
xsd:simpleType name=WSTypeUID38
xsd:restriction base=xsd:string
xsd:pattern
value='\{[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}\}'/
/xsd:restriction
/xsd:simpleType
Created classes WSTypeDate, WSTypeTime8,
WSTypeDateTime, WSTypeUID38 have
setter methods like:
public void setWSTypeDate(java.util.Date param)
{
if
(java.lang.String.valueOf(param).matches([0-9]{4}-[0-9]{2}-[0-9]{2}))
{
this.localWSTypeDate = param;
} else {
throw new java.lang.RuntimeException();
}
}
public void setWSTypeTime8(java.lang.String
param) {
if
(java.lang.String.valueOf(param).matches([0-9]{2}:[0-9]{2}:[0-9]{2}))
{
this.localWSTypeTime8 = param;
} else {
throw new java.lang.RuntimeException();
}
}
public void setWSTypeDateTime(java.util.Calendar
param) {
if (java.lang.String.valueOf(param)
.matches([0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}))
{
this.localWSTypeDateTime = param;
} else {
throw new java.lang.RuntimeException();
}
}
public void setWSTypeUID38(java.lang.String
param) {
if (java.lang.String.valueOf(param)
.matches(\\{[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}\\}))
{
this.localWSTypeUID38 = param;
} else {
throw new java.lang.RuntimeException();
}
}
When given parameter is String, then the matching of
pattern is OK, BUT if
it is Date or Calendar then it is problem due to
used String.valueOf(param)
because Date.toString() and Calendar.toString()
alaways use same String
pattern which never match given pattern and
furthermore in that case there
is no sense to check any pattern.
My question is: Is it a bug of WSDL2Java task to
create this part of code
when XSD use restriction base xsd:date or
xsd:dateTime or is it a feature? I
think it is a bug.
Thank you
Regards
--
Jozef Krššák
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with Adding Namespace Declaration and Attribute
basically, axis 1.1 is hardly being used in production. are you referring to the jboss implementation? --- Ghaznavi, Syed [EMAIL PROTECTED] wrote: Hi, I have been trying to resolve this problem for some time but have not been able to get my code to work!! I a sample WSClient application that adds digital signatures to the message. Basically I am trying to add a namespace declaration in the SOAPBody element using addNamespaceDeclaration method on the body element and then add a new Attribute associated with that namespace in the SOAPBody element. I am using Axis 1.1 API for this. SOAPBody body = sEnvelope.getBody(); Body.addNamespaceDeclaration(wsu, http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-util ity-1.0.xsd); body.addAttribute(sEnvelope.createName(Id,wsu http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-util ity-1.0.xsd), Body); But this above code doesn't add anything in the body, except, soapenv:Body Id=Body I was wondering if there is a Bug in Axis1.1 API that results in this above behavior ?? When I tried using Axis 1.4 and my code seems to work, that is I get a body element as follows... soapenv:Body wsu:Id=Body xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec urity-utility-1.0.xsd/soapenv:Body What if any is the workaround this, using Axis1.1, because we are restricted with using Axis1.1 API. Thanks! Frustrated Axis1.1 User - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to tell if an AxisOperation is using wrapper style ?
Hi, look within the generated code for wrapped worked with Axis 1 Cheers --- Luciano Resende [EMAIL PROTECTED] wrote: How can I tell if an AxisOperation is using wrapper style or not ? Could someone point me to some place where this is done in Axis, or give me some hints, please. -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS2 : JVM bursts when getting images in MB size
Hi u speaking of some MB ore some GB? doubt its the JVM. Rather restrictions on xml-element-size? just guessing Cheers --- Thilina Gunarathne [EMAIL PROTECTED] wrote: You won't be able to send large data inside the envelope using Base64 binary, as it'll cause Axis2 to load the whole of data in to memory. You should use MTOM or SwA if your data are large. Are you getting the error on client or on server side. IIRC in the service code of your earlier posting you were trying to do a system.out on the binary data. This needs to be avoided in any case. As this also makes the data to be loaded in to memory irrespective of whether you are sending them inline or as attachments. A wire trace using TCPMON(ws.apache.org/commons/tcpmon) for a smaller file would help a lot to better understand what's going on.. thanks, Thilina On 9/5/07, Sushil Dodake [EMAIL PROTECTED] wrote: Guys, I dont know whether this is a AXIS2 problem. I am trying to get the Image files from the documentum server using web service. when i try to get say 4 image files in a go and if the total size of the file is in some MBs then the JVM goes bm. i have done follwong things to avoid 1. Set a environmental Variable CATALINA_OPTS = -Xms512m -Xmx512m 2. Also set the same variable in the cataline.bat file set CATALINA_OPTS=-mx512m 3. even set the same values in the tomcat 5.0 configuration But still my JVM gives the same error java.lang.OutOfMemoryError can anybody suggest me what i need to do when i am sending large data using AXIS2 Please note i am sending the Images as the binary content in the XML response. any help in this respect will be appreciated regards, Sushil -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re : Re : Re : Tr : Axis problem returning byteArray
Hello, classical case of WSDL first. I'd suggest alter the type of CONTENT to base64Binary, then generate your java-code with WSDL2Java and use the resulting classes Worked with me. Cheers --- Thomas Beaujard [EMAIL PROTECTED] wrote: Hello, Here is the wsdl gnerated when I use the ?wsdl. The return object is GMDSRESPCT, adn the tag containing the byteArray is CONTENT. You will notice that CONTENT is defined as xsd:string type. This is weird because I generated the class using WSDL2java and when I first created the wsdl file I specified content as xsd:base64Binary. I really don't understand. The wsdl : wsdl:types complexType name=GMDSREQCT sequence element name=TYPE_ID type=xsd:string / element name=DOC_ID type=xsd:string / /sequence /complexType element name=GMDSREQCT type=tns1:GMDSREQCT / complexType name=GMDSRESPCT sequence element maxOccurs=1 minOccurs=0 name=CONTENT type=xsd:string / *// xsd:base64Binary// /sequence /complexType element name=GMDSRESPCT type=tns1:GMDSRESPCT / /schema complexType name=GMDSERRCT sequence element name=GMDSERRCT type=xsd:string / /sequence /complexType /schema element name=fault type=tns2:GMDSERRCT / /schema /wsdl:types wsdl:message name=getDocumentRequest wsdl:part element=tns1:GMDSREQCT name=GMDSREQCT / /wsdl:message wsdl:message name=GMDSERRCT wsdl:part element=impl:fault name=fault / /wsdl:message wsdl:message name=getDocumentResponse wsdl:part element=tns1:GMDSRESPCT name=GMDSRESPCT / /wsdl:message wsdl:portType name=DocContentPortType wsdl:operation name=getDocument parameterOrder=GMDSREQCT wsdl:input message=impl:getDocumentRequest name=getDocumentRequest / wsdl:output message=impl:getDocumentResponse name=getDocumentResponse / wsdl:fault message=impl:GMDSERRCT name=GMDSERRCT / /wsdl:operation /wsdl:portType wsdl:binding name=DocContentSOAPPortSoapBinding type=impl:DocContentPortType wsdl:operation name=getDocumentwsdlsoap:operation soapAction=getDocument / wsdl:input name=getDocumentRequest wsdlsoap:body use=literal / /wsdl:input wsdl:output name=getDocumentResponse wsdlsoap:body use=literal / /wsdl:output wsdl:fault name=GMDSERRCT wsdlsoap:fault name=GMDSERRCT use=literal / /wsdl:fault /wsdl:operation/wsdl:bindingwsdl:service name=DocContentService wsdl:port binding=impl:DocContentSOAPPortSoapBinding name=DocContentSOAPPort /wsdl:port /wsdl:service /wsdl:definitions - Message d'origine De : WJ Krpelan [EMAIL PROTECTED] À : axis-dev@ws.apache.org Envoyé le : Mardi, 4 Septembre 2007, 20h05mn 22s Objet : Re: Re : Re : Tr : Axis problem returning byteArray Hello, As it works with me, I'd suspect there is something wrong with your xsd-File or your WSDL-File Can I have a look at the WSDL? Cheers --- Thomas Beaujard [EMAIL PROTECTED] wrote: Hi Here is the SOAP-trace: HTTP/1.1 200 OK Content-Type: text/xml;charset=utf-8 Date: Tue, 04 Sep 2007 11:10:43 GMT Server: Apache-Coyote/1.1 Connection: close soapenv:Body GMDSRESPCT xmlns= CONTENT xsi:type=xsd:byte xmlns=37/CONTENT CONTENT xsi:type=xsd:byte xmlns=80/CONTENT CONTENT xsi:type=xsd:byte xmlns=68/CONTENT CONTENT xsi:type=xsd:byte xmlns=70/CONTENT CONTENT xsi:type=xsd:byte xmlns=45/CONTENT CONTENT xsi:type=xsd:byte xmlns=49/CONTENT .. CONTENT xsi:type=xsd:byte xmlns=13/CONTENT /GMDSRESPCT/soapenv:Body/soapenv:Envelope As you can see the tag CONTENT appears many times with a type byte, whereas it should only appear once with the type base64binary. I cannot use the xs:string workaround... do you have any other idea? Thanks for your help Thom - Message d'origine De : WJ Krpelan [EMAIL PROTECTED] À : axis-dev@ws.apache.org Envoyé le : Vendredi, 31 Août 2007, 12h24mn 28s Objet : Re: Re : Tr : Axis problem returning byteArray Hi Could you provice a SOAP-Trace (TCPMon)? Would it look similar to the one below? A less than satisfactory workaround, if you control both sides of the wire, would be to change type to xs:string and do the conversion within java. Cheers POST /axis/CalcArr.jws HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: 127.0.0.1:8088 Cache-Control: no-cache Pragma: no-cache SOAPAction: Content-Length: 334 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope
Re: axis-castor : unable to find fieldDescriptor
Hi Generally, only standard xml-schema-data types are being provided out of the box. The easy way to do it is to break it up into standard data types. Else I'm sure IBM is selling some serializing support for its special data types. Cheers --- Thomas Beaujard [EMAIL PROTECTED] wrote: Hello I am trying the example from this link : http://www.ibm.com/developerworks/webservices/library/ws-castor/ And I get the following error : org.xml.sax.SAXException: Unable to marshall between XML and Castor Objects :unable to find FieldDescriptor for 'DOC_ID' in ClassDescriptor of GMDSREQCT I have seen thread where people had the same problem as me. One person said that we have to modify the CastorSerializer class as explained in this link: http://www.mail-archive.com/[EMAIL PROTECTED]/msg15150.html However, I cannot access this link. Does anyone have a solution? Cheers Thom _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re : Tr : Axis problem returning byteArray
Hi
Could you provice a SOAP-Trace (TCPMon)? Would it look
similar to the one below?
A less than satisfactory workaround, if you control
both sides of the wire, would be to change type to
xs:string and do the conversion within java.
Cheers
POST /axis/CalcArr.jws HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime,
multipart/related, text/*
User-Agent: Axis/1.4
Host: 127.0.0.1:8088
Cache-Control: no-cache
Pragma: no-cache
SOAPAction:
Content-Length: 334
?xml version=1.0 encoding=UTF-8?
soapenv:Envelope
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:Body
Add xmlns=http://tempuri.org/;
i1ITAMWA==/i1
i2FxdiAg==/i2
/Add
/soapenv:Body
/soapenv:Envelope
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie:
JSESSIONID=887A1E5E02B52B88387CAD9B3FEA7F6C;
Path=/axis
Content-Type: text/xml;charset=utf-8
Date: Fri, 31 Aug 2007 10:16:54 GMT
Connection: close
?xml version=1.0 encoding=utf-8?
soapenv:Envelope
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:Body
ns1:AddResponse
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:ns1=http://tempuri.org/;
AddReturn
xsi:type=xsd:base64BinaryOEduWg==/AddReturn
/ns1:AddResponse
/soapenv:Body
/soapenv:Envelope
--- Thomas Beaujard [EMAIL PROTECTED] wrote:
Thanks for your answer, I will try to explain my
problem more precisely:
In fact, I generated my code from WSDL2java with a
wsdl file and a xsd file as input. In the xsd file I
defined the response as being xsd:base64binary.
Here is the service definition in my
server-config.wsdd:
service name=DocContent provider=java:RPC
style=document use=literal
operation name=getDocument qname=getDocument
returnQName=ns1:GMDSRESPCT
returnType=ns1:GMDSRESPCT soapAction=
xmlns:ns1=...
parameter qname=ns1:GMDSREQCT
type=ns1:GMDSREQCT/
fault class=com.messages.GMDSERRCT
qname=ns1:GMDSERRCT type=ns1:GMDSERRCT/
/operation
parameter name=allowedMethods
value=getDocument/
parameter name=typeMappingVersion value=1.2/
parameter name=wsdlPortType
value=DocContent/
parameter name=className
value=com.webservice.GetDocumentSoapBindingImpl/
parameter name=wsdlServicePort
value=DocContent/
parameter name=wsdlTargetNamespace
value=/
parameter name=wsdlServiceElement
value=DocContentService/
parameter name=schemaUnqualified
value=../
typeMapping
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle= qname=ns2:gt;GMDSREQCT
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
type=java:com..messages.GMDSREQCT
xmlns:ns2=./
typeMapping
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle= qname=ns3:gt;GMDSRESPCT
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
type=java:com.messages.GMDSRESPCT
xmlns:ns3=./
typeMapping
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle= qname=ns4:gt;GMDSERRCT
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
type=java:commessages.GMDSERRCT
xmlns:ns4=.../
/service
Here is the class corresponding to the response :
public class GMDSRESPCT implements Serializable {
private byte[] CONTENT;
private
public GMDSRESPCT() {
}
public GMDSRESPCT(byte[] CONTENT) {
this.CONTENT = CONTENT;
}
public byte[] getCONTENT() {
return CONTENT;
}
So the web service should return an object
GMDSRESPCT. But I get the error and when I use
tcpmon to see the messages exchanged, I notice that
the response include CONTENT tag for every single
byte instead of having the array of byte within the
tag CONTENT.
Hope it's not too messy.
Cheers
Thom
- Message d'origine
De : WJ Krpelan [EMAIL PROTECTED]
À : axis-dev@ws.apache.org
Envoyé le : Jeudi, 30 Août 2007, 17h18mn 03s
Objet : Re: Tr : Axis problem returning byteArray
Hello
you can't simply send binary data as on the
transport
level its converted to xml, which is basically plain
text.
One simple possibility would be to use datatype
base64binary
Cheers,
--- Thomas Beaujard [EMAIL PROTECTED] wrote:
Hello,
I'm using Axis 1.4.
I have a document style web service which returns
a
byteArray (actually a pdf file).
When I invoke the web service, I get the following
error:
org.apache.axis.encoding.ser.BeanPropertyTarget
set
Could not convert java.lang.Byte to bean field
'CONTENT', type [B
Does anyone have encounter similar problem?
Thanks in advance,
Thom
Ne gardez plus qu'une seule adresse mail
Re: Tr : Axis problem returning byteArray
Hello you can't simply send binary data as on the transport level its converted to xml, which is basically plain text. One simple possibility would be to use datatype base64binary Cheers, --- Thomas Beaujard [EMAIL PROTECTED] wrote: Hello, I'm using Axis 1.4. I have a document style web service which returns a byteArray (actually a pdf file). When I invoke the web service, I get the following error: org.apache.axis.encoding.ser.BeanPropertyTarget set Could not convert java.lang.Byte to bean field 'CONTENT', type [B Does anyone have encounter similar problem? Thanks in advance, Thom Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bug? SimpleType enumeration output is incorrect.
Right. I'd never bet on living in a perfect world,
however :-)
Wolfgang
--- Anne Thomas Manes [EMAIL PROTECTED] wrote:
That's an inappropriate restriction. XML has no such
reserved words
constraints. If Axis2 has a problem dealing with a
valid local name,
it's a bug.
Anne
On 8/16/07, WJ Krpelan [EMAIL PROTECTED] wrote:
Hi
Methinks you shouldn't use type as element name,
and
neither element nor attribute etc. as these
are
kind of reserved words. Use type1 or something
and
it should work imho.
Cheers
Wolfgang Krpelan
--- Amila Suriarachchi
[EMAIL PROTECTED]
wrote:
Can you please test this for Axis2 1.3 release.
And run this sample code which gives me the
correct
out put
public class TestClass extends TestCase {
public void testGetResponse(){
GetResponse getResponse = new
GetResponse();
getResponse.setOut(Test out);
getResponse.setType(Type_T.a);
try {
OMElement omElement =
getResponse.getOMElement(
GetResponse.MY_QNAME,
OMAbstractFactory.getOMFactory());
System.out.println(OM Element ==
+
omElement.toStringWithConsume());
} catch (ADBException e) {
e.printStackTrace(); //To change
body
of catch statement use
File | Settings | File Templates.
} catch (XMLStreamException e) {
e.printStackTrace(); //To change
body
of catch statement use
File | Settings | File Templates.
}
}
}
ns1:GetResponse
xmlns:ns1=http://localhost:8080/wsdlfile/;
ns1:outTest out/ns1:out
ns1:typea/ns1:type
/ns1:GetResponse
Amila.
On 8/10/07, Kevin TierOne
[EMAIL PROTECTED]
wrote:
1 - If I run the wsdl through the code
generator,
I get the file
WsdlfileSkeleton.java.
2 - I implement this method:
public localhost.wsdlfile.GetResponse
Get(localhost.wsdlfile.Get get0)
{
localhost.wsdlfile.GetResponse resp=new
localhost.wsdlfile.GetResponse
();
resp.setOut(get0.getIn());
resp.setType(get0.getType());
return resp;
}
3 - After deploying the webservice, I send the
request as shown in the
original post.
4 - In the TCP monitor, I see the response
shown
the original post. I
expect that the response should echo the same
values and structure as
in the request. However, in the response, the
Element ns4:Type_T is
incorrect. The name of the element should be
type.
Let me know if you need any other info.
Kevin
On 8/10/07, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
Can you please describe your qestion bit?
in other words How can I regenerate your
issue?
Amila.
On 8/9/07, Kevin TierOne
[EMAIL PROTECTED] wrote:
Sorry, I forgot to mention that I'm using
Axis2 1.2.
Kevin
On 8/9/07, Kevin TierOne
[EMAIL PROTECTED] wrote:
The XML tags in the response messsage of
an
enumerated element uses
the simpleType name. It should use the
element name. For example,
using the wsdl below I get the following
request and response.
Look at the output
ns4:Type_Tc/ns4:Type_T, this element
should
be ns4:typec/ns4:type
REQUEST:
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:q0=
http://localhost:8080/wsdlfile/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
soapenv:Body
q0:Get
q0:inwww/q0:in
q0:typec/q0:type
/q0:Get
/soapenv:Body
/soapenv:Envelope
RESPONSE:
?xml version=1.0
encoding=http://schemas.xmlsoap.org/soap/envelope/;?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
ns4:GetResponse xmlns:ns4=
http://localhost:8080/wsdlfile/;
out
xmlns=http://localhost:8080/wsdlfile/;www/out
ns4:Type_Tc/ns4:Type_T
/ns4:GetResponse
/soapenv:Body
/soapenv:Envelope
?xml version=1.0 encoding=UTF-8?
wsdl:definitions
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:tns=http://localhost:8080/wsdlfile/
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema
=== message truncated ===
Shape Yahoo! in your own image. Join our Network Research Panel today!
http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Re: Bug? SimpleType enumeration output is incorrect.
Hi
Methinks you shouldn't use type as element name, and
neither element nor attribute etc. as these are
kind of reserved words. Use type1 or something and
it should work imho.
Cheers
Wolfgang Krpelan
--- Amila Suriarachchi [EMAIL PROTECTED]
wrote:
Can you please test this for Axis2 1.3 release.
And run this sample code which gives me the correct
out put
public class TestClass extends TestCase {
public void testGetResponse(){
GetResponse getResponse = new GetResponse();
getResponse.setOut(Test out);
getResponse.setType(Type_T.a);
try {
OMElement omElement =
getResponse.getOMElement(
GetResponse.MY_QNAME,
OMAbstractFactory.getOMFactory());
System.out.println(OM Element == +
omElement.toStringWithConsume());
} catch (ADBException e) {
e.printStackTrace(); //To change body
of catch statement use
File | Settings | File Templates.
} catch (XMLStreamException e) {
e.printStackTrace(); //To change body
of catch statement use
File | Settings | File Templates.
}
}
}
ns1:GetResponse
xmlns:ns1=http://localhost:8080/wsdlfile/;
ns1:outTest out/ns1:out
ns1:typea/ns1:type
/ns1:GetResponse
Amila.
On 8/10/07, Kevin TierOne [EMAIL PROTECTED]
wrote:
1 - If I run the wsdl through the code generator,
I get the file
WsdlfileSkeleton.java.
2 - I implement this method:
public localhost.wsdlfile.GetResponse
Get(localhost.wsdlfile.Get get0)
{
localhost.wsdlfile.GetResponse resp=new
localhost.wsdlfile.GetResponse
();
resp.setOut(get0.getIn());
resp.setType(get0.getType());
return resp;
}
3 - After deploying the webservice, I send the
request as shown in the
original post.
4 - In the TCP monitor, I see the response shown
the original post. I
expect that the response should echo the same
values and structure as
in the request. However, in the response, the
Element ns4:Type_T is
incorrect. The name of the element should be
type.
Let me know if you need any other info.
Kevin
On 8/10/07, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
Can you please describe your qestion bit?
in other words How can I regenerate your issue?
Amila.
On 8/9/07, Kevin TierOne
[EMAIL PROTECTED] wrote:
Sorry, I forgot to mention that I'm using
Axis2 1.2.
Kevin
On 8/9/07, Kevin TierOne
[EMAIL PROTECTED] wrote:
The XML tags in the response messsage of an
enumerated element uses
the simpleType name. It should use the
element name. For example,
using the wsdl below I get the following
request and response.
Look at the output
ns4:Type_Tc/ns4:Type_T, this element should
be ns4:typec/ns4:type
REQUEST:
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:q0= http://localhost:8080/wsdlfile/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
soapenv:Body
q0:Get
q0:inwww/q0:in
q0:typec/q0:type
/q0:Get
/soapenv:Body
/soapenv:Envelope
RESPONSE:
?xml version=1.0
encoding=http://schemas.xmlsoap.org/soap/envelope/;?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
ns4:GetResponse xmlns:ns4=
http://localhost:8080/wsdlfile/;
out
xmlns=http://localhost:8080/wsdlfile/;www/out
ns4:Type_Tc/ns4:Type_T
/ns4:GetResponse
/soapenv:Body
/soapenv:Envelope
?xml version=1.0 encoding=UTF-8?
wsdl:definitions
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:tns=http://localhost:8080/wsdlfile/
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema
xmlns:wsaw=http://www.w3.org/2006/02/addressing/wsdl;
name=wsdlfile
targetNamespace=
http://localhost:8080/wsdlfile/;
wsdl:types
xsd:schema
attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=
http://localhost:8080/wsdlfile/;
xsd:element name=Get
xsd:complexType
xsd:sequence
xsd:element
name=in type=xsd:string /
xsd:element
name=type
type=tns:Type_T/xsd:element
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:element name=GetResponse
xsd:complexType
xsd:sequence
xsd:element
name=out type=xsd:string /
xsd:element
name=type
type=tns:Type_T
/xsd:element
/xsd:sequence
Re: standalone tool to generate xml schema from java?
Hi, why not simply use java2wsdl and extract the schema from the generated wsdl? Should be a simple exercise - Cheers, --- Josh [EMAIL PROTECTED] wrote: All, I am starting to develope contract first web services. There are many cases where there are objects in my system that closely match those that will be exchanged on the wire. Using a tool that would allow me to generate an xml schema from a given java object would give me a lift in writing these schema files. Is there a way to do this other than using the java2wsdl tool? For my purposes, I really just need a java to schema tool. Any ideas? Thanks, Josh Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. http://new.toolbar.yahoo.com/toolbar/features/mail/index.php - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: calling a service from another service?
Hi u calling ant at runtime? Cheers, --- Thirumalachar, Shree Rangan [EMAIL PROTECTED] wrote: Hi All, I am trying to call a service from another service and I am using ALSB for the messaging. Here is what I do: 1: My client makes a call to a service through ALSB (Client-Client Proxy-Service) 2: The service then makes a call to another service through ALSB (Service-Client Proxy-Service) When the Service makes a call to another Service I get the following exception: [java] org.apache.axis2.AxisFault: BEA-38: Internal Server Error [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:194) [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:747) [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:201) [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:104) [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) [java] at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:1 05) [java] at org.apache.tools.ant.Task.perform(Task.java:348) [java] at org.apache.tools.ant.Target.execute(Target.java:357) [java] at org.apache.tools.ant.Target.performTasks(Target.java:385) [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) [java] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleChe ckExecutor.java:38) [java] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) [java] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416) [java] at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105) [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) [java] at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:1 05) [java] at org.apache.tools.ant.Task.perform(Task.java:348) [java] at org.apache.tools.ant.Target.execute(Target.java:357) [java] at org.apache.tools.ant.Target.performTasks(Target.java:385) [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) [java] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut or.java:41) [java] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) [java] at org.apache.tools.ant.Main.runBuild(Main.java:698) [java] at org.apache.tools.ant.Main.startAnt(Main.java:199) [java] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) [java] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) [java] Caused by: org.apache.axis2.AxisFault: BEA-38: Internal Server Error [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:308) [java] at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579 ) [java] at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508 ) [java] at org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceCl ient.java:95) [java] at sample.pojo.rpcclient.JaguarClient.main(Unknown Source) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217) [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152) [java] ... 32 more [java] --- Nested Exception --- [java] org.apache.axis2.AxisFault: BEA-38: Internal Server Error [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:308) [java] at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579 ) ===
Re: SOAPAction required?
dear all, pls don't create a new bug. SOAPACTION is REQUIRED for HTTP-Transport (empty or otherwise) and it is PROHIBITED for every other transport other than HTTP. Noone is required to USE it, but there is some standard-usage within .NET. Cheers, Wolfgang Krpelan --- Amila Suriarachchi [EMAIL PROTECTED] wrote: On 1/10/07, Justin Schoeman [EMAIL PROTECTED] wrote: OK - Appending the operation name to the URL does work, but I am not sure if .Net does this (I do not have .Net, just some recorded messages). From what I can read on the web, routing is supposed to occur via the first tag in the SOAP body (in this case a confirmCustomerReq message). Yes. This is the case if you have rpc/literal as your soap binding style. In rpc style it is supposed to wrap the input message from an element of which name equals to operation name. (see the WSDL spec). hence it is possible to determine the operation using the message. but in document/literal style (in this case) input message is directly send in the soapbody. And also it is possible to have the same input message for two different operations. Therefore it is not possible to determine the operation from the first element. I realise this is a bit more complex, but it seems to be how it is supposed to be done, although the documentation is extremely vague on this point... -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disable Transfer-Encoding: chunked response
Hi, got nothing to do with axis nor with webservices as it is outside of soap:envelope Lookup http-protocol-messages. Cheers, Wolfgang Krpelan --- HHDirecto.Net [EMAIL PROTECTED] wrote: Hi, How can I disable Transfer-Encoding: chunked in the response of my axis 1.4 webservice? Thanks in advance __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Client hangs and server gets unavailable
A http-trace of the soap-message would be helpful.
(tcpmon)
Is the server configured to request authentication?
If so, which method?
Cheers
Wolfgang Krpelan
--- Jaliya Ekanayake [EMAIL PROTECTED] wrote:
Hi Nuno,
Can you please check the scenario with Axis only.
Then if it works add Sandesha module.
Please send us the results.
Are you using non-anonymous ReplyTo address for the
service invocation?
Thanks,
-Jaliya
- Original Message -
From: Nuno Rodrigues
To: axis-dev@ws.apache.org ;
sandesha-dev@ws.apache.org
Sent: Monday, September 11, 2006 8:09 AM
Subject: Client hangs and server gets unavailable
Hello all,
I'm using Axis2 and Sandesha2 and I'm having a
strange problem and I don't know if it's due to Axis
or due to Sandesha.
I have a client that wants to make 1 requests
but at the middle of all these requests (sometimes
it only makes 300 requests, other times it makes
700,1000,.) the server crashes and there's no more
availability from the server side. I must say that
the client doesn't throw any kind of exception.
If I browse to http://host:8080/axis2 everything
seems ok but if I click the listServices link I get:
HTTP Status 500 -
type Status report
message
description The server encountered an internal
error () that prevented
it from fulfilling this request.
Apache Tomcat/5.5.17
Looking at apache Logs I have:
(.)
INFO: Server startup in 4749 ms
(This is where the server hangs)
- I/O exception
(org.apache.commons.httpclient.NoHttpResponseException)
caught when processing request: The server
192.168.200.40 failed to respond
- Retrying request
- I/O exception (java.net.ConnectException) caught
when processing request: Connection refused
- Retrying request
- I/O exception (java.net.ConnectException) caught
when processing request: Connection refused
- Retrying request
(Down here is when I try to access the list
Services link)
- Servlet.service() for servlet jsp threw
exception
java.lang.NullPointerException
at
org.apache.jsp.axis2_002dweb.listServices_jsp._jspService(listServices_jsp.java:133)
(.)
- Error dispatching request
/axis2/services/listServices
java.lang.reflect.InvocationTargetException
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
(.)
The client code is:
//Generate Payload
OMFactory fac =
OMAbstractFactory.getOMFactory();
OMNamespace omNs =
fac.createOMNamespace(http://client.org/calculator2;,
calculator2);
payload = fac.createOMElement(add,
omNs);
rand1=(int)(Math.random()*100);
rand2=(int)(Math.random()*100);
// Send num1 num2 timestamp message id
payload.setText(rand1+ +rand2+ +
System.currentTimeMillis()+ +i);
if (i==NUM_REQUESTS-1)
clientOptions.setProperty(SandeshaClientConstants.LAST_MESSAGE,true);
// Async invocation
serviceClient.sendReceiveNonBlocking(payload,callback);
//Wait till the callback receives the
response.
while (!callback.isComplete()) {
Thread.sleep(1);
}
=== message truncated ===
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can I expose services of a new technology as web services?
Axis is open source, just do it! Cheers Wolfgang Krpelan --- Domenico Caputi [EMAIL PROTECTED] wrote: Hi, I have a new technology that I want expose with web services, using Axis. Web Services that I want expose is not a java class but is a particular technology that executes some process. Is it possible to extend Axis in this sense? Thanks, Domenico - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Isuru Suriarachchi wants to chat
I'm a little surprised. Google spams?? --- Isuru Suriarachchi [EMAIL PROTECTED] wrote: --- Isuru Suriarachchi wants to stay in better touch using some of Google's coolest new products. If you already have Gmail or Google Talk, visit: http://mail.google.com/mail/b-94e6dda450-1bfb8ea91f-f976d06989b2d5c7 You'll need to click this link to be able to chat with Isuru Suriarachchi. To get Gmail - a free email account from Google with over 2,600 megabytes of storage - and chat with Isuru Suriarachchi, visit: http://mail.google.com/mail/a-94e6dda450-1bfb8ea91f-f8946f09e4 Gmail offers: - Powerful spam protection - Built-in search for finding your messages and a helpful way of organizing emails into conversations - No pop-up ads or untargeted banners - just text ads and related information that are relevant to the content of your messages - Instant messaging capabilities right inside Gmail All this, and its yours for free. But wait, there's more! You can also get Google Talk: http://www.google.com/talk/ Its a small Windows* download that lets you make free calls to your friends through your computer. It's simple and clutter-free, and it works with any computer speaker and microphone. Gmail and Google Talk are still in beta. We're working hard to add new features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making our products even better! Thanks, The Google Team To learn more about Gmail and Google Talk, visit: http://mail.google.com/mail/help/about.html http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser). * Not a Windows user? No problem. You can also connect to the Google Talk service from any platform using third-party clients (http://www.google.com/talk/otherclients.html). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (AXIS2-986) WSDL2Java works for invalid WSDL
Hi, dont think so. Either the WSDL has been created by some faulty tool, in this case the error should be fixed there. Or it has been written by hand, then the author should have validated it by simply pushing some button. Methinks one has to draw the line somewhere. Cheers --- Keith Godwin Chapman (JIRA) [EMAIL PROTECTED] wrote: WSDL2Java works for invalid WSDL Key: AXIS2-986 URL: http://issues.apache.org/jira/browse/AXIS2-986 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 0.94 Reporter: Keith Godwin Chapman WSDL2Java works for invalid WSDL's instead of validating it and reporting an error. I tried using the WSDL2Java tool of axis 2 using the following WSDL's. Using the following valid WSDL it generates the java classes ?xml version=1.0 encoding=UTF-8 standalone=no? wsdl:definitions xmlns:ns1= http://org.apache.axis2/xsd; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/ xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:tns= http://org.apache.axis2/; targetNamespace= http://org.apache.axis2/; wsdl:types xs:schema xmlns:xs= http://www.w3.org/2001/XMLSchema; xmlns:ns1= http://org.apache.axis2/xsd; targetNamespace= http://org.apache.axis2/xsd; elementFormDefault=qualified attributeFormDefault=unqualified xs:element name=helloRequest xs:complexType xs:sequence xs:element type=xs:string name=param0/ /xs:sequence /xs:complexType /xs:element xs:element name=helloResponse xs:complexType xs:sequence xs:element type=xs:string name=return/ /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types wsdl:message name=helloRequestMessage wsdl:part name=part1 element=ns1:helloRequest/ /wsdl:message wsdl:message name=helloResponseMessage wsdl:part name=part1 element=ns1:helloResponse/ /wsdl:message wsdl:portType name=EchoServicePort wsdl:operation name=hello wsdl:input message=tns:helloRequestMessage/ wsdl:output message=tns:helloResponseMessage/ /wsdl:operation /wsdl:portType wsdl:binding name=EchoServiceBinding type=tns:EchoServicePort soap:binding transport= http://schemas.xmlsoap.org/soap/http style=document/ wsdl:operation name=hello soap:operation name=operation soapAction=hello style=document/ wsdl:input soap:body use=literal namespace=http://www.org.apache.axis2/ /wsdl:input wsdl:output soap:body use=literal namespace= http://www.org.apache.axis2/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=EchoService wsdl:port name=EchoServicePortType binding=tns:EchoServiceBinding soap:address location= http://127.0.0.1:8080/axis2/services/EchoService / /wsdl:port /wsdl:service /wsdl:definitions Then I deleted the message element corresponding to helloRequestMessage. Still it generates the classes for the following WSDL (with the helloRequestMessage element deleted) ?xml version=1.0 encoding=UTF-8 standalone=no? wsdl:definitions xmlns:ns1= http://org.apache.axis2/xsd; xmlns:xs= http://www.w3.org/2001/XMLSchema; xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; xmlns:tns=http://org.apache.axis2/; targetNamespace= http://org.apache.axis2/; wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ns1= http://org.apache.axis2/xsd targetNamespace=http://org.apache.axis2/xsd; elementFormDefault=qualified attributeFormDefault=unqualified xs:element name=helloRequest xs:complexType xs:sequence xs:element type=xs:string name=param0/ /xs:sequence /xs:complexType /xs:element xs:element name=helloResponse xs:complexType xs:sequence xs:element type=xs:string name=return/ /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types wsdl:message name=helloResponseMessage wsdl:part name=part1 element=ns1:helloResponse/ /wsdl:message wsdl:portType name=EchoServicePort wsdl:operation name=hello wsdl:input message=tns:helloRequestMessage/ wsdl:output message=tns:helloResponseMessage/ /wsdl:operation /wsdl:portType wsdl:binding name=EchoServiceBinding type=tns:EchoServicePort soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=hello soap:operation name=operation soapAction=hello style=document/ wsdl:input soap:body use=literal namespace= http://www.org.apache.axis2/ /wsdl:input
Re: Debug a web service invocation
Hi, very interesting, where can I find it?? Cheers, Wolfgang Krpelan --- Yueqiang [EMAIL PROTECTED] wrote: Hi All, We've developed a composite debugger for service invocations (based on axis 1.x), a web-scale debugger. It has following features: (1) Do not need always to turn on the debug conditional attribute when you inspect a service invocation; (2) Two levels to control a service invocation, message-level and source-level. The ml-debugging could control and interrupt the service invocation by issueing debug commands, and observe/update values of those fields in a message context and invoke its methods dynamically. When you want to debug a handler or provider in source-level, the handler can emigrate outside within an environment turning on the debug conditional attribute (another JVM). (3) The message-level debugging work on self-check and proactive modes. This means the debugging does not interfere other service invocations. It only employs to debug the invocation you want to. Not like the log and monitor in axis 1.x, which work on a possive mode. (4) It could support any JDI-based debuggers for dource-level debug. The composite debugger is a new approach to debugging service invocations other than the existing log and monitoring ways Any way the web-scale debugging is a intersting topic. Thanks Qaing Yue __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re : sending soap messages asynchronously
Hi axis 1, no axis 2, yes Cheers, --- Phani Sekhar [EMAIL PROTECTED] wrote: Hi all, We are implementing NETCONF on SOAP over HTTP. We are using Axis. We require the Axis web service to send some soap messages asynchronously to the Axis client without any initiation. Ofcourse for the first time, we can register the client at the server. We are trying to implement something similar to the snmp traps/notifications. Is is possible to do this using Axis Does Axis support asynchronous messaging??? Please help me. Thanks in advance Phani Sekhar -Original Message- From: Phani Sekhar [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 21, 2006 12:47 PM To: axis-user@ws.apache.org Subject: sending asynchronous soap messages Hi, Is there any way to send asynchronous soap messages from a webservice in Axis, something similar to snmp notifications ??? Thanks in Advance Phani Sekhar __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re : sending soap messages asynchronously
Sry, without initiation? Dont think so. Cheers --- Phani Sekhar [EMAIL PROTECTED] wrote: Hi all, We are implementing NETCONF on SOAP over HTTP. We are using Axis. We require the Axis web service to send some soap messages asynchronously to the Axis client without any initiation. Ofcourse for the first time, we can register the client at the server. We are trying to implement something similar to the snmp traps/notifications. Is is possible to do this using Axis Does Axis support asynchronous messaging??? Please help me. Thanks in advance Phani Sekhar -Original Message- From: Phani Sekhar [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 21, 2006 12:47 PM To: axis-user@ws.apache.org Subject: sending asynchronous soap messages Hi, Is there any way to send asynchronous soap messages from a webservice in Axis, something similar to snmp notifications ??? Thanks in Advance Phani Sekhar __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Duplicate namespace definitions are not removed
Hi, this seems a minor issue, dwarfed by the overall soap-overhead and compensated for by faster dezerialisation. Cheers, --- Benjamin Bender [EMAIL PROTECTED] wrote: Hi I'm using Axis2 for Java and I try to send messages with the following content and the following style between the server and a client soapenv:Header xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; wsa:EndpointReference wsa:Address http://localhost:5988/root/cimv2:Linux_OperatingSystem /wsa:Address wsa:ReferenceParameters xmlns:linux_os=http://localhost:8080/WSDM/Linux_OperatingSystem.xsd; linux_os:CreationClassName Linux_OperatingSystem /linux_os:CreationClassName linux_os:CSCreationClassName Linux_ComputerSystem /linux_os:CSCreationClassName linux_os:CSNamelocalhost.localdomain/linux_os:CSName linux_os:Namelocalhost.localdomain/linux_os:Name /wsa:ReferenceParameters /wsa:EndpointReference ... /soapenv:Header But if I try to construct this EndpointReference or any other OMElement then namespace definitions that are defined a second time in a subelement are not removed from the subelements. I can only construct the following: soapenv:Header xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; wsa:EndpointReference wsa:Address http://localhost:5988/root/cimv2:Linux_OperatingSystem /wsa:Address wsa:ReferenceParameters xmlns:linux_os=http://localhost:8080/WSDM/Linux_OperatingSystem.xsd; linux_os:CreationClassName xmlns:linux_os=http://localhost:8080/WSDM/Linux_OperatingSystem.xsd; Linux_OperatingSystem /linux_os:CreationClassName linux_os:CSCreationClassName xmlns:linux_os=http://localhost:8080/WSDM/Linux_OperatingSystem.xsd; Linux_ComputerSystem /linux_os:CSCreationClassName linux_os:CSName xmlns:linux_os=http://localhost:8080/WSDM/Linux_OperatingSystem.xsd; localhost.localdomain /linux_os:CSName linux_os:Name xmlns:linux_os=http://localhost:8080/WSDM/Linux_OperatingSystem.xsd; localhost.localdomain /linux_os:Name /wsa:ReferenceParameters /wsa:EndpointReference ... /soapenv:Header My problem is that the xmlns:linux_os is still defined in every subelement of wsa:ReferenceParameters although xmlns:linux_os is already defined in wsa:ReferenceParameters. This makes the message larger than it has to be. Can anybody tell me how I can build a message like in the first sample or is it a bug in Axis that the namespace definitions of the subelements are not removed. I don't have the problem with the definition of the xmlns:wsa, here the namespace definition is removed in the subelements. The problem appears only if an OMElement declares more than one namespace. Any hint is welcome. Thanks, Ben __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Can I add something to the Http header?
Hi cao, the SOAPAction-Header can hold arbitrary text (if you're using AXIS both Client and Server) For other HTTP-Headers, you'll have to use some HTTPClient. Cheers, --- xiangyu cao [EMAIL PROTECTED] wrote: If the SOAP call is over HTTP, I wonder if I can put some information in the HTTP header before I make the SOAP call. If yes, how? Any help is appreciated! Thanks a lot! A new guy of Axis: Shawn __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
