Re: new issue---- Getting new error while compiling web service dll in VC++7.0 for IIS
Hi You need to add axis2 libraries to your project. Add the .lib files in Axis2 Binary\lib to your project. You need to add axis2_engine.lib axis2_util.lib axis2_parser.lib axiom.lib to your project. Regards Nandika On 3/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: -- *From:* Venkada Swamy, Vijayalakshmi (Cognizant) *Sent:* Friday, March 09, 2007 2:12 PM *To:* Venkada Swamy, Vijayalakshmi (Cognizant); ' [EMAIL PROTECTED]'; 'axis-c-user@ws.apache.org' *Cc:* 'axis-c-dev@ws.apache.org' *Subject:* RE: Getting error while compiling web service dll in VC++7.0 for IIS Hi, Thanks Nandika, after adding the directive AXIS2_DECLARE_EXPORT that error is not coming but the following new error is coming. Can you tell me what could be the problem. myecho error LNK2001: unresolved external symbol [EMAIL PROTECTED] myecho error LNK2001: unresolved external symbol _axis2_log_impl_log_error myecho error LNK2005: [EMAIL PROTECTED] already defined in MSVCRTD.lib( dllmain.obj) myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol _AXIS2_ECHOSTRING_GET_PARAM0 referenced in function _axis2_skel_myecho_echoString myecho error LNK2019: unresolved external symbol _AXIS2_ECHOSTRUCTRESPONSE_SET_RETURN referenced in function _axis2_skel_myecho_echoString myecho error LNK2019: unresolved external symbol _axis2_log_impl_log_error referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol _axis2_log_impl_log_error referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in
RE: Getting error while compiling web service dll in VC++7.0 for IIS
Hi, Thanks Nandika, after adding the directive AXIS2_DECLARE_EXPORT that error is not coming but the following new error is coming. Can you tell me what could be the problem. myecho error LNK2001: unresolved external symbol [EMAIL PROTECTED] myecho error LNK2001: unresolved external symbol _axis2_log_impl_log_error myecho error LNK2005: [EMAIL PROTECTED] already defined in MSVCRTD.lib(dllmain.obj) myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol _AXIS2_ECHOSTRING_GET_PARAM0 referenced in function _axis2_skel_myecho_echoString myecho error LNK2019: unresolved external symbol _AXIS2_ECHOSTRUCTRESPONSE_SET_RETURN referenced in function _axis2_skel_myecho_echoString myecho error LNK2019: unresolved external symbol _axis2_log_impl_log_error referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol _axis2_log_impl_log_error referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho fatal error LNK1120: 25 unresolved externals d:\Axis2Cdll\myecho\ccodewsdltc1\axis2_skel_myecho.c(33): warning C4013: 'AXIS2_ECHOSTRING_GET_PARAM0' undefined; assuming extern returning int d:\Axis2Cdll\myecho\ccodewsdltc1\axis2_skel_myecho.c(37):
new issue---- Getting new error while compiling web service dll in VC++7.0 for IIS
From: Venkada Swamy, Vijayalakshmi (Cognizant) Sent: Friday, March 09, 2007 2:12 PM To: Venkada Swamy, Vijayalakshmi (Cognizant); '[EMAIL PROTECTED]'; 'axis-c-user@ws.apache.org' Cc: 'axis-c-dev@ws.apache.org' Subject: RE: Getting error while compiling web service dll in VC++7.0 for IIS Hi, Thanks Nandika, after adding the directive AXIS2_DECLARE_EXPORT that error is not coming but the following new error is coming. Can you tell me what could be the problem. myecho error LNK2001: unresolved external symbol [EMAIL PROTECTED] myecho error LNK2001: unresolved external symbol _axis2_log_impl_log_error myecho error LNK2005: [EMAIL PROTECTED] already defined in MSVCRTD.lib(dllmain.obj) myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol _AXIS2_ECHOSTRING_GET_PARAM0 referenced in function _axis2_skel_myecho_echoString myecho error LNK2019: unresolved external symbol _AXIS2_ECHOSTRUCTRESPONSE_SET_RETURN referenced in function _axis2_skel_myecho_echoString myecho error LNK2019: unresolved external symbol _axis2_log_impl_log_error referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol _axis2_log_impl_log_error referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function [EMAIL PROTECTED] myecho error LNK2019: unresolved
RE: building axis c++ (HEAD) using ANT / Visual Studio 2003 / WinXP SP2
Using the ANT build scripts for AXIS C++, what are the environment requirements / prerequisites for making sure that SSL DLL links in properly? I have OPEN SSL v.0.9.8e / Win32 installed and an environment variable set for OPENSSL_HOME. What else needs to be done? Thanks ScottM -Original Message- From: Nadir Amra [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 7:45 PM To: Apache AXIS C User List Cc: axis-c-user@ws.apache.org Subject: Re: building axis c++ (HEAD) using ANT / Visual Studio 2003 / WinXP SP2 Scott, I am not sure, but it looks like it is not linking in the SSL DLL library? Nadir K. Amra Scott McFadden [EMAIL PROTECTED] wrote on 03/08/2007 01:20:04 PM: I am attempting to compile the HEAD version of Axis C++ Client using the build.xml script. All goes well until the compileAxisHTTPTransportSSLChannel step. (Win32 OpenSSL v0.9.8e) OPENSSL_HOME = c:\dev\c++\OpenSSL What troubleshooting steps do I need to perform to track down the linker error? This is where the ANT script fails: compileAxisHTTPTransportSSLChannel: buildVersionResource: [copy] Copying 1 file to C:\dev\c++\Apache\axis\ws-axis\c\build [cc] Starting dependency analysis for 2 files. [cc] 2 files are up to date. [cc] 0 files to be recompiled from dependency analysis. [cc] 2 total files to be compiled. [cc] URL.cpp [cc] PlatformSpecificWindows.cpp [cc] Generating Code... [cc] Starting link [cc]Creating library HTTPSSLChannel.lib and object HTTPSSLChannel.exp [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ get_error referenced in function protected: int __thiscall HTTPSSLChannel::Read FromSocket(char *) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ read referenced in function protected: int __thiscall HTTPSSLChannel::ReadFromS ocket(char *) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ write referenced in function protected: int __thiscall HTTPSSLChannel::WriteToS ocket(char const *,int) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ library_init referenced in function protected: void __thiscall HTTPSSLChannel:: OpenSSL_Initialise(void) ([EMAIL PROTECTED]@@IAEXXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ load_error_strings referenced in function protected: void __thiscall HTTPSSLCha nnel::OpenSSL_Initialise(void) ([EMAIL PROTECTED]@@IAEXXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ connect referenced in function protected: bool __thiscall HTTPSSLChannel::OpenS SL_Open(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ set_fd referenced in function protected: bool __thiscall HTTPSSLChannel::OpenSS L_Open(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ set_connect_state referenced in function protected: bool __thiscall HTTPSSLChan nel::OpenSSL_Open(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ new referenced in function protected: bool __thiscall HTTPSSLChannel::OpenSSL_O pen(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ CTX_set_verify referenced in function protected: bool __thiscall HTTPSSLChannel ::OpenSSL_Open(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _ERR_ error_string referenced in function protected: bool __thiscall HTTPSSLChannel:: OpenSSL_Open(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _ERR_ get_error referenced in function protected: bool __thiscall HTTPSSLChannel::Ope nSSL_Open(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSL_ CTX_new referenced in function protected: bool __thiscall HTTPSSLChannel::OpenS SL_Open(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _SSLv 23_client_method referenced in function protected: bool __thiscall HTTPSSLChann el::OpenSSL_Open(void) ([EMAIL PROTECTED]@@IAE_NXZ) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _X509 _NAME_oneline referenced in function int __cdecl cert_verify_callback(int,struc t x509_store_ctx_st *) (?cert_verify_callback@@YAHHPAUx509_store_ctx_st@@@Z) [cc] HTTPSSLChannel.obj : error LNK2019: unresolved external symbol _X509 _get_subject_name
Re: [Axis2] soap serialization
This code could work, but if not, you can send te message to http://localhost, without server to answer and use the ~/tools/tcpmon to listen and display the message. I think SOAP headers in SOAP MESSAGE are added in AXIS2_SVC_CLIENT_SEND_RECEIVE( ) function, but I not sure. axiom_xml_writer_t *xml_writer = NULL; axiom_output_t *om_output = NULL; axis2_char_t *buffer = NULL; axis2_op_client_t* op_client; axis2_msg_ctx_t* mgg_ctx; struct axiom_soap_envelope* envelope; op_client = AXIS2_ SVC_CLIENT_GET_OP_CLIENT(svc_client, env); msg_ctx = AXIS2_OP_CLIENT_GET_MSG_CTX( op_client, env, AXIS2_WSDL_MESSAGE_OUT_VALUE); envelope = AXIS2_MSG_CTX_GET_SOAP_ENVELOPE(msg_ctx, env); xml_writer = axiom_xml_writer_create_for_memory(env, NULL, AXIS2_FALSE, AXIS2_FALSE,AXIS2_XML_PARSER_TYPE_BUFFER); om_output = axiom_output_create(env, xml_writer); AXIOM_SOAP_ENVELOPE_SERIALIZE(envelope, env, om_output, false); buffer = (axis2_char_t*)AXIOM_XML_WRITER_GET_XML(xml_writer, env); - Original Message From: George Stanchev [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Thursday, March 8, 2007 9:53:11 PM Subject: RE: [Axis2] soap serialization Acttually, let me make sure I understand it correctly. I might have send the thanks a bit too quick. That code snippet seem to serialize an axiom node. What I need is to send the message - thus applying all handler processing involved in creating a SOAP message. What I care in particular is applying all security, addressin and whatever handlers processing a normal send does (for example it should create all the wsse headers). Would the snippet you suggest do this? Best Regards, George -Original Message- From: George Stanchev [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 10:45 PM To: Apache AXIS C User List Subject: RE: [Axis2] soap serialization Atanacio, thanks a bunch! Best Regards, George -Original Message- From: Atanacio Reyes [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 6:15 PM To: Apache AXIS C User List Subject: Re: [Axis2] soap serialization axiom_xml_writer_t *xml_writer = NULL; axiom_output_t *om_output = NULL; axis2_char_t *buffer = NULL; xml_writer = axiom_xml_writer_create_for_memory(env, NULL, AXIS2_FALSE, AXIS2_FALSE, AXIS2_XML_PARSER_TYPE_BUFFER); om_output = axiom_output_create(env, xml_writer); AXIOM_NODE_SERIALIZE(node, env, om_output); buffer = (axis2_char_t*)AXIOM_XML_WRITER_GET_XML(xml_writer, env); axiom_node_t* node, is the document to serialize; - Original Message From: George Stanchev [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Thursday, March 8, 2007 3:15:52 PM Subject: [Axis2] soap serialization Hi, Another, probably basic, question: I need to serialize a SOAP call to a string buffer without sending it anywhere. How do I this with axis2/c? Can you give me some leads? On the java side, I had to go through some hoops to get this - I had to create a dummy transport that I used to reflect back the outbound message when I was doing a call-out serialization. How can I do the same thing in axis2/c? Thanks! George Stanchev 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SWA in WSDL2Java generated client using xmlbeans binding
wsdl:binding name=MmsSendServiceSOAP type=tns:MmsSendServicePortType soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http / wsdl:operation name=SendMms soap:operation soapAction=urn:mms/SendMms/ wsdl:input soap:body use=literal/ mime:multipartRelated mime:part name=parameterpart soap:body parts=Parameters use=literal/ /mime:part mime:part name=attachmentpart mime:content part=Attachment type=multipart/*/ /mime:part /mime:multipartRelated /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output wsdl:fault name=XError soap:fault name=XError use=literal/ /wsdl:fault /wsdl:operation /wsdl:binding Axis2 does not support the above binding yet.. :( If possible you can try using MTOM...[1] ...and with this change WSDL2Java completes successfully and the stub method has the expected parameters. Please note the only difference: an additional soap:body use=literal/ inside the wsdl:input, but outside the mime:multipartRelated My question: Can anyone please tell me if this is a proper fix? Another related questionI don't see anywhere in the resulting client stub class where I can set the MessageContext, or use any other technique to add attachments to the requesthave I missed something? It's not possible.. It's available only through the OperationClient API.. Have a look at the blog entry titled Use XMLBean generated objects with Axis2 in here [2] to figure out how to data bound only to schemas and to use operationClient respectively... Thilina [1] http://ws.apache.org/axis2/1_1_1/mtom-guide.html#25 [2] http://www.bloglines.com/blog/hemapani/2006_10 Many Thanks, Darren (P.S. I can provide the full WSDL and xsd files if that helps...I didn't include them in this post as they're pretty big) -- Thilina Gunarathne WSO2, Inc.; http://www.wso2.com/ Home page: http://webservices.apache.org/~thilina/ Blog: http://thilinag.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Retriveve username from HTTP request header
How can I retrieve the username in the service implementation when using Basic Authenitcation? The examples I have found suggests using msgContext.getProperty(HTTPConstants.HEADER_AUTHORIZATION ), but this returns null. -Baard
ntlm authentication and Axis 2
Hi, I am using Axis 2 to communicate with a server which has ntlm authentication. When I am invoking web service methods which do not involve any attachment, it is working fine. Using TCP packet capturing, I can even see the NTLM authentication happening via challenge/response handshaking. One problem that I see here is that for every method invocation the ntlm authentication is occuring which is a kind of redundancy. I think this is happening because pre-authentication feature is not built into Axis 2 or common httpclient. But the more serious problem is happening when I am trying to post data as attachment. The entire SOAP request is sent as a multipart MIME-encoded request. The first part is the SOAP envelope, and the second part is the attachment. But as it seems to me the ntlm authentication handshaking is getting into way and the client is not responding accordingly and is continuing with its multipart post. I am using Axis 2-1.1.1 version. The authentication code used is like below: HttpTransportProperties.Authenticator auth = new HttpTransportProperties.Authenticator(); auth.setUsername(Admin); auth.setPassword(password); auth.setRealm(); auth.setDomain(); auth.setHost(ip-addr); auth.setPort(80); options.setProperty(HTTPConstants.AUTHENTICATE, auth); options.setProperty(HTTPConstants.HEADER_CONNECTION_KEEPALIVE,Constants.VALUE_TRUE); options.setTo(targetEPR); options.setTransportInProtocol(Constants.TRANSPORT_HTTP); options.setProperty(Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE); options.setProperty(Constants.Configuration.CONTENT_TYPE, Constants.BASE_64_CONTENT_QNAME); ServiceClient servClient = new ServiceClient(); servClient.setOptions(options); OMElement result = servClient.sendReceive(method); I am new to Axis and authentication. Any suggestion would be of great help. _ Windows Live Spaces is here! It’s easy to create your own personal Web site. http://spaces.live.com/?mkt=en-in
RE: ntlm authentication and Axis 2
Hi all, I'm having a similar problem, where we are sending over 1000 calls in about one hour. However, for each call: - first a simple request is done - the proxy server responds that needs NTLM - then a request is sent with the proxyhost and the proxyport - the proxy server then responds that we don't have access to that URL - then a request is sent with all of the proxy parameters (host, port, user, domain, password) Is it possible to get Axis2 to send all of the parameters the first time? This would reduce sending time with at least one second, I think (so over 25%). Thanks, Brecht From: Arindam Roy [mailto:[EMAIL PROTECTED] Sent: vrijdag 9 maart 2007 11:05 To: axis-user@ws.apache.org Subject: ntlm authentication and Axis 2 Hi, I am using Axis 2 to communicate with a server which has ntlm authentication. When I am invoking web service methods which do not involve any attachment, it is working fine. Using TCP packet capturing, I can even see the NTLM authentication happening via challenge/response handshaking. One problem that I see here is that for every method invocation the ntlm authentication is occuring which is a kind of redundancy. I think this is happening because pre-authentication feature is not built into Axis 2 or common httpclient.
[Axis2] String[] problem
Hello, I found no solution for my problem in the archive, therefor I send a new email. I have a simple service with a method String[] logout. I generated the wsdl by java2wsdl tool. Relevant part looks okay: xs:element name=logoutResponse xs:complexType xs:sequence xs:element maxOccurs=unbounded name=return nillable=true type=xs:string / /xs:sequence /xs:complexType On the client side, I generate the Stub with wsdl2Java. The client Code, using this stub looks like: SessionBasedServiceStub.LogoutResponse logoutResponse = serviceStub.logout(); String[] value = logoutResponse.get_return(); get_return(); returns a String[]; But the problem is, by calling the logout() method, an exception is thrown: java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement return at de.nepatec.jzink.webservice.client.SessionBasedServiceStub.fromOM(SessionBasedServiceStub.java:2887) at de.nepatec.jzink.webservice.client.SessionBasedServiceStub.logout(SessionBasedServiceStub.java:586) at de.nepatec.jzink.webservice.client.Client.main(Client.java:38) Caused by: java.lang.RuntimeException: Unexpected subelement return at de.nepatec.jzink.webservice.client.SessionBasedServiceStub$LogoutResponse$Factory.parse(SessionBasedServiceStub.java:1721) at de.nepatec.jzink.webservice.client.SessionBasedServiceStub.fromOM(SessionBasedServiceStub.java:2881) ... 2 more The XMLParser does not know the return elements in the return message from the service: ns:logoutResponse xmlns:ns=http://org.apache.axis2/xsd; ns:returnfirstString/ns:return ns:returnsecondString/ns:return /ns:logoutResponse What is my fault? Does anyone know, how to return a String[]? Thanks a lot! The service.xml: service name=SessionBasedService scope=soapsession .. operation name=logout messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation parameter name=ServiceClassde.nepatec.jzink.webservice.SessionBasedService/parameter /service _ In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] String[] problem
I found the problem. Sorry for the post. I was a little bit stupid. The Service has yoused the wrong messagereceiver. I have not replaced the service.xml by the generated service.xml form wsdl2java thanks a lot! -Ursprüngliche Nachricht- Von: axis-user@ws.apache.org Gesendet: 09.03.07 11:52:43 An: axis-user@ws.apache.org Betreff: [Axis2] String[] problem Hello, I found no solution for my problem in the archive, therefor I send a new email. I have a simple service with a method String[] logout. I generated the wsdl by java2wsdl tool. Relevant part looks okay: xs:element name=logoutResponse xs:complexType xs:sequence xs:element maxOccurs=unbounded name=return nillable=true type=xs:string / /xs:sequence /xs:complexType On the client side, I generate the Stub with wsdl2Java. The client Code, using this stub looks like: SessionBasedServiceStub.LogoutResponse logoutResponse = serviceStub.logout(); String[] value = logoutResponse.get_return(); get_return(); returns a String[]; But the problem is, by calling the logout() method, an exception is thrown: java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement return at de.nepatec.jzink.webservice.client.SessionBasedServiceStub.fromOM(SessionBasedServiceStub.java:2887) at de.nepatec.jzink.webservice.client.SessionBasedServiceStub.logout(SessionBasedServiceStub.java:586) at de.nepatec.jzink.webservice.client.Client.main(Client.java:38) Caused by: java.lang.RuntimeException: Unexpected subelement return at de.nepatec.jzink.webservice.client.SessionBasedServiceStub$LogoutResponse$Factory.parse(SessionBasedServiceStub.java:1721) at de.nepatec.jzink.webservice.client.SessionBasedServiceStub.fromOM(SessionBasedServiceStub.java:2881) ... 2 more The XMLParser does not know the return elements in the return message from the service: ns:logoutResponse xmlns:ns=http://org.apache.axis2/xsd; ns:returnfirstString/ns:return ns:returnsecondString/ns:return /ns:logoutResponse What is my fault? Does anyone know, how to return a String[]? Thanks a lot! The service.xml: service name=SessionBasedService scope=soapsession .. operation name=logout messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation parameter name=ServiceClassde.nepatec.jzink.webservice.SessionBasedService/parameter /service _ In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS1.4] Deploy and sart StockQuoteService.java
Hi! I don't know very well how to use correctly Axis 1.4. I'm trying to deploy StockQuoteService.java placed into axis-1_4\webapps\axis\WEB-INF\classes\samples\stock folder with this deploy file deploy-base.wsdd placed in the same folder: deployment name=test xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; service name=xmltoday-delayed-quotes-base provider=java:RPC style=document use=literal parameter name=className value=samples.stock.StockQuoteService/ parameter name=allowedMethods value=getQuote/ parameter name=scope value=application/ /service /deployment I wrote a file .bat in the same folder: java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient samples/stock/server/deploy-base where axisclasspath is an environment variable that containe all .jar files paths in lib folder. But i have this error: Exception in thread main java.lang.noclassdefounderror org/sample/Axis/AdminClient When i'll solve this problem will be correct this way to start it? java -cp %AXISCLASSPATH% samples.stock.client.StockServiceClient XXX http://localhost:8080/axis/services/xmltoday-delayed-quotes-base Many thanks to all Antonio -- Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Unexpected creaton of an intermediate layer (wrapper class) by using Axis v1.1.1
Hi,
Using the invocation
%AXIS2_HOME%\bin\wsdl2java -uri addServicePort.wsdl -p danet -d adb -s
I created the stub AddServicePortServiceStub.java. Surprisingly an
additional intermediate layer represented by the class
AddService0(...) has been created. This class is needed for a proper
call of the service:
public AddServiceResponse addService(AddService0 param) {
EIMessageContext context =
param.getAddService().getEiMessageContext();
...
}
That is, the AddService0 wraps the original AddService class I'm
interested in. But why is this wrapping needed?
If I try the Axis2UserGuideService example
http://ws.apache.org/axis2/1_1_1/userguide-creatingclients.html#createcl
ients
such intermediate layers will be not created. For example there is no
TwoWayOneParameterEchoRequest0 class:
TwoWayOneParameterEchoResponse
TwoWayOneParameterEcho(TwoWayOneParameterEchoRequest param) {
...
}
At the present time we plan to migrate our connector from JBossWS to
Axis2. But the additional AddService0 class is a migration issue.
Is there an approach to avoid this wrapper class?
Because I used the same invocation as for the Axis2UserGuideService
example I guess it depends on the entries of the WSDL.
--
Karl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unexpected creaton of an intermediate layer (wrapper class) by using Axis v1.1.1
Karl
The wrapping is basically part of how many toolkits create WSDLs these
days. Its based on an approach from Microsoft.
The simple answer is add -uw (unwrap) to your WSDL2Java command line.
In 1.1.1 this only unwraps parameters not responses but in 1.2 its
fixed to do both.
If you want to understand the convention more, this explanation from
Anne Thomas Manes is probably the clearest available:
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
Paul
On 3/9/07, Philipp, Karl [EMAIL PROTECTED] wrote:
Hi,
Using the invocation
%AXIS2_HOME%\bin\wsdl2java -uri addServicePort.wsdl -p danet -d adb -s
I created the stub AddServicePortServiceStub.java. Surprisingly an
additional intermediate layer represented by the class
AddService0(...) has been created. This class is needed for a proper
call of the service:
public AddServiceResponse addService(AddService0 param) {
EIMessageContext context =
param.getAddService().getEiMessageContext();
...
}
That is, the AddService0 wraps the original AddService class I'm
interested in. But why is this wrapping needed?
If I try the Axis2UserGuideService example
http://ws.apache.org/axis2/1_1_1/userguide-creatingclients.html#createcl
ients
such intermediate layers will be not created. For example there is no
TwoWayOneParameterEchoRequest0 class:
TwoWayOneParameterEchoResponse
TwoWayOneParameterEcho(TwoWayOneParameterEchoRequest param) {
...
}
At the present time we plan to migrate our connector from JBossWS to
Axis2. But the additional AddService0 class is a migration issue.
Is there an approach to avoid this wrapper class?
Because I used the same invocation as for the Axis2UserGuideService
example I guess it depends on the entries of the WSDL.
--
Karl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
Oxygenating the Web Service Platform, www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
SimpleAxisServer on axis2
Hi! Does anybody have a tutorial on how to created a Embedded SimpleAxisServer on Axis2? The axis2 website does not have one. Thanks! Jonathan
[AXIS 1.4] WSDL Publish Problem
Hi, group, I have used WSDL2Java to generate service side code. The WSDL has several import to external schema files. Now I have some questions with the generated code deployment. Question 1 : After I deploy my server code to TOMCAT5.5 it does not have any problem to access the service and display WSDL on browser through URL?wsdl. The question is the displayed WSDL is different from my original WSDL file used to generate the service especially the import schema part. Is there any way to let client to retrieve my original WSDL file through browser? Or is there any way to add import in published schema instead of publish schema within displayed WSDL file? Question 2: When I deployed same service code to OC4J 10.1.3 I can access the service through client but the WSDL is NOT completely browseable. The browser shows Page Cannot Be Displayed (could be http 500). How is the different for TOMCAT and OC4J platform related to WSDL publication? What is the potential problem? I did have some custom fault type thrown by service but could this be problem? Can anyone help with this? Thanks
Not able to generate code
Hello. I'm using Axis2 1.1 to generate code for a service. I use the following command: /opt/axis2-1.1/bin/wsdl2java.sh -uri ./wsdl/wsctx.wsdl -ss -g -sn PriorService -o ./PriorService But got the following output: Using AXIS2_HOME: /opt/axis2-1.1 Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun-1.5.0.08 Unrecognized option: -uri Could not create the Java virtual machine. What's the problem? The shown paths are ok but it complains that uri is not a valid option while in the documentation says: WSDL2Code -uri Location of WSDL and also in the tutorial, the first example is: %AXIS2_HOME%\bin\wsdl2java -uri Axis2UserGuide.wsdl -p org.apache.axis2.axis2userguide -d adb -s So -uri option must be understood by Axis. -- Saludos. José Antonio Sánchez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] SOAP faults problem with InOnly Receiver
Hi,
I'm having problems returning SOAP faults from Axis2/Java 1.1.1 when
using methods that use the InOnly receiver (i.e. ones that don't
return any data).
Instead of retuning a HTTP/1.1 500 Internal Server Error response,
it returns HTTP/1.1 202 Accepted.
I believe that the 500 response is correct:
In case of a SOAP error while processing the request, the SOAP HTTP
server MUST issue an HTTP 500 Internal Server Error response and
include a SOAP message in the response containing a SOAP Fault element
(see section 4.4) indicating the SOAP processing error.
http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383529
To demonstrate I've created some WSDL that has two methods - one that
doesn't return any data (in), and one that does (inout):
--- Begin test.wsdl -
?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:tns=http://www.example.org/test/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema; name=test
targetNamespace=http://www.example.org/test/;
wsdl:types
xsd:schema targetNamespace=http://www.example.org/test/;
xsd:element name=in type=xsd:string /
xsd:element name=inout type=xsd:string /
xsd:element name=inoutResponse type=xsd:string /
/xsd:schema
/wsdl:types
wsdl:message name=inRequest
wsdl:part name=parameters element=tns:in /
/wsdl:message
wsdl:message name=inoutRequest
wsdl:part name=inoutRequest element=tns:inout /
/wsdl:message
wsdl:message name=inoutResponse
wsdl:part name=parameters element=tns:inoutResponse /
/wsdl:message
wsdl:portType name=test
wsdl:operation name=in
wsdl:input message=tns:inRequest/wsdl:input
/wsdl:operation
wsdl:operation name=inout
wsdl:input message=tns:inoutRequest/wsdl:input
wsdl:output message=tns:inoutResponse/wsdl:output
/wsdl:operation
/wsdl:portType
wsdl:binding name=testSOAP type=tns:test
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http; /
wsdl:operation name=in
soap:operation
soapAction=http://www.example.org/test/in; /
wsdl:input
soap:body use=literal /
/wsdl:input
/wsdl:operation
wsdl:operation name=inout
soap:operation
soapAction=http://www.example.org/test/inout; /
wsdl:input
soap:body use=literal /
/wsdl:input
wsdl:output
soap:body use=literal /
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:service name=test
wsdl:port binding=tns:testSOAP name=testSOAP
soap:address location=http://www.example.org/; /
/wsdl:port
/wsdl:service
/wsdl:definitions
--- End test.wsdl ---
I then create the Java classes from the WSDL:
wsdl2java -uri test.wsdl -ss -sd
I then populate the skeleton class with code that throws AxisFaults:
--- Begin src/org/example/www/test/TestSkeleton.java
package org.example.www.test;
import org.apache.axis2.AxisFault;
public class TestSkeleton{
public InoutResponse inout(Inout param0) throws AxisFault {
throw new AxisFault(Inout AxisFault);
}
public void in(In param2) throws AxisFault {
throw new AxisFault(In AxisFault);
}
}
--- End src/org/example/www/test/TestSkeleton.java --
I then build the aar file using ant and the wsdl2java-created
build.xml and deploy it to my Tomcat 5.0.28 server.
I then use Eclipse's Web Services Explorer to invoke the web service,
proxying the requests through Apache TCPMon so that I can view the
headers.
These are the responses I see:
--- Begin response to inout SOAP message --
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml;charset=utf-8
Date: Fri, 09 Mar 2007 14:23:47 GMT
Server: Apache-Coyote/1.1
Connection: close
?xml version='1.0' encoding='utf-8'?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header /
soapenv:Body
soapenv:Fault
faultcodesoapenv:Client/faultcode
faultstringInout AxisFault/faultstring
detail /
/soapenv:Fault
/soapenv:Body
/soapenv:Envelope
--- End response to inout SOAP message
Cannot Infer Transport Error
Hello, I'm attempting to use Apache Axis2 1.1.1 to create a web service client for accessing remote web services. I am currently using WebLogic 8.1's built in web service client, but I would like to migrate away from this to Axis2. I used the WSDL2Java tool from the command line to generate the client stubs from the WSDL. So far, so good. I know the WSDL is valid because it's the same one I currently use in production using WebLogic's web service client. When I try to use the Axis2 generated stub to access the web service, it fails with this message: org.apache.axis2.AxisFault: No address information in EPR, cannot infer transport I did some web searching and EPR seems to to with endpoints, but I don't know where to go from here. According to the examples I should just be able to generate the client stub and go from there, but it's failing with this error. Like I said, I know the WSDL is valid because I currently use it in production. Can anybody shed some light on what's going wrong here? Thank you!! This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you.
Loading a resource from the classpath in Axis2 with Spring
Hello, I'm running Axis2 1.1.1 with Spring. I've got my ServiceTCCL set to composite (It'd be great to see some documentation on this; I know there are three settings, but I'm not exactly sure what each of them does). My problem is that I'm using iBATIS, which tries to load resources from the classpath. This doesn't work because it is not possible to set the ClassLoader that iBATIS uses (I think). (In my ServiceLifeCycle.startUp, I set Spring's ClassLoader like this: )appCtx.setClassLoader(service.getClassLoader()). So my question is, is there a solution for this? Right now, the only thing I can think of is to put the resources in the servlet's WEB-INF/classes directory. Also, as a side note, I am able to load the first iBATIS config file (because this is set in my Spring app context XML file), it's the files that this first config file references that cannot be read (this happens in iBATIS code). I tried to put all my config data in that first file, but iBATIS will not let you do this. Thanks for any help, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Loading a resource from the classpath in Axis2 with Spring
Ian, So if we enforce the ServiceTCCL/composite for startUp would that fix it? Please log a JIRA enhancement issue. thanks, dims On 3/9/07, Ian Shafer [EMAIL PROTECTED] wrote: Hello, I'm running Axis2 1.1.1 with Spring. I've got my ServiceTCCL set to composite (It'd be great to see some documentation on this; I know there are three settings, but I'm not exactly sure what each of them does). My problem is that I'm using iBATIS, which tries to load resources from the classpath. This doesn't work because it is not possible to set the ClassLoader that iBATIS uses (I think). (In my ServiceLifeCycle.startUp, I set Spring's ClassLoader like this: )appCtx.setClassLoader(service.getClassLoader()). So my question is, is there a solution for this? Right now, the only thing I can think of is to put the resources in the servlet's WEB-INF/classes directory. Also, as a side note, I am able to load the first iBATIS config file (because this is set in my Spring app context XML file), it's the files that this first config file references that cannot be read (this happens in iBATIS code). I tried to put all my config data in that first file, but iBATIS will not let you do this. Thanks for any help, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Loading a resource from the classpath in Axis2 with Spring
I assume he's already loading spring via startUp() as the tutorial suggests, does the idea you have add to that concept somehow ? The issue is I was never able to get xml files via the classpath found for hibernate inside the AAR - iBATIS and Hibernate both can be configured via spring. So the issue is you can pass files to spring as such: property name=mappingLocations valueclasspath*:**/MyEntity.hbm.xml/value /property Running in spring DEBUG mode with that config will show all the classpath locations . The issue AFAICT is that I was never able to get the lib dir inside the aar to be found by spring as a classpath location. Robert On 3/9/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Ian, So if we enforce the ServiceTCCL/composite for startUp would that fix it? Please log a JIRA enhancement issue. thanks, dims On 3/9/07, Ian Shafer [EMAIL PROTECTED] wrote: Hello, I'm running Axis2 1.1.1 with Spring. I've got my ServiceTCCL set to composite (It'd be great to see some documentation on this; I know there are three settings, but I'm not exactly sure what each of them does). My problem is that I'm using iBATIS, which tries to load resources from the classpath. This doesn't work because it is not possible to set the ClassLoader that iBATIS uses (I think). (In my ServiceLifeCycle.startUp, I set Spring's ClassLoader like this: )appCtx.setClassLoader(service.getClassLoader()). So my question is, is there a solution for this? Right now, the only thing I can think of is to put the resources in the servlet's WEB-INF/classes directory. Also, as a side note, I am able to load the first iBATIS config file (because this is set in my Spring app context XML file), it's the files that this first config file references that cannot be read (this happens in iBATIS code). I tried to put all my config data in that first file, but iBATIS will not let you do this. Thanks for any help, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - 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]
Bad request error: what's wrong?
Hi all, I'm getting this (very) strange error while trying to send the SOAP message listed below. Any clue? (the message is actually received, so I don't know what's going on) Thanks in advance, Michele INFO [18:07:38,178] BootstrapHelper:register - SOAP message is ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header node:qosp xmlns:node=http://ncl.ac.uk/qosp; node:messageTypeNewnode/node:messageType /node:qosp /soapenv:Header soapenv:Body node:addNode xmlns:node=http://ncl.ac.uk/qosp; node:name127.0.0.2:18080/node:name /node:addNode /soapenv:Body /soapenv:Envelope ERROR [18:07:40,586] NodeModule$ListenerThread:run - Unable to register to [http://localhost:8081/axis2/services/RoutingService] org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request' at ncl.qosp.modules.node.NodeModule $ListenerThread.run(NodeModule.java:211) Caused by: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request' at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:359) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:519) at org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:250) at ncl.qosp.modules.node.BootstrapHelper.register(BootstrapHelper.java:230) at ncl.qosp.modules.node.NodeModule $ListenerThread.run(NodeModule.java:208) Caused by: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request' at org.apache.axis2.transport.http.SOAPOverHTTPSender.sendViaPost(SOAPOverHTTPSender.java:202) at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:57) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:349) ... 5 more ncl.qosp.modules.node.NodeModule$ListenerThread.run(NodeModule.java:215) ERROR [Thread-1] - Unable to register to [http://localhost:8081/axis2/services/RoutingService] org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request' at ncl.qosp.modules.node.NodeModule $ListenerThread.run(NodeModule.java:211) Caused by: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request' at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:359) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:519) at org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:250) at ncl.qosp.modules.node.BootstrapHelper.register(BootstrapHelper.java:230) at ncl.qosp.modules.node.NodeModule $ListenerThread.run(NodeModule.java:208) Caused by: org.apache.axis2.AxisFault: HTTP Transport error: '400' - 'Bad Request' at org.apache.axis2.transport.http.SOAPOverHTTPSender.sendViaPost(SOAPOverHTTPSender.java:202) at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:57) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:349) ... 5 more - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bad request error: what's wrong?
Some more detail below but I think the message is correct, isn't it? INFO [18:15:28,745] BootstrapHelper:register - SOAP message is ?xml version='1.0' encoding='utf-8'?soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Headernode:qosp xmlns:node=http://ncl.ac.uk/qosp;node:messageTypeNew node/node:messageType/node:qosp/soapenv:Headersoapenv:Bodynode:addNode xmlns:node=http://ncl.ac.uk/qosp;node:name127.0.0.2:18080/node:name/node:addNode/soapenv:Body/soapenv:Envelope ERROR [18:15:28,802] NodeModule$ListenerThread:run - Unable to register to [http://localhost:8081/axis2/services/RoutingService] org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output at ncl.qosp.modules.node.NodeModule $ListenerThread.run(NodeModule.java:211) Caused by: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:359) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:519) at org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:250) at ncl.qosp.modules.node.BootstrapHelper.register(BootstrapHelper.java:230) at ncl.qosp.modules.node.NodeModule $ListenerThread.run(NodeModule.java:208) Caused by: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output; nested exception is: org.apache.axis2.AxisFault: Invalid null character in text to output; nested exception is: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:99) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:547)
Re: Unexpected creaton of an intermediate layer (wrapper class) by using Axis v1.1.1
Just to clarify, the limitation on unwrapping only parameters and not
responses in 1.1.1 applies to ADB. Using JiBX data binding gives full
unwrapping of both parameters and responses. XMLBeans doesn't support
unwrapping at all, AFAIK.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Paul Fremantle wrote:
Karl
The wrapping is basically part of how many toolkits create WSDLs these
days. Its based on an approach from Microsoft.
The simple answer is add -uw (unwrap) to your WSDL2Java command line.
In 1.1.1 this only unwraps parameters not responses but in 1.2 its
fixed to do both.
If you want to understand the convention more, this explanation from
Anne Thomas Manes is probably the clearest available:
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
Paul
On 3/9/07, Philipp, Karl [EMAIL PROTECTED] wrote:
Hi,
Using the invocation
%AXIS2_HOME%\bin\wsdl2java -uri addServicePort.wsdl -p danet -d adb -s
I created the stub AddServicePortServiceStub.java. Surprisingly an
additional intermediate layer represented by the class
AddService0(...) has been created. This class is needed for a proper
call of the service:
public AddServiceResponse addService(AddService0 param) {
EIMessageContext context =
param.getAddService().getEiMessageContext();
...
}
That is, the AddService0 wraps the original AddService class I'm
interested in. But why is this wrapping needed?
If I try the Axis2UserGuideService example
http://ws.apache.org/axis2/1_1_1/userguide-creatingclients.html#createcl
ients
such intermediate layers will be not created. For example there is no
TwoWayOneParameterEchoRequest0 class:
TwoWayOneParameterEchoResponse
TwoWayOneParameterEcho(TwoWayOneParameterEchoRequest param) {
...
}
At the present time we plan to migrate our connector from JBossWS to
Axis2. But the additional AddService0 class is a migration issue.
Is there an approach to avoid this wrapper class?
Because I used the same invocation as for the Axis2UserGuideService
example I guess it depends on the entries of the WSDL.
--
Karl
-
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: Loading a resource from the classpath in Axis2 with Spring
Ian-- The scenario seems to manifest by which context loader you are using to load the config file where a WebApplicationContext classLoader will favour loading from /WEB-INF but other contexts such as ClassPathXmlApplicationContext or FileSystemXmlApplicationContext favour either locating the configfile on CLASSPATH -or- absolute path (usually specified as file:some valid file URL path) Cheers, Martin-- --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. - Original Message - From: Ian Shafer [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Friday, March 09, 2007 12:12 PM Subject: Loading a resource from the classpath in Axis2 with Spring Hello, I'm running Axis2 1.1.1 with Spring. I've got my ServiceTCCL set to composite (It'd be great to see some documentation on this; I know there are three settings, but I'm not exactly sure what each of them does). My problem is that I'm using iBATIS, which tries to load resources from the classpath. This doesn't work because it is not possible to set the ClassLoader that iBATIS uses (I think). (In my ServiceLifeCycle.startUp, I set Spring's ClassLoader like this: )appCtx.setClassLoader(service.getClassLoader()). So my question is, is there a solution for this? Right now, the only thing I can think of is to put the resources in the servlet's WEB-INF/classes directory. Also, as a side note, I am able to load the first iBATIS config file (because this is set in my Spring app context XML file), it's the files that this first config file references that cannot be read (this happens in iBATIS code). I tried to put all my config data in that first file, but iBATIS will not let you do this. Thanks for any help, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unexpected creaton of an intermediate layer (wrapper class) by using Axis v1.1.1
Thanks for the clarification Dennis. I assumed it was generic - my bad.
Paul
On 3/9/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
Just to clarify, the limitation on unwrapping only parameters and not
responses in 1.1.1 applies to ADB. Using JiBX data binding gives full
unwrapping of both parameters and responses. XMLBeans doesn't support
unwrapping at all, AFAIK.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Paul Fremantle wrote:
Karl
The wrapping is basically part of how many toolkits create WSDLs these
days. Its based on an approach from Microsoft.
The simple answer is add -uw (unwrap) to your WSDL2Java command line.
In 1.1.1 this only unwraps parameters not responses but in 1.2 its
fixed to do both.
If you want to understand the convention more, this explanation from
Anne Thomas Manes is probably the clearest available:
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
Paul
On 3/9/07, Philipp, Karl [EMAIL PROTECTED] wrote:
Hi,
Using the invocation
%AXIS2_HOME%\bin\wsdl2java -uri addServicePort.wsdl -p danet -d adb -s
I created the stub AddServicePortServiceStub.java. Surprisingly an
additional intermediate layer represented by the class
AddService0(...) has been created. This class is needed for a proper
call of the service:
public AddServiceResponse addService(AddService0 param) {
EIMessageContext context =
param.getAddService().getEiMessageContext();
...
}
That is, the AddService0 wraps the original AddService class I'm
interested in. But why is this wrapping needed?
If I try the Axis2UserGuideService example
http://ws.apache.org/axis2/1_1_1/userguide-creatingclients.html#createcl
ients
such intermediate layers will be not created. For example there is no
TwoWayOneParameterEchoRequest0 class:
TwoWayOneParameterEchoResponse
TwoWayOneParameterEcho(TwoWayOneParameterEchoRequest param) {
...
}
At the present time we plan to migrate our connector from JBossWS to
Axis2. But the additional AddService0 class is a migration issue.
Is there an approach to avoid this wrapper class?
Because I used the same invocation as for the Axis2UserGuideService
example I guess it depends on the entries of the WSDL.
--
Karl
-
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]
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
Oxygenating the Web Service Platform, www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports
Funny thing is I was just coming to the list to get clarification on this. I poured through the specs and couldn't find where it was explicitly stated as illegal. So, then I assume Amila's fix is the official correction of the problem. Thanks everyone for your input. --- Anne Thomas Manes [EMAIL PROTECTED] wrote: I asked for clarification on the xml-dev list. Michael Kay concurs with Dennis. Duplicate child elements are allowed, even when elementFormDefault=qualified. Anne On 3/8/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: Maybe we should ask for clarification from Priscilla on this, but my intepretation of Locally scoped attribute and element declarations is that the rule refers only to unqualified attributes and elements. If you specify elementFormDefault=qualified, then all elements in the schema are globally scoped unless you specify form=unqualified on a specific element. Anne On 3/8/07, Dennis Sosnoski [EMAIL PROTECTED] wrote: Hi Amila, No, there is no such constraint. Schema actually states explicitly (http://www.w3.org/TR/xmlschema-1/#concepts-nameSymbolSpaces) that: Locally scoped attribute and element declarations are special with regard to symbol spaces. Every complex type definition defines its own local attribute and element declaration symbol spaces, where these symbol spaces are distinct from each other and from any of the other symbol spaces. So, for example, two complex type definitions having the same target namespace can contain a local attribute declaration for the unqualified name priority, or contain a local element declaration for the name address, without conflict or necessary relation between the two. Like most parts of the schema specification, this doesn't appear to be written for clarity. Why the gratuitous reference to unqualified name when referring to the attribute, for instance, when it doesn't make any difference whether the name is qualified or unqualified? But the statement that each complex type definition defines its own local attribute and element declaration symbol spaces is as clear and definite as anything in schema. To make things even more complicated, according to Priscilla Walmsley (Definitive XML Schema, 13.4.4 Duplication of element-type names) you can reuse the same element name within a particular complex type definition providing the elements have the same type. This apparently means that it's fine to do a definition of the type: complexType sequence element name=name type=string/ element name=id type=long/ element name=name type=string/ /sequence /complexType I don't know the particular entrails which were read to come to this conclusion (which I haven't found documented in the schema recommendation), but since she's part of the Schema Working Group her statements on schema are generally considered authoritative. Something to keep in mind when you're writing your code to handle complex types. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Amila Suriarachchi wrote: On 3/8/07, *Dennis Sosnoski* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Your statement about the names is incorrect, Anne. Schema doesn't allow the same name to be used for different global definitions, but you're fine reusing names for local elements in different complexTypes. I am also not clear about this and would like to put this question? Is there any constranit that says *every element in schema should have a unique Qutalified name?* since the qualified name of an element only depends on the namespace and the local part of the element then we have to conclude that it is not possible. -- Amila Suriarachchi, WSO2 Inc. - 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] No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports
Sorry I didn't notice your earlier response on this, Anne. The schema specification is explicit that each complex type defines its own symbol spaces for the element and attribute definitions within that type, as I quoted. The locally scoped reference just means that it's not a top-level child of the schema element - top-level children of the schema are global definitions (and globally-scoped, meaning they're visible throughout the schema and also when the schema is included or imported), everything else is a local definition. The added part that I referenced Priscilla on was just that the same element or attribute name could be reused within a single complex type definition, providing all uses specify the same type. That's something I haven't found as part of the schema specification, but was passing on to Amila as something to keep in mind when implementing the code. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Anne Thomas Manes wrote: I asked for clarification on the xml-dev list. Michael Kay concurs with Dennis. Duplicate child elements are allowed, even when elementFormDefault=qualified. Anne On 3/8/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: Maybe we should ask for clarification from Priscilla on this, but my intepretation of Locally scoped attribute and element declarations is that the rule refers only to unqualified attributes and elements. If you specify elementFormDefault=qualified, then all elements in the schema are globally scoped unless you specify form=unqualified on a specific element. Anne On 3/8/07, Dennis Sosnoski [EMAIL PROTECTED] wrote: Hi Amila, No, there is no such constraint. Schema actually states explicitly (http://www.w3.org/TR/xmlschema-1/#concepts-nameSymbolSpaces) that: Locally scoped attribute and element declarations are special with regard to symbol spaces. Every complex type definition defines its own local attribute and element declaration symbol spaces, where these symbol spaces are distinct from each other and from any of the other symbol spaces. So, for example, two complex type definitions having the same target namespace can contain a local attribute declaration for the unqualified name priority, or contain a local element declaration for the name address, without conflict or necessary relation between the two. Like most parts of the schema specification, this doesn't appear to be written for clarity. Why the gratuitous reference to unqualified name when referring to the attribute, for instance, when it doesn't make any difference whether the name is qualified or unqualified? But the statement that each complex type definition defines its own local attribute and element declaration symbol spaces is as clear and definite as anything in schema. To make things even more complicated, according to Priscilla Walmsley (Definitive XML Schema, 13.4.4 Duplication of element-type names) you can reuse the same element name within a particular complex type definition providing the elements have the same type. This apparently means that it's fine to do a definition of the type: complexType sequence element name=name type=string/ element name=id type=long/ element name=name type=string/ /sequence /complexType I don't know the particular entrails which were read to come to this conclusion (which I haven't found documented in the schema recommendation), but since she's part of the Schema Working Group her statements on schema are generally considered authoritative. Something to keep in mind when you're writing your code to handle complex types. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Amila Suriarachchi wrote: On 3/8/07, *Dennis Sosnoski* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Your statement about the names is incorrect, Anne. Schema doesn't allow the same name to be used for different global definitions, but you're fine reusing names for local elements in different complexTypes. I am also not clear about this and would like to put this question? Is there any constranit that says *every element in schema should have a unique Qutalified name?* since the qualified name of an element only depends on the namespace and the local part of the element then we have to conclude that it is not possible. -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL
Re: [AXIS1.4] Deploy and sart StockQuoteService.java
I can't help you exactly with your specific problem (although it seems strange that your class is named org.apache.axis.client.AdminClient and yet the error says it can't find org.sample.axis.AdminClient) but one recommendation I would have is to see if you can use Apache Ant for your build, deployment, and execution tasks. This way, you don't have to worry about your AXISCLASSPATH working (you define your libraries within the Ant build script) and you won't have to memorize the syntax of the various commands because everything is written down in the Ant build script. Also, I am unsure but I believe Ant has a verbose debugging option that lists classes it can find while running, which may help in fixing your current problem. Glen Am Freitag, den 09.03.2007, 12:38 +0100 schrieb [EMAIL PROTECTED]: Hi! I don't know very well how to use correctly Axis 1.4. I'm trying to deploy StockQuoteService.java placed into axis-1_4\webapps\axis\WEB-INF\classes\samples\stock folder with this deploy file deploy-base.wsdd placed in the same folder: deployment name=test xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; service name=xmltoday-delayed-quotes-base provider=java:RPC style=document use=literal parameter name=className value=samples.stock.StockQuoteService/ parameter name=allowedMethods value=getQuote/ parameter name=scope value=application/ /service /deployment I wrote a file .bat in the same folder: java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient samples/stock/server/deploy-base where axisclasspath is an environment variable that containe all .jar files paths in lib folder. But i have this error: Exception in thread main java.lang.noclassdefounderror org/sample/Axis/AdminClient When i'll solve this problem will be correct this way to start it? java -cp %AXISCLASSPATH% samples.stock.client.StockServiceClient XXX http://localhost:8080/axis/services/xmltoday-delayed-quotes-base Many thanks to all Antonio -- Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind http://i-mode.wind.it - 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: Cannot Infer Transport Error
Just a guess, but in the below tutorial[1], do a search on the word transport within listing #21 (on page 4.) This is the code I see there: wsdl:binding name=ClassifiedServiceBinding type=tns:ClassifiedServicePortType soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document / ... Do you have something like this in your wsdl? Glen [1] http://www-128.ibm.com/developerworks/edu/ws-dw-ws-understand-web-services2.html Am Freitag, den 09.03.2007, 10:22 -0600 schrieb Asleson, Ryan: Hello, I'm attempting to use Apache Axis2 1.1.1 to create a web service client for accessing remote web services. I am currently using WebLogic 8.1's built in web service client, but I would like to migrate away from this to Axis2. I used the WSDL2Java tool from the command line to generate the client stubs from the WSDL. So far, so good. I know the WSDL is valid because it's the same one I currently use in production using WebLogic's web service client. When I try to use the Axis2 generated stub to access the web service, it fails with this message: org.apache.axis2.AxisFault: No address information in EPR, cannot infer transport I did some web searching and EPR seems to to with endpoints, but I don't know where to go from here. According to the examples I should just be able to generate the client stub and go from there, but it's failing with this error. Like I said, I know the WSDL is valid because I currently use it in production. Can anybody shed some light on what's going wrong here? Thank you!! This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Loading a resource from the classpath in Axis2 with Spring
Am Freitag, den 09.03.2007, 09:12 -0800 schrieb Ian Shafer: Also, as a side note, I am able to load the first iBATIS config file (because this is set in my Spring app context XML file), it's the files that this first config file references that cannot be read (this happens in iBATIS code). I tried to put all my config data in that first file, but iBATIS will not let you do this. There are other ways to store multiple configuration files in your app context XML file--I don't know if you have tried this, maybe it would help: http://www.jroller.com/page/gmazza?entry=refactoring_the_spring_mvc_web Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not able to generate code
For some reason I've had problems getting wsdl2java.sh to work on my
machine (using Ubuntu Linux) as well. What I did instead is use the
underlying command that wsdl2java.sh consists of:
./axis2.sh org.apache.axis2.wsdl.WSDL2Java {rest of parameters}
and had more success with it.
A better long-term solution IMHO though is to just use Apache Ant[1] and
keep all the parameters you used in a build file, so there's nothing to
forget a few weeks/months down the road when you need to run this again.
HTH,
Glen
[1] http://ws.apache.org/axis2/tools/1_0/CodegenToolReference.html#ant
Am Freitag, den 09.03.2007, 16:32 +0100 schrieb José Antonio Sánchez:
Hello. I'm using Axis2 1.1 to generate code for a service. I use the
following command:
/opt/axis2-1.1/bin/wsdl2java.sh -uri ./wsdl/wsctx.wsdl -ss -g -sn
PriorService -o ./PriorService
But got the following output:
Using AXIS2_HOME: /opt/axis2-1.1
Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun-1.5.0.08
Unrecognized option: -uri
Could not create the Java virtual machine.
What's the problem? The shown paths are ok but it complains that uri
is not a valid option while in the documentation says:
WSDL2Code -uri Location of WSDL
and also in the tutorial, the first example is:
%AXIS2_HOME%\bin\wsdl2java -uri Axis2UserGuide.wsdl -p
org.apache.axis2.axis2userguide -d adb -s
So -uri option must be understood by Axis.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
