Re: Failed. DLERROR IS DLL Load Error 126: The specified module could not be found.
Thanks for your help. I still need axis2_util.dll. (I am running Apache Tuscany Native module with AXIS2C) Any idea how I can get that? I have installed axis2c from a zip and not from source. rgds. Selvaratnam Uthaiyashankar wrote: Hi, Did you compiled Axis2/C with SSL enabled? In that case, you have to have OpenSSL library in you path. Can you do a dependency check on axis2_http_sender.dll (using dependency walker) and see whether there are any missing libraries reported? Regards, Shankar On Tue, Aug 25, 2009 at 10:06 PM, lekkielekkie.ay...@gmail.com wrote: Hi Guys, After downloading AXIS2C afresh (I am using it with Apache Tuscany Native). Itried starting up the server and it gives the following error [Mon Aug 24 19:53:44 2009] [debug] ..\..\src\core\deployment\conf_builder.c(379) Module tuscany found in axis2.xml [Mon Aug 24 19:53:44 2009] [error] ..\..\util\src\class_loader.c(167) Loading shared library ..//lib/axis2_http_sender.dll Failed. DLERROR IS DLL Load Error 126: The specified module could not be found. [Mon Aug 24 19:53:44 2009] [error] ..\..\src\core\deployment\conf_builder.c(903) Transport sender is NULL for transport http, unable to continue [Mon Aug 24 19:53:44 2009] [error] ..\..\src\core\deployment\conf_builder.c(262) Processing transport senders failed, unable to continue [Mon Aug 24 19:53:44 2009] [error] ..\..\src\core\deployment\dep_engine.c(752) Populating Axis2 Configuration failed [Mon Aug 24 19:53:44 2009] [error] ..\..\src\core\deployment\conf_init.c(64) Loading deployment engine failed for repository ../. [Mon Aug 24 19:53:44 2009] [error] ..\..\src\core\transport\http\receiver\http_receiver.c(126) unable to create private configuration contextfor repo path ../ [Mon Aug 24 19:53:44 2009] [error] ..\..\src\core\transport\http\server\simple_axis2_server\http_server_main.c(215) Server creation failed: Error code: 103 :: Failed in creating DLL Note: I am working on XP SP2, I have already added the lib to my path and I already have the AXIS2C_HOME env variable. kindly help, -- View this message in context: http://www.nabble.com/Failed.-DLERROR-IS-DLL-Load-Error-126%3A-The-specified-module-could-not-be-found.-tp25137868p25137868.html Sent from the Axis - C++ - User mailing list archive at Nabble.com. -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - The Open Source SOA Company -- View this message in context: http://www.nabble.com/Failed.-DLERROR-IS-DLL-Load-Error-126%3A-The-specified-module-could-not-be-found.-tp25137868p25151437.html Sent from the Axis - C++ - User mailing list archive at Nabble.com.
setting server cert from the api
Is the only way to do this via axis2_http_client_set_server_cert()? if so, how does one get a (axis2_http_client_t*) when you have a (axis2_svc_client_t*)?
Re: Problem with ns qualified attribute of a client message
Le mercredi 26 août 2009 à 10:08 +0530, Amila Suriarachchi a écrit : On Wed, Aug 26, 2009 at 12:48 AM, error3 err...@free.fr wrote: Le mardi 25 août 2009 à 07:23 +0200, error3 a écrit : Le lundi 24 août 2009 à 19:52 -0400, Martin Gainty a écrit : if your could convince the service provider to provide the wsdl and xsd schema we could get a working example for you Well, I think the wsdl and the xsd are the ones than could be download there : http://www.epcglobalinc.org/standards/epcis Anyone for help ? it seems type for this element value has declared as xs:anyType in the xsd. So ADB set the correct type to interpret at the server. If you can change the wsdl so that its type to be xs:string I think it should work. Thank you Amila, but this document (http://www.google.fr/url?sa=tsource=webct=rescd=3url=http%3A%2F% 2Fwww.epcglobalinc.org%2Fstandards%2Fepcis% 2Fepcis_1_0_1-standard-20070921.pdfei=0NCUSv6LLZPajQe4rZn0DQusg=AFQjCNF9XowoFXYlwQqS3NuqEulMhy4X3Qsig2=8WdqQqK6wA-XTl1a5zs8Tw page 113) tells me that the type could be one of (xsd:string, xsd:integer, xsd:double, xsd:dateTime, xsd:string, epcisq:ArrayOfString, epcisq:VoidHolder) Do you see any way of making the wsdl works with the server without restraining the type only to string ? Cheers, -- MBdC
Problem xmlbeans with swa
Hi all ! Is it possible to use SwA when source code is generated by xmlbeans ? Cause when i do it, the soap message is not well send. There is no body message. Thanks in advance, _ Découvrez toutes les possibilités de communication avec vos proches http://www.microsoft.com/windows/windowslive/default.aspx
Re: imcompatible issue between axis2 and weblogic 10
Amila, That is correct. You added the check for Weblogic (and Sun) in r693811 (September 2008), so Axiom 1.2.8 should actually work with Weblogic. Andreas On Wed, Aug 26, 2009 at 06:47, Amila Suriarachchiamilasuriarach...@gmail.com wrote: On Wed, Aug 26, 2009 at 10:09 AM, Hu, Mary - ITG mary...@jpmorgan.com wrote: Sorry I don’t get you. Can you provide more detail? Which Axiom fix are you talking about? What is the Axis2 version you use? I think as Andreas has mentioned this fix should be there with Axiom 1.2.8. so if you use Axis2 1.5 this should work. thanks, Amila. Thanks, Mary Hu From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] Sent: Wednesday, August 26, 2009 12:30 AM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 On Wed, Aug 26, 2009 at 2:43 AM, Andreas Veithen andreas.veit...@gmail.com wrote: Since I recently worked on improving the interoperability of Axiom with various StAX parser, I can give you a precise answer. The short answer is: none (with Axiom 1.2.8). The long answer is: - Sun's parser (when used with Axiom up to version 1.2.8) causes a concurrency issue; see WSCOMMONS-489. - Axiom 1.2.8 makes the assumption that all parsers except Woodstox, Sun and Weblogic are broken. This is wrong because only the one from IBM is broken [1]. This means that any parser other than Woodstox, Sun, Weblogic Sometimes back I tested the Axis2 with web logic. Then I had problems with the weblogic parser and when I put the that weblogic entry to Axiom it worked fine. So if you picked an Axis2 version with this Axiom fix it should work with weblogic parser. thanks, Amila. and XLXP (IBM) will not work with Axiom 1.2.8. This excludes BEA's reference implementation (which will work fine with Axiom 1.2.9). - Finally, the one from IBM (which should work with any Axiom version) is not freely available. Andreas [1] http://svn.apache.org/viewvc?rev=800141view=rev On Tue, Aug 25, 2009 at 22:40, Hu, Mary - ITGmary...@jpmorgan.com wrote: No, Weblogic parser doesn't work for axis2. I'm wondering, beside wstx stream parser, what other parser could possibly work for axiom from axix2. Mary Hu -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Tuesday, August 25, 2009 3:53 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 The probable reason for this error is that the TLD file has a DOCTYPE declaration referencing a network location. Woodstox insists on loading the referenced DTD, while for the same configuration Weblogic's parser wouldn't load the DTD. This is due to an ambiguity in the StAX specs. Assuming that this explanation is correct, you have two options: 1) Also remove Woodstox and cross fingers that Axis2 works correctly with Weblogic's parser. Chances are high, but it is not guaranteed. I'm not a Weblogic user, but maybe somebody on the list can share his experience. 2) Hack the TLDs so that they don't have a DOCTYPE declaration with a system ID referencing a network location. Not sure what Weblogic's expectations are. Maybe you can just remove the DOCTYPE declaration entirely, maybe only the system ID or maybe you need to add the DTD to the JAR and change the system ID from an absolute URL to a relative one. Andreas On Mon, Aug 24, 2009 at 23:32, Hu, Mary - ITGmary...@jpmorgan.com wrote: After removed this jar, weblogic can't parse TLD anymore: Error while parsing the Tag Library Descriptor at c: ... \war\WEB-INF\lib\struts-1.2.9-lib.jar!/META-INF/tlds/struts-tiles.tld. com.ctc.wstx.exc.WstxIOException: java.sun.com at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:683) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086) at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCacheHe lper.java:134) Mary Hu Int: 8.226.2620 Ext: 973.793.2620 -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Monday, August 24, 2009 4:54 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 Try removing geronimo-stax-api_1.0_spec-1.0.1.jar from WEB-INF/lib. Andreas On Mon, Aug 24, 2009 at 22:28, Hu, Mary - ITGmary...@jpmorgan.com wrote: In axis2 - Application Server Specific Configuration Guide, it mentions how to deploy axis2 into weblogic. However, I have seen an issue that is blocking me. I wonder anyone has a solution for it: 1. I have a WAR containing axis2 jars. 2. My application requires prefer-web-inf-classes to be set as true in weblogic.xml. 3. I got below exception: java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory
Re: Problem with ns qualified attribute of a client message
On Wed, Aug 26, 2009 at 11:48 AM, error3 err...@free.fr wrote: Le mercredi 26 août 2009 à 10:08 +0530, Amila Suriarachchi a écrit : On Wed, Aug 26, 2009 at 12:48 AM, error3 err...@free.fr wrote: Le mardi 25 août 2009 à 07:23 +0200, error3 a écrit : Le lundi 24 août 2009 à 19:52 -0400, Martin Gainty a écrit : if your could convince the service provider to provide the wsdl and xsd schema we could get a working example for you Well, I think the wsdl and the xsd are the ones than could be download there : http://www.epcglobalinc.org/standards/epcis Anyone for help ? it seems type for this element value has declared as xs:anyType in the xsd. So ADB set the correct type to interpret at the server. If you can change the wsdl so that its type to be xs:string I think it should work. Thank you Amila, but this document (http://www.google.fr/url?sa=tsource=webct=rescd=3url=http%3A%2F% 2Fwww.epcglobalinc.org%2Fstandards%2Fepcis% 2Fepcis_1_0_1-standard-20070921.pdfei=0NCUSv6LLZPajQe4rZn0DQusg=AFQjCNF9XowoFXYlwQqS3NuqEulMhy4X3Qsig2=8WdqQqK6wA-XTl1a5zs8Tw page 113) tells me that the type could be one of (xsd:string, xsd:integer, xsd:double, xsd:dateTime, xsd:string, epcisq:ArrayOfString, epcisq:VoidHolder) Do you see any way of making the wsdl works with the server without restraining the type only to string ? This is why the client should send the type. Server has said it is anyType so client has to send the type as the xsi type. As you have told your server does not process the runtime type, then it may have assume it as string. thanks, Amila. Cheers, -- MBdC -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Combining mtom and gzip compressed soap response
Hi That worked thanks for the help. cheers, Håkon 2009/8/25 Andreas Veithen andreas.veit...@gmail.com Håkon, Can you try to add multipart/related to the list of compressableMimeTypes? Andreas 2009/8/25 Håkon Sagehaug hakon.sageh...@bccs.uib.no: Hi Andreas, Well the problem I guess is that the response from the service is not gzipped. I run the request/response through tcpmon and the request is gzipped but not the response. In tomcat service.xml I've got this Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on compressionMinSize=2048 noCompressionUserAgents=gozilla, traviata compressableMimeType=text/html,text/xml/ The client has these option set to true org.apache.axis2.transport.http.HTTPConstants.MC_GZIP_REQUEST org.apache.axis2.transport.http.HTTPConstants.MC_GZIP_RESPONSE org.apache.axis2.transport.http.HTTPConstants.MC_ACCEPT_GZIP and on the service I've got this MessageContext inMessageContext = MessageContext.getCurrentMessageContext(); // Obtain the operation context from the request message context OperationContext operationContext = inMessageContext .getOperationContext(); // Obtain the response (outgoing) message context from the operation context MessageContext outMessageContext; outMessageContext = operationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE); outMessageContext.setProperty(HTTPConstants.MC_GZIP_RESPONSE,Boolean.TRUE); outMessageContext.setProperty(HTTPConstants.MC_ACCEPT_GZIP,Boolean.TRUE); I've got the same configuration for a service that does not have mtom enabled this works fine, but not in the service enabled. If I remove the parameter parameter name=enableMTOM locked=falsetrue/parameter from service.xml the response is gzipped. cheers, Håkon 2009/8/24 Andreas Veithen andreas.veit...@gmail.com Håkon, Could you please be a bit more precise about the problem you are encountering? Andreas 2009/8/21 Håkon Sagehaug hakon.sageh...@bccs.uib.no: Hi all, I wanted to know if it's possible to have both gzip compressed soap response that contains mtom, I got gzip response working on a non-mtom service, but not when mtom was enabled. cheers, Håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
Re: Problem with ns qualified attribute of a client message
This is why the client should send the type. Server has said it is anyType so client has to send the type as the xsi type. As you have told your server does not process the runtime type, then it may have assume it as string. thanks, Amila. Well, Amila, the server process the runtime time like this : if it's string, the client send valuestringthestringvalue/string/value it it's dateTime, the client send valuedatetimethedatetime/datetime/value There's no need of having fully qualified namespace. What makes the server send me an error is that string is fully qualified : string xmlns:xi=http:// without this, it works (I've tried with SOAPUI) What do you think ? Any possibilities to remove these fully qualified namespace attribute ? Cheers, and thanks again -- Martin
RE: Where's wsgen and wsimport?
Amila, Thanks for your reply. Since these jars weren't in the Axis distribution I eventually concluded that I had to get them from elsewhere and downloaded JAX-WS 2.1.5 from the Glassfish/Metro/JAX-WS site (I encountered a problem with the 2.1.7 download jar file). I can see that wsgen and wsimport are in the 'bin' folder. However, it's still not clear to me just how to integrate with Axis or why the documentation doesn't cover this, so I guess I'll experiment some more keeping your tip in mind. I'm curious as to how you figured this out from the provided documentation (or otherwise). I realize that Axis is open source, but it sure would be a monumental improvement if the Axis documentation were given as much attention as the product itself and explained in more detail so we wouldn't have to needlessly waste so much time trying to get it (or at least certain aspects of it like JAX-WS) working. For example, it doesn't seem like it would be that difficult to mention that you have to download JAX-WS separately, include a link, explain how to integrate it, and suggest when/why you might want to use it with Axis. Hopefully someone from Axis will read this and get the documentation improved. In any case, thanks again for the tip! Aaron Meyer Phone: (314) 387-4297 E-Mail: alme...@magellanhealth.com mailto:alme...@magellanhealth.com From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] Sent: Tuesday, August 25, 2009 11:50 PM To: axis-user@ws.apache.org Subject: Re: Where's wsgen and wsimport? hi, you need to put jaxws-rt.jar and jaxws-tools.jar s to lib folder. thanks, Amila. On Tue, Aug 25, 2009 at 11:36 PM, Meyer, Aaron L. alme...@magellanhealth.com wrote: The immediate problem I hope you can help me with: I can't find wsgen or wsimport in the distribution for 1.5. I'm wondering why there is documentation for JAXWS but apparently it's not included. Also, I would like to know if JAXWS is what I should learn if just starting out since (if I understand what I read correctly) it appears as though it will be the J2EE standard way of creating Web Services. So how do I get JAXWS to work with Axis - that's the missing part in the documentation. Other comments: I'm trying to learn Web Services and I just went through the JBoss In Action chapter and successfully created a simple web service (apparently based on JAXWS). I then decided I would like to also learn Axis (partly because we aren't on the latest JBoss server). I quickly became frustrated for the following reasons: The documentation is very confusing because it offers all these different technologies you can use but offers no guidelines as to which to use, and the examples under the different sections aren't even consistent (e.g. Quick Start vs. User Guide). This is only made worse by the (apparently) missing support for JAXWS (even though it's documented as though it is supported). It would save a lot of frustration if you could clarify all this in the documentation (especially the JAXWS part). By the way - this is not meant to 'trash' your product by any means, but rather to be constructive information in hopes of improvements. Thanks, Aaron Meyer Senior Programmer/Analyst - Provider Data Systems Magellan Health Services 14100 Magellan Plaza Maryland Heights, MO 63043 Phone: (314) 387-4297 E-Mail: alme...@magellanhealth.com mailto:alme...@magellanhealth.com -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Newbie question
Instead of using ArrayList, use complex type array as return type e.g instead of using public ArrayList listFunctions(), use public Function[] listFunction() Chinmoy On Thu, Aug 27, 2009 at 4:12 AM, Arvind Narayan arvind.nara...@gmail.comwrote: Hello: I am facing a strange problem where I see SOAP data coming back from the server, but my axis2 client is reading NULLs for all fields in an array_list response. Here are the steps I took: (1) Used the WSDL2C tool in AXIS2C version 1.5 to generate stub classes using adb binding and wv 1.1 ( all other versions fail ) (2) Server runs Axis2 inside tomcat. (3) Start a tcpdump to see client/server interaction. (4) Client starts up sends request to server. (5) Server responds with required data. ( its an array_list type ). tcpdump displays the returned data. (6) Client sees 190 items in adb_xxx_sizeof_return( response, env ); (6) Client uses adb_xxx_get_return_at( response, env, i ) to get element at i. (7) Element is not NULL, but all inner members of the element are NULL. what could I be doing wrong? what other details do you need? thanks arvind.
