axis2 c help : problem
axis2c installation guide states that it needs to download the Microsoft VSExpress2005 edition and Platform SDK. There the VSExpress2005 edition is a pack of : visual c#, visual web developer,visual c++. it makes the downloading quite confusing. any suggestions for this. because axis2c requires only single bat file (vsvars32.bat) as it states. samitha
Array namespace problem
Hi I am using Axis 1.4 and have two webservices sharing a common type of class 'Master'. This class has an array of another class 'Detail'. 'Master' and 'Detail' are in a separate package than the two web services (which are again in different packages). While generating the wsdl for the two webservices, each wsdl generates for the Master type an ArrayOf_tns2_Detail type descriptor defined in the namespace of the webservice and not in the namespace of the Master or Detail type. Now I use the .NET wsdl class generator, which creates two different master classes, because they contain arrays defined in different namespaces. How can I tell Axis to use a certain namespace for the array definitions? Can Axis2 solve this problem? Wsdl of Webservice1: wsdl:types schema targetNamespace=http://commonobjects.ws.arregulo.sowatec.com; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://webservice.ws1.arregulo.sowatec.com/ import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=Detail sequence element name=name nillable=true type=xsd:string/ /sequence /complexType complexType name=Master sequence element name=details nillable=true type=impl:ArrayOf_tns2_Detail/ /sequence /complexType /schema schema targetNamespace=http://webservice.ws1.arregulo.sowatec.com; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://commonobjects.ws.arregulo.sowatec.com/ import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=ArrayOf_tns2_Detail complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns2:Detail[]/ /restriction /complexContent /complexType /schema /wsdl:types Wsdl of Webservice2: wsdl:types schema targetNamespace=http://commonobjects.ws.arregulo.sowatec.com; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://webservice.ws2.arregulo.sowatec.com/ import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=Detail sequence element name=name nillable=true type=xsd:string/ /sequence /complexType complexType name=Master sequence element name=details nillable=true type=impl:ArrayOf_tns2_Detail/ /sequence /complexType /schema schema targetNamespace=http://webservice.ws2.arregulo.sowatec.com; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://commonobjects.ws.arregulo.sowatec.com/ import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=ArrayOf_tns2_Detail complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns2:Detail[]/ /restriction /complexContent /complexType /schema /wsdl:types Thanks, Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis 1.3, GZip, CommonHTTPSender - Service Invocation not possible
Hello there, I have a problem, that plagues me now for a while and I did not find any solution - I hope you could help me. The situation: A Axis Web Service on Tomcat 5.5 which is configured to handle gzip request (in server.xml). I have a client stub, that uses this web service. I modified the client with help of the wiki entry http://wiki.apache.org/ws/FrontPage/Axis/GzipCompression I added the client-config.wsdd and -Daxis.ClientConfigFile=client-config.wsdd to the eclipse launch configuration - the wsdd is recognized as I get an error if I delete it. The commonshttp jar is added in my library. The Problem now is: If the client-config.wsdd is in correct place and recognized, the client is not able to make any connection. This happens also if I use the default httpSender. With no connection I mean: There is no request send at all - tcpmonitor shows just nothing! If I delete the client-config.wsdd and the launch parameter everything works as ususal - service works and data is transferred, which is shown by TcpMon. Have you encountered a similar problem or do you have any tips? Thank you for your help WG - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Eran, On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote: I do agree with you that we need a reliable Axis2, but that doesn't mean we need to keep on postponing releases until we fix everything. there was no insult in my comments. My point, instead, is that if you want new features you can download the last nightly build. If you want something which works *properly* you download a release. Does it make sense to release a new version and then ask to people to download the next nightly build because the release is broken? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Temporary files/ Stress testing with Axis2 1.2 [SEC=UNCLASSIFIED]
Greg, Please create an issue in JIRA and upload your test ASAP. we are in the middle of perf testing. this would be a great scenario to fix for 1.3 release. thx, dims On 7/2/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, Our team is currently using Axis2 1.2 in our application and we are running some performance and stress tests with JMeter. While running these stress tests we have come across two issues that we hope someone can help us with. The first issue relates to temporary files. In our stress testing we were using the URLBasedAxisConfigurator to load .mar files on the client side, but got the error below with 1 user and 1000 iterations: java.lang.RuntimeException: java.io.IOException: Too many open files;; at org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java(Compiled Code));; at org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:684);; at au.gov.centrelink.jfs.proxy.axis2.ClientURLBasedAxisConfigurator.loadRepositoryFromURL(ClientURLBasedAxisConfigurator.java(Compiled Code));; at org.apache.axis2.deployment.URLBasedAxisConfigurator.getAxisConfiguration(URLBasedAxisConfigurator.java:72);; at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:60);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createStub(ProxyFactory.java:699);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createProxy(ProxyFactory.java:440);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createProxy(ProxyFactory.java:395);; at au.gov.centrelink.jsf.pst.core.CDCCustomerEmailAddressTester2.execute(CDCCustomerEmailAddressTester2.java:64);; at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421);; at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226);; at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164);; at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:763);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:856);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1521);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:113);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:759);; at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:334);; at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056);; at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:388);; at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231);; at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164);; at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:763);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:856);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1521);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:136);; at au.gov.centrelink.itsecurity.acs.web.SecureRequestFilter.doFilter(SecureRequestFilter.java:60);; at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121);; at au.gov.centrelink.jaf.liser.api.WebRequestLiser.doFilter(WebRequestLiser.java:267);; at au.gov.centrelink.jaf.interceptor.core.JAFFilter.doFilter(JAFFilter.java:99);; at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:759);; at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:89);; at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1924);; at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:98);; at
Re: More than one service name in a SINGLE WSDL file
which bug? have tried the nightly yet? please upload your wsdl/xsd if this is still a problem thx, dims On 7/2/07, Jess Fisher [EMAIL PROTECTED] wrote: The current Axis2 version still hasn't fixed this issue. This is not a problem in Axis1.4 version. There's a bug re-opened to address this problem in Axis2. I don't know when or if it will ever get fixed --- hopefully yes ??? Patrick Cook [EMAIL PROTECTED] wrote: First and foremost, I would like to take my hats off to Axis2 community. You all have definately raised the standards for SOAP Engines, Web Services and SOA in general. I would like to help out but don't know how. Please send me some information on how I could get involved. Secondly, I have a few questions. 1. How does Axis2 generate the ?wsdl for multiple services in a SINGLE WSDL file 2. Is there a one to one mapping of the service name in the service.xml file when there is a wsdl file in the META-INF folder 3. What is the connection of the service.xml and the *.wsdl file located in the META-INF folderHow does Axis2 1.2 handle Multiple Services in a SINGLE WSDL file. i.e. if the wsdl looks something like the wsdl below. The behavior that I am seeing is that when you ask for the wsdl via (?wsdl) the SOAP engine will correctly generate the wsdl for one service but NOT the other. ?xml version=1.0 encoding=UTF-8? definitions name=Stock ... service name=MyService1 documentationService Example/documentation port name=MyPort1 binding=tns:MyPortBinding1 soap:address location= http://localhost:8080/services/MyService1/ /port /service service name=MyService2 documentationService Example/documentation port name=MyPort2 binding=tns:MyPortBinding2 soap:address location= http://localhost:8080/services/MyService2/ /port /service /definitions And my service.xml file would look something like this serviceGroup service name=MyService1 description Example of Multiple Services within one wsdl /description parameter name=ServiceClass example.multiple.services.test.MyServcice1 /parameter messageReceivers messageReceiver mep= http://www.w3.org/2004/08/wsdl/in-out class=example.multiple.receivers.MyCustomMessageReceiver / /messageReceivers /service service name=MyService2 description Example of Multiple Services within one wsdl /description parameter name=ServiceClass example.multiple.services.test.MyServcice2 /parameter messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out class=example.multiple.receivers.MyCustomMessageReceiver / /messageReceivers /service /serviceGroup By the way, I am using the original wsdl file in the META-INF folder. all of the corresponding schemas and source class files are in the correct location. -Patrick Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
no it doesnt. this is a classic chicken and egg issue. thats why we make so many RC's but still end users dont play enough with RC's as much as we'd like them to :) thx, dims On 7/2/07, Michele Mazzucco [EMAIL PROTECTED] wrote: Eran, On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote: I do agree with you that we need a reliable Axis2, but that doesn't mean we need to keep on postponing releases until we fix everything. there was no insult in my comments. My point, instead, is that if you want new features you can download the last nightly build. If you want something which works *properly* you download a release. Does it make sense to release a new version and then ask to people to download the next nightly build because the release is broken? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Is this cleaning up phase also applicable for the Rampart module or only for the Axis2 framework ? In other words, can I vote for JIRA issues related to Rampart ? Regards, Stefan Lecho. dims wrote: Dear Axis2 Users, We are working hard on cleaning up the issues in JIRA. -- View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Get the username from UsernameTokens in Skeleton class
Another way is outlined at: http://wiki.apache.org/ws/FrontPage/WsFx/wss4jFAQ#usernme An interpretation of this I've been using is: import org.apache.axis2.context.MessageContext ; import java.util.Vector ; import org.apache.ws.security.handler.WSHandlerResult ; import org.apache.ws.security.handler.WSHandlerConstants ; import org.apache.ws.security.WSSecurityEngineResult ; import org.apache.ws.security.util.WSSecurityUtil ; import org.apache.ws.security.WSConstants ; import org.apache.ws.security.WSUsernameTokenPrincipal ; import java.security.Principal; [...] public String helloUsername() throws Exception { MessageContext msgCtx = MessageContext.getCurrentMessageContext() ; Vector results = (Vector) msgCtx.getProperty(WSHandlerConstants.RECV_RESULTS) ; // Results for all chained `RampartReceiver' etc handlers. WSHandlerResult rResult = (WSHandlerResult) results.get(0) ; // Result object for final handler. Vector wsResult = rResult.getResults() ; // Results for all actions by this handler. WSSecurityEngineResult actionResult = WSSecurityUtil.fetchActionResult(wsResult, WSConstants.UT) ; // Result for `UsernameToken' action. Principal principal = actionResult.getPrincipal() ; // Principal extracted from `UsernameToken/' element. WSUsernameTokenPrincipal wsPrincipal = (WSUsernameTokenPrincipal) principal ; return Hello + wsPrincipal.getName() + ! ; } Bryan Chad DeBauch wrote: I figured out how to do this. I got the SOAP Envelope from the MessageContext by calling getEnvelope() and parsing the SOAP Header for the username. I was hoping there were some helper methods that would do that for you but now it is done. Chad On 6/21/07, *Chad DeBauch* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: How do I get the username that was in the SOAP UsernameToken from my skeleton class? Is there a way to retrieve it from the MessageContext? I am using Rampart to validate the UsernameTokens using a PWCallback class. Thanks, Chad -- _ Dr David Bryan CarpenterPhone: +44 (0) 23 8059 8814 OMII, University of Southampton FAX : +44 (0) 23 8059 8870 6005 Faraday Building, Highfield Campus Email: [EMAIL PROTECTED] Southampton SO17 1BJ, UKURL : www.hpjava.org _ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Raw SOAP Request with Spring
Hi, I am using Axis2 + Spring to implement a Web Service. My service.xml looks something like this ==Start XML= serviceGroup class=com.somecompany.SpringAxisInit service name=SpringInit class=com.somecompany.SpringAxisInit description This web service initializes Spring. /description parameter name=ServiceClasscom.somecompany.SpringAxisInit/parameter parameter name=ServiceTCCLcomposite/parameter parameter name=load-on-startuptrue/parameter operation name=springInit messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service service name=TheGateway description A service /description parameter name=ServiceClasscom.somecompany.service.support.TheGatewayServiceImpl/parameter parameter name=ServiceObjectSupplier org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier /parameter parameter name=SpringBeanNameTheGatewayService/parameter operation name=provisionOrder messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class=com.somecompant.service.TheGatewayMessageReceiverInOut/ /operation /service /serviceGroup ==End XML= Is there anyway for me to view the RAW Soap request? Kind Regards, Richard Friend - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deploy TCPTransport
Hi everyone, i'm trying to develop an axis service with a tcptransport, but i really cant find a way to get it to work. I start the tcpserver with a given port () and a repository, with only 1 service file deployed (ConnectionManager.aar). The problem arise when i try to connect to it, because the ServiceClient keeps receiving exceptions: The service cannot be found for the endpoint reference (EPR) for the connection i use this simple code: ServiceClient service = new ServiceClient(); Options o = new Options(); EndpointReference er = new EndpointReference(tcp://localhost:777/ConnectionManager); o.setTo(er); o.setTransportInProtocol( tcp); service.setOptions(o); service.sendReceive(payload); but it seems im missing something, or im doing something wrong thx to anyone who can help, and sorry for my bad english best regards, Marchetti Yari - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploy TCPTransport
TCP only works when you engage addressing in both server side and client side. Thanks Deepal Yari Marchetti wrote: Hi everyone, i'm trying to develop an axis service with a tcptransport, but i really cant find a way to get it to work. I start the tcpserver with a given port () and a repository, with only 1 service file deployed (ConnectionManager.aar). The problem arise when i try to connect to it, because the ServiceClient keeps receiving exceptions: The service cannot be found for the endpoint reference (EPR) for the connection i use this simple code: ServiceClient service = new ServiceClient(); Options o = new Options(); EndpointReference er = new EndpointReference(tcp://localhost:777/ConnectionManager); o.setTo(er); o.setTransportInProtocol( tcp); service.setOptions(o); service.sendReceive(payload); but it seems im missing something, or im doing something wrong thx to anyone who can help, and sorry for my bad english best regards, Marchetti Yari - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Yes we will be releasing Rampart along with Axis2 as soon as 1.3 goes out! Thanks, Ruchith On 7/2/07, stlecho [EMAIL PROTECTED] wrote: Is this cleaning up phase also applicable for the Rampart module or only for the Axis2 framework ? In other words, can I vote for JIRA issues related to Rampart ? Regards, Stefan Lecho. dims wrote: Dear Axis2 Users, We are working hard on cleaning up the issues in JIRA. -- View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
yes! On 7/2/07, stlecho [EMAIL PROTECTED] wrote: Is this cleaning up phase also applicable for the Rampart module or only for the Axis2 framework ? In other words, can I vote for JIRA issues related to Rampart ? Regards, Stefan Lecho. dims wrote: Dear Axis2 Users, We are working hard on cleaning up the issues in JIRA. -- View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
I am really looking forwards to fixing this one: https://issues.apache.org/jira/browse/AXIS2-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel Second part of two-part message is ignored by WSDL2Java because in my project doing now, there is a this scenario: wsdl:message name=createRequest wsdl:part name=header element=abc:header/ wsdl:part name=create element=abcthis:createRequest / /wsdl:message It prevent me from using wsdl2c tool. Ruchith Fernando [EMAIL PROTECTED] wrote: Yes we will be releasing Rampart along with Axis2 as soon as 1.3 goes out! Thanks, Ruchith On 7/2/07, stlecho wrote: Is this cleaning up phase also applicable for the Rampart module or only for the Axis2 framework ? In other words, can I vote for JIRA issues related to Rampart ? Regards, Stefan Lecho. dims wrote: Dear Axis2 Users, We are working hard on cleaning up the issues in JIRA. -- View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
How to get an ordinal namespace sequence?
Hi, I used the following codes to generate a soap message with more than one namespace: ns0 = axiom_namespace_create(env, AXIOM_SOAP11_SOAP_ENVELOPE_NAMESPACE_URI, SOAP-ENV); ns1 = axiom_namespace_create(env, http://schemas.xmlsoap.org/soap/encoding/;, SOAP-ENC); ns2 = axiom_namespace_create(env, http://www.w3.org/1999/XMLSchema-instance;, xsi); ns3 = axiom_namespace_create(env, http://www.w3.org/1999/XMLSchema;, xsd); ns4 = axiom_namespace_create(env, http://stockquote;, ns1); envelope_ele = axiom_element_create(env, NULL, Envelope, ns0, envelope_node); axiom_element_declare_namespace(envelope_ele, env, envelope_node, ns1); axiom_element_declare_namespace(envelope_ele, env, envelope_node, ns2); axiom_element_declare_namespace(envelope_ele, env, envelope_node, ns3); axiom_element_declare_namespace(envelope_ele, env, envelope_node, ns4); The generated namespace sequence is: SOAP-ENV:Envelope xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; xmlns:ns1=http://stockquote; but I want to create an exact sequence namesapce like: SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:xsd=http://www.w3.org/1999/XMLSchema; xmlns:ns1=http://stockquote; How could I do this? Best regards. Kelvin.Lin - Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
Re: NullPointerException with axis1 1.4
Thanks for your response! We implemented WSRP service on axis1 1.2-RC1, but now we start to using axis1 1.4. WSRP service has the wsdl file from oasis ( wsrp_service.wsdl from http://www.oasis-open.org/committees/wsrp/specifications/version1/ ) http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl ---WSDL--- ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=urn:oasis:names:tc:wsrp:v1:wsdl xmlns:bind=urn:oasis:names:tc:wsrp:v1:bind xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; import namespace=urn:oasis:names:tc:wsrp:v1:bind location=wsrp_v1_bindings.wsdl/ wsdl:service name=WSRPService wsdl:port binding=bind:WSRP_v1_Markup_Binding_SOAP name=WSRPBaseService soap:address location=http://my.service:8080/WSRPService/ /wsdl:port wsdl:port binding=bind:WSRP_v1_ServiceDescription_Binding_SOAP name=WSRPServiceDescriptionService soap:address location=http://my.service:8080/WSRPService/ /wsdl:port wsdl:port binding=bind:WSRP_v1_Registration_Binding_SOAP name=WSRPRegistrationService soap:address location=http://my.service:8080/WSRPService/ /wsdl:port wsdl:port binding=bind:WSRP_v1_PortletManagement_Binding_SOAP name=WSRPPortletManagementService soap:address location=http://my.service:8080/WSRPService/ /wsdl:port /wsdl:service /wsdl:definitions -- Do you know where cause of this problem? Alexey On 6/27/07, Martin Gainty [EMAIL PROTECTED] wrote: Alexey please post the wsdl Thanks M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Alexey Zavizionov [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, June 27, 2007 11:10 AM Subject: Re: NullPointerException with axis1 1.4 I catch the soap message: POST /portal/services/WSRPServiceDescriptionService HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: localhost:8080 Cache-Control: no-cache Pragma: no-cache SOAPAction: urn:oasis:names:tc:wsrp:v1:getServiceDescription Content-Length: 421 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body getServiceDescription xmlns=urn:oasis:names:tc:wsrp:v1:types registrationContext xsi:nil=true/ desiredLocalesen/desiredLocales /getServiceDescription /soapenv:Body /soapenv:Envelope HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=D8D788AB8D4D347C7C65F5C3B3FAE75D; Path=/portal Content-Type: text/xml;charset=utf-8 Date: Wed, 27 Jun 2007 15:05:28 GMT Connection: close ?xml version=1.0 encoding=utf-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body soapenv:Fault faultcodesoapenv:Server.userException/faultcode faultstringjava.lang.NullPointerException/faultstring detail ns1:hostname xmlns:ns1=http://xml.apache.org/axis/;Alex/ns1:hostname /detail /soapenv:Fault /soapenv:Body /soapenv:Envelope Any idea are appreciable! Regards, Alexey On 6/27/07, Alexey Zavizionov [EMAIL PROTECTED] wrote: Hello, I am using axis1 version 1.4 for wsrp service. I have an exc: AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.lang.NullPointerException faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:Alex java.lang.NullPointerException at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222) at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at
Re: [Axis2] Temporary files/ Stress testing with Axis2 1.2 [SEC=UNCLASSIFIED]
Greg Are you running the system on Windows or Linux? The OS decides the number of files a process can open. If you are using a Unix system, try to increase the number of files as follows. This is not a solution for a possible Axis2 issue, but something to make sure before you run a typical load test. You may be able to find alternatives for Windows on Google. Maybe http://coldfused.blogspot.com/2007/02/mystery-of-too-many-open-files.html would be of interest too. /etc/sysctl.conf fs.file-max = 2097152 /etc/security/limits.conf * soft nofile 4096 * hard nofile 65535 asankha Davanum Srinivas wrote: Greg, Please create an issue in JIRA and upload your test ASAP. we are in the middle of perf testing. this would be a great scenario to fix for 1.3 release. thx, dims On 7/2/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, Our team is currently using Axis2 1.2 in our application and we are running some performance and stress tests with JMeter. While running these stress tests we have come across two issues that we hope someone can help us with. The first issue relates to temporary files. In our stress testing we were using the URLBasedAxisConfigurator to load .mar files on the client side, but got the error below with 1 user and 1000 iterations: java.lang.RuntimeException: java.io.IOException: Too many open files;; at org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java(Compiled Code));; at org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:684);; at au.gov.centrelink.jfs.proxy.axis2.ClientURLBasedAxisConfigurator.loadRepositoryFromURL(ClientURLBasedAxisConfigurator.java(Compiled Code));; at org.apache.axis2.deployment.URLBasedAxisConfigurator.getAxisConfiguration(URLBasedAxisConfigurator.java:72);; at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:60);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createStub(ProxyFactory.java:699);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createProxy(ProxyFactory.java:440);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createProxy(ProxyFactory.java:395);; at au.gov.centrelink.jsf.pst.core.CDCCustomerEmailAddressTester2.execute(CDCCustomerEmailAddressTester2.java:64);; at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421);; at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226);; at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164);; at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:763);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:856);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1521);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:113);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:759);; at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:334);; at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056);; at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:388);; at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231);; at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164);; at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:763);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:856);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1521);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:136);; at au.gov.centrelink.itsecurity.acs.web.SecureRequestFilter.doFilter(SecureRequestFilter.java:60);; at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121);; at au.gov.centrelink.jaf.liser.api.WebRequestLiser.doFilter(WebRequestLiser.java:267);; at au.gov.centrelink.jaf.interceptor.core.JAFFilter.doFilter(JAFFilter.java:99);; at
Re: [Rampart] Ignore Timestamp and Addressing from client
All, Is there a solution or workaround for this issue ? Regards, Stefan Lecho. stlecho wrote: Hi, I have configured the InflowSecurity parameter (extracted included underneath) on the server side with the Signature item. One of our clients is using a C# client. The SOAP request that is received from this client contains Timestamp and Addressing related elements. This results in an WSDoAllReceiver: security processing failed (actions mismatch) AxisFault. Is there a way to ignore the Timestamp and Addressing related elements on the server ? Extract axis2.xml: parameter name=InflowSecurity action itemsSignature/items signaturePropFileinteropin.properties/signaturePropFile signatureKeyIdentifierDirectReference/signatureKeyIdentifier signatureParts{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body/signatureParts /action /parameter Regards, Stefan Lecho. -- View this message in context: http://www.nabble.com/-Rampart--Ignore-Timestamp-and-Addressing-from-client-tf3882252.html#a11392800 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 1.1.1] Exception generated based on wsdl:fault
All, Is there a solution or workaround for this issue ? Regards, Stefan Lecho. stlecho wrote: Hi, The WSDL that I am using in the development of a webservice contains a wsdl:fault element. Based on this element Axis2 v1.1.1 generates a StatussesException that inherits from Exception. For pre-processing reasons, I have developed my own MessageReceiverInOut that inherits from AbstractInOutSyncMessageReceiver. I would like to use the StaussesException class in the MessageReceiverInOut, but the invokeBusinessLogic method throws an AxisFault. As a result I can not use the generated StatussesException in this method :-(. Is there a way to change the generated StatussesException, so that it inherits from AxisFault ? --- Extract WSDL - begin --- wsdl:portType ... wsdl:operation name=ping wsdl:input message=ns:pingIn/ wsdl:output message=ns:pingOut/ wsdl:fault name=FaultName message=ns:Statusses/ /wsdl:operation wsdl:binding ... wsdl:operation name=ping soap:operation soapAction=ping/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output wsdl:fault name=FaultName soap:fault name=FaultName use=literal/ /wsdl:fault /wsdl:operation --- Extract WSDL - end --- Regards, Stefan Lecho. -- View this message in context: http://www.nabble.com/-Axis2-1.1.1--Exception-generated-based-on-wsdl%3Afault-tf3876565.html#a11392819 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 1.1.1] Unable to generate WSDL for this service
All, Is there a solution or workaround for this issue ? Regards, Stefan Lecho. stlecho wrote: Some precisions: The generated MessageReceiver inherits from org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver. Regards, Stefan Lecho. stlecho wrote: Switching to Axis2 1.2 is not really an option. Adding the RPCMessageReceiver to the list of MessageReceivers solves the problem, but there is a conflict with another MessageReceiver that has the same http://www.w3.org/2004/08/wsdl/in-out; mep as the RPCMessageReceiver. This MessageReceiver is automatically generated by the WSDL2Java tool. So, how can I display the WSDL linked with a Service when using the generated MessageReveiver instead of the RPCMessageReceiver ? Regards, Stefan Lecho. Davanum Srinivas wrote: Please switch to Axis2 1.2 and let us know if you still see this problem. thanks, dims On 5/29/07, Stefan Lecho [EMAIL PROTECTED] wrote: All, I would like to display the WSDL of a WebService generated with Axis2 v1.1.1 and deployed in Tomcat v5.5.17. When using http://localhost:9091/itpartners-axis2-0.0.1/services/ASFInterface?wsdl;, the following error message is generated: Unable to generate WSDL for this service. After a search in the mailing list of Axis2, I've noticed that there are solutions to this problem: -check that the name attribute of the service element in services.xml is the same as the name attribute of the wdsl:service element in the WSDL file = OK -use the useOriginalwsdl parameter = OK -use RPCMessageReceiver as messageReceiver = OK All the above checks are OK (files are included underneath), but I still do not get my WSDL file displayed correctly. Can anyone help me with this issue ? The messageReceivers and parameter section from the services.xml file: service name=ASFInterface class=be.credoc.service.SpringInit messageReceivers /messageReceivers parameter name=ServiceTCCL locked=falsecomposite/parameter parameter name=load-on-startuptrue/parameter parameter name=useOriginalwsdltrue/parameter The wsdl:service section from the WSDL file that has been deployed in the WEB-INF directory of the AAR file: wsdl:service name=ASFInterface Regards, Stefan Lecho. Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-Axis2-1.1.1--Unable-to-generate-WSDL-for-this-service-tf3832868.html#a11392820 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Performance ServiceClient vs. OperationClient
Hi list, I have a question rg. performance of the ServiceClient compared to the OperationClient interface. Personally, I would expect the performance* to be roughly the same for both interfaces since ServiceClient is just a more convenient wrapper for simple tasks. But now I have measured the invocation times (as defined below), and found that my handwritten client (which uses ServiceClient and AXIOM) takes about 4 times as long as the stubs generated by wsdl2java (which use the OperationClient interface) to produce a result against the same service. I guess the reason for this performance boost of the client is either that (a) the OperationClient interface is for some reason a lot faster than the ServiceClient interface or that (b) there is some tricky optimization going on somewhere in the ADB stubs that I failed to see so far. Has anybody any insight here that could help me to improve my self-produced client, or any other information that would help me understand the differences here? thanks in advance, philipp P.S.: I also did a few comparisons with other frameworks (WSIF and XFire), and Axis2 seems to be doing quite well so far. Definitely quicker than WSIF, and in a good tie with XFire (but I still have to do a lot to get really conclusive results here). *in this context I mean with performance the time between calling eg. ServiceClient.sendReceive() and the response being returned to the client. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Lack of getting the RC's being used by end users has I think been one of the main causes for instability. I'd really like to try something new this time around that might get more users using them. I'm all for Release early and often - in fact arguably we don't do enough point releases. I realize though that there are lots of deps and its hard to coordinate all the releases. Anyways, IIRC the RC's never got put on the download page. The only announcement is to the list. Other projects have better usage of their RC's and I think it'd be worth exploring what could be done differently to get more RC usage of axis2. I've noticed xmlbeans, for example, has been broken on every release so far. And while I tested svn in the middle of dev, I never did test the RC's so I accept part of the blame. This time around I plan on testing xmlbeans on some of my complex schemas, and the other things I personally use like spring and the soapmonitor. Michele, from what I've seen you're had some of the most advanced use cases of axis2. If you could do some RC testing with some of your use cases I'd think that'd go a long way to making 1.3 the most stable yet. No one uses 100% of axis2, but I'd think that if we got more people using the RC's on _their_ code, it'd help plenty. Robert On 7/2/07, Davanum Srinivas [EMAIL PROTECTED] wrote: no it doesnt. this is a classic chicken and egg issue. thats why we make so many RC's but still end users dont play enough with RC's as much as we'd like them to :) thx, dims On 7/2/07, Michele Mazzucco [EMAIL PROTECTED] wrote: Eran, On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote: I do agree with you that we need a reliable Axis2, but that doesn't mean we need to keep on postponing releases until we fix everything. there was no insult in my comments. My point, instead, is that if you want new features you can download the last nightly build. If you want something which works *properly* you download a release. Does it make sense to release a new version and then ask to people to download the next nightly build because the release is broken? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploy TCPTransport
first thanks for the quick answer. what do u mean with i should engage addressing? could you point me in the right direction? i tried to look everywhere but the only thing i could find was the short page in the axis project, but i couldnt figure out how to solve the addressing problem.. thx, yari Deepal Jayasinghe ha scritto: TCP only works when you engage addressing in both server side and client side. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Performance ServiceClient vs. OperationClient
Philipp, Am afraid the key to performance is not ServiceClient vs OperationClient as you rightly pointed guessed. The key is AXIOM itself and its usage. If you post your code with request/response sample then we may be able to help. But the best way to understand is to look at the generated code for ADB databinding. All tricks we know in terms of perfomance gets into the generated code :) thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: Hi list, I have a question rg. performance of the ServiceClient compared to the OperationClient interface. Personally, I would expect the performance* to be roughly the same for both interfaces since ServiceClient is just a more convenient wrapper for simple tasks. But now I have measured the invocation times (as defined below), and found that my handwritten client (which uses ServiceClient and AXIOM) takes about 4 times as long as the stubs generated by wsdl2java (which use the OperationClient interface) to produce a result against the same service. I guess the reason for this performance boost of the client is either that (a) the OperationClient interface is for some reason a lot faster than the ServiceClient interface or that (b) there is some tricky optimization going on somewhere in the ADB stubs that I failed to see so far. Has anybody any insight here that could help me to improve my self-produced client, or any other information that would help me understand the differences here? thanks in advance, philipp P.S.: I also did a few comparisons with other frameworks (WSIF and XFire), and Axis2 seems to be doing quite well so far. Definitely quicker than WSIF, and in a good tie with XFire (but I still have to do a lot to get really conclusive results here). *in this context I mean with performance the time between calling eg. ServiceClient.sendReceive() and the response being returned to the client. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Performance ServiceClient vs. OperationClient
Hi Dims, I already expected something like this ... I just couldn't find much optimization in the generated ADB stubs - I probably just looked at the wrong places ... Currently my AXIOM code is quite naive. I am using the createOMElement and createOMText methods of OMFactory to iteratively create my SOAP payload, and invoke the service using the ServiceClient interface snip ServiceClient sender = new ServiceClient(); OMelement result = sender.sendReceive(axisOp); /snip /philipp Davanum Srinivas schrieb: Philipp, Am afraid the key to performance is not ServiceClient vs OperationClient as you rightly pointed guessed. The key is AXIOM itself and its usage. If you post your code with request/response sample then we may be able to help. But the best way to understand is to look at the generated code for ADB databinding. All tricks we know in terms of perfomance gets into the generated code :) thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: Hi list, I have a question rg. performance of the ServiceClient compared to the OperationClient interface. Personally, I would expect the performance* to be roughly the same for both interfaces since ServiceClient is just a more convenient wrapper for simple tasks. But now I have measured the invocation times (as defined below), and found that my handwritten client (which uses ServiceClient and AXIOM) takes about 4 times as long as the stubs generated by wsdl2java (which use the OperationClient interface) to produce a result against the same service. I guess the reason for this performance boost of the client is either that (a) the OperationClient interface is for some reason a lot faster than the ServiceClient interface or that (b) there is some tricky optimization going on somewhere in the ADB stubs that I failed to see so far. Has anybody any insight here that could help me to improve my self-produced client, or any other information that would help me understand the differences here? thanks in advance, philipp P.S.: I also did a few comparisons with other frameworks (WSIF and XFire), and Axis2 seems to be doing quite well so far. Definitely quicker than WSIF, and in a good tie with XFire (but I still have to do a lot to get really conclusive results here). *in this context I mean with performance the time between calling eg. ServiceClient.sendReceive() and the response being returned to the client. - 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] org.apache.axis2.AxisFault: First Element must contain the local name, Envelope
Hi Dims, Have you got a change to take a look at this issue, I've attached the log file to the JIRA. I'm kind of stuck and not able to proceed further without resolving this issue. Thanks Raghu -Original Message- From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Friday, June 29, 2007 2:52 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [Axis2] org.apache.axis2.AxisFault: First Element must contain the local name, Envelope Hi Dims, I've attached the log file to the JIRA (AXIS2-2352), Can you please take a look at it and see if you can find anything related to this issue or if you need more info from me. Thanks Raghu -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 27, 2007 11:58 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] org.apache.axis2.AxisFault: First Element must contain the local name, Envelope Raghu, I've reviewed the code in question..need more info. Can you switch on log4j based logging and upload the log in a JIRA? You have to edit commons-logging.properties and log4j.properties and put them in WEB-INF/classes and then hit the server with your client again. thanks, dims On 6/27/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi, Has anyone got this issue? I need a resolution as our development is not working because of this AxisFault. Just to recap the issue When I deploy my webservices on my localhost (desktop) and test it using a java client, it is working fine. But when the same webservices project is built deployed on our development server and tested using java client, I'm getting the below exception. org.apache.axis2.AxisFault: First Element must contain the local name, Envelope First Element must contain the local name, Envelope org.apache.axis2.AxisFault: First Element must contain the local name, Envelope at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti ls.java:81) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:356) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:294) at com.rsys.ws.client.ResponsysWSServiceStub.login(ResponsysWSServiceStub.j ava:276) at com.rsys.ws.samples.TestRILoginCmd.execute(TestRILoginCmd.java:29) at com.rsys.ws.samples.TestRILoginCmd.execute(TestRILoginCmd.java:16) at com.rsys.ws.samples.TestResponsysWSClient.main(TestResponsysWSClient.jav a:40) Caused by: org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(St AXSOAPModelBuilder.java:221) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement( StAXSOAPModelBuilder.java:179) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1 35) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope( StAXSOAPModelBuilder.java:163) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPM odelBuilder.java:111) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:474 ) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti ls.java:142) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti ls.java:77) ... 6 more I've also specified the SOAP Request Response to from this server in the below email for reference. PS: I'm using Axis2 1.2, deploying the application in JBoss on a Linux machine. Thanks Raghu From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 11:29 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [Axis2] org.apache.axis2.AxisFault: First Element must contain the local name, Envelope Hi Dims, I've tried to get the request response SOAP messages for this request. Here is the request response for this. Any idea why I'm getting a NPE in AxisServlet. Dev-Orion Login SOAP Request POST /webservices/services/ResponsysWSService HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: User-Agent: Axis2 Host: dev-orion.corp.responsys.com:1234 Transfer-Encoding: chunked 119 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns1:login xmlns:ns1=urn:ws.rsys.com ns1:usernameraghu/ns1:username ns1:passwordraghu/ns1:password /ns1:login /soapenv:Body /soapenv:Envelope 0 Dev-Orion Login SOAP Response HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type:
Re: Performance ServiceClient vs. OperationClient
For best performance, lot of effort mind you :) is to use OMDataSource (see test case in AXIOM svn) on the send side. You will have to use the serialize method the gives you XMLStreamWriter and you can write out the xml directly to the output stream. On the other side, you can get a XMLStreamReader using getXMLStreamReaderWithoutCaching on the returned OMElement. using that you can read whatever pieces you need from the response. thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: Hi Dims, I already expected something like this ... I just couldn't find much optimization in the generated ADB stubs - I probably just looked at the wrong places ... Currently my AXIOM code is quite naive. I am using the createOMElement and createOMText methods of OMFactory to iteratively create my SOAP payload, and invoke the service using the ServiceClient interface snip ServiceClient sender = new ServiceClient(); OMelement result = sender.sendReceive(axisOp); /snip /philipp Davanum Srinivas schrieb: Philipp, Am afraid the key to performance is not ServiceClient vs OperationClient as you rightly pointed guessed. The key is AXIOM itself and its usage. If you post your code with request/response sample then we may be able to help. But the best way to understand is to look at the generated code for ADB databinding. All tricks we know in terms of perfomance gets into the generated code :) thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: Hi list, I have a question rg. performance of the ServiceClient compared to the OperationClient interface. Personally, I would expect the performance* to be roughly the same for both interfaces since ServiceClient is just a more convenient wrapper for simple tasks. But now I have measured the invocation times (as defined below), and found that my handwritten client (which uses ServiceClient and AXIOM) takes about 4 times as long as the stubs generated by wsdl2java (which use the OperationClient interface) to produce a result against the same service. I guess the reason for this performance boost of the client is either that (a) the OperationClient interface is for some reason a lot faster than the ServiceClient interface or that (b) there is some tricky optimization going on somewhere in the ADB stubs that I failed to see so far. Has anybody any insight here that could help me to improve my self-produced client, or any other information that would help me understand the differences here? thanks in advance, philipp P.S.: I also did a few comparisons with other frameworks (WSIF and XFire), and Axis2 seems to be doing quite well so far. Definitely quicker than WSIF, and in a good tie with XFire (but I still have to do a lot to get really conclusive results here). *in this context I mean with performance the time between calling eg. ServiceClient.sendReceive() and the response being returned to the client. - 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] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Performance ServiceClient vs. OperationClient
OK, so it actually is that much quicker to use XMLStreamWriter and writeStartElement(), writeEndElement() instead of createOMElement() and the like? What is the reason for this? I experimented a little with the generated Axis2 stubs, and added a simple env.toStringWithConsume(); just to see how this preliminary consumation of the AXIOM model influences the invocation time. To my surprise this didn't quite change the invocation time that much ... Is there any good documentation on AXIOM and stream parsing available? I definitely need to understand AXIOM a lot better before I am able to make significant process here ... thanks for your help, philipp Davanum Srinivas wrote: For best performance, lot of effort mind you :) is to use OMDataSource (see test case in AXIOM svn) on the send side. You will have to use the serialize method the gives you XMLStreamWriter and you can write out the xml directly to the output stream. On the other side, you can get a XMLStreamReader using getXMLStreamReaderWithoutCaching on the returned OMElement. using that you can read whatever pieces you need from the response. thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: Hi Dims, I already expected something like this ... I just couldn't find much optimization in the generated ADB stubs - I probably just looked at the wrong places ... Currently my AXIOM code is quite naive. I am using the createOMElement and createOMText methods of OMFactory to iteratively create my SOAP payload, and invoke the service using the ServiceClient interface snip ServiceClient sender = new ServiceClient(); OMelement result = sender.sendReceive(axisOp); /snip /philipp Davanum Srinivas schrieb: Philipp, Am afraid the key to performance is not ServiceClient vs OperationClient as you rightly pointed guessed. The key is AXIOM itself and its usage. If you post your code with request/response sample then we may be able to help. But the best way to understand is to look at the generated code for ADB databinding. All tricks we know in terms of perfomance gets into the generated code :) thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: Hi list, I have a question rg. performance of the ServiceClient compared to the OperationClient interface. Personally, I would expect the performance* to be roughly the same for both interfaces since ServiceClient is just a more convenient wrapper for simple tasks. But now I have measured the invocation times (as defined below), and found that my handwritten client (which uses ServiceClient and AXIOM) takes about 4 times as long as the stubs generated by wsdl2java (which use the OperationClient interface) to produce a result against the same service. I guess the reason for this performance boost of the client is either that (a) the OperationClient interface is for some reason a lot faster than the ServiceClient interface or that (b) there is some tricky optimization going on somewhere in the ADB stubs that I failed to see so far. Has anybody any insight here that could help me to improve my self-produced client, or any other information that would help me understand the differences here? thanks in advance, philipp P.S.: I also did a few comparisons with other frameworks (WSIF and XFire), and Axis2 seems to be doing quite well so far. Definitely quicker than WSIF, and in a good tie with XFire (but I still have to do a lot to get really conclusive results here). *in this context I mean with performance the time between calling eg. ServiceClient.sendReceive() and the response being returned to the client. - 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]
SAML Issued Token
I am trying to find a sample to demonstrate a Secured Token Service using a SAML 1.1 security tokens. I have found a few WS-SecurityPolicy snippets that reference IssuedToken, Address, RequestedSecurityTokenTemplate and KeyType but I have not been able to piece them together and have a working sample. I am not sure if I needs other XML nodes such as SamlToken. I am running Rampart 1.2 on Axis2 1.2. This will be running the STS and the service. The client throws an exception. I am running TCPMonitor and see no traffic so I assume the issue is how I have specified the STS. I can supply my Policy.xml but would rather have a new one since the one I have just pieced together and it has no significance. I would appreciate any samples. Thanks, Wes.
Re: [Axis2] ConvertUtil.convertToDateTime - Unparseable date
It could be a problem with the date string format. You can have a look at the http://www.w3.org/TR/xmlschema-2/#isoformats to see the allowed date string formats. It seems that this date string may have a problem but I could be mistaken since I went through it rather quickly Ajith On 7/2/07, Tom Hughes [EMAIL PROTECTED] wrote: Hello, Just starting out with Axis2. I'm trying to interface with an existing web service. I generated my client using the wsdltojava tool and the adb binding. When I send a request I get the following stacktrace : Jul 1, 2007 7:25:33 PM org.apache.commons.httpclient.HttpMethodBase readResponse INFO: Discarding unexpected response: HTTP/1.1 100 Continue java.lang.RuntimeException: java.lang.NumberFormatException: Unparseable date: 2007-07-01T19:20:11.4766598GMT+01:00 at com.globalbettingexchange.www.externalapi.SecureServiceStub.fromOM(Unknown Source) at com.globalbettingexchange.www.externalapi.SecureServiceStub.GetAccountBalances(Unknown Source) at com.tom.sportsbetting.Main.main(Main.java:25) Caused by: java.lang.NumberFormatException: Unparseable date: 2007-07-01T19:20:11.4766598GMT+01:00 at org.apache.axis2.databinding.utils.ConverterUtil.convertToDateTime(ConverterUtil.java:589) at com.globalbettingexchange.www.externalapi.SecureServiceStub$GetAccountBalancesResponse$Factory.parse(Unknown Source) at com.globalbettingexchange.www.externalapi.SecureServiceStub$GetAccountBalancesResponse99$Factory.parse(Unknown Source) ... 3 more I'm using the latest release, 1.2 I've attached the wsdl. Can anyone help? thanks, Tom _ Txt a lot? Get Messenger FREE on your mobile. https://livemessenger.mobile.uk.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Performance ServiceClient vs. OperationClient
That's because you already created the AXIOM model in memory...I'd recommend starting from this test case :) http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/modules/axiom-tests/src/test/java/org/apache/axiom/om/impl/llom/OMSourcedElementTest.java thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: OK, so it actually is that much quicker to use XMLStreamWriter and writeStartElement(), writeEndElement() instead of createOMElement() and the like? What is the reason for this? I experimented a little with the generated Axis2 stubs, and added a simple env.toStringWithConsume(); just to see how this preliminary consumation of the AXIOM model influences the invocation time. To my surprise this didn't quite change the invocation time that much ... Is there any good documentation on AXIOM and stream parsing available? I definitely need to understand AXIOM a lot better before I am able to make significant process here ... thanks for your help, philipp Davanum Srinivas wrote: For best performance, lot of effort mind you :) is to use OMDataSource (see test case in AXIOM svn) on the send side. You will have to use the serialize method the gives you XMLStreamWriter and you can write out the xml directly to the output stream. On the other side, you can get a XMLStreamReader using getXMLStreamReaderWithoutCaching on the returned OMElement. using that you can read whatever pieces you need from the response. thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: Hi Dims, I already expected something like this ... I just couldn't find much optimization in the generated ADB stubs - I probably just looked at the wrong places ... Currently my AXIOM code is quite naive. I am using the createOMElement and createOMText methods of OMFactory to iteratively create my SOAP payload, and invoke the service using the ServiceClient interface snip ServiceClient sender = new ServiceClient(); OMelement result = sender.sendReceive(axisOp); /snip /philipp Davanum Srinivas schrieb: Philipp, Am afraid the key to performance is not ServiceClient vs OperationClient as you rightly pointed guessed. The key is AXIOM itself and its usage. If you post your code with request/response sample then we may be able to help. But the best way to understand is to look at the generated code for ADB databinding. All tricks we know in terms of perfomance gets into the generated code :) thanks, dims On 7/2/07, Philipp Leitner [EMAIL PROTECTED] wrote: Hi list, I have a question rg. performance of the ServiceClient compared to the OperationClient interface. Personally, I would expect the performance* to be roughly the same for both interfaces since ServiceClient is just a more convenient wrapper for simple tasks. But now I have measured the invocation times (as defined below), and found that my handwritten client (which uses ServiceClient and AXIOM) takes about 4 times as long as the stubs generated by wsdl2java (which use the OperationClient interface) to produce a result against the same service. I guess the reason for this performance boost of the client is either that (a) the OperationClient interface is for some reason a lot faster than the ServiceClient interface or that (b) there is some tricky optimization going on somewhere in the ADB stubs that I failed to see so far. Has anybody any insight here that could help me to improve my self-produced client, or any other information that would help me understand the differences here? thanks in advance, philipp P.S.: I also did a few comparisons with other frameworks (WSIF and XFire), and Axis2 seems to be doing quite well so far. Definitely quicker than WSIF, and in a good tie with XFire (but I still have to do a lot to get really conclusive results here). *in this context I mean with performance the time between calling eg. ServiceClient.sendReceive() and the response being returned to the client. - 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] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/
Martin, Thanks for your help. I got it working! I was confused about what the directory structure needed to be. Once I built the axis2.war and placed it under C:\Tomcat6\webapps it all started working. Anyway, thank you very much for all of your assistance. Best, Jon Martin Gainty wrote: Hi Jon- 1st) do you'llhave jsp-api.jar if so which version? myjsp-api.jar has a date timestamp of04/14/2006 and is 50,501 and is located in %CATALINA_HOME%\common\lib 2nd) please provide the wsdl Thanks Martin This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Willard To: axis-user@ws.apache.org Sent: Sunday, July 01, 2007 12:29 PM Subject: Re: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/ Hi Martin, Sorry for my confusion but jetspeed appears to be a portal ... I am trying to use Axis / WebService with Tomcat 6. Can you clarify for me? I apologize for being such a newbie ... Alos, jetspeed says it is compatible with Tomcat 5.0.x Tomcat 5.5.x but I have Tomcat6 Best, Jon Martin Gainty wrote: Good Evening Willard please verify your jsp-api.jar is fairly recent (I was able to d/l from jetspeed2.1 site) http://portals.apache.org/jetspeed-2/download.html 04/14/2006 02:09 PM 50,501 jsp-api.jar If youcan attachthe WSDL I'll try to re-producethat errorhere... HTH M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Willard To: axis-user@ws.apache.org Sent: Saturday, June 30, 2007 6:15 PM Subject: Re: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/ Thanks Martin, I have tomcat 6.0.1.3 and I do not have a common/lib, just a /lib under tomcat. I added my C:\Tomcat6\lib\jsp-api.jar to my classpath, rebooted, verified and it still does not work. Do you know if tomcat6.0 uses the Windows env var for CLASSPATH? I rebooted because tomcat is running as a service and I know that there are issues with SCM picking up env changes. Any other ideas? Best, Jon Martin Gainty wrote: known bug add "$TOMCAT_HOME\common\lib\jsp-api.jar" to classpath http://mail-archives.apache.org/mod_mbox/ws-axis-user/200704.mbox/[EMAIL PROTECTED] HTH M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Willard To: axis-user@ws.apache.org Sent: Saturday, June 30, 2007 4:02 PM Subject: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/ New to axis ... Trying to access http://127.0.0.1:8080/axis2-web/ while running Tomcat6.0.1.3. I have placed the Axis2 war in the tomcat webapps as specified. The tomcat Manager page is fine. Any ideas? type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 6 in the generated java file Only a type can be imported. org.apache.axis2.Constants resolves to a package An error occurred at line: 7 in the generated java file Only a type can be imported. org.apache.axis2.context.ConfigurationContext resolves to a package An error occurred at line: 8 in the generated java file Only a type can be imported. org.apache.axis2.description.Parameter resolves to a package An error occurred at line: 9 in the generated java file Only a type can be imported. org.apache.axis2.transport.http.AxisServlet resolves to a package An error occurred at line: 12 in the jsp
Re: [Axis2] ConvertUtil.convertToDateTime - Unparseable date
I believe the offending tag is the TimeStamp in the BaseResponse type. It is defined as xs:dateTime. According to the document the required format is : '-'? '-' mm '-' dd 'T' hh ':' mm ':' ss ('.' s+)? (zz)? It seems to me the date: 2007-07-01T19:20:11.4766598GMT+01:00 is valid. Is there a way to hook into the conversion and add my own formatters? thanks, Tom From: Ajith Ranabahu [EMAIL PROTECTED] Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: Re: [Axis2] ConvertUtil.convertToDateTime - Unparseable date Date: Mon, 2 Jul 2007 11:19:04 -0700 It could be a problem with the date string format. You can have a look at the http://www.w3.org/TR/xmlschema-2/#isoformats to see the allowed date string formats. It seems that this date string may have a problem but I could be mistaken since I went through it rather quickly Ajith On 7/2/07, Tom Hughes [EMAIL PROTECTED] wrote: Hello, Just starting out with Axis2. I'm trying to interface with an existing web service. I generated my client using the wsdltojava tool and the adb binding. When I send a request I get the following stacktrace : Jul 1, 2007 7:25:33 PM org.apache.commons.httpclient.HttpMethodBase readResponse INFO: Discarding unexpected response: HTTP/1.1 100 Continue java.lang.RuntimeException: java.lang.NumberFormatException: Unparseable date: 2007-07-01T19:20:11.4766598GMT+01:00 at com.globalbettingexchange.www.externalapi.SecureServiceStub.fromOM(Unknown Source) at com.globalbettingexchange.www.externalapi.SecureServiceStub.GetAccountBalances(Unknown Source) at com.tom.sportsbetting.Main.main(Main.java:25) Caused by: java.lang.NumberFormatException: Unparseable date: 2007-07-01T19:20:11.4766598GMT+01:00 at org.apache.axis2.databinding.utils.ConverterUtil.convertToDateTime(ConverterUtil.java:589) at com.globalbettingexchange.www.externalapi.SecureServiceStub$GetAccountBalancesResponse$Factory.parse(Unknown Source) at com.globalbettingexchange.www.externalapi.SecureServiceStub$GetAccountBalancesResponse99$Factory.parse(Unknown Source) ... 3 more I'm using the latest release, 1.2 I've attached the wsdl. Can anyone help? thanks, Tom _ Txt a lot? Get Messenger FREE on your mobile. https://livemessenger.mobile.uk.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Win tickets to the sold out Live Earth concert! http://liveearth.uk.msn.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] ConvertUtil.convertToDateTime - Unparseable date
Like Tom said, the format date string is probably like this: -MM-dd'T'HH:mm:ss.SSS'Z' The code following works for me. ... Date theDate = null; String formattedStr = 2007-05-10T15:22:07.000Z; SimpleDateFormat tempFormat = new SimpleDateFormat(-MM-dd'T'HH:mm:ss.SSS'Z'); try { theDate = tempFormat.parse(formattedStr); } catch (java.text.ParseException pe) { System.out.println(We got a parsing exception: + pe.getMessage()); } Calendar cal = new GregorianCalendar(); cal.setTime(theDate); .. -jeff -Original Message- From: Tom Hughes [mailto:[EMAIL PROTECTED] Sent: Monday, July 02, 2007 3:48 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] ConvertUtil.convertToDateTime - Unparseable date I believe the offending tag is the TimeStamp in the BaseResponse type. It is defined as xs:dateTime. According to the document the required format is : '-'? '-' mm '-' dd 'T' hh ':' mm ':' ss ('.' s+)? (zz)? It seems to me the date: 2007-07-01T19:20:11.4766598GMT+01:00 is valid. Is there a way to hook into the conversion and add my own formatters? thanks, Tom From: Ajith Ranabahu [EMAIL PROTECTED] Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: Re: [Axis2] ConvertUtil.convertToDateTime - Unparseable date Date: Mon, 2 Jul 2007 11:19:04 -0700 It could be a problem with the date string format. You can have a look at the http://www.w3.org/TR/xmlschema-2/#isoformats to see the allowed date string formats. It seems that this date string may have a problem but I could be mistaken since I went through it rather quickly Ajith On 7/2/07, Tom Hughes [EMAIL PROTECTED] wrote: Hello, Just starting out with Axis2. I'm trying to interface with an existing web service. I generated my client using the wsdltojava tool and the adb binding. When I send a request I get the following stacktrace : Jul 1, 2007 7:25:33 PM org.apache.commons.httpclient.HttpMethodBase readResponse INFO: Discarding unexpected response: HTTP/1.1 100 Continue java.lang.RuntimeException: java.lang.NumberFormatException: Unparseable date: 2007-07-01T19:20:11.4766598GMT+01:00 at com.globalbettingexchange.www.externalapi.SecureServiceStub.fromOM(Unk nown Source) at com.globalbettingexchange.www.externalapi.SecureServiceStub.GetAccount Balances(Unknown Source) at com.tom.sportsbetting.Main.main(Main.java:25) Caused by: java.lang.NumberFormatException: Unparseable date: 2007-07-01T19:20:11.4766598GMT+01:00 at org.apache.axis2.databinding.utils.ConverterUtil.convertToDateTime(Con verterUtil.java:589) at com.globalbettingexchange.www.externalapi.SecureServiceStub$GetAccount BalancesResponse$Factory.parse(Unknown Source) at com.globalbettingexchange.www.externalapi.SecureServiceStub$GetAccount BalancesResponse99$Factory.parse(Unknown Source) ... 3 more I'm using the latest release, 1.2 I've attached the wsdl. Can anyone help? thanks, Tom _ Txt a lot? Get Messenger FREE on your mobile. https://livemessenger.mobile.uk.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Win tickets to the sold out Live Earth concert! http://liveearth.uk.msn.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ServiceGroupID
Any ideas on this?? Using SOAP sessin, If I call a method and it throws an exception, and just after that I call a second one I observe different behaviour depending on this second method. If the second method is the same as the first, Axis2 recognises that the session was opened. Buf if the second method is a different one, Axis2 opens a new SOAP session. I'm always using the same client and the same service. Thanks in advance, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi Deepal, I was asking this because I'm trying to implement SOAP sessions using the service group id as an id for the session on my own and I'm having a strange behaviour. First my client validates, after that, ha can do any operation. If he receives a exception for any reason, he should be able to do the operation again or invoke another. I'm throwing exceptions when a non-logged user invokes an operation and when a user validates twice with the same session ID. When he invokes another operation, axis gives him another serviceGroupID, so the session is new and he receives an exception because he hasn't validated. But if he tries to validate again instead of that, he receives an exception telling that he was already validated. How is this possible?? What depends the generation of the service group id on??? Thanks, Jorge Fernández Deepal Jayasinghe [EMAIL PROTECTED] escribió: Hi Jorge , Nope you can not do so, the service group id will be send by the server after the first request. Thanks Deepal Hi! Can anybody tell me if it's possible to set the service group id from the client in a first call to a service??? Thanks in advandce, Jorge Fernández - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
int values lost
Hi! I updated Axis from 1.2 to 1.4 and now I can't use a couple of web-service that have a int as first argument. The webservice-call doesn't fail but the int-value is always one. I have debugged my code and as far as I can follow it do what it should but the reciving server only recives a 0 (zero). java -cp activation.jar:axis.jar:commons-logging-1.0.4.jar:mailapi.jar:commons-discovery-0.2.jar:wsdl4j-1.5.1.jar:jaxrpc.jar:saaj.jar org.apache.axis.wsdl.WSDL2Java and those libraries are available at the client that uses the stubs. I'm guessing that I have some kind of versioning-problem in the library (.jar) but I have no idea of how to figure out wich one it could be. How to find out what's wrong. Thanks in advance Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ServiceGroupID
ServiceGroupID is used as a SessionID. So same ServiceGroupID means same session. Hailong From: Jorge Fernandez [mailto:[EMAIL PROTECTED] Sent: Monday, July 02, 2007 4:53 PM To: axis-user Subject: Re: ServiceGroupID Any ideas on this?? Using SOAP sessin, If I call a method and it throws an exception, and just after that I call a second one I observe different behaviour depending on this second method. If the second method is the same as the first, Axis2 recognises that the session was opened. Buf if the second method is a different one, Axis2 opens a new SOAP session. I'm always using the same client and the same service. Thanks in advance, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi Deepal, I was asking this because I'm trying to implement SOAP sessions using the service group id as an id for the session on my own and I'm having a strange behaviour. First my client validates, after that, ha can do any operation. If he receives a exception for any reason, he should be able to do the operation again or invoke another. I'm throwing exceptions when a non-logged user invokes an operation and when a user validates twice with the same session ID. When he invokes another operation, axis gives him another serviceGroupID, so the session is new and he receives an exception because he hasn't validated. But if he tries to validate again instead of that, he receives an exception telling that he was already validated. How is this possible?? What depends the generation of the service group id on??? Thanks, Jorge Fernández Deepal Jayasinghe [EMAIL PROTECTED] escribió: Hi Jorge , Nope you can not do so, the service group id will be send by the server after the first request. Thanks Deepal Hi! Can anybody tell me if it's possible to set the service group id from the client in a first call to a service??? Thanks in advandce, Jorge Fernández - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com http://us.rd.yahoo.com/mail/es/tagline/messenger/*http:/es.voice.yahoo.com/ ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas http://us.rd.yahoo.com/mail/es/tagline/answers/*http:/es.answers.yahoo.com/;_ylc=X3oDMTEzNWwxbTZtBF9TAzIxMTQ3MTQxOTAEc2VjA01haWwEc2xrA3RhZ2xpbmVz .
RE: int values lost
Not sure if this helps, but you can call org.apache.axis.Version.getVersionText() to get the version of Axis you're running. I'm running Axis1.3 and they are the versions of the jars I have. I suggest you undeploy everything, copy 1.4 again, and start again with a clean deployment. -jeff -Original Message- From: Roland Carlsson [mailto:[EMAIL PROTECTED] Sent: Monday, July 02, 2007 4:56 PM To: axis-user@ws.apache.org Subject: int values lost Hi! I updated Axis from 1.2 to 1.4 and now I can't use a couple of web-service that have a int as first argument. The webservice-call doesn't fail but the int-value is always one. I have debugged my code and as far as I can follow it do what it should but the reciving server only recives a 0 (zero). java -cp activation.jar:axis.jar:commons-logging-1.0.4.jar:mailapi.jar:commons-di scovery-0.2.jar:wsdl4j-1.5.1.jar:jaxrpc.jar:saaj.jar org.apache.axis.wsdl.WSDL2Java and those libraries are available at the client that uses the stubs. I'm guessing that I have some kind of versioning-problem in the library (.jar) but I have no idea of how to figure out wich one it could be. How to find out what's wrong. Thanks in advance Roland - 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]
Best Practices for- Contract-First, Error-Handling and non-functional data
We are in the process of developing fairly large enterprise application. We have taken Contract-First approach. 1. What are some of the best practices for the Contract-First approach? 2. Are there any design patterns/practices for error handling and exception handling? 3. For non-functional data (example: Session id/transaction id for asynchronous service), are there any best practices? 4. Any case studies/strategies of reducing conversation between WS client and services? Any pointers for resources would be appreciated. Thank you in advance. Vipul Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
RE: ServiceGroupID
Hi Hailong, Yes, what you say is true. I know that. If I invoke different methods secuentially, I get the same ServiceGroupID but my problem is: if I receive an exception from one of them and I try to invoke another method after that, depending on which method is this, I receive the same ServiceGroupID or a different one and I don't know why. Thanks Jorge Fernández Wang, Hailong (NIH/CIT) [C] [EMAIL PROTECTED] escribió:v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} ServiceGroupID is used as a SessionID. So same ServiceGroupID means same session. Hailong - From: Jorge Fernandez [mailto:[EMAIL PROTECTED] Sent: Monday, July 02, 2007 4:53 PM To: axis-user Subject: Re: ServiceGroupID Any ideas on this?? Using SOAP sessin, If I call a method and it throws an exception, and just after that I call a second one I observe different behaviour depending on this second method. If the second method is the same as the first, Axis2 recognises that the session was opened. Buf if the second method is a different one, Axis2 opens a new SOAP session. I'm always using the same client and the same service. Thanks in advance, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi Deepal, I was asking this because I'm trying to implement SOAP sessions using the service group id as an id for the session on my own and I'm having a strange behaviour. First my client validates, after that, ha can do any operation. If he receives a exception for any reason, he should be able to do the operation again or invoke another. I'm throwing exceptions when a non-logged user invokes an operation and when a user validates twice with the same session ID. When he invokes another operation, axis gives him another serviceGroupID, so the session is new and he receives an exception because he hasn't validated. But if he tries to validate again instead of that, he receives an exception telling that he was already validated. How is this possible?? What depends the generation of the service group id on??? Thanks, Jorge Fernández Deepal Jayasinghe [EMAIL PROTECTED] escribió: Hi Jorge , Nope you can not do so, the service group id will be send by the server after the first request. Thanks Deepal Hi! Can anybody tell me if it's possible to set the service group id from the client in a first call to a service??? Thanks in advandce, Jorge Fernández - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas. - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
Re: NullPointerException with axis1 1.4
I Googled wsrp axis null pointer exception getServiceDescription and found a reference to a problem with sending a null to .NET. What happens if you send a value (as opposed to nil=true) in the registrationContext element? Anne On 7/2/07, Alexey Zavizionov [EMAIL PROTECTED] wrote: Thanks for your response! We implemented WSRP service on axis1 1.2-RC1, but now we start to using axis1 1.4. WSRP service has the wsdl file from oasis ( wsrp_service.wsdl from http://www.oasis-open.org/committees/wsrp/specifications/version1/ ) http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl ---WSDL--- ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=urn:oasis:names:tc:wsrp:v1:wsdl xmlns:bind=urn:oasis:names:tc:wsrp:v1:bind xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; import namespace=urn:oasis:names:tc:wsrp:v1:bind location=wsrp_v1_bindings.wsdl/ wsdl:service name=WSRPService wsdl:port binding=bind:WSRP_v1_Markup_Binding_SOAP name=WSRPBaseService soap:address location=http://my.service:8080/WSRPService/ /wsdl:port wsdl:port binding=bind:WSRP_v1_ServiceDescription_Binding_SOAP name=WSRPServiceDescriptionService soap:address location=http://my.service:8080/WSRPService/ /wsdl:port wsdl:port binding=bind:WSRP_v1_Registration_Binding_SOAP name=WSRPRegistrationService soap:address location=http://my.service:8080/WSRPService/ /wsdl:port wsdl:port binding=bind:WSRP_v1_PortletManagement_Binding_SOAP name=WSRPPortletManagementService soap:address location=http://my.service:8080/WSRPService/ /wsdl:port /wsdl:service /wsdl:definitions -- Do you know where cause of this problem? Alexey On 6/27/07, Martin Gainty [EMAIL PROTECTED] wrote: Alexey please post the wsdl Thanks M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Alexey Zavizionov [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, June 27, 2007 11:10 AM Subject: Re: NullPointerException with axis1 1.4 I catch the soap message: POST /portal/services/WSRPServiceDescriptionService HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: localhost:8080 Cache-Control: no-cache Pragma: no-cache SOAPAction: urn:oasis:names:tc:wsrp:v1:getServiceDescription Content-Length: 421 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body getServiceDescription xmlns=urn:oasis:names:tc:wsrp:v1:types registrationContext xsi:nil=true/ desiredLocalesen/desiredLocales /getServiceDescription /soapenv:Body /soapenv:Envelope HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=D8D788AB8D4D347C7C65F5C3B3FAE75D; Path=/portal Content-Type: text/xml;charset=utf-8 Date: Wed, 27 Jun 2007 15:05:28 GMT Connection: close ?xml version=1.0 encoding=utf-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body soapenv:Fault faultcodesoapenv:Server.userException/faultcode faultstringjava.lang.NullPointerException/faultstring detail ns1:hostname xmlns:ns1=http://xml.apache.org/axis/;Alex/ns1:hostname /detail /soapenv:Fault /soapenv:Body /soapenv:Envelope Any idea are appreciable! Regards, Alexey On 6/27/07, Alexey Zavizionov [EMAIL PROTECTED] wrote: Hello, I am using axis1 version 1.4 for wsrp service. I have an exc: AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.lang.NullPointerException faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:Alex java.lang.NullPointerException at org.apache.axis.message.SOAPFaultBuilder.createFault( SOAPFaultBuilder.java:222) at org.apache.axis.message.SOAPFaultBuilder.endElement( SOAPFaultBuilder.java:129) at org.apache.axis.encoding.DeserializationContext.endElement( DeserializationContext.java:1087) at
Different XML order in WSDL File with Axis 1.2
Hi, I am deploying my axis services on one machine and I see different wsdl and on other machine , same service generates different wsdl. The difference is only in ordering of operations. I rearranged the wsdl and they both are same. Only difference in environment I could see is different JRE different versions besides that environment is same. I am accessing wsdl via URL if it does matter. How could I maintain the same order of wsdl every time when I deploy service.. Thanks, Petr V. - Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
Re: Array namespace problem
First, if you intend to support interoperability between Axis and .NET, do not use SOAP encoding. You should switch to wrapped document/literal style. (specify style=Wrapped in your WSDD). Even with wrapped style, though, array interoperability can be tricky. Second, if you want to use specific namespaces, you should either: 1- use the WSDL first development approach (preferred) 2- generate your WSDL using Java2WSDL and specify the Pkg2NS option. Be prepared to tweak the generated WSDL to ensure it comes out the way you want it to, and then run WSDL2Java. Alternatively, you can try Axis2 (which does not support SOAP encoding, by the way). Anne On 7/2/07, Lukas Füllemann [EMAIL PROTECTED] wrote: Hi I am using Axis 1.4 and have two webservices sharing a common type of class 'Master'. This class has an array of another class 'Detail'. 'Master' and 'Detail' are in a separate package than the two web services (which are again in different packages). While generating the wsdl for the two webservices, each wsdl generates for the Master type an ArrayOf_tns2_Detail type descriptor defined in the namespace of the webservice and not in the namespace of the Master or Detail type. Now I use the .NET wsdl class generator, which creates two different master classes, because they contain arrays defined in different namespaces. How can I tell Axis to use a certain namespace for the array definitions? Can Axis2 solve this problem? Wsdl of Webservice1: wsdl:types schema targetNamespace=http://commonobjects.ws.arregulo.sowatec.com; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://webservice.ws1.arregulo.sowatec.com/ import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=Detail sequence element name=name nillable=true type=xsd:string/ /sequence /complexType complexType name=Master sequence element name=details nillable=true type=impl:ArrayOf_tns2_Detail/ /sequence /complexType /schema schema targetNamespace=http://webservice.ws1.arregulo.sowatec.com; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://commonobjects.ws.arregulo.sowatec.com/ import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=ArrayOf_tns2_Detail complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns2:Detail[]/ /restriction /complexContent /complexType /schema /wsdl:types Wsdl of Webservice2: wsdl:types schema targetNamespace=http://commonobjects.ws.arregulo.sowatec.com; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://webservice.ws2.arregulo.sowatec.com/ import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=Detail sequence element name=name nillable=true type=xsd:string/ /sequence /complexType complexType name=Master sequence element name=details nillable=true type=impl:ArrayOf_tns2_Detail/ /sequence /complexType /schema schema targetNamespace=http://webservice.ws2.arregulo.sowatec.com; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://commonobjects.ws.arregulo.sowatec.com/ import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=ArrayOf_tns2_Detail complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns2:Detail[]/ /restriction /complexContent /complexType /schema /wsdl:types Thanks, Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: minoccurs in sequence
Michael, First let me explain the problem with your original schema -- it was not valid. You specified: wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://quickstart.samples/xsd; xs:element name=MyArray xs:complexType xs:element name=My minOccurs=1 maxOccurs=unbounded / xs:sequence xs:element name=MyOne type=xs:string / xs:element name=MyTwo type=xs:string / xs:element name=MyThree type=xs:string / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types but, you can't define the My element immediately after the xs:complexType, and then you can't define an xs:sequence immediately after the My element. Amila provided a correction by defining named types (my preference), but if you wanted to use anonymous types, you would need to define it like this: wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://quickstart.samples/xsd; xs:element name=MyArray xs:complexType xs:sequence xs:element name=My minOccurs=1 maxOccurs=unbounded xs:complexType xs:sequence xs:element name=MyOne type=xs:string / xs:element name=MyTwo type=xs:string / xs:element name=MyThree type=xs:string / /xs:sequence /xs:complexType /xs:element /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types As for multipart message support -- based on the example you provided in your question, I assume you are asking whether Axis2 supports multiple parts in an input or output message. This capability depends on the SOAP message style you're using. If you are using document style, then the message may contain only one message part in the SOAP body. That message part represents the document that you are sending in the message. If you want to send multiple XML fragments, then you must define a wrapper element that encompasses all your fragments into a single element. (You may define additional message parts that will be conveyed in the SOAP header, but typically you define header parts using WS-Policy rather than the WSDL.) This is a SOAP protocol constraint of the document style, not an Axis2 constraint. The SOAP Body may convey only one child element. If you are using rpc style, then you can specify any number of message parts -- each part representing a parameter in the RPC message. At runtime, Axis2 automatically generates a single wrapping element that encompasses the parameters, so that the SOAP Body still conveys only one child element. Hope that helps. Anne On 6/30/07, Michael Potter [EMAIL PROTECTED] wrote: Amila, Thanks for this reply. I will use this information. I think the confusion (on my part or yours, does not matter tho ;) is that I posted two different questions. My minoccurs in sequence question has been answered. My multipart message question was not answered. I will add some sample code to that thread on monday when I am back at work. from memory: message name=xxx part name=part1 element=xxx/ part name=part2 element=yyy/ /message gives this error: SEVERE: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException: More than one part for message Thanks a bunch. -- Michael Potter On 6/28/07, Amila Suriarachchi [EMAIL PROTECTED] wrote: I am not sure what you mean by multipart messages? can you give an sample schema? Actually I have not gone through your initial mail clearly and just reply seen the subject . There you have given, xs:element name=MyArray xs:complexType xs:element name=My minOccurs=1 maxOccurs=unbounded / xs:sequence xs:element name=MyOne type=xs:string / xs:element name=MyTwo type=xs:string / xs:element name=MyThree type=xs:string / /xs:sequence /xs:complexType /xs:element Is this schema valid? I think you can not declare and element just after a complex Type. What I mean was ADB supports following types of schema now xs:element name=MyArray xs:complexType xs:sequence minOccurs=1 maxOccurs=unbounded xs:element name=My / xs:element name=MyOne type=xs:string / xs:element name=MyTwo type=xs:string / xs:element name=MyThree type=xs:string / /xs:sequence /xs:complexType /xs:element in you first mail you have said ADB databinding does not support minOccurs and maxOccurs attributes in sequence and choice elements ( i.e., sequence minOccurs=0 maxOccurs=unbounded /sequence) This is true for Axis2 1.2. but now we have added this feature. Amila. On 6/29/07,
Re: Weird Generated WSDL with Axis 2
Try the WSDL first approach. On 6/29/07, Petr V. [EMAIL PROTECTED] wrote: Okay I figure out the issue but I have no solution. If your service is implementing some interface then the parameters are named as param0 and param1 of functions from interface. It has nothing to do with debug option. Is there any work around ?? Thanks *Petr V. [EMAIL PROTECTED]* wrote: Thanks Davanum, I am using maven to compile my classes and by default debug flag is on for compiling code.I als opexplicitly set it true. Any more ideas please. Thanks, Petr *Davanum Srinivas [EMAIL PROTECTED]* wrote: It's a basic java problem. you can test it using javap command, if you compile a class with debug on, it stores the names of the parameters, if you don't then the class does not have that information. If the class does not have that information, then obviously we can't get it from the class when we construct the wsdl. thanks, dims On 6/29/07, Petr V. wrote: Thanks for such a quick reply. Would you like to see the log or would it solve the problem. Is that known problem with Axis2, some one in my team told me that it is known issue and I did not believe him as this is such a basic issue. Thanks, Petr Davanum Srinivas wrote: compile your classes with debug option on before you deploy the classes. On 6/29/07, Petr V. wrote: I generated wsdl via Axis2 by accessing my service via URL and I see param names as param0 and param1 etc. I did not expect that, I was hoping to see my proper parameters name in wsdl. Can any one let me know please what is going on or is there any work around. Thanks, Petr Shape Yahoo! in your own image. Join our Network Research Panel today! -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Take the Internet to Go: Yahoo!Go puts the Internet in your pocket:http://us.rd.yahoo.com/evt=48253/*http://mobile.yahoo.com/go?refer=1GNXICmail, news, photos more. -- Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Nowhttp://us.rd.yahoo.com/evt=48223/*http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow(it's updated for today's economy) at Yahoo! Games.
Re: multipart message alternatives
As I said in my last reply to you, this is a limitation of SOAP document style. If you want to use multiple parts, switch to RPC, but a better approach is to stick with document style and define a single wrapper element for your multiple types. Anne On 6/26/07, Michael Potter [EMAIL PROTECTED] wrote: I would like to use multipart messages. When I run this command: ksh $AXIS2_HOME/bin/wsdl2java.sh -uri ./MyService.wsdl -p samples.quickstart -o . -d adb -s -wv 1.1 -ss -sd on a file with multiple parts in a message, I get this error: SEVERE: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException: More than one part for message I suspect I can combine the multiple parts in the types area of the wsdl, but are there other options? -- Michael Potter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble with incoming .NET request
I sounds like the .NET endpoint is sending the message using the TCP transport. Tell the .NET folks to use their SOAP/HTTP binding instead. Anne On 6/26/07, Michael Nishizawa [EMAIL PROTECTED] wrote: I seem to be having some trouble with an incoming request from a .NET server. I get the following error org.apache.axis2.transport.tcp.TCPServer - Unable to generate EPR for the transport tcp I am not using a TCP transport reciever, but there has never been a problem recieving messages until recently. The local environment is a java web service, the remote client is .NET. I have a test client which allows me to hit the url successfully. The raw messages are identical, the only difference is that they are using .NET and I am using java. Anyone have an idea on this?
Re: WSDL2Java issue and/or help
Jeff, This URL: https://uat-atc.regents.ohio.gov/ccx/OrgInfo/CoreMain_v1.0.0.xsd?wsdl does indeed point to the XSD in question. This problem looks to me to be caused by WSDL2Java's inability to reference a remote XSD. Keith should do as Haneef recommends and download the XSD and store it locally, and change the schemaLocation attribute in the WSDL to point to the new location. Also, the urn:org:pesc:core:Coremain:v1.0.0 namespace is not badly formed. A namespace must be a valid URI (not any unique string), but it doesn't have to start with http://;. In this case, it's a URN rather than a URL, which is quite appropriate for a namespace URI. See the Wikipedia definition of Uniform Resource Identifier [1] for a layman's definition, or see RFC 3986 [2] for the formal specification. [1] http://en.wikipedia.org/wiki/Uniform_Resource_Identifier [2] http://gbiv.com/protocols/uri/rfc/rfc3986.html Anne On 6/26/07, Walker, Jeff [EMAIL PROTECTED] wrote: This line looks odd to me also: xsd:import namespace=urn:org:pesc:core:CoreMain:v1.0.0 schemaLocation=OrgInfo/CoreMain_v1.0.0.xsd?wsdl/ Here is a definition of how import works in XML Schema: http://www.w3.org/TR/xmlschema-0/ section 5.4. So, the ?wsdl at the end of the schemaLocation string looks weird. I did in fact download that wsdl file, and got the same error in Axis 1.3as you did. I do believe the web service development team is wrong at this point. -- I also think the namespace urn:org:pesc:core:Coremain:v1.0.0 is badly formatted. They usually start with http://;, but I did read somewhere they can be any unique string. Perhaps on this point, they are right. -jeff -- *From:* Keith Veleba [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, June 26, 2007 4:03 PM *To:* axis-user@ws.apache.org *Subject:* WSDL2Java issue and/or help I'm writing a client for a web service and I am having an issue with stub generation. This wsdl is causing the generation to fail: https://uat-atc.regents.ohio.gov/ccx/OrgInfo?wsdl Specifically, I get an error saying it cannot find the schemaLocation of the imported schema on line 4: xsd:import namespace=urn:org:pesc:core:CoreMain:v1.0.0 schemaLocation=OrgInfo/CoreMain_v1.0.0.xsd?wsdl/ This schemaLocation looks very odd to me, but the folks who run the web service say it is valid and should be working. Here's the error when I run wsdl2java.sh: Retrieving schema at 'OrgInfo/CoreMain_v1.0.0.xsd?wsdl', relative to ' file:/Users/velebak/https:/uat-atc.regents.ohio.gov/ccx'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init( CodeGenerationEngine.java:114) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'OrgInfo/CoreMain_v1.0.0.xsd?wsdl', relative to ' file:/Users/velebak/https:/uat-atc.regents.ohio.gov/ccx'.: java.io.FileNotFoundException: This file was not found: file:/Users/velebak/https:/uat-atc.regents.ohio.gov/OrgInfo/CoreMain_v1.0.0.xsd?wsdl at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile( CodeGenerationEngine.java:276) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init( CodeGenerationEngine.java:97) ... 2 more Caused by: java.io.FileNotFoundException: This file was not found: file:/Users/velebak/https:/uat-atc.regents.ohio.gov/OrgInfo/CoreMain_v1.0.0.xsd?wsdl at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown Source) ... 11 more Any ideas what may be going on here? It looks like it is looking for an actual local file, but it is not local, it is hosted remotely. Thanks in advance. -- Keith E. Veleba President Intellitek Services Ltd. 419-202-2676 cell [EMAIL PROTECTED] http://www.intellitekservices.com
Re: WSDL2Java issue and/or help
Anne, Jeff, The problem is the https://; the normal URL connection expects the cert to be in the local jks store AFAICT. thanks, dims On 7/2/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: Jeff, This URL: https://uat-atc.regents.ohio.gov/ccx/OrgInfo/CoreMain_v1.0.0.xsd?wsdl does indeed point to the XSD in question. This problem looks to me to be caused by WSDL2Java's inability to reference a remote XSD. Keith should do as Haneef recommends and download the XSD and store it locally, and change the schemaLocation attribute in the WSDL to point to the new location. Also, the urn:org:pesc:core:Coremain:v1.0.0 namespace is not badly formed. A namespace must be a valid URI (not any unique string), but it doesn't have to start with http://;. In this case, it's a URN rather than a URL, which is quite appropriate for a namespace URI. See the Wikipedia definition of Uniform Resource Identifier [1] for a layman's definition, or see RFC 3986 [2] for the formal specification. [1] http://en.wikipedia.org/wiki/Uniform_Resource_Identifier [2] http://gbiv.com/protocols/uri/rfc/rfc3986.html Anne On 6/26/07, Walker, Jeff [EMAIL PROTECTED] wrote: This line looks odd to me also: xsd:import namespace=urn:org:pesc:core:CoreMain:v1.0.0 schemaLocation=OrgInfo/CoreMain_v1.0.0.xsd?wsdl/ Here is a definition of how import works in XML Schema: http://www.w3.org/TR/xmlschema-0/ section 5.4. So, the ?wsdl at the end of the schemaLocation string looks weird. I did in fact download that wsdl file, and got the same error in Axis 1.3 as you did. I do believe the web service development team is wrong at this point. -- I also think the namespace urn:org:pesc:core:Coremain:v1.0.0 is badly formatted. They usually start with http://;, but I did read somewhere they can be any unique string. Perhaps on this point, they are right. -jeff From: Keith Veleba [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 4:03 PM To: axis-user@ws.apache.org Subject: WSDL2Java issue and/or help I'm writing a client for a web service and I am having an issue with stub generation. This wsdl is causing the generation to fail: https://uat-atc.regents.ohio.gov/ccx/OrgInfo?wsdl Specifically, I get an error saying it cannot find the schemaLocation of the imported schema on line 4: xsd:import namespace=urn:org:pesc:core:CoreMain:v1.0.0 schemaLocation=OrgInfo/CoreMain_v1.0.0.xsd?wsdl/ This schemaLocation looks very odd to me, but the folks who run the web service say it is valid and should be working. Here's the error when I run wsdl2java.sh: Retrieving schema at 'OrgInfo/CoreMain_v1.0.0.xsd?wsdl', relative to 'file:/Users/velebak/https:/uat-atc.regents.ohio.gov/ccx'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:114) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'OrgInfo/CoreMain_v1.0.0.xsd?wsdl', relative to 'file:/Users/velebak/https:/uat-atc.regents.ohio.gov/ccx'.: java.io.FileNotFoundException: This file was not found: file:/Users/velebak/https:/uat-atc.regents.ohio.gov/OrgInfo/CoreMain_v1.0.0.xsd?wsdl at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:276) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:97) ... 2 more Caused by: java.io.FileNotFoundException: This file was not found: file:/Users/velebak/https:/uat-atc.regents.ohio.gov/OrgInfo/CoreMain_v1.0.0.xsd?wsdl at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown Source) ... 11 more Any ideas what may be going on here? It looks like it is looking for an actual local file, but it is not local, it is hosted remotely. Thanks in advance. -- Keith E. Veleba President Intellitek Services Ltd. 419-202-2676 cell [EMAIL PROTECTED] http://www.intellitekservices.com -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe,
Re: WSDL2Java issue and/or help
Hmm..actually this may be a bug. i'll check in a fix tonight. Please try a nightly tomorrow. -- dims On 7/2/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Anne, Jeff, The problem is the https://; the normal URL connection expects the cert to be in the local jks store AFAICT. thanks, dims On 7/2/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: Jeff, This URL: https://uat-atc.regents.ohio.gov/ccx/OrgInfo/CoreMain_v1.0.0.xsd?wsdl does indeed point to the XSD in question. This problem looks to me to be caused by WSDL2Java's inability to reference a remote XSD. Keith should do as Haneef recommends and download the XSD and store it locally, and change the schemaLocation attribute in the WSDL to point to the new location. Also, the urn:org:pesc:core:Coremain:v1.0.0 namespace is not badly formed. A namespace must be a valid URI (not any unique string), but it doesn't have to start with http://;. In this case, it's a URN rather than a URL, which is quite appropriate for a namespace URI. See the Wikipedia definition of Uniform Resource Identifier [1] for a layman's definition, or see RFC 3986 [2] for the formal specification. [1] http://en.wikipedia.org/wiki/Uniform_Resource_Identifier [2] http://gbiv.com/protocols/uri/rfc/rfc3986.html Anne On 6/26/07, Walker, Jeff [EMAIL PROTECTED] wrote: This line looks odd to me also: xsd:import namespace=urn:org:pesc:core:CoreMain:v1.0.0 schemaLocation=OrgInfo/CoreMain_v1.0.0.xsd?wsdl/ Here is a definition of how import works in XML Schema: http://www.w3.org/TR/xmlschema-0/ section 5.4. So, the ?wsdl at the end of the schemaLocation string looks weird. I did in fact download that wsdl file, and got the same error in Axis 1.3 as you did. I do believe the web service development team is wrong at this point. -- I also think the namespace urn:org:pesc:core:Coremain:v1.0.0 is badly formatted. They usually start with http://;, but I did read somewhere they can be any unique string. Perhaps on this point, they are right. -jeff From: Keith Veleba [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 4:03 PM To: axis-user@ws.apache.org Subject: WSDL2Java issue and/or help I'm writing a client for a web service and I am having an issue with stub generation. This wsdl is causing the generation to fail: https://uat-atc.regents.ohio.gov/ccx/OrgInfo?wsdl Specifically, I get an error saying it cannot find the schemaLocation of the imported schema on line 4: xsd:import namespace=urn:org:pesc:core:CoreMain:v1.0.0 schemaLocation=OrgInfo/CoreMain_v1.0.0.xsd?wsdl/ This schemaLocation looks very odd to me, but the folks who run the web service say it is valid and should be working. Here's the error when I run wsdl2java.sh: Retrieving schema at 'OrgInfo/CoreMain_v1.0.0.xsd?wsdl', relative to 'file:/Users/velebak/https:/uat-atc.regents.ohio.gov/ccx'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:114) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'OrgInfo/CoreMain_v1.0.0.xsd?wsdl', relative to 'file:/Users/velebak/https:/uat-atc.regents.ohio.gov/ccx'.: java.io.FileNotFoundException: This file was not found: file:/Users/velebak/https:/uat-atc.regents.ohio.gov/OrgInfo/CoreMain_v1.0.0.xsd?wsdl at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:276) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:97) ... 2 more Caused by: java.io.FileNotFoundException: This file was not found: file:/Users/velebak/https:/uat-atc.regents.ohio.gov/OrgInfo/CoreMain_v1.0.0.xsd?wsdl at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown Source) ... 11 more Any ideas what may be going on here? It looks like it is looking for an actual local file, but it is not local, it is hosted remotely. Thanks in
Re: Different XML order in WSDL File with Axis 1.2
Please create a JIRA and upload both wsdl;s and add result of java -version on both boxes. thanks, dims On 7/2/07, Petr V. [EMAIL PROTECTED] wrote: Hi, I am deploying my axis services on one machine and I see different wsdl and on other machine , same service generates different wsdl. The difference is only in ordering of operations. I rearranged the wsdl and they both are same. Only difference in environment I could see is different JRE different versions besides that environment is same. I am accessing wsdl via URL if it does matter. How could I maintain the same order of wsdl every time when I deploy service.. Thanks, Petr V. Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Soap fault and ADB -- How to set the fault code
faultCode and faultString properties should have been available in MyFaultException. MyFaultException extends Exception class, so you can set faultString by setting message in Exception class. What I did was I had included error code and error message (read fault code and fault message) in MyFaultType This is the soap trace when exception is thrown soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringMyFaultException/faultstring detail ns2:MyFault xmlns:ns2=http://www.test.com/general/exception/xsd; !-- elements in MyFaultType -- ns2:errorCodeTEST ERROR/ns2:errorCode ns2:messageError Message/ns2:message /ns2:MyFault /detail /soapenv:Fault /soapenv:Body /soapenv:Envelope -Original Message- From: Ali, Haneef [mailto:[EMAIL PROTECTED] Sent: 02 July 2007 08:01 To: axis-user@ws.apache.org Subject: Soap fault and ADB -- How to set the fault code Hi, I have a wsdl operation which throws fault of type MyFault. (i.e) element name=MyFault type=MyFaultType / For this scenario ADB generates the following classes a) MyFaultException b) MyFault derived from ADBbean c) MyFaultType Class MyFault has MyFaultType as instance variable. Exception MyFault goes as detail in SOAPFault which is fine. Now I don't understand how to set faultCode and faultString. I believe ADB should inherit the class MyFaultException from AxisFault instead of Exception? Can some one please let me know how to set the faultCode and faultString? Thanks, Haneef -Original Message- From: Ali, Haneef Sent: Monday, June 11, 2007 8:44 PM To: axis-user@ws.apache.org Subject: RE: SOAP fault - custom detail namespace Thanks for the response. I do have the element and wsdl declaration. I believe in this case Axis2 works as expected, and looks like Axis1.4 has a bug. 1) Axis 2 desterilizes the elements only if the qName of the xmlFragment matches. 1) Axis 1.4 tries to look for Qname. If it can't find Qname then it looks for localName. If it finds localName then it desterilizes the request, which I think is wrong Can you please confirm whether this is a feature or bug in Axis 1.4? I debugged the code and found that the following file is accepting the fields even if they are not in the proper namespace. Method : BeanDeSerializer.onStartChild Line : 216 The code is trying to get BeanPropertyDescriptor based on Qname. If it can't find then it tries to find the BeanPropertyDescriptor using localname, which is causing the problem. (i.e) if you have xmlFragment where only localName matches, then it desterilizes the bean which I think is wrong Thanks, Haneef -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Monday, June 11, 2007 3:19 PM To: axis-user@ws.apache.org Subject: Re: SOAP fault - custom detail namespace Based on your schema, the fault message should look like this: env:Fault faultcodeenv:Server/faultcode faultstringSome message/faultstring detail n1:MyException xmlns:n1=http://MyNamespace; ns1:mesg1 xsi:nil=true/ns1:mesg1 ns1:mesg2 xsi:nil=true/ns1:mesg2 /n1:MyExceptio /detail /env:Fault Also, please verify that you have in fact defined an *element*. (The schema fragment you showed us only defines a complex type.) Make sure that this declaration is included in your schema: xsd:element name=MyException type=tns:MyException/ And make sure your WSDL fault message part references this element. Anne On 6/11/07, Ali, Haneef [EMAIL PROTECTED] wrote: Hi, I have the following complex Element xsd:schema elementFormDefault=qualified attributeFormDefault=qualified targetNamespace=http://MyNamespace; xsd:complexType name=MyException xsd:sequence element name=mesg1 type=xsd:string / element name=mesg2 type=xsd:string / /xsd:sequence xsd:complexType xsd:schema I have omitted unnecessary implementation details. Bascially my weblogic webservice throws this excecption and the xml in the wire look like env:Fault faultcodeenv:Server/faultcode faultstringSome message/faultstring detail n1:MyException xmlns:n1=http://MyNamespace; mesg1 xsi:nil=true/mesg1 mesg2 xsi:nil=true/mesg2 /n1:MyExceptio /detail /env:Fault This xml fragment is accepted by both Axis 1.4 client and weblogic client. Axis 2.0 rejects this. Axis 2.0 is not able to findout the namespace for the element mesg1' and mesg2. Can you please let me know who is correct? I believe Axis2.0 is correct Thanks, Haneef - To unsubscribe, e-mail: [EMAIL PROTECTED]
[Axis2] Problem with service deployment
Hi, I am new to Axis2, i am trying to develop a webservice using it. I am not using any servlet containers like tomcat, just i want to run an Axis soap server as a standalone server, and i want to create create stubs and skeletons of my service and i would deploy my skeletons on to this server and by using stubs i want to communicate with the server. In this process i would be able to create stubs, skeletons and also able to run Axis as a standalone server, but my problem is with deployment, i am not able to deploy my service to Axis server. Can any one help me?. Regards, Naga.
Re: More than one service name in a SINGLE WSDL file
Thanks for your response. By the way, do you know the bug report number? Or better yet, where do I go to search (and/or) submit bugs On 7/2/07, Jess Fisher [EMAIL PROTECTED] wrote: The current Axis2 version still hasn't fixed this issue. This is not a problem in Axis1.4 version. There's a bug re-opened to address this problem in Axis2. I don't know when or if it will ever get fixed --- hopefully yes ??? *Patrick Cook [EMAIL PROTECTED]* wrote: First and foremost, I would like to take my hats off to Axis2 community. You all have definately raised the standards for SOAP Engines, Web Services and SOA in general. I would like to help out but don't know how. Please send me some information on how I could get involved. Secondly, I have a few questions. 1. How does Axis2 generate the ?wsdl for multiple services in a SINGLE WSDL file 2. Is there a one to one mapping of the service name in the service.xmlfile when there is a wsdl file in the META-INF folder 3. What is the connection of the service.xml and the *.wsdl file located in the META-INF folder How does Axis2 1.2 handle Multiple Services in a SINGLE WSDL file. i.e. if the wsdl looks something like the wsdl below. The behavior that I am seeing is that when you ask for the wsdl via (?wsdl) the SOAP engine will correctly generate the wsdl for one service but NOT the other. ?xml version=1.0 encoding=UTF-8? definitions name=Stock ... service name=MyService1 documentationService Example/documentation port name=MyPort1 binding=tns:MyPortBinding1 soap:address location= http://localhost:8080/services/MyService1/ /port /service service name=MyService2 documentationService Example/documentation port name=MyPort2 binding=tns:MyPortBinding2 soap:address location= http://localhost:8080/services/MyService2/ /port /service /definitions And my service.xml file would look something like this serviceGroup service name=MyService1 description Example of Multiple Services within one wsdl /description parameter name=ServiceClass example.multiple.services.test.MyServcice1 /parameter messageReceivers messageReceiver mep= http://www.w3.org/2004/08/wsdl/in-out class=example.multiple.receivers.MyCustomMessageReceiver / /messageReceivers /service service name=MyService2 description Example of Multiple Services within one wsdl /description parameter name=ServiceClass example.multiple.services.test.MyServcice2 /parameter messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out class=example.multiple.receivers.MyCustomMessageReceiver / /messageReceivers /service /serviceGroup By the way, I am using the original wsdl file in the META-INF folder. all of the corresponding schemas and source class files are in the correct location. -Patrick -- Luggage? GPS? Comic books? Check out fitting gifts for gradshttp://us.rd.yahoo.com/evt=48249/*http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bzat Yahoo! Search.
Re: Different XML order in WSDL File with Axis 1.2
Okay, I will file the bug but this behavior has been confirmed when I removed 1.6 JRE, all went fine. Davanum Srinivas [EMAIL PROTECTED] wrote: Please create a JIRA and upload both wsdl;s and add result of java -version on both boxes. thanks, dims On 7/2/07, Petr V. wrote: Hi, I am deploying my axis services on one machine and I see different wsdl and on other machine , same service generates different wsdl. The difference is only in ordering of operations. I rearranged the wsdl and they both are same. Only difference in environment I could see is different JRE different versions besides that environment is same. I am accessing wsdl via URL if it does matter. How could I maintain the same order of wsdl every time when I deploy service.. Thanks, Petr V. Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends.
Re: More than one service name in a SINGLE WSDL file
You can search (and/or) submit bugs here http://issues.apache.org/jira/browse/AXIS2 Thanks, Keith. On 7/3/07, Patrick Cook [EMAIL PROTECTED] wrote: Thanks for your response. By the way, do you know the bug report number? Or better yet, where do I go to search (and/or) submit bugs On 7/2/07, Jess Fisher [EMAIL PROTECTED] wrote: The current Axis2 version still hasn't fixed this issue. This is not a problem in Axis1.4 version. There's a bug re-opened to address this problem in Axis2. I don't know when or if it will ever get fixed --- hopefully yes ??? *Patrick Cook [EMAIL PROTECTED]* wrote: First and foremost, I would like to take my hats off to Axis2 community. You all have definately raised the standards for SOAP Engines, Web Services and SOA in general. I would like to help out but don't know how. Please send me some information on how I could get involved. Secondly, I have a few questions. 1. How does Axis2 generate the ?wsdl for multiple services in a SINGLE WSDL file 2. Is there a one to one mapping of the service name in the service.xmlfile when there is a wsdl file in the META-INF folder 3. What is the connection of the service.xml and the *.wsdl file located in the META-INF folder How does Axis2 1.2 handle Multiple Services in a SINGLE WSDL file. i.e. if the wsdl looks something like the wsdl below. The behavior that I am seeing is that when you ask for the wsdl via (?wsdl) the SOAP engine will correctly generate the wsdl for one service but NOT the other. ?xml version=1.0 encoding=UTF-8? definitions name=Stock ... service name=MyService1 documentationService Example/documentation port name=MyPort1 binding=tns:MyPortBinding1 soap:address location=http://localhost:8080/services/MyService1/ /port /service service name=MyService2 documentationService Example/documentation port name=MyPort2 binding=tns:MyPortBinding2 soap:address location= http://localhost:8080/services/MyService2/ /port /service /definitions And my service.xml file would look something like this serviceGroup service name=MyService1 description Example of Multiple Services within one wsdl /description parameter name=ServiceClass example.multiple.services.test.MyServcice1 /parameter messageReceivers messageReceiver mep= http://www.w3.org/2004/08/wsdl/in-out class=example.multiple.receivers.MyCustomMessageReceiver / /messageReceivers /service service name=MyService2 description Example of Multiple Services within one wsdl /description parameter name=ServiceClass example.multiple.services.test.MyServcice2 /parameter messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out class=example.multiple.receivers.MyCustomMessageReceiver / /messageReceivers /service /serviceGroup By the way, I am using the original wsdl file in the META-INF folder. all of the corresponding schemas and source class files are in the correct location. -Patrick -- Luggage? GPS? Comic books? Check out fitting gifts for gradshttp://us.rd.yahoo.com/evt=48249/*http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bzat Yahoo! Search. -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: [Axis2] Problem with service deployment
Hi, I presume that you have given a repository location when creating a server. If not the following code might help you. The repository location will be /opt/repo. Create two folders called services, modules within the repo. Drop in your services to /ope/repo/services and drop in your modules to /opt/repo/modules. Hope this answers your problem. String AXIS2_SERVER_PATH = /opt/repo/; String AXIS2_XML = /opt/repo/conf/axis2.xml; ConfigurationContext configContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem (AXIS2_SERVER_PATH,AXIS2_XML); SimpleHTTPServer server = new SimpleHTTPServer (configContext,); server.start(); Thanks, Keith. On 7/3/07, Naga Srinivas [EMAIL PROTECTED] wrote: Hi, I am new to Axis2, i am trying to develop a webservice using it. I am not using any servlet containers like tomcat, just i want to run an Axis soap server as a standalone server, and i want to create create stubs and skeletons of my service and i would deploy my skeletons on to this server and by using stubs i want to communicate with the server. In this process i would be able to create stubs, skeletons and also able to run Axis as a standalone server, but my problem is with deployment, i am not able to deploy my service to Axis server. Can any one help me?. Regards, Naga. -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: Deploy TCPTransport
Hi Yari , When you start the server , you have to give axis2.xml or there will be axis2.xml in your repository . Please add module ref=addressing/ , there in that axis2.xml. In the client side , you have to call ServiceClient client = new ServiceClient(); client.engageModule(addressing); The problem is discuss in http://wso2.org/library/233 Thanks Deepal first thanks for the quick answer. what do u mean with i should engage addressing? could you point me in the right direction? i tried to look everywhere but the only thing i could find was the short page in the axis project, but i couldnt figure out how to solve the addressing problem.. thx, yari Deepal Jayasinghe ha scritto: TCP only works when you engage addressing in both server side and client side. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WG: An exception when porting from axis2 1.1.1 to axis 1.2
Hy all, I have the same problem but no answer given so far matches my demand. When Client compiles against axis2-1.2, engages addressing-1.1.mar and then talks to an axis2-1.1.1 service, herby engaging addressing-1.1.mar all is ok Client code compiled with axis2-1.2 addressing-1.2.mar engaged works fined talking to an axis2-1.1.1 Service which has addressing-1.1.mar engaged. When I port my Service to axis2-1.2, engaging addressing-1.2.mar the stacke trace below happens, and the trouble starts at the server with at the line at java.util.ResourceBundle.getObject(ResourceBundle.java:325)#xd; indicated below. This call can raise an exception a) if the key is not present b) if no object is returned; and that is where the problem starts. The rest is just a follow up in my mind. Please note I send wsa:Actionurn:login/wsa:Actionon the wire, this as per TCP-Monitor My PC has Windows 2000/SP4 and runs a U.S. English but cultures are set to Swiss-German for currency and the like; also I can see the same problem when my axis2-1.2 server with addressin-1.2.mar engaged runs on a HP Alpha OpenVMS machine, U.S. English only. I am a bit confused ! question: where is the Resource Bundel in question which must have a) the key: spec.FAULT_ACTION_NOT_SUPPORTED_REASON ? and b) what shall be returned by that key ? question: is there a later nigthly build of addressing-1.2.mar which potentially fixes the problem seen? Amy help appreciated. Thanks Josef.Stadelmann @winterthur.ch My TcpMonitor Log'ed *** Request from Client *** POST /axis2/services/SpezplaService HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: urn:login User-Agent: Axis2 Host: localhost:9090 Transfer-Encoding: chunked 219 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:9090/axis2/services/SpezplaService/wsa:To wsa:MessageIDurn:uuid:474EEFF146963E51071183381718923/wsa:MessageID wsa:Actionurn:login/wsa:Action /soapenv:Header soapenv:Body SPS:login xmlns:SPS=http://axawl.org/SpezplaService; SPS:TextAxis2 'SOAPSession' Login-String/SPS:Text /SPS:login /soapenv:Body /soapenv:Envelope Answer from Server *** HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Mon, 02 Jul 2007 13:08:40 GMT Connection: close fbb ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Actionhttp://www.w3.org/2005/08/addressing/soap/fault/wsa:Action wsa:RelatesTourn:uuid:474EEFF146963E51071183381718923/wsa:RelatesTo /soapenv:Header soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringjava.util.MissingResourceException: Can't find resource for bundle org.apache.axis2.i18n.ProjectResourceBundle, key spec.FAULT_ACTION_NOT_SUPPORTED_REASON/faultstring detail Exceptionorg.apache.axis2.AxisFault: java.util.MissingResourceException: Can't find resource for bundle org.apache.axis2.i18n.ProjectResourceBundle, key spec.FAULT_ACTION_NOT_SUPPORTED_REASON#xd; at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:178)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)#xd; at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)#xd; at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)#xd; at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)#xd; at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)#xd; at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)#xd; at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)#xd; at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)#xd; at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)#xd; at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)#xd; at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)#xd; at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)#xd; at
[Axis2] Problem with invoking web service by using Stub classes
*Hi, I am new to Axis2, i am trying to develop a web service, and trying to invoke it by using it's stub classes. I had created Stubs and Skeletons of web service and successfully deployed services to a standalone Axis2 server. but now, i would like to know how can we sent request to that services, by using stub classes in our application. Can any one help me?. Regards, Naga.*