[Axis2][ANN]Mercury 0.91 released
The WSO2 Mercury team is happy to announce the release of WSO2 Mercury 0.91. WSO2 Mercury is a WS-Reliable Messaging Specification and Replay Model implementation for Apache Axis2 1.4. It currently interoperates completely with the WCF 3.0. This release has been tested in the following scenarios with HTTP and SMTP transports (Apache Synapse NIO transport for Replay model scenarios). 1.In-only operations for duplex mode 2.In-out operations for duplex mode 3.In-only operations for anonymous mode (Replay model) 4.In-out operations for anonymous mode (Replay model) 5.Persistence for In-only operations WSO2 Mercury has also been tested for Application fault messages and with Apache rampart 1.4 which will be available soon[1]. New features in this release include 1. Sample for above scenarios 2. Performance improvement by notifications to waiting threads 3. Configuration parameter support at Axis2.xml, Services.xml and MercuryClient level Release artefacts can be found at[2] PS: Some times back we try to donate the this code to Apache ws project with this jira[3]. thanks, Amila. [1] http://ws.apache.org/rampart/download/1.4/download [2] http://wso2.org/downloads/commons/mercury [3] https://issues.apache.org/jira/browse/SANDESHA2-144 -- Amila Suriarachchi, WSO2 Inc.
Validating Services.xml
Hi, A quick search did not show up any XSD or DTD to validate the services.xml that is used in the axis2 services archive. Maybe I was not looking in the right places, is there any way I can determine if a given XML is a valid services XML or not? Thanks, ~ Vikas
problem with Arrays Axis2 and Xmlbeans
hi all we are facing a problem with AXIS2 and Xmlbeans while using Arrays WSDL having the following entry element name=cardHolderDTOArray nillable=true type=impl:ArrayOf_tns2_nillable_CardHolderDTO/ Also having complexType name=ArrayOf_tns2_nillable_CardHolderDTO complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns2:CardHolderDTO[]/ /restriction /complexContent /complexType when we generates the corresponding class using the wsdl2java it will generates the ArrayOfTns2NillableCardHolderDTOImpl and ArrayOfTns2NillableCardHolderDTO our problem is We were not able to set the CardHolderDTO[] in the skeleton also not able to retrieve the elements from the ArrayOfTns2NillableCardHolderDTO in the stub the problem is ArrayOfTns2NillableCardHolderDTO is not proving any get or set methods to set and get the DTO. only we can create an instance using the factory by this axis generated class Can anyone help us in this regard Thanks Sreejith -- View this message in context: http://www.nabble.com/problem-with-Arrays-Axis2-and-Xmlbeans-tp17595689p17595689.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
questions about one way invoking?
Hi, all. When I use one way invoking, the FireAndForget is invoked. However, I must wait for some time to ensure the invoking succeed. Is there another way like (flushing) I can make sure the invoking request was sending? Or is there ways to invoke a one way function in a blocking way? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: questions about one way invoking?
Hi, all. When I use one way invoking, the FireAndForget is invoked. However, I must wait for some time to ensure the invoking succeed. Is there another way like (flushing) I can make sure the invoking request was sending? Yes , use sendRoubust. -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
UTF-8 Encoding problem
Hi; I have problem sending Persian String over SOAP from client to server on axis2 .Response strings are correct and but when I use Persian string as my method parameters I get garbage characters on server side. I used RPCServiceClient to call the web service and set character encoding to UTF-8. Anybody can help? Thanks Hamid
Socket connect every time?
Hi all, I just start to use Axis2. I need to send array frequently. But I found that when every time I send a array, I need to reconnect to the server. This may cause the performace problem. How could I configure so that the continuous sending can make use of just one connection? Thanks. Wenhao - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OSGi implementation/ versioned imports and exports
Hi Axis Team, will you add support for OSGi versioning to your OSGi bundle? Meaning the imports and exports declared in the manifest file? Kind regards, Georg
Spring service bean not initialized in the skeleton class.
Hi, I am in the process of integrating Axis2 with Spring2.5. Scenario - I have created the aar with the xsds, services.xml, the wsdl file. The rest of my classes are present under the WEB-INF/classes folder and the dependant jars in the WEB-INF/lib of the axis2 app. I've updated the services.xml to have the serviceObjectSupplier as org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier and SpringBeanName set as the skeleton class. When I call this web-service, I get a NullpointerException from this skeleton class because the service (which is supposed to be injected by Spring) class was not initialised. I am not sure if I've missed out something here; Any help or pointers would be of great help. Thanks, Dwipin Chandran ForwardSourceID:NT00014DF2 ForwardSourceID:NT00014E02 =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
Re: Spring service bean not initialized in the skeleton class.
The way you describe your service, you would need some web.xml entries to load spring, ie, axis2 expects spring to be configured when using SpringServletContextObjectSupplier. By putting spring in debug, you should see it initializing correctly - in which case axis2 should be able to find it. If you can start spring, but axis2 can't find it - try looking at the servlet container logs. If you still have problems after all that, let us know. HTH, Robert On Mon, Jun 2, 2008 at 9:54 AM, Dwipin C [EMAIL PROTECTED] wrote: Hi, I am in the process of integrating Axis2 with Spring2.5. Scenario - I have created the aar with the xsds, services.xml, the wsdl file. The rest of my classes are present under the WEB-INF/classes folder and the dependant jars in the WEB-INF/lib of the axis2 app. I've updated the services.xml to have the serviceObjectSupplier as org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier and SpringBeanName set as the skeleton class. When I call this web-service, I get a NullpointerException from this skeleton class because the service (which is supposed to be injected by Spring) class was not initialised. I am not sure if I've missed out something here; Any help or pointers would be of great help. Thanks, Dwipin Chandran ForwardSourceID:NT00014DF2 ForwardSourceID:NT00014E02 =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spring service bean not initialized in the skeleton class.
Hi Robert, I have the required web.xml entries - listener listener-classorg.springframework.web.context.ContextLoaderListener/listener-class /listener context-param param-namecontextConfigLocation/param-name param-value/WEB-INF/applicationContext.xml/param-value /context-param From the spring logs, I can see the beans being initialised. Its just that axis skeleton and the spring service bean did not get linked. I couldnt find anything in the server log too. Thanks and Regards, Dwipin Chandran Tata Consultancy Services Discoverer Bldg, 4th Floor International Technology Park Ltd, Whitefield Road Bangalore - 560066,Karnataka India Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty. IT Services Business Solutions Outsourcing robert lazarski [EMAIL PROTECTED] 06/02/2008 06:34 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Spring service bean not initialized in the skeleton class. The way you describe your service, you would need some web.xml entries to load spring, ie, axis2 expects spring to be configured when using SpringServletContextObjectSupplier. By putting spring in debug, you should see it initializing correctly - in which case axis2 should be able to find it. If you can start spring, but axis2 can't find it - try looking at the servlet container logs. If you still have problems after all that, let us know. HTH, Robert On Mon, Jun 2, 2008 at 9:54 AM, Dwipin C [EMAIL PROTECTED] wrote: Hi, I am in the process of integrating Axis2 with Spring2.5. Scenario - I have created the aar with the xsds, services.xml, the wsdl file. The rest of my classes are present under the WEB-INF/classes folder and the dependant jars in the WEB-INF/lib of the axis2 app. I've updated the services.xml to have the serviceObjectSupplier as org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier and SpringBeanName set as the skeleton class. When I call this web-service, I get a NullpointerException from this skeleton class because the service (which is supposed to be injected by Spring) class was not initialised. I am not sure if I've missed out something here; Any help or pointers would be of great help. Thanks, Dwipin Chandran ForwardSourceID:NT00014DF2 ForwardSourceID:NT00014E02 =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT00014E1A =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
Re: Spring service bean not initialized in the skeleton class.
To have the skeleton and the spring service bean get linked, you need to manually tweak your services.xml . Try that, and if you still have problems, paste your services.xml . Robert On Mon, Jun 2, 2008 at 10:29 AM, Dwipin C [EMAIL PROTECTED] wrote: Hi Robert, I have the required web.xml entries - listener listener-classorg.springframework.web.context.ContextLoaderListener/listener-class /listener context-param param-namecontextConfigLocation/param-name param-value/WEB-INF/applicationContext.xml/param-value /context-param From the spring logs, I can see the beans being initialised. Its just that axis skeleton and the spring service bean did not get linked. I couldnt find anything in the server log too. Thanks and Regards, Dwipin Chandran Tata Consultancy Services Discoverer Bldg, 4th Floor International Technology Park Ltd, Whitefield Road Bangalore - 560066,Karnataka India Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty.IT Services Business Solutions Outsourcing robert lazarski [EMAIL PROTECTED] 06/02/2008 06:34 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Spring service bean not initialized in the skeleton class. The way you describe your service, you would need some web.xml entries to load spring, ie, axis2 expects spring to be configured when using SpringServletContextObjectSupplier. By putting spring in debug, you should see it initializing correctly - in which case axis2 should be able to find it. If you can start spring, but axis2 can't find it - try looking at the servlet container logs. If you still have problems after all that, let us know. HTH, Robert On Mon, Jun 2, 2008 at 9:54 AM, Dwipin C [EMAIL PROTECTED] wrote: Hi, I am in the process of integrating Axis2 with Spring2.5. Scenario - I have created the aar with the xsds, services.xml, the wsdl file. The rest of my classes are present under the WEB-INF/classes folder and the dependant jars in the WEB-INF/lib of the axis2 app. I've updated the services.xml to have the serviceObjectSupplier as org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier and SpringBeanName set as the skeleton class. When I call this web-service, I get a NullpointerException from this skeleton class because the service (which is supposed to be injected by Spring) class was not initialised. I am not sure if I've missed out something here; Any help or pointers would be of great help. Thanks, Dwipin Chandran ForwardSourceID:NT00014DF2 ForwardSourceID:NT00014E02 =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT00014E1A =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spring service bean not initialized in the skeleton class.
This the services.xml I am using - ?xml version=1.0 encoding=UTF-8? !-- This file was auto-generated from WSDL -- !-- by the Apache Axis2 version: 1.4 Built on : Apr 26, 2008 (06:24:30 EDT) -- serviceGroup service name=ACLAndAuthService messageReceivers messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class= services.ACLAndAuthServiceMessageReceiverInOut/ /messageReceivers parameter name=serviceObjectSupplier locked=false org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier /parameter parameter name=SpringBeanName locked=false aclService /parameter parameter name=ServiceClass services.ACLAndAuthServiceSkeleton /parameter parameter name=useOriginalwsdltrue/parameter parameter name=modifyUserWSDLPortAddresstrue/parameter operation name=authenticate mep= http://www.w3.org/ns/wsdl/in-out; namespace=http://foundation.com; actionMappingurn:authenticate/actionMapping outputActionMapping urn:authenticateResponse /outputActionMapping faultActionMapping faultName=AuthenticationException urn:authenticateAuthenticationException /faultActionMapping /operation operation name=retrieveAcl mep= http://www.w3.org/ns/wsdl/in-out; namespace=http://foundation.com; actionMappingurn:retrieveAcl/actionMapping outputActionMapping urn:retrieveAclResponse /outputActionMapping faultActionMapping faultName=AclRetrievalException urn:retrieveAclAclRetrievalException /faultActionMapping /operation /service /serviceGroup Dwipin Chandran Tata Consultancy Services Discoverer Bldg, 4th Floor International Technology Park Ltd, Whitefield Road Bangalore - 560066,Karnataka India Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty. IT Services Business Solutions Outsourcing robert lazarski [EMAIL PROTECTED] 06/02/2008 07:03 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Spring service bean not initialized in the skeleton class. To have the skeleton and the spring service bean get linked, you need to manually tweak your services.xml . Try that, and if you still have problems, paste your services.xml . Robert On Mon, Jun 2, 2008 at 10:29 AM, Dwipin C [EMAIL PROTECTED] wrote: Hi Robert, I have the required web.xml entries - listener listener-classorg.springframework.web.context.ContextLoaderListener/listener-class /listener context-param param-namecontextConfigLocation/param-name param-value/WEB-INF/applicationContext.xml/param-value /context-param From the spring logs, I can see the beans being initialised. Its just that axis skeleton and the spring service bean did not get linked. I couldnt find anything in the server log too. Thanks and Regards, Dwipin Chandran Tata Consultancy Services Discoverer Bldg, 4th Floor International Technology Park Ltd, Whitefield Road Bangalore - 560066,Karnataka India Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty.IT Services Business Solutions Outsourcing robert lazarski [EMAIL PROTECTED] 06/02/2008 06:34 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Spring service bean not initialized in the skeleton class. The way you describe your service, you would need some web.xml entries to load spring, ie, axis2 expects spring to be configured when using SpringServletContextObjectSupplier. By putting spring in debug, you should see it initializing correctly - in which case axis2 should be able to find it. If you can start spring, but axis2 can't find it - try looking at the servlet container logs. If you still have problems after all that, let us know. HTH, Robert On Mon, Jun 2, 2008 at 9:54 AM, Dwipin C [EMAIL PROTECTED] wrote: Hi, I am in the process of integrating Axis2 with Spring2.5. Scenario - I have created the aar with the xsds, services.xml, the wsdl file. The rest of my classes are present under the WEB-INF/classes folder and the dependant jars in the WEB-INF/lib of the axis2 app. I've updated the services.xml to have the serviceObjectSupplier as
Re: Spring service bean not initialized in the skeleton class.
Dwipin, I see no obvious problem. I'm afraid you're going to have to put all your axis2, spring, and userspace classes in debug and check the logs. Sure you don't have a name mismatch and that you really are using this services.xml ? Try double checking that your applicationContext.xml and services.xml are matching correctly. Robert On Mon, Jun 2, 2008 at 10:44 AM, Dwipin C [EMAIL PROTECTED] wrote: This the services.xml I am using - ?xml version=1.0 encoding=UTF-8? !-- This file was auto-generated from WSDL -- !-- by the Apache Axis2 version: 1.4 Built on : Apr 26, 2008 (06:24:30 EDT) -- serviceGroup service name=ACLAndAuthService messageReceivers messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class=services.ACLAndAuthServiceMessageReceiverInOut/ /messageReceivers parameter name=serviceObjectSupplier locked=false org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier /parameter parameter name=SpringBeanName locked=false aclService /parameter parameter name=ServiceClass services.ACLAndAuthServiceSkeleton /parameter parameter name=useOriginalwsdltrue/parameter parameter name=modifyUserWSDLPortAddresstrue/parameter operation name=authenticate mep=http://www.w3.org/ns/wsdl/in-out; namespace=http://foundation.com; actionMappingurn:authenticate/actionMapping outputActionMapping urn:authenticateResponse /outputActionMapping faultActionMapping faultName=AuthenticationException urn:authenticateAuthenticationException /faultActionMapping /operation operation name=retrieveAcl mep=http://www.w3.org/ns/wsdl/in-out; namespace=http://foundation.com; actionMappingurn:retrieveAcl/actionMapping outputActionMapping urn:retrieveAclResponse /outputActionMapping faultActionMapping faultName=AclRetrievalException urn:retrieveAclAclRetrievalException /faultActionMapping /operation /service /serviceGroup Dwipin Chandran Tata Consultancy Services Discoverer Bldg, 4th Floor International Technology Park Ltd, Whitefield Road Bangalore - 560066,Karnataka India Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty.IT Services Business Solutions Outsourcing robert lazarski [EMAIL PROTECTED] 06/02/2008 07:03 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Spring service bean not initialized in the skeleton class. To have the skeleton and the spring service bean get linked, you need to manually tweak your services.xml . Try that, and if you still have problems, paste your services.xml . Robert On Mon, Jun 2, 2008 at 10:29 AM, Dwipin C [EMAIL PROTECTED] wrote: Hi Robert, I have the required web.xml entries - listener listener-classorg.springframework.web.context.ContextLoaderListener/listener-class /listener context-param param-namecontextConfigLocation/param-name param-value/WEB-INF/applicationContext.xml/param-value /context-param From the spring logs, I can see the beans being initialised. Its just that axis skeleton and the spring service bean did not get linked. I couldnt find anything in the server log too. Thanks and Regards, Dwipin Chandran Tata Consultancy Services Discoverer Bldg, 4th Floor International Technology Park Ltd, Whitefield Road Bangalore - 560066,Karnataka India Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty.IT Services Business Solutions Outsourcing robert lazarski [EMAIL PROTECTED] 06/02/2008 06:34 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Spring service bean not initialized in the skeleton class. The way you describe your service, you would need some web.xml entries to load spring, ie, axis2 expects spring to be configured when using SpringServletContextObjectSupplier. By putting spring in debug, you should see it initializing correctly - in which case axis2 should be able to find it. If you can start spring, but axis2 can't find it - try looking at the servlet container logs. If you still have problems after all that, let us know. HTH, Robert On Mon, Jun 2,
Re: Validating Services.xml
See http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/resources/services.xsd?view=log Nadir Amra vikas kumar [EMAIL PROTECTED] wrote on 06/02/2008 02:04:46 AM: Hi, A quick search did not show up any XSD or DTD to validate the services.xml that is used in the axis2 services archive. Maybe I was not looking in the right places, is there any way I can determine if a given XML is a valid services XML or not? Thanks, ~ Vikas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Spring service bean not initialized in the skeleton class.
Here is the services.xml which accompanies the axis2.1.3 SpringAwareService sample service name=SpringAwareService description simple spring example which uses 2 parameters and 1 service /description parameter name=ServiceObjectSupplier locked=falseorg.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier/parameter parameter name=SpringBeanName locked=falsespringAwareService/parameter operation name=getValue messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service spring classes/jars should be located in $AXIS_HOME/modules/spring RawXMLINOUTMessageReceiver should be located in $AXIS_HOME/modules/kernel I would work with the working Spring sample and then add 1 parameter at a time until you find your error HTH Martin Gainty __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Date: Mon, 2 Jun 2008 11:14:07 -0300 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: Spring service bean not initialized in the skeleton class. Dwipin, I see no obvious problem. I'm afraid you're going to have to put all your axis2, spring, and userspace classes in debug and check the logs. Sure you don't have a name mismatch and that you really are using this services.xml ? Try double checking that your applicationContext.xml and services.xml are matching correctly. Robert On Mon, Jun 2, 2008 at 10:44 AM, Dwipin C [EMAIL PROTECTED] wrote: This the services.xml I am using - ?xml version=1.0 encoding=UTF-8? !-- This file was auto-generated from WSDL -- !-- by the Apache Axis2 version: 1.4 Built on : Apr 26, 2008 (06:24:30 EDT) -- serviceGroup service name=ACLAndAuthService messageReceivers messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class=services.ACLAndAuthServiceMessageReceiverInOut/ /messageReceivers parameter name=serviceObjectSupplier locked=false org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier /parameter parameter name=SpringBeanName locked=false aclService /parameter parameter name=ServiceClass services.ACLAndAuthServiceSkeleton /parameter parameter name=useOriginalwsdltrue/parameter parameter name=modifyUserWSDLPortAddresstrue/parameter operation name=authenticate mep=http://www.w3.org/ns/wsdl/in-out; namespace=http://foundation.com; actionMappingurn:authenticate/actionMapping outputActionMapping urn:authenticateResponse /outputActionMapping faultActionMapping faultName=AuthenticationException urn:authenticateAuthenticationException /faultActionMapping /operation operation name=retrieveAcl mep=http://www.w3.org/ns/wsdl/in-out; namespace=http://foundation.com; actionMappingurn:retrieveAcl/actionMapping outputActionMapping urn:retrieveAclResponse /outputActionMapping faultActionMapping faultName=AclRetrievalException urn:retrieveAclAclRetrievalException /faultActionMapping /operation /service /serviceGroup Dwipin Chandran Tata Consultancy Services Discoverer Bldg, 4th Floor International Technology Park Ltd, Whitefield Road Bangalore - 560066,Karnataka India Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty.IT Services Business Solutions Outsourcing robert lazarski [EMAIL PROTECTED] 06/02/2008 07:03 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Spring service bean not initialized in the skeleton class. To have the skeleton and the spring service bean get linked, you need to manually tweak your services.xml . Try that, and if you still have problems, paste your services.xml . Robert On Mon, Jun 2, 2008 at 10:29 AM, Dwipin C [EMAIL PROTECTED] wrote: Hi Robert, I have the required web.xml entries - listener listener-classorg.springframework.web.context.ContextLoaderListener/listener-class /listener
Re: UTF-8 Encoding problem
Hi; I found that is this problem occurs when I use rampart and without rampart evrything is ok. does anybody knows why? Is it a bug? Thanks, Hamid On 6/2/08, hamidreza sahlolbey [EMAIL PROTECTED] wrote: Hi; I have problem sending Persian String over SOAP from client to server on axis2 .Response strings are correct and but when I use Persian string as my method parameters I get garbage characters on server side. I used RPCServiceClient to call the web service and set character encoding to UTF-8. Anybody can help? Thanks Hamid
Re: Validating Services.xml
Hi Vikas, You can use WSO2 online services.xml validator [1] [1] http://tools.wso2.org/tools_aarvalidator/ regards Charitha vikas kumar wrote: Hi, A quick search did not show up any XSD or DTD to validate the services.xml that is used in the axis2 services archive. Maybe I was not looking in the right places, is there any way I can determine if a given XML is a valid services XML or not? Thanks, ~ Vikas No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 269.24.4/1477 - Release Date: 6/1/2008 5:28 PM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 w/ HttpClient
Hi all. I have deployed my web services using Axis2, from an in-house servet design. I understand I can use Wsdl2Java and create a stub client for each service, but I have an existing test package that I would like to keep as-is. In this test package, I use the Apache HttpClient to send my request (my custom SOAP Header, request in SOAP body) to the server. It worked perfect for my previous design, but not working well for Axis2. I am having trouble sending the request from my test package using HttpClient to my Axis2 service. I always get the same response . I can use JMeter to send the request and it works fine (the SOAPAction is always set to the operation name). But it does not work when I use the existing test package as-is. Does something else need to be set somewhere? Has anyone else seen/solved this? I am sorry if this is posted somewhere. I took a quick look, but didn't see anything that solved my problem. Thanks. Jeff
Re: Axis2 w/ HttpClient
Sorry, the response didn't paste right and I over-looked it. Response is The endpoint reference (EPR) for the Operation not found is /axis2/services/MY_SERVICE and the WSA Action = null Does something need to be put in the request, either the SOAP header or the HTTP header identifying the operation? Shouldn't Axis2 be able to figure that out from what is in the SOAP body? Thanks. Jeff On Mon, Jun 2, 2008 at 11:47 AM, Jeff Garrett [EMAIL PROTECTED] wrote: Hi all. I have deployed my web services using Axis2, from an in-house servet design. I understand I can use Wsdl2Java and create a stub client for each service, but I have an existing test package that I would like to keep as-is. In this test package, I use the Apache HttpClient to send my request (my custom SOAP Header, request in SOAP body) to the server. It worked perfect for my previous design, but not working well for Axis2. I am having trouble sending the request from my test package using HttpClient to my Axis2 service. I always get the same response . I can use JMeter to send the request and it works fine (the SOAPAction is always set to the operation name). But it does not work when I use the existing test package as-is. Does something else need to be set somewhere? Has anyone else seen/solved this? I am sorry if this is posted somewhere. I took a quick look, but didn't see anything that solved my problem. Thanks. Jeff
Re: Axis2 w/ HttpClient
Jeff, you have to set the SOAP action (required by WS-addressing) as specified into your services.xml. Michele On 2 Jun 2008, at 17:01, Jeff Garrett wrote: Sorry, the response didn't paste right and I over-looked it. Response is The endpoint reference (EPR) for the Operation not found is /axis2/services/MY_SERVICE and the WSA Action = null Does something need to be put in the request, either the SOAP header or the HTTP header identifying the operation? Shouldn't Axis2 be able to figure that out from what is in the SOAP body? Thanks. Jeff On Mon, Jun 2, 2008 at 11:47 AM, Jeff Garrett [EMAIL PROTECTED] wrote: Hi all. I have deployed my web services using Axis2, from an in-house servet design. I understand I can use Wsdl2Java and create a stub client for each service, but I have an existing test package that I would like to keep as-is. In this test package, I use the Apache HttpClient to send my request (my custom SOAP Header, request in SOAP body) to the server. It worked perfect for my previous design, but not working well for Axis2. I am having trouble sending the request from my test package using HttpClient to my Axis2 service. I always get the same response . I can use JMeter to send the request and it works fine (the SOAPAction is always set to the operation name). But it does not work when I use the existing test package as-is. Does something else need to be set somewhere? Has anyone else seen/solved this? I am sorry if this is posted somewhere. I took a quick look, but didn't see anything that solved my problem. Thanks. Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Minimal set of JARs to embed Axis2 into a webapp?
+---lib axiom-api-1.2.5.jar axiom-impl-1.2.5.jar axis2-kernel-1.3.jar backport-util-concurrent-2.2.jar commons-fileupload-1.1.1.jar commons-httpclient-3.0.1.jar jax-qname-1.5.jar (QName API part of stax-api) neethi-2.0.2.jar wsdl4j-1.6.2.jar wstx-asl-3.2.1.jar xbean-2.3.0.jar XmlSchema-1.3.2.jar Doesn't the AxisServlet depend on annogen-0.1.0.jar.? import org.codehaus.jam.JMethod; JMethod[] method = schemaGenerator.getMethods(); Kurt
Re: Axis2 w/ HttpClient
Is this an element in the SOAP Header request? If so, this might make things very difficult (will explain further if you reply and say that it is). Here is a sample of my services.xml for a service (from the wsdl2java tool). Just unsubscribe from notificiations. service name=NotificationProducerV2 messageReceivers messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class=out.NotificationProducerV2MessageReceiverInOut/ /messageReceivers parameter name=ServiceClassout.NotificationProducerV2/parameter parameter name=useOriginalwsdltrue/parameter parameter name=modifyUserWSDLPortAddresstrue/parameter operation name=unsubscribe mep=http://www.w3.org/ns/wsdl/in-out; actionMappingunsubscribe/actionMapping outputActionMappingaddress/NotificationProducer/unsubscribeResponse/outputActionMapping faultActionMapping faultName=unsubscribe address/NotificationProducer/unsubscribe/Fault/unsubscribeExceptionhttp://www.tmforum.org/mtop/fmw/wsdl/notp/v1/NotificationProducer/unsubscribe/Fault/unsubscribeException /faultActionMapping /operation /service Just looking at this, the OutputActionMapping might not be right, just what was compiled from schema. Should it be something else ( http://localhost:52492/axis2/services/NotificationProducerV2/unsubscribe). So, I want to send a request and set the SOAPAction element to unsubscribe. Jeff On Mon, Jun 2, 2008 at 1:35 PM, Michele Mazzucco [EMAIL PROTECTED] wrote: Jeff, you have to set the SOAP action (required by WS-addressing) as specified into your services.xml. Michele On 2 Jun 2008, at 17:01, Jeff Garrett wrote: Sorry, the response didn't paste right and I over-looked it. Response is The endpoint reference (EPR) for the Operation not found is /axis2/services/MY_SERVICE and the WSA Action = null Does something need to be put in the request, either the SOAP header or the HTTP header identifying the operation? Shouldn't Axis2 be able to figure that out from what is in the SOAP body? Thanks. Jeff On Mon, Jun 2, 2008 at 11:47 AM, Jeff Garrett [EMAIL PROTECTED] wrote: Hi all. I have deployed my web services using Axis2, from an in-house servet design. I understand I can use Wsdl2Java and create a stub client for each service, but I have an existing test package that I would like to keep as-is. In this test package, I use the Apache HttpClient to send my request (my custom SOAP Header, request in SOAP body) to the server. It worked perfect for my previous design, but not working well for Axis2. I am having trouble sending the request from my test package using HttpClient to my Axis2 service. I always get the same response . I can use JMeter to send the request and it works fine (the SOAPAction is always set to the operation name). But it does not work when I use the existing test package as-is. Does something else need to be set somewhere? Has anyone else seen/solved this? I am sorry if this is posted somewhere. I took a quick look, but didn't see anything that solved my problem. Thanks. Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 Packaging and Distribution Best Practices
Hello, I am wondering if anyone is aware of a best practices guide for Axis 2, specifically for packaging and distribution. I would appreciate if you could provide me with pointers. Thanks Sumit
Re: Include imported XSDs in generated WSDL
Hi, I would be glad if someone could have a look at this issue. Regards, Stefan Lecho. stlecho wrote: Hi, In the WSDL I'm using different XSDs are imported: xsd:import namespace=... schemaLocation=.../. When generating and deploying an AAR that contains this WSDL, the WSDL shown to the user when accessing http://host/servicename?wsdl; does not contain the content of the imported XSDs. Instead the import statement is used. This behavior is correct, but a global overview of the WSDL and the different XSDs is not possible :o(. Is there a way to avoid this default behavior and to include the content of the imported XSDs directly in the WSDL (I was thinking about a includeXSDs parameter in services.xml) ? Regards, Stefan Lecho. -- View this message in context: http://www.nabble.com/Include-imported-XSDs-in-generated-WSDL-tp17511649p17610416.html 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: Validating Services.xml
Any idea why this XSD is not included in the current distribution ? Will it be included in one of the next releases of Axis2 ? Regards, Stefan Lecho. Nadir Amra wrote: See http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/resources/services.xsd?view=log Nadir Amra vikas kumar [EMAIL PROTECTED] wrote on 06/02/2008 02:04:46 AM: Hi, A quick search did not show up any XSD or DTD to validate the services.xml that is used in the axis2 services archive. Maybe I was not looking in the right places, is there any way I can determine if a given XML is a valid services XML or not? Thanks, ~ Vikas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Validating-Services.xml-tp17595217p17610505.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 wsdl2java codegen gives different structures than Axis1
I'm having a problem where I can't get Axis2 to generate a java class so
that it is compabible with how Axis1 generated the java for the same
portion of wsdl.
Specifically, with Axis1 the wsld resulted in generating a primitive
array, but with Axis2 it generates an additional ArrayOf class and then
this new class contains the primative array.
These are the arguments I used in my ant task
arg line=--databinding-method ${databiding}/
arg line=--server-side${serverside}/
arg line=-uri ${wsdlfilename}/
arg value=--unpack-classes/ !-- This option specifies whether
to unpack the
classes and generate separate
classes for
the databinders. --
arg value=--generate-all/ !-- Generates all the classes. This
option is
valid only with the -ss (server
side code
generation) option. When on, the
client code
(stubs) will also be generated
along with the
skeleton. --
arg value=--all-ports/ !-- Generate code for all ports --
arg value=--flatten-files/ !-- Flattens the generated files --
arg value=--sync/ !-- Generate code only for sync
style --
arg line=-Ejavaversion 1.5/
arg value=--unwrap-params/ !-- Switch on un-wrapping --
arg value=--noBuildXML/!-- Don't generate the build.xml in
the output directory --
arg value=--noWSDL/!-- Don't generate WSDL's in the
resources directory --
arg line=--output ${output.generated.src}/
arg value=--backword-compatible / !-- Generate Axis 1.x
backword compatible code. --
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Soap Header
Hello, I am new to web services. I created WSDL file also request and response parameter. Generated soap message have only Body no Header information. I want to include Header information for user id and password. Please provide me some point so i will update my WSDL file and how to write server side code for authorization. Thanks, Pritesh Agrawal
RE: Socket connect every time?
Maybe you should set your service scope to session or application. -Original Message- From: Wenhao Xu [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2008 06:19 PM To: axis-user@ws.apache.org Subject: Socket connect every time? Hi all, I just start to use Axis2. I need to send array frequently. But I found that when every time I send a array, I need to reconnect to the server. This may cause the performace problem. How could I configure so that the continuous sending can make use of just one connection? Thanks. Wenhao - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
type:anyType and OMElement not fixed ?
Hi everyone, after a lot hours on internet looking for my problem, I still
don't have any solutions...
I think maybe some people are familiar with a bug from axis2 codegen
(wsdl2java), where an element defined as type=anyType
was generated as an OMelement (or array of OMElements) within the java side.
I saw that it was fixed some months ago, and so I should have a
java.lang.Object type when I use an element defined as type=anyType.
But, whatever verison of axis2 I use (1.3 with axis2-adb-1.3, 1.2, 1.1.1,
1.1 or the axis2 1.3 snapshot, or axis2 1.4), I have every time an
OMElement[] instead of an Object[].
Does every one as found a solution, I thought the bug was fixed so why it
don't work at home ?
for who want to help me, here is a part of my schema, and the java code
generated..
__
complexType name=SearchConditionClauseType
annotation
documentation Search Clause Fragment is a comparison between
a field and a value. /documentation
/annotation
sequence
element name=Comparator type=tns:SearchComparatorType
nillable=true
annotation
documentation comparator /documentation
/annotation
/element
element name=FieldName type=string nillable=true
annotation
documentation FieldName to search. Pay attention,
fieldnames that are not defined by a type will throw an exception.
/documentation
/annotation
/element
element name=Values *type=anyType* maxOccurs=unbounded
nillable=true
annotation
documentation Value for the test. When using the
Like operator, the wildcard % can be used. Multiples values can be tested
(via OR operator) /documentation
/annotation
/element
element name=RelationName type=string maxOccurs=1
minOccurs=0 nillable=true
annotation
documentationThere are some relation between
types./documentation
/annotation
/element
/sequence
/complexType
___
public class SearchConditionClauseType implements
org.apache.axis2.databinding.ADBBean {
/**
* field for Comparator
*/
protected
com.vslitc.service._2008.schema._2008.vslcommontypes.SearchComparatorType
localComparator;
/**
* field for FieldName
*/
protected java.lang.String localFieldName;
/**
* field for Values
* This was an Array!
*/
* protected org.apache.axiom.om.OMElement[] localValues;*
/**
* field for RelationName
*/
protected java.lang.String localRelationName;
/* This tracker boolean wil be used to detect whether the user called
the set method
* for this attribute. It will be used to determine whether to include
this field
* in the serialized XML
*/
protected boolean localRelationNameTracker = false;
Even if nobody know why it does not work at home, maybe someone could send a
generated code with axi2 *1.3* which worked and generated a good
java.lang.Object[] ?
So I can edit my files and solve my problems ?
In fact, if I can't generate the good code, I will juste need an exemple of
generated code to apply it in my proper code.
thanks a lot for yours answers !
Re: Document literal style - Send XML as string
Something is generated according to the operation name defined in your WSDL. With this I'm assuming that you are using the WSDL2Java tool or eclipse plug in. I still don't understand completely your problem. Is the SOAPUI able to send a successful message to the WS? What are you receiving back? I'll do a test later but what is curious to me is the fact that in your SOAP message the XML string parameter is not been escaped as lt; What code are you using to call your stub? -Pablo Melchi http://pablo-melchi.blogspot.com http://www.linkedin.com/pub/8/747/354 Mohan Radhakrishnan wrote: Hi, The WSDL is copied at the end of this mail. According to soap UI and the stub bindings what I am sending seems to be right. What I am sending is ?xml version=...? soapenv:Envelope xmlns:soapenv=http: //schemas.xmlsoap.org/soap/envelope/ soapenv:Bodysomething:test xmlns: something=http://test.com; something:arg0![CDATA[Request xsi: noNamespaceSchemaLocation=Test1.0.4.xsd xmlns:xsi=http://www.w3. org/2001/XMLSchemainstance Header .. . /soapenv:Envelope But the service generated by somebody else seems to look for the XML as a child of something:arg0 Next question is about this 'something'. It is generated for me according to what rule. Can I override it ? If this WSDL is used by both the server and the client then there should not be any problem. That is what you are trying to say ? _ ?xml version='1.0' encoding='UTF-8'? s0:definitions name=TestServiceDefinitions targetNamespace=http://test.com; xmlns= xmlns:s0=http://schemas.xmlsoap.org/wsdl/; xmlns:s1=http://test.com; xmlns:s2=http://schemas.xmlsoap.org/wsdl/soap/; s0:types xs:schema attributeFormDefault=unqualified elementFormDefault=qualified targetNamespace=http://test.com; xmlns:s0=http://schemas.xmlsoap.org/wsdl/; xmlns:s1=http://test.com; xmlns:s2=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xs=http://www.w3.org/2001/XMLSchema; xs:element name=test xs:complexType xs:sequence xs:element name=arg0 type=xs:string/ /xs:sequence /xs:complexType /xs:element xs:element name=testResponse xs:complexType xs:sequence xs:element name=return type=xs:string/ /xs:sequence /xs:complexType /xs:element /xs:schema /s0:types s0:message name=test s0:part element=s1:test name=parameters/ /s0:message s0:message name=testResponse s0:part element=s1:testResponse name=parameters/ /s0:message s0:portType name=TestPortType s0:operation name=test parameterOrder=parameters s0:input message=s1:test/ s0:output message=s1:testResponse/ /s0:operation /s0:portType s0:binding name=TestServiceSoapBinding type=s1:TestPortType s2:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ s0:operation name=test s2:operation soapAction=http://test.com/test; style=document/ s0:input s2:body parts=parameters use=literal/ /s0:input s0:output s2:body parts=parameters use=literal/ /s0:output /s0:operation /s0:binding s0:service name=TestService s0:port binding=s1:TestServiceSoapBinding name=TestPort s2:address location=http://localhost:8081/axis2/services/TestService/ /s0:port /s0:service /s0:definitions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 SSL Configuration [Exception javax.crypto.Cipher.getInstance]
I generated self signed certificate, using keytool utility. Imported server certificate to client keystore. Set these system properties as: System.setProperty(javax.net.ssl.trustStore, C:/cert/clientTrustStore); System.setProperty(javax.net.ssl.trustStorePassword, passwd); Environment details are as Axis version: Axis2 1.3 Server : Tomcat 5.5.26 JDK: 1.5 At client I am getting this error Exception in thread main java.lang.NoClassDefFoundError at javax.crypto.Cipher.getInstance(DashoA12275) at com.sun.net.ssl.internal.ssl.JsseJce.getCipher(Unknown Source) at com.sun.net.ssl.internal.ssl.RSACipher.init(Unknown Source) at com.sun.net.ssl.internal.ssl.RSACipher.getInstance(Unknown Source) at com.sun.net.ssl.internal.ssl.PreMasterSecret.init(Unknown Source) Am I missing any required jar? --Thanks in Advance Prash On 5/24/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Prash, -prashants b [EMAIL PROTECTED] wrote: - Still its giving error at client Exception in thread main java.lang.NoClassDefFoundError at javax.crypto.Cipher.getInstance(DashoA12275) Sorry if this stating the obvious, but something (I'm guessing the jar for your security provider implementation) if not being found in your classpath. If you do a Google search on javax.crypto.Cipher.getInstance(DashoA12275) you'll get some suggestions. You don't say anything about your environment - application server, Axis version, etc - so I can't suggest anything more specific. And quite possibly I couldn't even with that information. :-) - Steve - 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: Document literal style - Send XML as string
Hi, This is the code I am using. WSDL2Java is used. I meant to say that SOAP UI gave me a SOAP message similar to what I get using this method. It is like this test:arg0This is where the XML goes as a String/test:arg0. My operation name in the WSDL does not match the the prefix 'test'. java2wsdl has -tp( targetnamespaceprefix override ). So I thought I can override it using wsdl2java also. stub = new TestServiceStub( SECURE_WEB_SERVICE ); document = TestDocument.Factory.newInstance(); File file = new File(Request.xml ); Request request = Request. Factory. parse( getXml( file ) ); //Set XML as string test = document.addNewTest(); test.setArg0( request.toString() ); document.setTest( test ); Basically my question is - Does the SOAP message match my WSDL contract ? Thanks, Mohan -- View this message in context: http://www.nabble.com/Document-literal-style---Send-XML-as-string-tp17586208p17616168.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
