Yogesh Dhake is out of the office.
I will be out of the office starting 12/09/2009 and will not return until 12/29/2009. I will respond to your message when I return. Please contact Alex Okrainsky 201-626-9189 or Colin Huang 201-626-9043 for urgent issue. == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (Mizuho). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information. If you have any questions, or if you no longer wish to receive e-mail in accordance with Japanese Act on Regulation of the Transmission of Specified Electronic Mail, please contact the sender of this e-mail. お問い合わせまたは特定電子メール法に 基づく送信停止のご要望等は、本電子メールの送信者にその旨ご連絡ください。
Re: MTOM file upload webservice
I hope your issue is you don't have field for passing for attachementID/mime header .But in MTOM you dont need it.. Have you tried MTOM and SWA samples with Axis source? If you are using MTOM AttachmentType attachmentRequest = param0.getAttachmentRequest(); Base64Binary binaryData = attachmentRequest.getBinaryData(); DataHandler dataHandler = binaryData.getBase64Binary(); File file = new File( attachmentRequest.getFileName()); FileOutputStream fileOutputStream = new FileOutputStream(file); dataHandler.writeTo(fileOutputStream); if using SWA. ( you need attachment ID here..) MessageContext msgCtx = MessageContext.getCurrentMessageContext(); Attachments attachment = msgCtx.getAttachmentMap(); DataHandler dataHandler = attachment.getDataHandler(attchmentID); File file = new File( name); FileOutputStream fileOutputStream = new FileOutputStream(file); dataHandler.writeTo(fileOutputStream); Regards Yogesh Dhake Attharkar, Asmita aatth...@telcordia.com 02/12/2009 03:41 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org axis-user@ws.apache.org cc Subject MTOM file upload webservice Hi, I am trying to write a web service which uploads a file so that it can be retrieved by the client. Most of the articles that I have read talks about file upload web service using SwA. My Web service is uploading the file with no issues and adding it to outMsgContext (like the eg shown for SwA) but I am having problem receiving it on the client side. My web service doesn’t contain any argument which stands for the attachment/data Handler). Any help is appreciated. Thanks, Asmita (Tel) 732-699-4657 | 4B566 | Telcordia Technologies | Piscataway NJ 08854 == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (Mizuho). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information. If you have any questions, or if you no longer wish to receive e-mail in accordance with Japanese Act on Regulation of the Transmission of Specified Electronic Mail, please contact the sender of this e-mail. お問い合わせまたは特定電子メール法に 基づく送信停止のご要望等は、本電子メールの送信者にその旨ご連絡ください。
Axis2 SoapWithAttachement issue extra new line when attachment of specific size.
Hi All I am using Axis 1.3and seen a weird behavior with SWA feature. It look like when my size is of 849 bytes a additional /r/n is added to message. If I send attachment of 848 bytes I do receive of exactly 848 bytes . But if I send attachment of 849 bytes. I receive 851 bytes. Way I receive Attachment MessageContext msgCtx= MessageContext.getCurrentMessageContext(); AttachmentsaxiomAttachment = msgCtx.getAttachmentMap(); DataHandlerfileAttachmentDataHandler = axiomAttachment.getDataHandler(SWAAttachmentId); byteArrayOutputStream = new ByteArrayOutputStream(); fileAttachmentDataHandler.writeTo(byteArrayOutputStream); logger.debug( Data received length: + data.length); My Question 1) Is this a know issue in Axis? 2) Have any one seen this kind of behavior earlier. Or it could be just me due to way I have done coding. Thanking you regards Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (Mizuho). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information. If you have any questions, or if you no longer wish to receive e-mail in accordance with Japanese Act on Regulation of the Transmission of Specified Electronic Mail, please contact the sender of this e-mail. お問い合わせまたは特定電子メール法に 基づく送信停止のご要望等は、本電子メールの送信者にその旨ご連絡ください。
Re: Axis2 - MTOM Sample error
1)Try putting attached xmime.xsd local in you wsdl folder 2) put following import statement in wsdl or schema xsd:import namespace=http://www.w3.org/2005/05/xmlmime; schemaLocation=xmlmime.xsd / I hope this will work for you. Else you need to enable proxy setting in JVM regards Yogesh PR, Rajesh (GE Infra, Energy, Non-GE) [EMAIL PROTECTED] 05/01/2008 05:09 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Axis2 - MTOM Sample error Hi all, am getting the following error, when i try to build the mtom sample which comes with Axis2 - Version 1.3 Exception in thread main java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: Could not load resource xmime.xsd (network downloads disabled). at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:103) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:79) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:28) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:22) Caused by: org.apache.xmlbeans.XmlException: error: Could not load resource xmime.xsd (network downloads disabled). at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:69) ... 3 more Please help me. This is the base for a new project am building Thanks Rajesh == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information. xmlmime.xsd Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Soap with attachment with Sandesha2 in Axis2
Hi All Sorry confusing title earlier . My Query is regarding Sandesha2 usage I am already have running implementation of WS generated from WSDL. and Client use OperationClient instead of ServiceClient as I need to send Soap with attachment messages. Now I am trying to add reliability for my communication using rampart. I just wondering is it possible to do this. 1) I seen sample provided by client . All are written using ServiceClient and Sandesha api does not have waitUntilSequenceCompleted which take OperationalClient. Can we use Axis OperationClient api to send invoke WS with rampart 2) Any WSDL changes required for this ? ( MY WS implementation code depend on this ) 3) Any documentation or sample link will be really helpful Thanks for your time regards Yogesh Dhake [EMAIL PROTECTED] 04/07/2008 05:30 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org, [EMAIL PROTECTED] cc Subject Soap with attachment with Rampart in Axis2 == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
Soap with attachment with Rampart in Axis2
Hi All I am already have running implementation of WS generated from WSDL. and Client use OperationClient instead of ServiceClient as I need to send Soap with attachment messages. Now I am trying to add reliability for my communication using rampart. I just wondering is it possible to do this. 1) I seen sample provided by client . All are written using ServiceClient and Sandesha api does not have waitUntilSequenceCompleted which take OperationalClient. Can we use Axis OperationClient api to send invoke WS with rampart 2) Any WSDL changes required for this ? ( MY WS implementation code depend on this ) 3) Any documentation or sample link will be really helpful Thanks for your time in reading this regards Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
Re: Using SWA with ADB in axis2
Can you place TCPMON inbetween and show us what kind of request you send and receive. regards Yogesh ndthuy [EMAIL PROTECTED] 04/02/2008 10:05 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Using SWA with ADB in axis2 I were trying the same method call when I tried to download the file then I received the exception. I was able to see the attachment but I couldn't retrieve it. Thanks. ndthuy wrote: Hi Thilina, After taking a look at those articles, I am able to upload the file without any problem. But when I download the file, I received this error: Exception in thread main org.apache.axiom.om.OMException: javax.mail.MessagingException: Error in input stream; nested exception is: java.io.IOException: Attempted read on closed stream. at org.apache.axiom.attachments.Attachments.getPart(Attachments.java:602) at org.apache.axiom.attachments.Attachments.getNextPartDataHandler(Attachments.java:462) at org.apache.axiom.attachments.Attachments.getDataHandler(Attachments.java:278) at org.apache.axis2.context.MessageContext.getAttachment(MessageContext.java:1623) at com.cvg.ap.service.publicservices.impl.APContentManagementServicesStub.fetchContentFile(APContentManagementServicesStub.java:810) at com.cvg.ap.service.publicservices.impl.APContentManagementServicesImpl.fetchContentFile(APContentManagementServicesImpl.java:256) at com.cvg.ap.service.publicservices.impl.APContentManagementServicesImpl.main(APContentManagementServicesImpl.java:463) Caused by: javax.mail.MessagingException: Error in input stream; nested exception is: java.io.IOException: Attempted read on closed stream. at javax.mail.internet.InternetHeaders.load(InternetHeaders.java:142) at javax.mail.internet.InternetHeaders.init(InternetHeaders.java:93) at javax.mail.internet.MimeBodyPart.init(MimeBodyPart.java:124) at org.apache.axiom.attachments.PartOnMemory.init(PartOnMemory.java:34) at org.apache.axiom.attachments.Attachments.getPart(Attachments.java:598) ... 6 more This is the soap message when I upload and download: /soapenv:Envelope--MIMEBoundaryurn_uuid_1ADD9EC725995A3FD11206998815387Content-Type: application/octet-streamContent-Transfer-Encoding: binaryContent-ID: urn:uuid:1ADD9EC725995A3FD11206998814743/*Pogue.cs - Custom Rogue class3a--MIMEBoundaryurn_uuid_1ADD9EC725995A3FD11206998815387--0 This is soap message when I download: --MIMEBoundaryurn_uuid_5042108D598DCCE8AE1206999131913 7e8 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: urn:uuid:5042108D598DCCE8AE1206999117974/*Pogue.cs - Custom Rogue class 38 --MIMEBoundaryurn_uuid_5042108D598DCCE8AE1206999131913 2 -- 0 Do you think it is because the way it prepares the SOAP message on server side ? Thanks for your help. Thanks. Thilina Gunarathne wrote: Hi, I would have a WSDL with a string return field (or a complex type containing a string element) and would assign the content-id to that string. You can have a look at the following articles to figure out how to add the attachment in the service implementation class.. http://wso2.org/library/1675 http://wso2.org/library/1148 String contentId = messageContext.addAttachment(dataHandler); thanks, Thilina On Mon, Mar 31, 2008 at 11:14 AM, ndthuy [EMAIL PROTECTED] wrote: Thanks Thilina, I was able to modify according to your suggestion to upload the file using ADB with SwA. But for the dowload using ADB with SwA, how do we modify the SOAP message to attach the binary data ? Do we have to modify in invokeBusinessLogic(...) function ? Thanks. Thilina Gunarathne wrote: Hi, You cannot generate WSDL with the knowledge of SwA in them.. AFAIK there isn't a standard way to mention SwA attachments in WSDL.. ADB does not support SwA directly.. What you can do in the server side is to have your method signature take in an String which will be the content-id of the attachment, then retrieve your attachment from the messageContext manually using it... Have a look at [1] [2].. Your following method will result in an MTOM WSDL, where dataHandler will get bound to an base64Binary element. addContentFile(String userID, String password, String serviceID, DataHandler dataHandler, String relAddFilepathName, String contentType, String source) thanks, Thilina [1] Using SOAP with Attachments in Apache Axis2 - http://wso2.org/library/1148 [2] Downloading a Binary File from a Web Service using Axis2 and SOAP with Attachments - http://wso2.org/library/1675
can we pass xmlnode.
Hi We have implemented axis2 web service which take xml structure. While sending parameters to Web service I create structured OMElements as per my schema and send across. This works perfect. My question is 1) Can I add complex xml node to any sub element. of type xsd:anytype. 2) I need to send xml complex data structure element to my axis2 web service. My webservice will not use it but for doing its work but send back same xml structure 3) We don't want to analyze what is in that complex node. Just should go there and cached. 4) While returning back it may goto either of two cluster web application. We want to some polling job using ws where onwakeup event we want to send back this appcontext to identify which polling job is triggerd. if any thing is not clear please let me know. regard Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
Re: Axis2.1.2 MTOM problem with large files
Hi Can you be more specific with exception stack trace. What kind of logic you implementing? If you are reading file in memory for processing then you may have this issue due to available heap size regard yogesh Srihari [EMAIL PROTECTED] 10/31/2007 02:10 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Axis2.1.2 MTOM problem with large files Hi, I am using Axis2.1.2 and I am trying to upload 10mb file. I can upload the file to the server and the server also gets the file in the temporary directory specified. but before it starts my implementation logic the server throws as out of memory error. Do anybody have a similar issue. I am using MTOM on both the server and the client side. Thanks Regards, Srihari == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
Re: Best way to realize stateful servicesarchitecturewithmassivedata?
Steps similar to MTOM sample with file caching enabled. Received dataStream is loaded in XML object for further transformation. regards Yogesh robert lazarski [EMAIL PROTECTED] 10/22/2007 05:17 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Best way to realize stateful servicesarchitecturewithmassivedata? That's pretty kool. Did you use any streaming to avoid putting the data in memory and building the tree? Or did you just more or less follow the same steps in the mtom tutorial? Robert On 10/22/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi We were in similar situation we were planning to transfer 1GB file as SOAP as attachment. 1) Axis2 give pretty good support using MTOM and SWA for transferring any size file. 1GB file transferred in 67sec on local network. File caching feature is great. 2) But it is not good idea to transfer SOAP with such large attachment. We also hit some our app server service bus handling limitation. So we decided to process data in chunk. We get file data in chunk and till we get all data correctly we dont send confirm to end point (which really delete file on source system . End of our getFile operation / confirming file received at server ). Same way on reverse we put data in chunk to some temp file on destination endpoint. after placing all data at end we rename it to required file. Let me know your thoughts Regards Yogesh Dhake Walker, Jeff [EMAIL PROTECTED] 10/22/2007 11:46 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject RE: Best way to realize stateful servicesarchitecturewithmassivedata? Michele, I'm not sure JMS is a viable alternative if large amounts of data are transferred. That statement would imply there is some sort of size cutoff. There isn't. Just remember, that with JMS you can have persisted queues and then all of that data would have to be stored temporarily. Personally, I think some of the lessons from JMS (message queuing in general) can be applied to web services; keep the msgs as small as possible. Large data transfer (across the network) is a serious problem. There is no easy solution that I've seen. Having said that, there are quite a few posters who have used attachments with their web services. I have used the older DIME format, but other posters have used the newer MTOM. I would be interested to see what their performance was like, with large files (ie. around a Gigabyte, say). Since MTOM chunks up the files, transferring any sized file should theoretically be possible. Does anyone have any opinions on using MTOM for transferring Gb and and multi-Gb files?? -jeff -Original Message- From: Michele Mazzucco [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 11:21 AM To: axis-user@ws.apache.org Subject: RE: Best way to realize stateful servicesarchitecturewithmassivedata? Jeff, I mentioned JMS as possible choice if one has to transfer large amount of data since it is asynchronous. Michele On Mon, 2007-10-22 at 11:10 -0400, Walker, Jeff wrote: You mentioned WS over JMS. Again, added delay, since another protocol layer is employed. - 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] == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (Mizuho). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel
RE: Best way to realize stateful servicesarchitecturewithmassivedata?
Hi We were in similar situation we were planning to transfer 1GB file as SOAP as attachment. 1) Axis2 give pretty good support using MTOM and SWA for transferring any size file. 1GB file transferred in 67sec on local network. File caching feature is great. 2) But it is not good idea to transfer SOAP with such large attachment. We also hit some our app server service bus handling limitation. So we decided to process data in chunk. We get file data in chunk and till we get all data correctly we dont send confirm to end point (which really delete file on source system . End of our getFile operation / confirming file received at server ). Same way on reverse we put data in chunk to some temp file on destination endpoint. after placing all data at end we rename it to required file. Let me know your thoughts Regards Yogesh Dhake Walker, Jeff [EMAIL PROTECTED] 10/22/2007 11:46 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject RE: Best way to realize stateful servicesarchitecturewithmassivedata? Michele, I'm not sure JMS is a viable alternative if large amounts of data are transferred. That statement would imply there is some sort of size cutoff. There isn't. Just remember, that with JMS you can have persisted queues and then all of that data would have to be stored temporarily. Personally, I think some of the lessons from JMS (message queuing in general) can be applied to web services; keep the msgs as small as possible. Large data transfer (across the network) is a serious problem. There is no easy solution that I've seen. Having said that, there are quite a few posters who have used attachments with their web services. I have used the older DIME format, but other posters have used the newer MTOM. I would be interested to see what their performance was like, with large files (ie. around a Gigabyte, say). Since MTOM chunks up the files, transferring any sized file should theoretically be possible. Does anyone have any opinions on using MTOM for transferring Gb and and multi-Gb files?? -jeff -Original Message- From: Michele Mazzucco [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 11:21 AM To: axis-user@ws.apache.org Subject: RE: Best way to realize stateful servicesarchitecturewithmassivedata? Jeff, I mentioned JMS as possible choice if one has to transfer large amount of data since it is asynchronous. Michele On Mon, 2007-10-22 at 11:10 -0400, Walker, Jeff wrote: You mentioned WS over JMS. Again, added delay, since another protocol layer is employed. - 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] == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
Re: Problems with Schemas and WSDL in Axis2
Hi I did same successfully some time back. xsd:schema xmlns=http://schemas.xmlsoap.org/wsdl/; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace= http://mizuho.com/emis/ep/paraminfo; xsd:include schemaLocation=CommandInfo.xsd/ /xsd:schema Use similar include to include you xsd in WSDL and have attribute name qualified in XSD. Keep xsd in same folder. regards Yogesh Matthew Fadoul [EMAIL PROTECTED] 10/18/2007 04:06 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Problems with Schemas and WSDL in Axis2 Hello all, I’m having trouble using my own schemas in WSDL. Part of it may be related to the Axis2 code generation. So, I’ve made my own “HelloWorld” example. Here’s my process: 1) Make WSDL file (attached) 2) Process with Axis2 code generation to build client/server code. Fill in a little of the skeleton code. 3) Build inside Eclipse using Ant 4) Package with the Axis2 Service Archiver. I’ve attached my WSDL and Schema. The schema has little more than a type definition based on “xs:string”. I’ve placed my XSD file on a local server. This is reflected in the attached WSDL here: xs:import namespace=HW schemaLocation= http://strawberry/schema/HelloWorldSimple.xsd; / By the time the service gets placed on the Axis server, the to the schema in “HelloWorldExternalSchemaService?wsdl” becomes: xs:import namespace=HW schemaLocation= HelloWorldExternalSchemaService?xsd=http://strawberry/schema/HelloWorldSimple.xsd / Unfortunately, Axis can’t seem to resolve my schema with the “xsd” option. Because of this, the schema and all of its types are unresolved. As a side note, I’ve also toyed with locale schema (i.e. the XSD file is in the same directory as the WSDL file), though I haven’t had much success with that route either. Questions. Are there: Any ideas or advice for integrating schemas with WSDL? Any ideas why the code generator is changing the schema location? Any glaring mistakes (e.g. namespace problems or DOC/RPC stuff) in my WSDL/XSD? Thank you! Matt- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information. HelloWorldSimple.xsd Description: Binary data HelloWorldExternalSchema.wsdl Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: java client from wsdl
Try looking MTOM sample in axis. replace your wsdl here.
!-- Generate Client --
target name=generate.client
java classname=org.apache.axis2.wsdl.WSDL2Java
arg value=-uri /
arg value=resources/MTOMSample.wsdl /
arg value=-p /
arg value=-ap /
arg value=sample.mtom.service /
arg value=-o /
arg value=${client.dir} /
classpath refid=class.path /
/java
copy file=${client.path}
tofile=${client.dir}/${client.path} overwrite=true /
mkdir dir=${client.classes.dir} /
!-- Compile client --
javac srcdir=${client.dir}/src
destdir=${client.classes.dir}
classpath refid=class.path /
/javac
/target
Sudhir Sharma [EMAIL PROTECTED]
10/18/2007 10:12 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
java client from wsdl
Hi,
I am new to web services and axis. I have a webservice in .NET that is
into production. I need to make a java client from the wsdl of that web
service.can anyone help me how to automaticaly generate a java client from
the wsdl.I am using axis 1.4 and Tomcat 5.0
Thanx in advance.
Thanks Best Regards,
Sudhir Sharma
==
This transmittal and any attachments may contain confidential, privileged or
sensitive information and is solely for the use of the intended recipient. If
you are not the intended recipient, you are hereby notified that you have
received this transmittal and any attachments in error and any review,
dissemination, distribution or copying thereof is strictly prohibited. If you
have received this transmittal and any attachments in error please notify the
sender and immediately destroy the message and all its attachments. Any
opinions herein expressed may be those of the author and not necessarily of
Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA
Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho
accepts no responsibility for the accuracy or completeness of any information
herein contained.
E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is
a registered U.S. broker-dealer and the entity through which Mizuho generally
conducts its investment banking, capital markets, and securities business in
the United States) is electronically archived and recorded and is subject to
review and monitoring by and/or disclosure to persons other than the recipient,
including (but not limited to) Mizuho Securities USA Inc. supervisory
personnel. Such communications may be produced to regulatory authorities or
others with legal rights to the information.
Re: Axis2 SWA client communicating Axis2 MTOM service
:checksum121/ns1:checksum /ns1:attachment ns1:responseStatustrue/ns1:responseStatus ns1:hasAttachmenttrue/ns1:hasAttachment /ns1:response ns1:EPInfo ns1:node ns1:namesasdf/ns1:name ns1:id12/ns1:id /ns1:node ns1:system ns1:namesasdf/ns1:name ns1:id12/ns1:id /ns1:system /ns1:EPInfo ns1:currentInterface ns1:namesdfa/ns1:name ns1:id12/ns1:id /ns1:currentInterface /ns1:getFileResponse /soapenv:Body /soapenv:Envelope--MIME_BoundaryContent-Type: text/plainContent-Transfer-Encoding: binaryContent-ID: 1.urn:uuid:[EMAIL PROTECTED]Test Data created by 12:00 at 10/4/2007 to test attachment at ALSB0015--MIME_Boundary-- Exception stack trace. I am getting. java.lang.ClassCastException: org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder at com.mizuho.emis.ep.EMISEPServiceStub$Base64Binary$Factory.parse(EMISEPServiceStub.java:2228) at com.mizuho.emis.ep.EMISEPServiceStub$Attachment$Factory.parse(EMISEPServiceStub.java:6121) at com.mizuho.emis.ep.EMISEPServiceStub$ResponseData$Factory.parse(EMISEPServiceStub.java:3595) at com.mizuho.emis.ep.EMISEPServiceStub$CommandInfo$Factory.parse(EMISEPServiceStub.java:4698) at com.mizuho.emis.ep.EMISEPServiceStub$GetFileResponse$Factory.parse(EMISEPServiceStub.java:4003) at com.mizuho.emis.ep.EMISEPServiceStub.fromOM(EMISEPServiceStub.java:1684) at com.mizuho.emis.ep.EMISEPServiceStub.getFile(EMISEPServiceStub.java:1221) at com.mizuho.yogesh.WebServiceControlImpl.getFile(WebServiceControlImpl.java:89) at com.mizuho.yogesh.NoWeblogic.webServiceControlGetFile(NoWeblogic.java:80) at com.mizuho.yogesh.NoWeblogic.main(NoWeblogic.java:42) org.apache.axis2.AxisFault: org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at com.mizuho.emis.ep.EMISEPServiceStub.fromOM(EMISEPServiceStub.java:1752) at com.mizuho.emis.ep.EMISEPServiceStub.getFile(EMISEPServiceStub.java:1221) Thanks Regards Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (Mizuho). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information. -- Thilina Gunarathne - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 SWA client communicating Axis2 MTOM service
Regards Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
Re: Axis2 SWA client communicating Axis2 MTOM service
/soapenv:Envelope--MIME_BoundaryContent-Type: text/plainContent-Transfer-Encoding: binaryContent-ID: 1.urn:uuid:[EMAIL PROTECTED]Test Data created by 12:00 at 10/4/2007 to test attachment at ALSB0015--MIME_Boundary-- Exception stack trace. I am getting. java.lang.ClassCastException: org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder at com.mizuho.emis.ep.EMISEPServiceStub$Base64Binary$Factory.parse(EMISEPServiceStub.java:2228) at com.mizuho.emis.ep.EMISEPServiceStub$Attachment$Factory.parse(EMISEPServiceStub.java:6121) at com.mizuho.emis.ep.EMISEPServiceStub$ResponseData$Factory.parse(EMISEPServiceStub.java:3595) at com.mizuho.emis.ep.EMISEPServiceStub$CommandInfo$Factory.parse(EMISEPServiceStub.java:4698) at com.mizuho.emis.ep.EMISEPServiceStub$GetFileResponse$Factory.parse(EMISEPServiceStub.java:4003) at com.mizuho.emis.ep.EMISEPServiceStub.fromOM(EMISEPServiceStub.java:1684) at com.mizuho.emis.ep.EMISEPServiceStub.getFile(EMISEPServiceStub.java:1221) at com.mizuho.yogesh.WebServiceControlImpl.getFile(WebServiceControlImpl.java:89) at com.mizuho.yogesh.NoWeblogic.webServiceControlGetFile(NoWeblogic.java:80) at com.mizuho.yogesh.NoWeblogic.main(NoWeblogic.java:42) org.apache.axis2.AxisFault: org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at com.mizuho.emis.ep.EMISEPServiceStub.fromOM(EMISEPServiceStub.java:1752) at com.mizuho.emis.ep.EMISEPServiceStub.getFile(EMISEPServiceStub.java:1221) Thanks Regards Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (Mizuho). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information. -- Thilina Gunarathne - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] ADBException: Unexpected subelement contentType
ns1:fileNametest1Meg/ns1:fileName
ns1:folderNamec:\TEMP/ns1:folderName
ns1:scriptName*/ns1:scriptName
ns1:attachment
ns1:size1231/ns1:size
ns1:checksum1231/ns1:checksum
/ns1:attachment
/ns1:FileDataInfo
/ns1:parameters
ns1:response
ns1:attachment
ns1:binaryNode
xop:Include
href=cid:1.urn:uuid:[EMAIL PROTECTED]
xmlns:xop=http://www.w3.org/2004/08/xop/include; /
/ns1:binaryNode
ns1:size121/ns1:size
ns1:checksum121/ns1:checksum
/ns1:attachment
ns1:responseStatustrue/ns1:responseStatus
ns1:hasAttachmenttrue/ns1:hasAttachment
/ns1:response
ns1:EPInfo
ns1:node
ns1:namesasdf/ns1:name
ns1:id12/ns1:id
/ns1:node
ns1:system
ns1:namesasdf/ns1:name
ns1:id12/ns1:id
/ns1:system
/ns1:EPInfo
ns1:currentInterface
ns1:namesdfa/ns1:name
ns1:id12/ns1:id
/ns1:currentInterface
/ns1:getFileResponse
/soapenv:Body
/soapenv:Envelope
38
--MIMEBoundaryurn_uuid_BEA3504621155EBAFD1191441357256
2000
Content-Type: text/plain
Content-Transfer-Encoding: binary
Content-ID:
1.urn:uuid:[EMAIL PROTECTED]Test Data
.Test
Data
v
Test Data
.
vTest Data
.Test
Data
.Test
Data
DATA Deleted ..
Test Data
.
38
--MIMEBoundaryurn_uuid_BEA3504621155EBAFD1191441357256
2
--
0
Regard
Yogesh Dhake
Amila Suriarachchi [EMAIL PROTECTED]
10/04/2007 01:36 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Re: [AXIS2] ADBException: Unexpected subelement contentType
Can you send your wsdl? and your request and responses.
have you enabled the MTOM or not?
Amila.
On 10/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi
I am bit new to Axis2 but I worked on SOAP / MTOM.I think element type
need to be xmime:base64Binary as shown in axis2 sample.
Etienne if you are planning to use MTOM then Axis sample on MTOM is quite
useful. See how you can define your content element . I was succcessful
in transferring file upto 1 GB in 67 sec using MTOM.
Let me know if you need more help
Regards
Yogesh
Ajith Ranabahu [EMAIL PROTECTED]
10/03/2007 02:48 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Re: [AXIS2] ADBException: Unexpected subelement contentType
Hmm..
It could be a bug. I'm thinking that since we have special treatment
for base64Binary, the problem could be that. Can you try putting the
base64Binary type as the last element of the sequence ? (I have a
feeling that the issue could be with something immediately following
the base64bin type)
Ajith
On 10/3/07, Etienne Giraudy [EMAIL PROTECTED] wrote:
Hi,
I'm working on migrating a web service client from axis 1.4 to axis2
1.3.
With axis2 I have an issue with a complex type containing a
base64Binary element:
xsd:complexType name=BinaryFile
xsd:sequence
xsd:element minOccurs=0 name=content nillable=true
type=xsd:base64Binary/
xsd:element minOccurs=0 name=contentType nillable=true
type=xsd:string/
xsd:element minOccurs=0 name=id type=xsd:int/
xsd:element minOccurs=0 name=name nillable=true
type=xsd:string/
/xsd:sequence
/xsd:complexType
When the client fails with the following exception;
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement contentType
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
com.foo.MyServiceStub.fromOM(KnowledgeBaseServiceStub.java:5805)
For testing, we did removed the base64binary element from the response
and the exception disappeared.
Is there a known issue in axis2 1.3 with that kind of complex types?
The client is generated from the wsdl with:
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath/
arg value=-uri/
arg file=${wsdl.path}/MyService.wsdl/
arg value=-o
Re: Issue with Axis2 MTOM client
Hi Mr Thilina Thanks for answering query. My Issue got resolved when I upgraded to axis2 1.3 . I was using axis2.1.1 on tomcat. Summary. 1) Axis2 can work as MTOM client or server. 2) For memory optimization we can do file caching on both sides. Thanks again. regards Yogesh Dhake Thilina Gunarathne [EMAIL PROTECTED] 10/02/2007 01:23 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Issue with Axis2 MTOM client Hi, When I use AXIS2 generated stub as clients to MTOM service I see my .att file grow indefinitely with following character get added. ÿÿÿ. And grow continuously till run out of space. Which Axis2 version are you using... There was an issue where Axis2 did not wrote the terminating MIME boundary, when deployed in tomcat resulting in the above indefinite file. IIRC we fixed this in Axis2 1.2.. Does Axis2 support as MTOM client. ? Yes. I don't suspect my WSDL element post your WSDL If possible.. definition has problem as same element works fine when I do reverse operation i.e. put file. I don't see any MTOM sample which receives MTOM attachment using axis2 . Is this a bug or axis2 does not support file caching as client. In the above you have mentioned that a temporary .att file is generated.. That means file caching is working... thanks, Thilina I am enabling MTOM on client side by following statements. EMISEPServiceStub serviceStub = new EMISEPServiceStub(); // Enable MTOM in the client side serviceStub._getServiceClient().getOptions().setProperty( Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE); // Increase the time out when sending large attachments serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds( 1); serviceStub._getServiceClient().getOptions().setProperty(Constants.Configuration.CACHE_ATTACHMENTS, Constants.VALUE_TRUE); serviceStub._getServiceClient().getOptions().setProperty(Constants.Configuration.ATTACHMENT_TEMP_DIR, C:\\TEMP\\cache); serviceStub._getServiceClient().getOptions().setProperty(Constants.Configuration.FILE_SIZE_THRESHOLD, 4000); Please let me know if you need more details for analysing this.? Thanks to all regards Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (Mizuho). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information. -- Thilina Gunarathne - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] ADBException: Unexpected subelement contentType
Hi
I am bit new to Axis2 but I worked on SOAP / MTOM.I think element type
need to be xmime:base64Binary as shown in axis2 sample.
Etienne if you are planning to use MTOM then Axis sample on MTOM is quite
useful. See how you can define your content element . I was succcessful
in transferring file upto 1 GB in 67 sec using MTOM.
Let me know if you need more help
Regards
Yogesh
Ajith Ranabahu [EMAIL PROTECTED]
10/03/2007 02:48 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Re: [AXIS2] ADBException: Unexpected subelement contentType
Hmm..
It could be a bug. I'm thinking that since we have special treatment
for base64Binary, the problem could be that. Can you try putting the
base64Binary type as the last element of the sequence ? (I have a
feeling that the issue could be with something immediately following
the base64bin type)
Ajith
On 10/3/07, Etienne Giraudy [EMAIL PROTECTED] wrote:
Hi,
I'm working on migrating a web service client from axis 1.4 to axis2
1.3.
With axis2 I have an issue with a complex type containing a
base64Binary element:
xsd:complexType name=BinaryFile
xsd:sequence
xsd:element minOccurs=0 name=content nillable=true
type=xsd:base64Binary/
xsd:element minOccurs=0 name=contentType nillable=true
type=xsd:string/
xsd:element minOccurs=0 name=id type=xsd:int/
xsd:element minOccurs=0 name=name nillable=true
type=xsd:string/
/xsd:sequence
/xsd:complexType
When the client fails with the following exception;
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement contentType
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
com.foo.MyServiceStub.fromOM(KnowledgeBaseServiceStub.java:5805)
For testing, we did removed the base64binary element from the response
and the exception disappeared.
Is there a known issue in axis2 1.3 with that kind of complex types?
The client is generated from the wsdl with:
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath/
arg value=-uri/
arg file=${wsdl.path}/MyService.wsdl/
arg value=-o/
arg file=output/
arg value=-u/
/java
Thanks in advance
Etienne
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ajith Ranabahu
Reading, after a certain age, diverts the mind too much from its
creative pursuits. Any man who reads too much and uses his own brain
too little falls into lazy habits of thinking - Albert Einstein
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
==
This transmittal and any attachments may contain confidential, privileged or
sensitive information and is solely for the use of the intended recipient. If
you are not the intended recipient, you are hereby notified that you have
received this transmittal and any attachments in error and any review,
dissemination, distribution or copying thereof is strictly prohibited. If you
have received this transmittal and any attachments in error please notify the
sender and immediately destroy the message and all its attachments. Any
opinions herein expressed may be those of the author and not necessarily of
Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA
Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho
accepts no responsibility for the accuracy or completeness of any information
herein contained.
E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is
a registered U.S. broker-dealer and the entity through which Mizuho generally
conducts its investment banking, capital markets, and securities business in
the United States) is electronically archived and recorded and is subject to
review and monitoring by and/or disclosure to persons other than the recipient,
including (but not limited to) Mizuho Securities USA Inc. supervisory
personnel. Such communications may be produced to regulatory authorities or
others with legal rights to the information.
Issue with Axis2 MTOM client
Hi All Does any one has faced following issue with AXIS MTOM client When I use AXIS2 generated stub as clients to MTOM service I see my .att file grow indefinitely with following character get added. ÿÿÿ. And grow continuously till run out of space. Does Axis2 support as MTOM client. ? I don't suspect my WSDL element definition has problem as same element works fine when I do reverse operation i.e. put file. I don't see any MTOM sample which receives MTOM attachment using axis2 . Is this a bug or axis2 does not support file caching as client. I am enabling MTOM on client side by following statements. EMISEPServiceStub serviceStub = new EMISEPServiceStub(); // Enable MTOM in the client side serviceStub._getServiceClient().getOptions().setProperty( Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE); // Increase the time out when sending large attachments serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds( 1); serviceStub._getServiceClient().getOptions().setProperty(Constants.Configuration.CACHE_ATTACHMENTS, Constants.VALUE_TRUE); serviceStub._getServiceClient().getOptions().setProperty(Constants.Configuration.ATTACHMENT_TEMP_DIR, C:\\TEMP\\cache); serviceStub._getServiceClient().getOptions().setProperty(Constants.Configuration.FILE_SIZE_THRESHOLD, 4000); Please let me know if you need more details for analysing this.? Thanks to all regards Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
does any one has sample for receiving MTOM attachment using axis2
Hi Does any one has sample for receiving MTOM attachment using axis2 with file caching. MTOM sample in axis2 does not work in reverse for me . Though It sends MTOM attachment correctly does not receive mtom attachment with file caching. It fails when I enable file caching . Without file caching it works perfect.( i.e sending and receiving attachment). Thanks Yogesh Dhake == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (”Mizuho”). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such communications may be produced to regulatory authorities or others with legal rights to the information.
