[axis2] WSDL2C support for any type elements (InvocationTargetException)
Hi folks, did anyone run into problems with converting WSDL to C structures a document containing 'any' elements? I have the same problem submitted as a bug (https://issues.apache.org/jira/browse/AXIS2C-643). This bug is claimed to be resolved in the latest svn. So I've downloaded the latest binary snapshot (05.11.07), run WSDL2C tool on the example.wsdl file (taken from the bug description) and... guess what, the InvocationTargetException still remains. Does anyone have a clue? I'm using Java 1.5, but it's not related to the problem, I guess... Regards, Michal signature.asc Description: OpenPGP digital signature
Re: Axis2C: WSDL2C not properly handling attributes
Yes, I still see the problem when using Adder.wsdl. See below for an
example serialize method. Also, how do I update woden.jar? I'm working
with an axis2java snapshot from last week that I think has the most recent
version of woden. Or, am I missing something?
axiom_node_t* AXIS2_CALL
adb_matrixAddResponse_serialize(
adb_matrixAddResponse_t* _matrixAddResponse,
const axutil_env_t *env, axiom_node_t* parent, int
parent_tag_closed)
{
axiom_namespace_t *ns1 = NULL;
axis2_char_t text_value_1[64];
axiom_node_t *current_node = NULL;
axiom_element_t *current_element = NULL;
axis2_char_t *start_input_str = NULL;
axis2_char_t *end_input_str = NULL;
unsigned int start_input_str_len = 0;
unsigned int end_input_str_len = 0;
axiom_data_source_t *data_source = NULL;
axutil_stream_t *stream = NULL;
AXIS2_ENV_CHECK(env, NULL);
ns1 = axiom_namespace_create (env,
http://ws.apache.org/axis2;,
ns3);
current_element = axiom_element_create (env, NULL,
matrixAddResponse, ns1 , current_node);
axiom_element_set_namespace(current_element, env, ns1,
current_node);
ns1 = axiom_namespace_create (env,
http://ws.apache.org/axis2/xsd;,
ns1);
axiom_element_declare_namespace(current_element, env,
current_node, ns1);
parent = current_node;
data_source = axiom_data_source_create(env, parent,
current_node);
stream = axiom_data_source_get_stream(data_source,
env);
/*
* parsing return element
*/
start_input_str = ns3:return
xmlns:ns1=\http://ws.apache.org/axis2/xsd\;;
start_input_str_len =
axutil_strlen(start_input_str);
end_input_str = /ns3:return;
end_input_str_len = axutil_strlen(end_input_str);
axutil_stream_write(stream, env,
start_input_str, start_input_str_len);
adb_Matrix_serialize(_matrixAddResponse-property_return,
env, current_node,
AXIS2_FALSE
);
axutil_stream_write(stream, env,
end_input_str, end_input_str_len);
return parent;
}
Thanks again,
Mike
Michael J Molé
Software Engineer
IBM Software Group - Rational
(781)676-2710
Dimuthu Gamage [EMAIL PROTECTED]
11/06/2007 03:46 AM
Please respond to
Apache AXIS C User List axis-c-user@ws.apache.org
To
Apache AXIS C User List axis-c-user@ws.apache.org
cc
Subject
Re: Axis2C: WSDL2C not properly handling attributes
Hi,
With my wsdls I didnt found such a problem:(. For now please try generate
with the Adder.wsdl in the case2.tar.gz that I sent earlier and check
whether the same issue exist. If so it s better to update woden jar and
try.
Thanks
Dimuthu
On 11/5/07, Michael Mole [EMAIL PROTECTED] wrote:
Hey Dimuthu,
My WSDL does specify a soapAction. Also, this was working until I moved
to the nightly snapshot from last week.
My WSDL looks something like this:
operation name=foo
soap:operation soapAction=http://ibm.com/foo/
input
soap:body parts=body use=literal
namespace=http://ibm.com/fooservice;
encodingStyle=http://schemas.xmlsoap.org/soap/encoding//
/input
output
soap:body parts=body use=literal
namespace=http://ibm.com/fooservice;
encodingStyle=http://schemas.xmlsoap.org/soap/encoding//
/output
fault name=fault
soap:fault name=fault use=literal
encodingStyle=http://schemas.xmlsoap.org/soap/encoding//
/fault
/operation
Thanks again,
Mike
Michael J Molé
Software Engineer
IBM Software Group - Rational
(781)676-2710
Dimuthu Gamage [EMAIL PROTECTED]
11/02/2007 10:10 PM
Please respond to
Apache AXIS C User List axis-c-user@ws.apache.org
To
Apache AXIS C User List axis-c-user@ws.apache.org
cc
Subject
Re: Axis2C: WSDL2C not properly handling attributes
Hi Michael,
This happens when the soapAction in the WSDL is empty or just doesn't
exist. E.g. soap:operation soapAction= style=document/
In this case it doesnt matter either the soap_action = \\ or
soap_action = , axis2/c always sends the SOAPAction: in the http
headers in the soap request. So I think it is not a bug:).
Thanks
Dimuthu
On 11/3/07, Michael Mole [EMAIL PROTECTED] wrote:
Hey Dimuthu,
One other thing I'm noticing
Re: Urgent: Specifying scope in Axis2c
Hi Subra, On Nov 6, 2007 10:57 PM, Subra A Narayanan [EMAIL PROTECTED] wrote: Hello Samisa, Do you have any updates on this issue? Do you have an approximate time frame when this issue would be fixed in the framework? Is this feature under development? I have looked into this and proposed a solution to this on dev list. However, as of now, I find it difficult to find time to attend to this. I have to check if any other developer is attending this. I cannot gaurentee if the proposed solution would work, as we have to implemnt and see it in action to verify that it works. Given the risk, I would propose that you look in to a database driven solution for the time being until this is solved as I recommended earlier. As I mentioned, Savan module had done something similar, so that you can get an idea form that to solve this temporarily. Thanks, Samisa... This capability is very important for the application I am working on. If it wont't be fixed in the framework anytime soon, I will have to come up with a fix in my code. Your help is much appreciated. Subra On 10/12/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Subra A Narayanan wrote: thanks samisa. where would i store such a flag? service group context like in the add.c example from sg_math service? Nop, if you do that, I think you will get the same problem again. I think you may have to use a database to do that. Savan module, the WS-Eventing module, came across such a problem and used sqlite. Can someone please explain how it was done in Savan? In the mean time, the matter is discussed on dev list, and would have a solution for this. Thanks, Samisa... On 10/11/07, *Samisa Abeysinghe* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Subra A Narayanan wrote: Hello everyone, I have run in to an issue which I can't seem to figure out. In my init method in the service skeleton I call the initialization routine of one of the libraries that my web service uses. I notice in my logs that the library initialization function is being called 8 times. This corresponds to the number of apache processes that are running. This is a problem yet to be solved in Axis2/C. See http://damithakumarage.wordpress.com/2007/09/23/an-axis2-c-design-issue/. This is a pending issue that needs to be fixed. The workaround for the time being would be to use some persistent storage to keep a flag and call the init routine based on the flag value. Samisa... This is causing a lot of issues because I was under the impression that my web service init function is called only once when the first request comes in. My library sets up some resources which I want to share among all processes. Can this be done? In Axis2/Java there is a way to specify scope for the webservice (request, session, application) in the services.xml file? can something similar be done in Axis2/c? I took a look at the axis2c code and saw that there is an enum called axis2_scope defined. Is it used for the same purpose as in Axis2/Java? Thanks for any help. Subra -- Samisa Abeysinghe : WSO2 WSF/PHP http://wso2.org/projects/wsf/php?WSO2nbsp;Webnbsp;Servicesnbsp;Framework%2FPHPnbsp;-nbsp;Opennbsp;sourcenbsp;PHPnbsp;extentionnbsp;fornbsp;providingnbsp;andnbsp;consumingnbsp;Webnbsp;servicesnbsp;innbsp;PHP http://wso2.org/projects/wsf/php?WSO2nbsp;Webnbsp;Servicesnbsp;Framework%2FPHPnbsp;-nbsp;Opennbsp;sourcenbsp;PHPnbsp;extentionnbsp;fornbsp;providingnbsp;andnbsp;consumingnbsp;Webnbsp;servicesnbsp;innbsp;PHP - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Samisa Abeysinghe : WSO2 WSF/PHP http://wso2.org/projects/wsf/php?WSO2nbsp;Webnbsp;Servicesnbsp;Framework%2FPHPnbsp;-nbsp;Opennbsp;sourcenbsp;PHPnbsp;extentionnbsp;fornbsp;providingnbsp;andnbsp;consumingnbsp;Webnbsp;servicesnbsp;innbsp;PHP - 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]
[Axis2] How to enforce AxisFault message to MTOM encoded?
Hi, Microsoft WSE3 requires that MTOM is to be used either not at all or for every message involved in a request (the reasoning behind this can questioned ...). So in order to work with WSE3 and MTOM, WSE3 expects all input-, output- and possible error message as MTOM encoded message. Thilina recently helped me out on how to enforce the output encoding to be MTOM if input is also MTOM, using this kind of code: MessageContextinMessageContextL= MessageContext.getCurrentMessageContext(); OperationContextoperationContextL= inMessageContextL.getOperationContext(); MessageContextoutMessageContextL= operationContextL.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE); booleanisInputMtomL= inMessageContextL.isDoingMTOM(); outMessageContextL.setProperty(Constants.Configuration.ENABLE_MTOM, isInputMtomL); The problem I now encounter is that WSE3 also expects AxisFaults to be dummy-encoded in MTOM. In ...MessageReceiverInOut.java I have tried to use code similar to the above like MessageContextinMessageContextL= MessageContext.getCurrentMessageContext(); OperationContextoperationContextL= inMessageContextL.getOperationContext(); MessageContextoutMessageContextL= operationContextL.getMessageContext(WSDLConstants.MESSAGE_LABEL_FAULT_VALUE); booleanisInputMtomL= inMessageContextL.isDoingMTOM(); outMessageContextL.setProperty(Constants.Configuration.ENABLE_MTOM, isInputMtomL); which did not work. Neither did a msgContext.setProperty(Constants.Configuration.ENABLE_MTOM, isInputMtomL); in the catch-handler of invokeBusinessLogic() do it. The AxisFault is always formatted as XML/Text message. I would appreciate if anybody could give me a hint on how to resolve this final issue. Axis seems to be flexible enough to compensate the peculiarities of other well-known vendor's software. Thanks, -Rainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Timeout issues
Hi, We're using Eclipse 3.3.0 to generate code from WSDL's. It uses Axis 1.4. The code seems to be generated fine and we can compile it execute the web services fine. However, when the web service is not available, it just hangs and doesn't timeout. We have a wrapper transaction in WebSphere that eventually times out after approx 12 minutes, but why doesn't the Axis client code time out? I looked at the generated stub code and if you do a getTimeout() in the stub, it returns 0. If I put a setTimeout(15000) in the constructors of the stub, the call to the web service times out nicely after the expected 15 seconds with a SocketTimeoutException message. That's what we want. I was under the impression that Axis has a default 60 second timeout? Why doesn't this kick in? Is there a way to set timeouts by not fiddling in the generated stub code? We want do not want to touch generated code - its all part of a big ant build process and a manual step would not be ideal. Any help or suggestions? Thanks! Charl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: port name and binding name overwriting
Here are a pair of WSDL files and an Ant file to generate the Java. Ant libraries (jar files) should be in a directory called axis_lib. My current version is Axis2 1.3 (downloaded 13/09/2007). Reminder: the issue is when port and binding have the same name, generated Java files are overwritten. Note that the same WSDL files have been tested with Axis (1.2) and JAX-WS RI and work fine in both cases. In fact these WSDLs have been derived from production ones. * Results from the diff version: - port and binding have different names - The generated code doesn't compile. I don't know why. I'd say it is a distinct problem. Any idea to make it compile? - There are two stubs: * BuzzerSoapBindingStub, which may be used by a client to invoke the service * BuzzerSoapStub, which is the interface of the service * Results from the same version: - in the same version, port and binding have the same name. There is a missing class, the binding stub class (for calling the service). Obviously, it seems to have been overwritten by the interface stub. - note that if we use overwrite=true, the overwrite is the other way round: we have the binding stub class, but not the interface! Any help would be appreciated. Julien -Message d'origine- De : Amila Suriarachchi [mailto:[EMAIL PROTECTED] Envoyé : mardi 6 novembre 2007 05:32 À : axis-user@ws.apache.org Objet : Re: port name and binding name overwriting can you send your wsdl or a sample wsdl to show the problem? Amila. On 11/5/07, ROBINSON JULIEN [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all, I'm generating code from a WSDL using org.apache.axis2.tool.ant.AntCodegenTask In my WSDL, the service definition looks like this: wsdl:service name=someService wsdl:documentationBlabla/wsdl:documentation wsdl:port name=someServiceSoap binding=myns:someServiceSoap soap:address location=http://localhost:8080/jarname/services/some / /wsdl:port /wsdl:service Note that the port name and binding name are the same. This works fine for Axis 1 and JAX-WS RI, but Axis2 generates two classes, one for the port type (interface describing the port) and one for the binding (utility for calling an instance). Problem is, one of these classes overwrites the other one! So that the other one, overwritten, is missing in the generated package. I have several WSDL files in my project, some are editable but others are legacy, and I don't want to edit them. Plus, as I said, this works fine with other tools. Is there any way, possibly a bug fix or simply a configuration of the WSDL2Java (codegen) task, for a workaround? Perhaps to tell it to generate binding somewhere else? Thanks for any tips! Julien ?xml version=1.0 ? project name=Axis2 duplicate test default=runtest basedir=. path id=axis2.classpath fileset dir=axis_lib include name=**/*.jar/ /fileset /path target name=init mkdir dir=diff/ mkdir dir=same/ /target target name=clean delete dir=diff/ delete dir=same/ /target taskdef name=axis2-wsdl2java classname=org.apache.axis2.tool.ant.AntCodegenTask classpathref=axis2.classpath/ presetdef name=mywsdl2java axis2-wsdl2java targetresourcesfolderlocation=ressources targetsourcefolderlocation=src language=java synconly=true serverside=true generateservicexml=true generateallclasses=true unpackClasses=true serverSideInterface=true allports=false testcase=no unwrap=true backwardcompatible=true / /presetdef target name=wsdl2java_same depends=init mywsdl2java wsdlfilename=buzzer_same.wsdl output=same/output/ /target target name=wsdl2java_diff depends=init mywsdl2java wsdlfilename=buzzer_diff.wsdl output=diff/output/ /target target name=runtest depends=wsdl2java_diff, wsdl2java_same/ /project buzzer_diff.wsdl Description: buzzer_diff.wsdl buzzer_same.wsdl Description: buzzer_same.wsdl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 sample - pojoguide Unexpected EOF in prolog
Hi Martin, Thank you for your suggestions. I still the get the same prolog error for the pojoguide sample I checked and tried various ideas along with your suggestions without a sample client working. I dont believe CHUNKED_ENCODING is enabled as a default?.. to verify please display contents of %CATALINA_HOME%/webapps/axis2/WEB-INF/conf/axis2.xml Also prolog error codes are caused by the parser so verifying the version of xerces is critical My xerces is located at %CATALINA_HOME%/webapps/axis2/WEB-INF/lib/xercesImpl-2.8.1.jar (i.e. Xerces version 2.8.1) Martin 1.) I un-installed the windows Tomcat installation and downloaded the tomcat5.5.25 zip and moved it on c/tomcat 2.) using notepad %CATALINA_HOME%/webapps/axis2/WEB-INF/conf/axis2.xml my axis2.xml shows that encoding check is enabled. part of the standard axis2.xml .. transportSender name=tcp class= org.apache.axis2.transport.tcp.TCPTransportSender/ transportSender name=local class= org.apache.axis2.transport.local.LocalTransportSender/ transportSender name=http class= org.apache.axis2.transport.http.CommonsHTTPTransportSender parameter name=PROTOCOLHTTP/1.1/parameter parameter name=Transfer-Encodingchunked/parameter .. 3.) I used filemon.exe and traced the startup of Tomcat 12:26:13java.exe:3000READ C:\apache- tomcat-5.5.25\webapps\axis2\WEB-INF\conf\axis2.xmlSUCCESSOffset: 0 Length: 24161 to check that the correct file was read. 4.) I used filemon to trace the run of sample pojoguide ant rpc.client.run 12:30:41java.exe:3760READC:\apache- tomcat-5.5.25\webapps\axis2\WEB-INF\lib\xercesImpl-2.8.1.jarSUCCESS Offset: 1123181 Length: 89762 to check that the correct file was read. The xeces*.jar and the axis2.xml seem to be correct and in the right place Maybe there is something else incorrectly configured? Is there any way to get more tracing information after the call to serviceClient.invokeRobust(opSetWeather, opSetWeatherArgs); ? Is there a site where I could compare my installation against a working one? Rick
Axis2 and JAXB
Hi at all I try to use a JAXB implementation inside axis2, but I did not get it to run. There comes ever the Exception package doesnt contain ObjectFactory.class or jaxb.index, but there is a ObjectFactory.class file in the definied package. The same implementation works fine outside of axis2. I tried to make a package of the classes generated by xjc and set this package to the lib-folder of the aar-archive, but there is the same exception. Can anyone help? Many thanks kind regards, -- Oliver Hirschi http://www.FamilyHirschi.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Timeout issues
Charl, Why don't you call setTimeout() on the Stub reference that you use in the client code? E.g. ... ExampleAxisService_ServiceLocator locator = new ExampleAxisService_ServiceLocator(); ExampleAxisServiceSoapBindingStub myStub = (ExampleAxisServiceSoapBindingStub)locator.getExampleAxisService(); myStub.setMaintainSession(true); myStub.setTimeout(1000); ... Or, if you call the service more dynamically (that is, you create a Call object yourself) you can set the timeout on the Call reference as well. You don't need to change the generated stub class. -jeff -Original Message- From: Charl Gerber [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 5:07 AM To: axis-user@ws.apache.org Subject: Timeout issues Hi, We're using Eclipse 3.3.0 to generate code from WSDL's. It uses Axis 1.4. The code seems to be generated fine and we can compile it execute the web services fine. However, when the web service is not available, it just hangs and doesn't timeout. We have a wrapper transaction in WebSphere that eventually times out after approx 12 minutes, but why doesn't the Axis client code time out? I looked at the generated stub code and if you do a getTimeout() in the stub, it returns 0. If I put a setTimeout(15000) in the constructors of the stub, the call to the web service times out nicely after the expected 15 seconds with a SocketTimeoutException message. That's what we want. I was under the impression that Axis has a default 60 second timeout? Why doesn't this kick in? Is there a way to set timeouts by not fiddling in the generated stub code? We want do not want to touch generated code - its all part of a big ant build process and a manual step would not be ideal. Any help or suggestions? Thanks! Charl - 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: Referring to Creating Web Services with Apache Axis -- 5/22/2002
When I installed Axis2, it didn't require for an separate install of Zerces. I just followed the directions per the Axis2 home page. I ran the Java2WSDL and WSDL2Java both did not require anything else being intalled. Why do I need Zerces?? Teresa -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, November 05, 2007 5:23 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: Referring to Creating Web Services with Apache Axis -- 5/22/2002 which version xerces are you running ? M-- - Original Message - From: Teresa mailto:[EMAIL PROTECTED] Canales To: axis-user@ws.apache.org ; [EMAIL PROTECTED] Sent: Monday, November 05, 2007 4:18 PM Subject: Referring to Creating Web Services with Apache Axis -- 5/22/2002 I was going through your article written in 2002 on Apache Axis. Since then Axis2 has come out. I am new to Axis2 and Web Services. I was trying to follow the steps you wrote for Axis2. I was going through step 2 -- Java2WSDL: Generate WSDL File For the Given Fibonacci Interface. I ran the following for Axis2. C:\Documents and Settings\tcanales\workspace\Fibonacci\bin%AXIS2_HOME%\bin\Java 2WSDL -o fib.wsdl -l http://localhost:8080/axis/services/fibonacci; -tn urn: fibonacci -tp fibonacci -cn fibonacci.Fibonacci It created the attached wsdl. Then I tried to run the third step 3 -- WSDL2Java: Generate the Server-side Wrapper Code and Stubs For Easy client Access. I ran it with C:\Documents and Settings\tcanales\workspace\Fibonacci\bin%AXIS2_HOME%\bin\WSDL 2Java -o . -p fibonacci.ws -uri fib.wsdl I get the following error: Using AXIS2_HOME: C:\Teresa\Downloads\Axis\axis2-1.3 Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_13 Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat ionEngine.java:150) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Pars er SAX Error: org.xml.sax.SAXException: Fatal Error: URI= file:///C:/Documents%20 and%20Settings/tcanales/workspace/Fibonacci/bin/fib.wsdl Line=1: Content is not allowed in prolog. at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile( CodeGenerationEngine.java:292) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat ionEngine.java:105) ... 2 more Caused by: org.xml.sax.SAXException: Fatal Error: URI= file:///C:/Documents%20and %20Settings/tcanales/workspace/Fibonacci/bin/fib.wsdl Line=1: Content is not all owed in prolog. at org.apache.axis2.util.XMLUtils$ParserErrorHandler.fatalError(XMLUtils .java:390) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispat ch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un known Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:205) at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:250) at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:233) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile( CodeGenerationEngine.java:285) ... 3 more I think I have to run Java2WSDL with different options and that may be the reason for the problem in WSDL2Java. Can you tell me what I am doing wrong?? If I need to email someone else please let me know. Thanks, Teresa Canales Fibonacci.wsdl _ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSDL-document indirection in ServiceClient
WSDL4J provides the WSDLLocator interface to provide an extensible mechanism for providing WSDL content. This would be helpful for situations in which WSDL content must be provided from some unusual repository such as a database or custom dispatching or generating mechanism. However, when org.apache.axis2.client.ServiceClient instances are created for a particular service, they require either a URL for the wsdl or an already-parsed Definition. Adding an additional constructor which takes a WSDLLocator as an argument and being able to pass that argument through to the AxisService.createClientSideAxisService() method that actually cracks the WSDL, would be beneficial. If there is some interest beyond my own in having this capability, I'm can probably contribute it. Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Configuration to use my WSDL rather than AXIS generated WSDL
All: I am having some interoperability problems with a .NET client, and they've suggested that it's because of the changes that AXIS makes to my WSDL when the services are published. I'd like to make the services use the original WSDL, and it looks like there used to be a way to do that in the server-config.wsdd file. Is there a corollary to that for Axis 2? Thanks, Jennifer Ford - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Please remove me from this list EOM
Kishore, Send a mail to [EMAIL PROTECTED] Thanks Raghu From: Kishore Reddy Vaddipalle [mailto:[EMAIL PROTECTED] Sent: Monday, November 05, 2007 8:28 PM To: axis-user@ws.apache.org Subject: Please remove me from this list EOM CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS***
Exception Handling
I am looking at exceptions/faults, and I noticed that the fault handling
sample returns a SOAP exception with attached data in addition to the
code/error that is normally returned.
Is there a way to return custom SOAP exceptions that can be caught at
the client side as an Exception inherited class? i.e.,
Server-side code and Wsdl contain: MyCustomBusinessException extends
Exception
Client contains:
try {
..
svc.callMyService();
} catch (MyCustomBusinessException mcbe) {
} catch (Exception e) {
}
Thanks,
Nadeem
RE: Configuration to use my WSDL rather than AXIS generated WSDL
Thanks for your help! When I did that, I got the following when I clicked on the service link from the listServices page: - error descriptionUnable to generate WSDL 1.1 for this service/description reasonIf you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml/reason /error I would have thought it would just display the WSDL I gave it in the resources directory. Is that incorrect? Is there another location where it is expected? Thanks, Jennifer -Original Message- From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 12:08 PM To: axis-user@ws.apache.org Subject: RE: Configuration to use my WSDL rather than AXIS generated WSDL In the services.xml there is a parameter named useOriginalwsdl, set that to true. Thanks Raghu -Original Message- From: Ford, Jennifer M. [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 9:55 AM To: axis-user@ws.apache.org Subject: Configuration to use my WSDL rather than AXIS generated WSDL All: I am having some interoperability problems with a .NET client, and they've suggested that it's because of the changes that AXIS makes to my WSDL when the services are published. I'd like to make the services use the original WSDL, and it looks like there used to be a way to do that in the server-config.wsdd file. Is there a corollary to that for Axis 2? Thanks, Jennifer Ford - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuration to use my WSDL rather than AXIS generated WSDL
You need to put your WSDL file into the aar's META-INF directory. HTH, Robert On 11/6/07, Ford, Jennifer M. [EMAIL PROTECTED] wrote: Thanks for your help! When I did that, I got the following when I clicked on the service link from the listServices page: - error descriptionUnable to generate WSDL 1.1 for this service/description reasonIf you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml/reason /error I would have thought it would just display the WSDL I gave it in the resources directory. Is that incorrect? Is there another location where it is expected? Thanks, Jennifer -Original Message- From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 12:08 PM To: axis-user@ws.apache.org Subject: RE: Configuration to use my WSDL rather than AXIS generated WSDL In the services.xml there is a parameter named useOriginalwsdl, set that to true. Thanks Raghu -Original Message- From: Ford, Jennifer M. [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 9:55 AM To: axis-user@ws.apache.org Subject: Configuration to use my WSDL rather than AXIS generated WSDL All: I am having some interoperability problems with a .NET client, and they've suggested that it's because of the changes that AXIS makes to my WSDL when the services are published. I'd like to make the services use the original WSDL, and it looks like there used to be a way to do that in the server-config.wsdd file. Is there a corollary to that for Axis 2? Thanks, Jennifer Ford - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuration to use my WSDL rather than AXIS generated WSDL
Try this: In .aar file keep your generated wsdl inside META-INF directory. Axis engine picks wsdl from there and if it does not find one it generates one. -- Regards, -Shrish Mishra On 11/6/07, Ford, Jennifer M. [EMAIL PROTECTED] wrote: Thanks for your help! When I did that, I got the following when I clicked on the service link from the listServices page: - error descriptionUnable to generate WSDL 1.1 for this service/description reasonIf you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml/reason /error I would have thought it would just display the WSDL I gave it in the resources directory. Is that incorrect? Is there another location where it is expected? Thanks, Jennifer -Original Message- From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 12:08 PM To: axis-user@ws.apache.org Subject: RE: Configuration to use my WSDL rather than AXIS generated WSDL In the services.xml there is a parameter named useOriginalwsdl, set that to true. Thanks Raghu -Original Message- From: Ford, Jennifer M. [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 9:55 AM To: axis-user@ws.apache.org Subject: Configuration to use my WSDL rather than AXIS generated WSDL All: I am having some interoperability problems with a .NET client, and they've suggested that it's because of the changes that AXIS makes to my WSDL when the services are published. I'd like to make the services use the original WSDL, and it looks like there used to be a way to do that in the server-config.wsdd file. Is there a corollary to that for Axis 2? Thanks, Jennifer Ford - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] How to enforce AxisFault message to MTOM encoded?
Hi, Thilina recently helped me out on how to enforce the output encoding to be MTOM if input is also MTOM, using this kind of code: This is little bit more easy with the 1.3 release.. You can change the enableMTOM parameter as follows to get the behaviour you wanted.. parameter name=enableMTOMoptional/parameter But unfortunately Axis2 1.3 release seems to have a problem with interoperating MTOM with .net. That issue is fixed in the nightly builds.. I'm not sure whether the above would work for faults though... What is the behaviour you get if you set the parameter to true.. Does it send the faults using MTOM encoding.. thanks, Thilina MessageContextinMessageContextL= MessageContext.getCurrentMessageContext(); OperationContextoperationContextL= inMessageContextL.getOperationContext(); MessageContextoutMessageContextL= operationContextL.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE); booleanisInputMtomL= inMessageContextL.isDoingMTOM(); outMessageContextL.setProperty(Constants.Configuration.ENABLE_MTOM, isInputMtomL); The problem I now encounter is that WSE3 also expects AxisFaults to be dummy-encoded in MTOM. In ...MessageReceiverInOut.java I have tried to use code similar to the above like MessageContextinMessageContextL= MessageContext.getCurrentMessageContext(); OperationContextoperationContextL= inMessageContextL.getOperationContext(); MessageContextoutMessageContextL= operationContextL.getMessageContext(WSDLConstants.MESSAGE_LABEL_FAULT_VALUE); booleanisInputMtomL= inMessageContextL.isDoingMTOM(); outMessageContextL.setProperty(Constants.Configuration.ENABLE_MTOM, isInputMtomL); which did not work. Neither did a msgContext.setProperty(Constants.Configuration.ENABLE_MTOM, isInputMtomL); in the catch-handler of invokeBusinessLogic() do it. The AxisFault is always formatted as XML/Text message. I would appreciate if anybody could give me a hint on how to resolve this final issue. Axis seems to be flexible enough to compensate the peculiarities of other well-known vendor's software. Thanks, -Rainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[newbie] server-application for soap-messages?
Hi,
I want to create a socket server to be able to get soap-messages from
connected clients. The client should get a response as soap-messag too.
The SocketServer reads data as follows
public void run() {
try {
InputStream inputStream = socket.getInputStream();
ByteArrayOutputStream byteArrayOutputStream = new
ByteArrayOutputStream();
byte[] buf = new byte[4096];
int bufcount;
while ((bufcount = inputStream.read(buf)) 0) {
byteArrayOutputStream.write(buf, 0, bufcount);
}
The data consist of a multipart/related message:
POST HTTP/1.0
Content-Type: multipart/related;
boundary==_Part_1_5546792.1194363637711; type=text/xml;
start=3fa4a6eef42c6ae1bc2af56c84ffdeb4479e
Content-Length: 20388
Authorization: Basic dTAwMDFhNGQ6Nm5ScXNXbzE=
SOAPAction:
--=_Part_1_5546792.1194366154523
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-ID: 0b3a28cf8e010f2f83c1edabe8b29546b8d776bc
?xml version=1.0 encoding=UTF-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header
ns1:TransactionID soapenv:mustUnderstand=1 xsi:type=xsd:string
xmlns:ns1=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/
schema/REL-5-MM7-1-2d3050f28b717095923f65657d427a8a8c63b5ea2/ns1:TransactionID
/soapenv:Header
soapenv:Body
/soapenv:Body
/soapenv:Envelope
--=_Part_1_5546792.1194366154523
Content-Type: multipart/mixed;
boundary==_Part_0_20590970.1194366154479
Content-Transfer-Encoding: binary
Content-ID: EA3DDCF918B7D8BB4388D3B59C58270FA55FB2FB
--=_Part_0_20590970.1194366154479
Content-Type: text/plain; name=message.txt; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-ID: message.txt
my picture
--=_Part_0_20590970.1194366154479
Content-Type: image/jpg; name=pic.jpg
Content-Transfer-Encoding: base64
Content-ID: pic.jpg
/9j/4AAQSkZJRgABAQEASABIAAD/4QAWRXhpZgAATU0AKggAAAD//gAXQ3JlYXRlZCB3
vUjAXvgHAoXMZ9VIyDLmH7G7Luc6P6JYflW6eqniBGPDpg64ed5zl0+HdLC8q5raP1Le32NJOo//
2Q==
--=_Part_0_20590970.1194363637674--
--=_Part_1_5546792.1194363637711--
Can you give me a hint of how to use axis to get the elements of the
message ? I just want to save the attachement of such a message as a
file and send the status code as a soap message back to connected client.
Regards,
Thomas B
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
org.apache.axis2.deployment.DeploymentException: com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix wsp
When I deploy the webservice .aar file in Weblogic 8.1 application
server below error is displayed in the console. JDK is 1.4.2_08.
Please let me know how to resolve this issue.
org.apache.axis2.deployment.DeploymentException:
com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix wsp
at [row,col {unknown-source}]: [35,49]
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:144)
at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:
78)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(De
ploymentFileData.java:137)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.j
ava:571)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList
.java:141)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener
.java:318)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryL
istener.java:220)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngi
ne.java:118)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBas
edAxisConfigurator.java:272)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfiguration
Context(ConfigurationContextFactory.java:78)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle
t.java:500)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
at
weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletS
tubImpl.java:1094)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.
java:970)
at
weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImp
l.java:949)
at
weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl
.java:888)
at
weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServ
letContext.java:3430)
at
weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppSer
vletContext.java:3375)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
rvletContext.java:3356)
at
weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletC
ontext.java:6208)
at
weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:864)
at
weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.ja
va:2134)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer
.java:2175)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer
.java:2122)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation
(SlaveDeployer.java:3099)
at
weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllA
pplications(SlaveDeployer.java:1768)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java
:351)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(D
eploymentManagerServerLifeCycleImpl.java:229)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
Caused by: org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix wsp
at [row,col {unknown-source}]: [35,49]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:2
39)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:318)
at
org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:614
)
at
org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilde
r.java:97)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGr
oup(ArchiveReader.java:70)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:137)
... 33 more
Thanks Regards,
Peter Rajesh
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*
Re: Soap Request Date Format
Why don't you just take the date from the soap message, format it with SimpleDateFormat into the form you want and then use it? You need to keep in mind that having a standard date format in your service means third parties can easily connect to it without having to run date formatting code (e.g. .NET clients) Nguyen Le wrote: Hi, I was wondering if the date format for SOAP request generated by axis are hardcoded. In my SOAP request I have the following format 2007-11-21T18:00: 55.437Z But I need it to be the following 2007-11-21T18:00: I have tried modifying the SimpleDateFormat but to no avail. I have tried to do a search on google but nothing has come up. Does anybody know how to modify the date format. Any tip would be greatly appreciated. Best Regards, Le - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Anthony - Anthony Bull Senior Developer Black Coffee Software Ltd PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.apache.axis2.deployment.DeploymentException: com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix wsp
Hi,
Please send your services.xml file used in the service archive. Seems
like the you are missing the declaration of the policy namespace with
prefix wsp .
Thanks,
Ruchith
p.s. Please try not to cross post to all three axis-user, axis-dev and
rampart-dev lists.
Rajesh, Peter (CLAIMS, WIP) wrote:
When I deploy the webservice .aar file in Weblogic 8.1 application
server below error is displayed in the console. JDK is 1.4.2_08.
Please let me know how to resolve this issue.
org.apache.axis2.deployment.DeploymentException:
com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix wsp
at [row,col {unknown-source}]: [35,49]
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:144)
at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:
78)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(De
ploymentFileData.java:137)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.j
ava:571)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList
.java:141)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener
.java:318)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryL
istener.java:220)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngi
ne.java:118)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBas
edAxisConfigurator.java:272)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfiguration
Context(ConfigurationContextFactory.java:78)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle
t.java:500)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
at
weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletS
tubImpl.java:1094)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.
java:970)
at
weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImp
l.java:949)
at
weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl
.java:888)
at
weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServ
letContext.java:3430)
at
weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppSer
vletContext.java:3375)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
rvletContext.java:3356)
at
weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletC
ontext.java:6208)
at
weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:864)
at
weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.ja
va:2134)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer
.java:2175)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer
.java:2122)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation
(SlaveDeployer.java:3099)
at
weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllA
pplications(SlaveDeployer.java:1768)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java
:351)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(D
eploymentManagerServerLifeCycleImpl.java:229)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
Caused by: org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix wsp
at [row,col {unknown-source}]: [35,49]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:2
39)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:318)
at
org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:614
)
at
org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilde
r.java:97)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGr
oup(ArchiveReader.java:70)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:137)
... 33 more
Thanks Regards,
Peter Rajesh
*
This communication, including attachments, is
for the exclusive use of addressee and may contain
Soap Request Date Format
Hi, I was wondering if the date format for SOAP request generated by axis are hardcoded. In my SOAP request I have the following format 2007-11-21T18:00: 55.437Z But I need it to be the following 2007-11-21T18:00: I have tried modifying the SimpleDateFormat but to no avail. I have tried to do a search on google but nothing has come up. Does anybody know how to modify the date format. Any tip would be greatly appreciated. Best Regards, Le - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ExceptionInInitializerError when trying to create a new ServiceClient
Thanks for the help. It turns out I did not have wstx-asl-3.2.1.jar in my classpath. --kumar From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Monday, November 05, 2007 12:07 PM To: axis-user@ws.apache.org Subject: Re: ExceptionInInitializerError when trying to create a new ServiceClient The ExceptionInInitialiser error also occurs in the following situations when using the xml-beans data binding: 1. You don't have all (or some) of the .xsb files in your classpath. 2. You have different versions of the .xsb files than those referenced in the .class files for the xml-beans. If you're using xml-beans, let me know and I can give more info on how to work out if this is the problem. cheers, Ants. Ted Jones wrote: I had that issue once before. I didn't have the correct StAX jar version in my classpath. HTH, Ted Iyengar, Kumar wrote: Hi all, Has anyone seen this? It was working for me till I tried removing some of the jar files that are part of axis2. After that I added the removed ones back in and still get this error. I am using Axis2 1.3 and it is generating this error when trying to create a ServiceClient. Exception in thread main java.lang.ExceptionInInitializerError at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:564) at org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilde r.java:96) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigB uilder.java:79) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(D eploymentEngine.java:615) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration( FileSystemConfigurator.java:115) at org.apache.axis2.context.ConfigurationContextFactory.createConfiguration Context(ConfigurationContextFactory.java:64) at org.apache.axis2.context.ConfigurationContextFactory.createConfiguration ContextFromFileSystem(ConfigurationContextFactory.java:180) at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClie nt.java:146) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:139) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:228) at com.bmc.arsys.ws.client.WebServiceSoapClient.call(WebServiceSoapClient.j ava:178) at com.bmc.arsys.ws.client.WebServiceSoapClient.getTestWS(WebServiceSoapCli ent.java:795) at com.bmc.arsys.ws.client.WebServiceSoapClient.main(WebServiceSoapClient.j ava:616) Caused by: java.lang.IllegalStateException: No valid ObjectCreator found. at org.apache.axiom.om.util.StAXUtils$Pool.init(StAXUtils.java:64) at org.apache.axiom.om.util.StAXUtils.clinit(StAXUtils.java:88) ... 13 more Any help is appreciated. Thanks -kumar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Anthony - Anthony Bull Senior Developer Black Coffee Software Ltd PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 sample - pojoguide Unexpected EOF in prolog
Hi Rick- if you display the wsdl I'll try WSDL2Java to produce the service which I will then upload the aar/activate the service then write a client to extract at least 1 parameter.. Thanks/ Martin- - Original Message - Wrom: OWCONEUQZAAFXI To: axis-user@ws.apache.org Sent: Tuesday, November 06, 2007 8:18 AM Subject: Re: Axis2 sample - pojoguide Unexpected EOF in prolog Hi Martin, Thank you for your suggestions. I still the get the same prolog error for the pojoguide sample I checked and tried various ideas along with your suggestions without a sample client working. I dont believe CHUNKED_ENCODING is enabled as a default?.. to verify please display contents of %CATALINA_HOME%/webapps/axis2/WEB-INF/conf/axis2.xml Also prolog error codes are caused by the parser so verifying the version of xerces is critical My xerces is located at %CATALINA_HOME%/webapps/axis2/WEB-INF/lib/xercesImpl-2.8.1.jar (i.e. Xerces version 2.8.1) Martin 1.) I un-installed the windows Tomcat installation and downloaded the tomcat5.5.25 zip and moved it on c/tomcat 2.) using notepad %CATALINA_HOME%/webapps/axis2/WEB-INF/conf/axis2.xml my axis2.xml shows that encoding check is enabled. part of the standard axis2.xml .. transportSender name=tcp class=org.apache.axis2.transport.tcp.TCPTransportSender/ transportSender name=local class=org.apache.axis2.transport.local.LocalTransportSender/ transportSender name=http class=org.apache.axis2.transport.http.CommonsHTTPTransportSender parameter name=PROTOCOLHTTP/1.1/parameter parameter name=Transfer-Encodingchunked/parameter .. 3.) I used filemon.exe and traced the startup of Tomcat 12:26:13java.exe:3000READ C:\apache-tomcat-5.5.25\webapps\axis2\WEB-INF\conf\axis2.xmlSUCCESS Offset: 0 Length: 24161 to check that the correct file was read. 4.) I used filemon to trace the run of sample pojoguide ant rpc.client.run 12:30:41java.exe:3760READ C:\apache-tomcat-5.5.25\webapps\axis2\WEB-INF\lib\xercesImpl-2.8.1.jar SUCCESSOffset: 1123181 Length: 89762 to check that the correct file was read. The xeces*.jar and the axis2.xml seem to be correct and in the right place Maybe there is something else incorrectly configured? Is there any way to get more tracing information after the call to serviceClient.invokeRobust(opSetWeather, opSetWeatherArgs); ? Is there a site where I could compare my installation against a working one? Rick
RE: Problem with client side exceptions
I also have the same problem. I could not get back the original exception at
client side. I tried using sample/faulthandling code with the axis2
distribution and it works fine. But now the problem is, this example
generates client side and server side code from the wsdl ... but the source
code (service code) from which this wsdl was generated is not present with
the distribution:
In the faulthandinling example it soap message has exception information in
the detail/detail tag
?xml version='1.0' encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://sc
hemas.xmlsoap.org/soap/envelope/soapenv:Bodysoapenv:Faultfaultcodesoapen
v:Server/faultcodefaultstringAccount does not
exist!/faultstringdetailn
s1:AccountNotExistFault
xmlns:ns1=http://example;ns1:account13/ns1:account
/ns1:AccountNotExistFault/detail/soapenv:Fault/soapenv:Body/soapenv:Env
elope
So soap engine is able to read and regenerate the exception. but when I
tried with my service implementaion this information does not come in the
soap message rather it comes in the header of the http response as action
but detail/detail tag is empty. Please See below
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml;
action=urn:testExceptionMyCheckedException
;charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 07 Nov 2007 01:46:49 GMT
Connection: close
187
?xml version='1.0' encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://ww
w.w3.org/2003/05/soap-envelopesoapenv:Bodysoapenv:Faultsoapenv:Codesoap
env:Valuesoapenv:Receiver/soapenv:Value/soapenv:Codesoapenv:Reasonsoapen
v:Text xml:lang=en-USChecked Exception thrown
!!/soapenv:Text/soapenv:Reas
onsoapenv:Detail //soapenv:Fault/soapenv:Body/soapenv:Envelope
0
Can someone please give me some pointer or at lease provide the source code
for that faulthanding example.
Thanks !!
Pär Malmqvist wrote:
I also have problem with this.
My best shot is to set the parameter DrillDownToRootCauseForFaultReason to
true in the axis2.xml configuration file at the server side.
Then I can read the exceptionnbsp;namenbsp;(among a lot of other
exceptions)nbsp;in a field in the AxisFault message at the client side. I
thinknbsp;I usednbsp;the method getDetails().
But I dont think this is a good solution... :(
/Pär
nbsp;
From:nbsp;nbsp;John McLaughlin lt;[EMAIL PROTECTED]gt;
Reply-To:nbsp;nbsp;axis-user@ws.apache.org
To:nbsp;nbsp;axis-user@ws.apache.org Subject:nbsp;nbsp;Problem with
client side exceptions Date:nbsp;nbsp;Wed, 5 Sep 2007 15:50:39 +0100
Hinbsp; all, nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; I'm a newbie to
Axis2, though have used Axis1 before, and am having trouble with
exceptions on the client end. nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;
I've deployed a POJO as a service under Tomcat. I generated the service
and client using Eclipse WTP, so to be as brief as possible, the service
has a method:
nbsp;nbsp;nbsp; public CounterLight getCounter(Long nsuk)
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; throws CounterNotFoundException
nbsp;nbsp;nbsp; { nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; :
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; throw new
CounterNotFoundException(Exception) ; nbsp;nbsp;nbsp; }
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; CounterNotFoundException is
simply an extension of
java.lang.Exception (it implements Serializable as well, though I don't
think this makes any difference) nbsp;nbsp;nbsp; Wsdl2java generates a
class called CounterNotFoundExceptionException2 alongside the stub for the
service
nbsp;nbsp;nbsp; On the client side I have: nbsp;nbsp; try {
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; stub.getCounter(params) ; //
Params initialised properly etc nbsp;nbsp; } nbsp;nbsp;
catch(CounterNotFoundExceptionException2 e) {
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; e.printStackTrace() ;
nbsp;nbsp;nbsp; } nbsp;nbsp;nbsp; catch (AxisFault e) {
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; e.printStackTrace() ;
nbsp;nbsp;nbsp; } nbsp;nbsp;nbsp; The AxisFault is ALWAYS the one
that is received, never the generated exception (though the compiler
insists that I check for it).
nbsp;nbsp;nbsp; On the server side, I also get a
java.lang.reflect.InvocationTargetException...Caused by CounterException
nbsp;nbsp;nbsp; Can anybody point me in the right direction here, am I
missing something? I've googled extensively, searched the list archives
etc, but couldn't find much of help.
Thanks for any help! John
Express yourself instantly with MSN Messenger! MSN Messenger Download
today it's FREE!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Problem-with-client-side-exceptions-tf4384590.html#a13620214
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
RE: [Axis2] 1.3 wsdl2java generates code with missing methods
- I downloaded the latest nightly Axis2 1.3 build (dated 06-Nov-2007) - included the relevant axis2 jars into my lib space (which has other non-axis jars that I need) - then running wsdl2java using my ant task gave following error: o[java] Error on line -1 o[java] Error reported by XML parser: Premature end of file. - Ant build gave completed successfully message and some java code has got built from the wsdl, it seems to be ok - I need to look in more detail. I have following questions: - I then ran wsdl2java with only the axis nightly build jars (i.e. deleted other non-axis jars from my lib space) and it worked fine without any errors. So this seems to be a jar conflict issue. Does anyone know offhand what jar conflicts can cause above error? - I was not getting this error with the regular 1.3 download - so is this jar conflict introduced by any changes since 1.3? Looking into this, I think that Sun bundling apache classes into java 1.4.2 and 5.0 rt.jar adds uncertainty into which classes are getting used by wsdl2java. Any thoughts how I can improve upon this and get some certainty? From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Monday, November 05, 2007 8:34 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] 1.3 wsdl2java generates code with missing methods yes, now the nighly build should have this. On 11/6/07, Pantvaidya, Vishwajit [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi Amila, Should I try the latest nightly build now if the fix has been checked in? - Vish. From: Pantvaidya, Vishwajit [mailto: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2007 10:43 AM To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org Subject: RE: [Axis2] 1.3 wsdl2java generates code with missing methods Thanks Amila. Can you let me know which nightly build I should take to try out the fix? From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2007 4:57 AM To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org Subject: Re: [Axis2] 1.3 wsdl2java generates code with missing methods I have fixed this issue locally. will commit soon. Amila. On 10/25/07, Pantvaidya, Vishwajit [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: A quick clarification - the MessageReceiverInOut class generated by wsdl2java contains references to the missing methods. As this is an autogenerated class, I do not want to edit it myself to remove these problems. Any insights? From: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2007 5:25 PM To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org Subject: Axis2 1.3 wsdl2java generates code with missing methods I am using wsdl2java to generate java code from a wsdl using wsdl2java options -o -ss -sd -ssi -f -uw -uri -ns2p. The result includes a MessageReceiverInOut class that is missing a method resulting in a compiletime error method wrapIsUploadAllowed(OperationStatusType) is undefined for the type ...MessageReceiverInOut. I observed that this seems to happen when wsdl parts in different messages refer to the same complex type. In such cases, the wrap methods in the MessageReceiver class for the first operation is created while that for the other one is not created. E.g. in this case the method wrapUpload(OperationStatusType) gets created while wrapIsUploadAllowed(OperationStatusType) is missing. Wsdl snippet is included below. Is this a bug? s:complexType name=OperationStatusType s:sequence s:element name=successFlag type=s:boolean/ s:element name=messageLevel type=s:string/ s:element name=messageCode type=s:string/ s:element name=message type=s:string/ /s:sequence /s:complexType s:element name=OperationStatusElement type=tns:OperationStatusType/ s:element name=UploadRequestElement s:complexType s:sequence s:element name=sessiontoken type=s:string/ s:element name=trackingnumber type=s:string/
[Axis2] SOAP with HTTPS
Hi, Part of project I am working on is to transmit some information using soap to the service running elsewhere. My app will be a client to this service. Currently its working fine using http. Next task is to do the same over https. We will be provided with customer's digital certificates. I am new this SSL. Can somebody guide me through the steps I need to take to communicate over https and also recommend any additional packages required. My app (client) will be running on Tomcat using java 1.5 and Axis2. Regards, Srikanth
Re: [Axis2] SOAP with HTTPS
ServiceClient client = new ServiceClient(); Options opts = new Options(); opts.setAction(urn:divide); client.setOptions(opts); System.setProperty(javax.net.ssl.keyStoreType, JKS); // key store password System.setProperty(javax.net.ssl.keyStorePassword, my_password); //trust store password System.setProperty(javax.net.ssl.trustStorePassword, my_password); //location of the certificate File file = new File( truststore.jks); System.setProperty(javax.net.ssl.trustStore, file.getAbsolutePath()); invoke the client On Nov 6, 2007 11:15 PM, Srikanth Muthyala [EMAIL PROTECTED] wrote: Hi, Part of project I am working on is to transmit some information using soap to the service running elsewhere. My app will be a client to this service. Currently its working fine using http. Next task is to do the same over https. We will be provided with customer's digital certificates. I am new this SSL. Can somebody guide me through the steps I need to take to communicate over https and also recommend any additional packages required. My app (client) will be running on Tomcat using java 1.5 and Axis2. Regards, Srikanth -- Deepal Jayasinghe Lanka Software Foundation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
