Re: Dynamically Set Preemptive Authentication
FYI - Found a way to bypass preemptive authentication. Added a servlet filter in front of the Axis2 servlet to interrogate the http authorization header. If not present, return a 401 with a dummy realm in the WWW-Authenticate header. This will allow both preemptive and non-preemptive modes of Basic authentication to work. Ted Jones wrote: Let me re-phrase my question... Is it possible to disable preemptive authentication in Axis2? Thanks, Ted On Mon, 2008-07-28 at 14:30 -0500, Ted Jones wrote: I have a client that uses HTTP Basic authentication and was coded for a Systinet web service engine. The HTTP Client code did not use preemptive authentication with Systinet, but Axis2 does since it uses the commons-httpclient code base. Is there anyway to set preemptive authentication to true without modifying all the client code? Perhaps a setting in axis2.xml or a handler of some sort? Also, not setting this value to true and also the absence of the credentials altogether results in a HTTP 500 error, shouldn't this be a 401? Thanks, Ted - 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: Dynamically Set Preemptive Authentication
Let me re-phrase my question... Is it possible to disable preemptive authentication in Axis2? Thanks, Ted On Mon, 2008-07-28 at 14:30 -0500, Ted Jones wrote: I have a client that uses HTTP Basic authentication and was coded for a Systinet web service engine. The HTTP Client code did not use preemptive authentication with Systinet, but Axis2 does since it uses the commons-httpclient code base. Is there anyway to set preemptive authentication to true without modifying all the client code? Perhaps a setting in axis2.xml or a handler of some sort? Also, not setting this value to true and also the absence of the credentials altogether results in a HTTP 500 error, shouldn't this be a 401? Thanks, Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dynamically Set Preemptive Authentication
I have a client that uses HTTP Basic authentication and was coded for a Systinet web service engine. The HTTP Client code did not use preemptive authentication with Systinet, but Axis2 does since it uses the commons-httpclient code base. Is there anyway to set preemptive authentication to true without modifying all the client code? Perhaps a setting in axis2.xml or a handler of some sort? Also, not setting this value to true and also the absence of the credentials altogether results in a HTTP 500 error, shouldn't this be a 401? Thanks, Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiple Axis2 security mechanisms for a given web service
Is it possible to have Rampart engaged for a web service but also allow support for HTTPBasic, or is it just one or the other? TIA, Ted
Re: Globally Disengage Module from Client
Thanks for the reply Martin. This just works for the client though, not the server, right? On Mon, 2008-02-25 at 21:42 -0500, Martin Gainty wrote: Ted- ServiceClient has 2 methods which will disengage a previously engaged Module either disengageModule(String moduleName) public void disengageModule(QName moduleName) Martin - Original Message - From: Ted Jones To: axis-user@ws.apache.org Sent: Monday, February 25, 2008 4:17 PM Subject: Globally Disengage Module from Client Is there a way to globally disengage a module (Rampart for example) on the server from an Axis2 client? Thanks, Ted
Globally Disengage Module from Client
Is there a way to globally disengage a module (Rampart for example) on the server from an Axis2 client? Thanks, Ted
The CLIENT_SIDE parameter is already locked and the value cannot be overridden
We have a JMeter instance running load tests against our Axis2 server. After 4 threads are started, we get the following exception: 2007/12/06 18:22:34 ERROR - jmeter.protocol.java.sampler.AbstractJavaSamplerClient: SampleResult: error during sample org.apache.axis2.AxisFault: Error in extracting message properties at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:63) at org.apache.axis2.engine.Phase.invoke(Phase.java:383) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:433) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at com.metamatrix.qbweb.axis.client.SqlQueryWebServiceSqlQueryWebServiceSOAP11Port_httpStub.getConnection(SqlQueryWebServiceSqlQueryWebServiceSOAP11Port_httpStub.java:459) at test.widget.soap.sqlquerywebservice.testframework.jmeter.sqlquerywebservice.BatchQuerySampler.runBatchQuery(BatchQuerySampler.java:600) at test.widget.soap.sqlquerywebservice.testframework.jmeter.sqlquerywebservice.BatchQuerySampler.runTest(BatchQuerySampler.java:446) at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSampler.java:168) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:281) at java.lang.Thread.run(Thread.java:534) Caused by: org.apache.rampart.RampartException: Error in extracting message properties at org.apache.rampart.RampartMessageData.init(RampartMessageData.java:310) at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:57) at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:57) ... 11 more Caused by: org.apache.axis2.AxisFault: The CLIENT_SIDE parameter is already locked and the value cannot be overridden. at org.apache.axis2.description.AxisDescription.addParameter(AxisDescription.java:60) at org.apache.rampart.RampartMessageData.init(RampartMessageData.java:172) ... 13 more We are using Rampart with usernametoken and plain text password. We tried setting the locked option to true for the OutflowSecurity parameter in the client axis2.xml, but received a ClassCastException within Axis2. Has anyone encountered this before? Thanks, Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JMS on axis2
Make that version.aar... Ted Jones wrote: I would try stripping down your service.xml to the bare minimum. Something like this: service name="MyService" messageReceivers messageReceiver mep="http://www.w3.org/ns/wsdl/in-out" class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver" / /messageReceivers parameter name="ServiceClass" locked="false" Server.MyService /parameter /service Your axis2.xml seems correct. Also, try adding the version.sar and view through JConsole to see if it shows up as a queue. zze-TRABELSI Anis RD-BIZZ-ISS wrote: JMS on axis2 I changed axis2.xml as you told me and I keptevery thing else unchanged but I still have this exception : 14 nov. 2007 11:07:14 org.apache.axis2.transport.jms.JMSOutTransportInfo getDestination ATTENTION: Cannot get or lookup JMS destination : MyService from url : jms:/MyService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.provider.url="" : MyService 14 nov. 2007 11:07:45 org.apache.axis2.transport.jms.JMSSender invoke ATTENTION: Did not receive a JMS response within 3 ms to destination : queue://MyService org.apache.axis2.AxisFault: The input stream for an incoming message is null. at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:61) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:356) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at clientstub.MyServiceMyServiceSOAP12Port_jmsStub.AddNumbers(MyServiceMyServiceSOAP12Port_jmsStub.java:165) at service.Client.test(Client.java:27) at service.Client.main(Client.java:40) For information,here are my services.xml and a the part of axis2.xml dealing with JMS transport: services.xml !-- This file was auto-generated from WSDL -- !-- by the Apache Axis2 version: #axisVersion# #today# -- serviceGroup service name="MyService" transports transportjms/transport /transports messageReceivers messageReceiver mep="http://www.w3.org/ns/wsdl/in-out" class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver" / /messageReceivers parameter name="ServiceClass" locked="false" Server.MyService /parameter parameter name="useOriginalwsdl" locked="false" false /parameter parameter name="modifyUserWSDLPortAddress" locked="false" true /parameter operation name="addNumbers" mep="http://www.w3.org/ns/wsdl/in-out" actionMappingurn:addNumbers/actionMapping outputActionMappingurn:addNumbers/outputActionMapping /operation /service /serviceGroup axis2.xml ... transportReceiver name="jms" class="org.apache.synapse.transport.jms.JMSListener" parameter name="myTopicConnectionFactory" parameter name="java.naming.factory.initial" org.apache.activemq.jndi.ActiveMQInitialContextFactory /parameter parameter name="java.naming.provider.url" tcp://localhost:61616 /parameter parameter name="transport.jms.ConnectionFactoryJNDIName" TopicConnectionFactory /parameter /parameter parameter name="myQueueConnectionFactory" parameter name="java.naming.factory.initial" org.apache.activemq.jndi.ActiveMQInitialContextFactory /parameter parameter name="java.naming.provider.url" tcp://localhost:61616 /parameter parameter name="transport.jms.ConnectionFactoryJNDIName" QueueConnectionFactory /parameter /parameter parameter name="default" parameter name="java.naming.factory.initial" org.apache.activemq.jndi.ActiveMQInitialContextFactory /parameter parameter name="java.naming.provider.url" tcp://localhost:61616 /parameter parameter name="transport.jms.ConnectionFactoryJNDIName" QueueConnectionFactory /parameter /parameter /transportReceiver ... transportSender name="jms" class="org.apache.synapse.transport.jms.JMSSender" / ... Anis De: Asankha C. Perera [mailto:[EMAIL PROTECTED]] Envoy: mardi 13 novembre 2007 18:17 : axis-user@ws.apache.org Objet: Re: JMS on axis2 Can I suggest you try something ..? Can you download http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/synapse/synapse-transports/1.1/synapse-transports-1.1.jar into your lib folder (i.e. where your axis2-kernel.jar currently resides) and edit your axis2.xml as transportReceiver name="jms
Re: JMS on axis2
Title: JMS on axis2 It does look like it's starting up correctly. Any chance you could post your service.xml and axis2.xml (client and server)? zze-TRABELSI Anis RD-BIZZ-ISS wrote: Thank you for your answer I have already seen this thread, I think the problem does not come from the deployment of the service. Here is what I get when I start tomcat (the JMS transport is initialized): 13 nov. 2007 15:40:10 org.apache.catalina.core.AprLifecycleListener init INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Java\JDK\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;c:\orawin\bin;C:\oracle\ora81\bin\;C:\Program Files\Oracle\jre\1.1.7bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Axalto\Access Client\v5\;C:\Program Files\QuickTime\QTSystem\;C:\Sun\SDK\bin;C:\Sun\jwsdp-2.0\jwsdp-shared\bin;C:\Sun\AppServer\bin;C:\Java\Sun\bin;C:\JOnAS-4.8.5ant\bin;C:\Java\JDK\bin;C:\JOnAS-4.8.5\bin\nt;C:\Sun\jwsdp-2.0\jwsdp-shared\bin;AXIS2_HOME;AXIS2_HOME\bin;J2EE_HOME\bin;M2_HOME;M2_HOME\bin 13 nov. 2007 15:40:10 org.apache.coyote.http11.Http11Protocol init INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 13 nov. 2007 15:40:10 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 525 ms 13 nov. 2007 15:40:10 org.apache.catalina.core.StandardService start INFO: Dmarrage du service Catalina 13 nov. 2007 15:40:10 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.13 13 nov. 2007 15:40:10 org.apache.catalina.startup.HostConfig deployWAR INFO: Dploiement de l'archive axis2.war de l'application web 13 nov. 2007 15:40:11 org.apache.axis2.deployment.ModuleDeployer deploy INFO: Deploying module: addressing-1.2 13 nov. 2007 15:40:11 org.apache.axis2.deployment.ModuleDeployer deploy INFO: Deploying module: soapmonitor-1.2 13 nov. 2007 15:40:11 org.apache.axis2.deployment.ServiceDeployer deploy INFO: Deploying Web service: MyService.aar 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSConnectionFactory getDestinationName ATTENTION: Error looking up destination with JNDI name : MyService to map its corresponding provider specific Destination name 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSConnectionFactory addDestination ATTENTION: JMS Destination with JNDI name : MyService does not exist 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSConnectionFactory addDestination ATTENTION: JMS Destination with JNDI name : MyService created 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSConnectionFactory addDes tinationINFO: Mapping JNDI name : MyService and JMS Destination name : MyService againstservice : MyService 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSListener init INFO: JMS Transport Receiver (Listener) initialized... 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSConnectionFactory listenOnDestination ATTENTION: Cannot find destination : MyService Creating a Queue with this name 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSConnectionFactory listen INFO: Connection factory : default initialized... 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSConnectionFactory listen INFO: Connection factory : myTopicConnectionFactory initialized... 13 nov. 2007 15:40:12 org.apache.axis2.transport.jms.JMSConnectionFactory listen INFO: Connection factory : myQueueConnectionFactory initialized... 13 nov. 2007 15:40:13 org.apache.coyote.http11.Http11Protocol start INFO: Dmarrage de Coyote HTTP/1.1 sur http-8080 13 nov. 2007 15:40:13 org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 13 nov. 2007 15:40:13 org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/32 config=null 13 nov. 2007 15:40:13 org.apache.catalina.startup.Catalina start INFO: Server startup in 2732 ms De: Ted Jones [mailto:[EMAIL PROTECTED]] Envoy: mardi 13 novembre 2007 17:12 : axis-user@ws.apache.org Objet: Re: JMS on axis2 Here is a thread on JMS with Axis2 that may be helpful to you. http://www.mail-archive.com/axis-user@ws.apache.org/msg26522.html HTH, Ted zze-TRABELSI Anis RD-BIZZ-ISS wrote: Hello, I'm trying to run JMS over axis2 1.2 I create a web service called MyService which I deploy on tomcat 6.0.13 I generate the client stub and I start activemq (as JMS provider) The problem appears when I invoke MyService, I get the following exception : 13 nov. 2007 15:56:51 org.apache.axis2.transport.jms.JMSOutTransportInfo getDestination ATTENTION: Cannot get or lookup JMS destination : MyService from url : jms:/MyService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.provider.url="" : MyService org.apache.axis2.AxisFault: at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Util
Re: ExceptionInInitializerError when trying to create a new ServiceClient
I had that issue once before. I didn't have the correct StAX jar version in my classpath. HTH, Ted Iyengar, Kumar wrote: Hi all, Has anyone seen this? It was working for me till I tried removing some of the jar files that are part of axis2. After that I added the removed ones back in and still get this error. I am using Axis2 1.3 and it is generating this error when trying to create a ServiceClient. Exception in thread "main" java.lang.ExceptionInInitializerError at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:564) at org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:96) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:79) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:615) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:115) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:180) at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:146) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:139) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:228) at com.bmc.arsys.ws.client.WebServiceSoapClient.call(WebServiceSoapClient.java:178) at com.bmc.arsys.ws.client.WebServiceSoapClient.getTestWS(WebServiceSoapClient.java:795) at com.bmc.arsys.ws.client.WebServiceSoapClient.main(WebServiceSoapClient.java:616) Caused by: java.lang.IllegalStateException: No valid ObjectCreator found. at org.apache.axiom.om.util.StAXUtils$Pool.init(StAXUtils.java:64) at org.apache.axiom.om.util.StAXUtils.clinit(StAXUtils.java:88) ... 13 more Any help is appreciated. Thanks -kumar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating from Tomcat AXIS2 to Standalone AXIS2
Thank you Ajith. I will check it out. Ted - Original Message - From: Ajith Ranabahu [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Tuesday, October 2, 2007 10:00:06 AM (GMT-0600) America/Chicago Subject: Re: Migrating from Tomcat AXIS2 to Standalone AXIS2 Hi Ted, There is an Axis2 based production quality server called WSAS(http://wso2.com/products/wsas/) (fully opensource) from WSO2. It is based on the tomcat core and can act much more reliably than the simple Axis server. Ajith On 10/2/07, redhatter [EMAIL PROTECTED] wrote: If I could chime in on this... I see a need for a production quality standalone Axis2 server. To assume that users of a web service are content using Tomcat or some other J2EE container may be incorrect. From personal experience, I have seen customers that have sworn allegiance to one container or another and need our web service to run in their environment. This means mimicking multiple environments to test our web services which is time and resource intensive. A production caliber standalone Axis2 container would alleviate the need for this additional resource drain and simplify technical support. Thanks, Ted Demetris G wrote: Exactly ... thanks for the good feedback Anne and Amila. Anne Thomas Manes wrote: You'll find this to be the case with most open source projects -- why reimplement the application container capability again when systems like Tomcat already exist? The Axis and Axis2 teams are focusing on solving a different problem -- processing and dispatching XML messaging requests. The projects are designed to run in any Java EE or servlet engine. If you do find a commercial or open source project that includes an application container, most likely it includes a copy of Tomcat or Jetty or it is built on a Java EE app server. Axis does support a stand-alone runtime mode, but it is intended only for testing purposes, not for production runtime. Anne On 9/19/07, Demetris G [EMAIL PROTECTED] wrote: In other words - and excuse the multiple emails on this - although I do have a good understanding on how Axis and Axis2 work, my point is that I noticed in the literature that some researchers are using the wrong terminology to explain their functionality that confuses some people. These projects are the implementations of the SOAP (and REST processing) specifications, they can expose WS and process their communications with the world. What people should understand is that the service implementations are not really contained in these engines and thus the Tomcats etc. Well in any case, thanks for the feedback Amila. Demetris G wrote: Would you say the same for Axis ? Axis can be used as a standalone web services container - yes ? If not then we have people publishing papers on that that may have it wrong. Thanks Demetris G wrote: That's what I thought :) Thanks Amila. Amila Suriarachchi wrote: On 9/19/07, *Amila Suriarachchi* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: On 9/18/07, *Demetris G* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: So hold on a sec - Amila, are you saying that Axis2 is not considered a stable and reliable enough standalone web service container Axis2 is not a web service container. Axis2 is a soap and REST message processor which supports WS*. Axis2 is a stable product. Basically it concentrates on Soap and REST message processing. Sorry I mean It is not a standalone web application container. It alows users to deploy web services and expose them with the soap and REST message processing capabilities. and it should always be deployed within other proven containers (i.e. Tomcat etc.)? Yes this is the recommended way. if you want an standalone server you can use WSAS ( http://wso2.com/products/wsas/) which uses the axis2 and embedded tomcat server. Is this the case only for Axis2 or also Axis? Where is this documented? Amila Suriarachchi wrote: On 9/18/07, *Marko Simic* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Since the only remote part of application is single web service I thought it would be much easer for deployment/management to deploy preconfigured standalone dedicated server. Also it could take less memory and performance could be better. Anyway, these are only assumptions = something that should be tested. If you think I am wrong, I would like to hear why and what you may
Re: How to pass user id and password to Webservice
Ashish, You can use one of several authentication protocols with Axis2. Here are some useful links: http://wso2.org/library/161 http://ws.apache.org/axis2/modules/rampart/1_1/security-module.html Thanks, Ted - Original Message - From: Ashish Kulkarni [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Monday, September 24, 2007 2:18:38 PM (GMT-0600) America/Chicago Subject: How to pass user id and password to Webservice Hi How to pass userid and password, to validate user calling web service. I want to validate userid and password against some validation framework, so what is the best way to pass it Weather to put it in Header element of web service? or weather in Body Element? What is the best practise, are there any sample code for doing so Ashish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Web Services Transactions in Axis2
Does anyone know the status of Kandula2 for Axis2? Is anyone using Kandula/Kandula2 with Axis2? If so, do you know of any example code/configurations I could reference. TIA, Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [AXIS2] Engage module problem
Lorenzo, To engage programmatically: stub._getServiceClient().engageModule(PD); This assumes that the module is available as well, meaning it is in your repository. Thanks, Ted -Original Message- From: Lorenzo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 05, 2007 8:42 AM To: AXIS Subject: [AXIS2] Engage module problem I have to add a module to a service. All go fine id i engage it globally in axis.xml, but how to engage it programmatically? --- CODE START --- AxisConfiguration axisCfg = configurationContext.getAxisConfiguration(); AxisService openspcoopService = new AxisService(OPENSPCOOP_SERVICE_NAME); AxisOperation operation = new InOutAxisOperation(OPERATION_Q_NAME); operation.setMessageReceiver(new OpenSPCoopMessageReceiver()); openspcoopService.addOperation(operation); List transports = new ArrayList(); transports.add(org.apache.axis2.Constants.TRANSPORT_HTTP); transports.add(https); openspcoopService.setExposedTransports(transports); axisCfg.addService(openspcoopService); --- CODE END --- i tryed with openspcoopService.engageModule(axisCfg.getModule(PD), axisCfg); (PD is the name of the module) but it log that it is just engaged (but it not work) openspcoopService.addModuleref(PD); doesn't work too... any suggestion? thx, Lorenzo - 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] WS-Addressing version on server
Thanks for the reply Anthony. My use case is the actually the reverse: Axis2 Server with a .NET WSE 3 client. Is there some way to configure the WS-Addressing namespace version to be the older version in the Axis2 server? Thanks, Ted -Original Message- From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Sun 8/26/2007 4:31 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-Addressing version on server I am - I've done three different interop projects with .NET WSE 3 clients and servers. I use the options object to tell my client to use the older namespace (see below) when sending to .NET servers, but you wanted a different way of achieving it? options.setProperty(org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION, org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE); anthony. Ted Jones wrote: Is anyone using WS-Addressing with Axis2 web services and a .Net client? *From:* Ted Jones [mailto:[EMAIL PROTECTED] *Sent:* Thursday, August 23, 2007 3:49 PM *To:* axis-user@ws.apache.org *Subject:* [Axis2] WS-Addressing version on server I am testing a .Net client with WSE 3.0 for compatibility with an Axis2 1.2 deployed web service. I have the addressing enabled and engaged on the server along with Rampart. WSE 3.0 only supports the submission version of WS-Addressing while Axis2 defaults to the final version (I believe). Is there a way in the Axis2 server to tell it to use the submission version (perhaps in the service.xml as a parameter to the moduleConfig)? If not, is there another way of having the client indicating to the server which version to use other than the Options object? Thanks, Ted -- Anthony - Anthony Bull Senior Developer Black Coffee Software Ltd PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mobile 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] winmail.dat- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] WS-Addressing version on server
Is anyone using WS-Addressing with Axis2 web services and a .Net client? From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, August 23, 2007 3:49 PM To: axis-user@ws.apache.org Subject: [Axis2] WS-Addressing version on server I am testing a .Net client with WSE 3.0 for compatibility with an Axis2 1.2 deployed web service. I have the addressing enabled and engaged on the server along with Rampart. WSE 3.0 only supports the submission version of WS-Addressing while Axis2 defaults to the final version (I believe). Is there a way in the Axis2 server to tell it to use the submission version (perhaps in the service.xml as a parameter to the moduleConfig)? If not, is there another way of having the client indicating to the server which version to use other than the Options object? Thanks, Ted
[Axis2] WS-Addressing version on server
I am testing a .Net client with WSE 3.0 for compatibility with an Axis2 1.2 deployed web service. I have the addressing enabled and engaged on the server along with Rampart. WSE 3.0 only supports the submission version of WS-Addressing while Axis2 defaults to the final version (I believe). Is there a way in the Axis2 server to tell it to use the submission version (perhaps in the service.xml as a parameter to the moduleConfig)? If not, is there another way of having the client indicating to the server which version to use other than the Options object? Thanks, Ted
RE: [axis2-1.1.1] Use of stubs
Alan, It doesn't look like the Addressing module is engaged on the client. If it were, a default anonymous replyTo value would be used. With Addressing engaged, you could then set this value using Options.setReplyTo(EndpointReference) in your client. Thanks, Ted -Original Message- From: Jones, Alan R [mailto:[EMAIL PROTECTED] Sent: Thursday, August 23, 2007 4:21 PM To: axis-user@ws.apache.org Subject: [axis2-1.1.1] Use of stubs Hi, I've looked around and was not able to find the info I'm looking for regarding the following questions: 1. I am using a stub generated with the Axis2 Eclipse plugin. I cannot figure how to set the ReplyTo property for my outgoing Request message. Is there an example of that? 2. Related to the above, I am using TCPMon to view the request and response messages passing between my web client which contains the stub, and the deployed service, in order to test my setting of the ReplyTo property. However, I see no default wsa:ReplyTo in the SOAP message, the header seems to be empty. Below is what I get in TCPMon on the client side. I do have the addressing module engaged from the Admin console for all services: POST /axis2/services/RuleCacheService HTTP/1.1 SOAPAction: urn:getCacheContents User-Agent: Axis2 Host: 127.0.0.1:8082 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 c8 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body getCacheContents / /soapenv:Body /soapenv:Envelope0 ...Is there something I'm missing in order to view the wsa: parameters/elements? Thanks, Alan J Alan R Jones Boeing SIS Mission Systems Denver Engineering Center (BDEC) - 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: Problems adding Axis2 to an existing Webapp
Sebastian, Your ClassNotFoundException is due to the package of your deployed Echo class not matching the ServiceClass package value in your services.xml. -- WEB-INF | |-- classes | | `-- de | | `-- hpfsc | | |-- Echo.class vs parameter name=ServiceClassde.echo.Echo/parameter So, the ServiceClass value should be: parameter name=ServiceClassde.hpfsc.Echo/parameter There is no need to explicitly identify a class location, it just needs to be in the classpath of the web app (classes, web-inf/lib) or in the service aar file directly. Thanks, Ted -Original Message- From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sun 8/12/2007 9:58 AM To: axis-user@ws.apache.org Subject: Re: Problems adding Axis2 to an existing Webapp Hi, In prder to validate ur services.xml you can use a tool hosted at http://tools.wso2.org:19762/wservices/AarValidatorXSL/ by WSO2. It consists of a tool to validate ur aar file as well. Thanks, Keith. On 8/12/07, Sebastian Stein [EMAIL PROTECTED] wrote: Hi, I have an existing webapp. Now, I want to add Axis2 to expose some classes as web service. I can't alter the structure of the existing webapp. I added the Axis2 libs to WEB-INF/ and I will later strip out the libs not actually needed. At the moment the content of WEB-INF/lib is: activation-1.1.jarcommons-logging-1.1.jar activation-LICENSE.txtcommons-logging-LICENSE.txt annogen-0.1.0.jar geronimo-spec-jms-1.1-rc4.jar annogen-LICENSE.txt geronimo-spec-jms-LICENSE.txt axiom-api-1.2.4.jar jakarta-httpcore-4.0-alpha4.jar axiom-api-LICENSE.txt jakarta-httpcore-LICENSE.txt axiom-dom-1.2.4.jar jaxb-api-2.0.2.jar axiom-dom-LICENSE.txt jaxb-impl-2.0.2.jar axiom-impl-1.2.4.jar jaxb-xjc-2.0.2.jar axiom-impl-LICENSE.txtjaxen-1.1-beta-10.jar axis2-adb-1.2.jar jaxen-LICENSE.txt axis2-adb-codegen-1.2.jar jettison-1.0-RC1.jar axis2-codegen-1.2.jar jibx-bind-1.1.4.jar axis2-fastinfoset-1.2.jar jibx-run-1.1.4.jar axis2-java2wsdl-1.2.jar mail-1.4.jar axis2-jaxbri-1.2.jar mail-LICENSE.txt axis2-jaxws-1.2.jar neethi-2.0.1.jar axis2-jaxws-api-1.2.jar neethi-LICENSE.txt axis2-jibx-1.2.jarstax-api-1.0.1.jar axis2-json-1.2.jarstax-api-LICENSE.txt axis2-kernel-1.2.jar stax-utils-20060915.jar axis2-LICENSE.txt stax-utils-LICENSE.txt axis2-metadata-1.2.jarwoden-1.0-incubating-M7a.jar axis2-saaj-1.2.jarwoden-LICENSE.txt axis2-saaj-api-1.2.jarwsdl4j-1.6.2.jar axis2-soapmonitor-1.2.jar wsdl4j-LICENSE.txt axis2-spring-1.2.jar wstx-asl-3.2.1.jar axis2-tools-1.2.jar wstx-LICENSE.txt axis2-xmlbeans-1.2.jarxalan-2.7.0.jar backport-util-concurrent-2.2.jar xbean-2.2.0.jar backport-util-concurrent-LICENSE.txt xbean-LICENSE.txt commons-codec-1.3.jar xercesImpl-2.8.1.jar commons-codec-LICENSE.txt xercesImpl-LICENSE.txt commons-fileupload-1.1.1.jar xml-apis-1.3.03.jar commons-fileupload-LICENSE.txtxml-apis-LICENSE.txt commons-httpclient-3.0.1.jar XmlSchema-1.3.1.jar commons-httpclient-LICENSE.txtXmlSchema-LICENSE.txt commons-io-1.2.jar I created a small example, just consisting of a servlet and a POJO java class, which should be exposed as web service. The webapp folder structure looks as follows: |-- META-INF |-- WEB-INF | |-- classes | | `-- de | | `-- hpfsc | | |-- Echo.class | | `-- EchoServlet.class | |-- lib | | |-- ... | |-- services | | `-- Echo | | |-- META-INF | | | `-- services.xml | `-- web.xml `-- index.jsp I added Axis to my web.xml: ?xml version=1.0 encoding=UTF-8? web-app id=WebApp_ID version=2.4 xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd; display-nameAxis2Test/display-name servlet display-nameEcho Servlet/display-name servlet-nameEchoServlet/servlet-name servlet-classde.hpfsc.EchoServlet/servlet-class /servlet servlet display-nameApache-Axis Servlet/display-name servlet-nameAxisServlet/servlet-name servlet-classorg.apache.axis2.transport.http.AxisServlet /servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameEchoServlet/servlet-name
RE: Axis2 - how to add custom handler to a specific service
One option is to add a check in your custom handler for the service name you want the logic to apply to. You can get it in the invoke() method like so: messageContext.getAxisService().getName() HTH, Ted -Original Message- From: Shantanu Sen [mailto:[EMAIL PROTECTED] Sent: Friday, July 13, 2007 4:48 PM To: axis-user Subject: Axis2 - how to add custom handler to a specific service Is the only way of adding a custom handler in the dispatch phase (say after the AddressingBasedDispatcher) is to add it in the axis2.xml? If I want this handler only for a specific service among the various other deployed services, can I configure this in the services.xml without touching the axis2.xml? I want to avoid adding this as a global handler for all services. Or is the recommended way is to add this handler in a module and engage the module in the services.xml of the specific service? If this is true, I still have to modify the axis2.xml or I just drop the module in the modules repository? Thanks for any help. Shantanu Sen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] JMS Client Options Not Passed
I have a JMS listener enabled in an Axis2 1.2 war. I have a JMS client where I am adding a property to the client of a stub instance. I have a handler at the top of the transport phase that interrogates the properties of the context options for the property added by the client. The property is not there. Is this not the correct approach for this scenario? Is there another way to accomplish this? Also, the to EPR is null in my handler even though I am setting this value in the client. Is this expected? Here is my client code: stub = new MyServiceStub(ctx, http://chicago:8080/axis2/services/myservice); String url = jms:/myservice? transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.nami ng.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactor yjava.naming.provider.url=tcp://localhost:61616; Options options = stub._getServiceClient().getOptions(); options.setProperty(Constants.Configuration.TRANSPORT_URL, url); options.setProperty(test, Some value I need in my handler); options.setTo(new EndpointReference(http://chicago:8080/axis2/services/myservice;)); GetBookCollectionByTitleRequestDocument getBookCollectionByTitleRequest2 = (GetBookCollectionByTitleRequestDocument) getTestObject(GetBookCollectionByTitleRequestDocument.class); GetBookCollectionTypeByTitle getBookCollectionTypeByTitle = GetBookCollectionTypeByTitle.Factory .newInstance(); getBookCollectionTypeByTitle.setBookName(Compilers); getBookCollectionByTitleRequest2 .setGetBookCollectionByTitleRequest(getBookCollectionTypeByTitle); BookCollectionDocument bookCollectionDocument = stub .getBookCollection(getBookCollectionByTitleRequest2); assertNotNull(bookCollectionDocument); TIA, Ted
RE: [Axis2/Rampart] NullPointerException when calling non-existing Webservice
FYI - I am seeing the same behavior in Axis2 1.2 and Rampart 1.2. Ted -Original Message- From: stlecho [mailto:[EMAIL PROTECTED] Sent: Friday, June 15, 2007 2:32 AM To: axis-user@ws.apache.org Subject: [Axis2/Rampart] NullPointerException when calling non-existing Webservice Hi, We have deployed our Webservices with Axis2 v1.1.1 and Rampart v1.1.1. When calling a non-existing Webservice, the client receives a NullPointerException :o(. Tracing down the problem I've found that the cause of this problem is the getServicePolicyKey method in the RampartMessageData class: msgCtx.getAxisService() returns null. Is there a patch available that solves - i.e. generates a user friendly error message - this issue ? Regards, Stefan Lecho. -- View this message in context: http://www.nabble.com/-Axis2-Rampart--NullPointerException-when-calling- non-existing-Webservice-tf3926271.html#a11134524 Sent from the Axis - User mailing list archive at Nabble.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: [Axis2] Sandesha2 1.2 plus Rampart 1.2 in Axis2 1.2
Chamikara, Thanks for the reply. I reset the SecurityManager to the dummy and I am now getting this: 2007-06-13 10:42:12,703 ERROR org.apache.sandesha2.workers.SenderWorker - Sandesha2 got an exception when sending a message: org.apache.axis2.AxisFault: WSDoAllSender: Empty username for specified action. org.apache.axis2.AxisFault: WSDoAllSender: Empty username for specified action at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.ja va:94) at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) at org.apache.axis2.engine.Phase.invoke(Phase.java:383) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) at org.apache.axis2.engine.AxisEngine.resumeSend(AxisEngine.java:318) at org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:258) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker .runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker .run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:534) When using Rampart UsernameToken security with Sandesha2, does the phase order need to change? Perhaps the WS-Security headers need to be added prior to the RM phase? I will log a JIRA (assuming it is not just a user error). FYI - I switched to HTTP Basic security with Sandesha2 and it worked fine. Thanks again, Ted From: Chamikara Jayalath [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 11:34 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Sandesha2 1.2 plus Rampart 1.2 in Axis2 1.2 Hi Ted, You do not need the SecurityManager in Non-SecureConversation scenarios. Can u please try without that. Also it will be helpful if you can raise a JIRA and attach ur client code, the error logs etc. Chamikara On 6/13/07, Ted Jones [EMAIL PROTECTED] wrote: I am able to use Rampart 1.2 (UsernameToken) and Sandesha2 1.2 in Axis2 1.2 as standalone modules, but when I engage them both I do not see any messages in TCPMon and my client times out before I get a response. I updated the Sandesha2.mar module.xml Security Manager to use org.apache.sandesha2.security.rampart.RampartBasedSecurityManager. Are there any steps I am missing? (I apologize if this is the wrong group for this posting. If so, kindly point me to the correct forum.) Thanks, Ted -- Chamikara Jayalath WSO2 Inc. http://wso2.com/ http://wso2.org/ - For your Oxygen needs
RE: Total Newb has Stupid Questions
Chris, I was able to get Paul's sample working with Axis2 1.2. It looks like Chris is using a prior version judging by the Sandesha1.1 reference? You need to make sure you get the Sandesha1.2 mar and jars if you are using Axis2 1.2. Ted -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 1:11 PM To: Chris Schumann; axis-user@ws.apache.org Subject: Re: Total Newb has Stupid Questions Chris Thanks for the debug and issues. You need to edit the first (src/) services.xml because the other one is copied over during the ant build. Then rebuild. The other option is to enable it globally across your server's axis2.xml Under the global modules section you will find: module ref=addressing/ Add module ref=sandesha2/ Paul On 6/12/07, Chris Schumann [EMAIL PROTECTED] wrote: Thanks Paul! Thanks so much for your help. Your page is kind of terse, and a little out of date. Here are my notes: - Sandesha 1.2 is available - There is no services tag in services.xml. There is a service tag. - There are two services.xml in the sample source: o samples/version/src/sample/axisversion/META-INF/services.xml o samples/version/build/classes/META-INF/services.xml In any case, I already had Version running, but not quite as your guide suggests. Here's what I get from localhost:8080/axis2/services: Deployed Services Version Available operations o getVersion I did add the phases, and when I start axis2 running there is this line: INFO: Deploying module: sandesha2-1.1 There are no errors reported. I figured I should stop here because I'm not seeing the Sandesha2Operations. What's next? Edit the services.xml file? Which one? Chris Paul Fremantle said: Chris I posted a getting started guide on my blog. http://pzf.fremantle.org/2007/05/getting-started-with-wsrm-and-axis2 .html Let me know if it helps (or doesn't!) Paul On 6/12/07, Chris Schumann [EMAIL PROTECTED] wrote: I've been tasked with showing WS-RM using Sandesha, but I'm totally inexperienced in making Java work. I'm running Fedora Core 6, and I think I have Axis2 running. I tried following the Sandesha instructions, but FC6 comes with some other Java, and I get Incompatible magic number. I have installed Sun's jdk, but I don't know how to set my CLASSPATH properly to get the demo to compile. I'm getting errors like package org.apache.axiom.om does not exist Tips and pointers greatly appreciated. Thanks, Chris --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.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]
[Axis2] Sandesha2 1.2 plus Rampart 1.2 in Axis2 1.2
I am able to use Rampart 1.2 (UsernameToken) and Sandesha2 1.2 in Axis2 1.2 as standalone modules, but when I engage them both I do not see any messages in TCPMon and my client times out before I get a response. I updated the Sandesha2.mar module.xml Security Manager to use org.apache.sandesha2.security.rampart.RampartBasedSecurityManager. Are there any steps I am missing? (I apologize if this is the wrong group for this posting. If so, kindly point me to the correct forum.) Thanks, Ted
RE: [Axis2] Message Receiver Not Found for in-only Operation
This is working now after a plethora of changes (including schema changes). Must have had one or two ducks out of row. Thanks, Ted From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 30, 2007 9:15 AM To: axis-user@ws.apache.org Subject: [Axis2] Message Receiver Not Found for in-only Operation I am upgrading to Axis2 1.2 from 1.1.1. I have a service with 6 operations (2 in-only and 4 in-out). After converting from Axis2 1.1.1 to 1.2, I receive the following error for the two in-only operations: org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation: inOnlyOperation The in-out operations work fine. Here are the message receivers defined in the service.xml: messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ /messageReceivers Any insight would be greatly appreciated. Thanks, Ted
[Axis2] Message Receiver Not Found for in-only Operation
I am upgrading to Axis2 1.2 from 1.1.1. I have a service with 6 operations (2 in-only and 4 in-out). After converting from Axis2 1.1.1 to 1.2, I receive the following error for the two in-only operations: org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation: inOnlyOperation The in-out operations work fine. Here are the message receivers defined in the service.xml: messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ /messageReceivers Any insight would be greatly appreciated. Thanks, Ted
RE: soapAction versus wsaAction
One major difference is the wsaAction is transport neutral. If you use JMS to execute a web service, the soapAction would not available without some intermediary router logic. As long as you are using WS-Addressing, the wsaAction will always be available. Ted From: Gul Onural [mailto:[EMAIL PROTECTED] Sent: Friday, May 25, 2007 11:07 AM To: axis-user@ws.apache.org Subject: soapAction versus wsaAction In the wsdl, what is the difference between soapAction and wsaAction ? Gul
RE: soapAction versus wsaAction
The values need to be valid URIs. They may or may not look the same. Based on what I have seen, the WSDL generated by Axis2 with addressing engaged will create equivalent values for both SOAP and WSA Actions. From: Gul Onural [mailto:[EMAIL PROTECTED] Sent: Friday, May 25, 2007 12:49 PM To: axis-user@ws.apache.org Subject: RE: soapAction versus wsaAction If you use http (or https) as transport mechanism, are these two (syntactically) look the same in the wsdl ? From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, May 25, 2007 1:42 PM To: axis-user@ws.apache.org Subject: RE: soapAction versus wsaAction One major difference is the wsaAction is transport neutral. If you use JMS to execute a web service, the soapAction would not available without some intermediary router logic. As long as you are using WS-Addressing, the wsaAction will always be available. Ted From: Gul Onural [mailto:[EMAIL PROTECTED] Sent: Friday, May 25, 2007 11:07 AM To: axis-user@ws.apache.org Subject: soapAction versus wsaAction In the wsdl, what is the difference between soapAction and wsaAction ? Gul
[Axis2] Beating a dead horse...
I know this has come up quite a bit, but what is the status of a Rampart module that is compatible with Axis2 1.2? The download link on the Axis2 1.2 module site is still pointing to 1.1. Thanks, Ted
RE: [Axis2] Beating a dead horse...
Sorry, I missed that posting. Thanks for the update. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, May 24, 2007 2:41 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Beating a dead horse... First of all, this is the wrong mailing list for that question. Secondly, i answered it just yesterday. http://mail-archives.apache.org/mod_mbox/ws-rampart-dev/200705.mbox/%3c1 [EMAIL PROTECTED] -- dims On 5/24/07, Ted Jones [EMAIL PROTECTED] wrote: I know this has come up quite a bit, but what is the status of a Rampart module that is compatible with Axis2 1.2? The download link on the Axis2 1.2 module site is still pointing to 1.1. Thanks, Ted -- Davanum Srinivas :: http://davanum.wordpress.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: [Axis2] Beating a dead horse...
Great. Thanks Paul/Dims. -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Thursday, May 24, 2007 3:16 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: [Axis2] Beating a dead horse... Thanks Dims! Paul On 5/24/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Paul, it's at: http://people.apache.org/dist/rampart/nightly/ On 5/24/07, Paul Fremantle [EMAIL PROTECTED] wrote: Real Soon Now! We are trying hard. It should be here within a week. You could try a nightly build which are meant to be here http://ws.zones.apache.org/dist/rampart/nightly/ But its not up. I'll chase it. Paul On 5/24/07, Ted Jones [EMAIL PROTECTED] wrote: I know this has come up quite a bit, but what is the status of a Rampart module that is compatible with Axis2 1.2? The download link on the Axis2 1.2 module site is still pointing to 1.1. Thanks, Ted -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.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] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.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: [Axis2] Getting started with Axis2 and Sandesha2 to do WS-ReliableMessaging
Very nice Paul. Nice job. Just curious, will this work with Axis2 1.1.1? I'm not sure that I have time to upgrade to Axis2 1.2 given that I've seen several posts stating things have broken moving from 1.1.1 to 1.2 and time is running out on my project. Thanks again for the great example. Ted -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tue 5/22/2007 4:54 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [Axis2] Getting started with Axis2 and Sandesha2 to do WS-ReliableMessaging Based on a post I made on axis-user, I've posted a blog entry on how to do your first WS-ReliableMessaging interaction with Axis2 and RM. Let me know if I can improve it. http://pzf.fremantle.org/2007/05/getting-started-with-wsrm-and-axis2.html Paul -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] winmail.dat- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Getting started with Axis2 and Sandesha2 to do WS-ReliableMessaging
Hi Paul. I tried the example with Axis2 1.1.1 and Sandesha2 1.1 and received the following error: org.apache.axis2.AxisFault: Incoming message input stream is null at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti ls.java:64) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:252) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:202) at sample.axisversion.VersionStub.getVersion(VersionStub.java:155) at sample.axisversion.TestRM.main(TestRM.java:47) This was the same error I ran into with my previous attempt. I then changed my code to use a callback with a separate listener per an email thread I came across. That prevented my service from being executed and the onComplete() of the callback was never executing. The files I posted reproduce this issue. I tried the same change with the example (added a callback and separate listener) and saw the same behavior. The web service is never executed and consequently neither is the callback's onComplete() method. Is it possible the separate listener is not working for Axis2 1.1.1 either? Do I need to bite the bullet and upgrade to Axis2 1.2 is I want to use WS-RM? Thanks very much for your help! Ted -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 22, 2007 7:27 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Getting started with Axis2 and Sandesha2 to do WS-ReliableMessaging Ted Should work fine, as long as you use Sandesha2 1.1 with Axis2 1.1.1. Let me know if it doesn't and I'll fix it :-) Paul On 5/22/07, Ted Jones [EMAIL PROTECTED] wrote: Very nice Paul. Nice job. Just curious, will this work with Axis2 1.1.1? I'm not sure that I have time to upgrade to Axis2 1.2 given that I've seen several posts stating things have broken moving from 1.1.1 to 1.2 and time is running out on my project. Thanks again for the great example. Ted -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tue 5/22/2007 4:54 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [Axis2] Getting started with Axis2 and Sandesha2 to do WS-ReliableMessaging Based on a post I made on axis-user, I've posted a blog entry on how to do your first WS-ReliableMessaging interaction with Axis2 and RM. Let me know if I can improve it. http://pzf.fremantle.org/2007/05/getting-started-with-wsrm-and-axis2.h tml Paul -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.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] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.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: [Axis2] WS-RM and Axis2 Asynch Client not Returning
Sorry to repost, but I just figured the more eyes the better. I would really appreciate any WS-RM/Sandesha2 experts that could take a look at this. Here is a link to the service aar, wsdl, test client, and the client and server config files. http://jonested.tripod.com/ The behavior I'm seeing is the onComplete() method of my callback is never getting executed (and neither is my web service). The service is a simple echo service (nothing to fancy). TIA, Ted -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 11:24 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Ted My machine has gone haywire and I'm just rebuilding it (well actually just backing everything up before rebuilding it). I'll debug this as soon as I get running. Paul On 5/11/07, Ted Jones [EMAIL PROTECTED] wrote: In case you have problems accessing the files via these links, you can get to them here: http://jonested.tripod.com/ and use 'Save As to download them. Thanks, Ted From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 7:17 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Martin, Paul, Amila, anybody I missed, Here are links to the service aar, wsdl, test client, and the client and server config files. Hopefully there is some glaring mistake I have made. ;-) http://jonested.tripod.com/echoClient.java http://jonested.tripod.com/client_axis2.xml http://jonested.tripod.com/server_axis2.xml http://jonested.tripod.com/echo.wsdl http://jonested.tripod.com/echo.aar I am running the client and server on the same machine. For what it's worth, in debug I am seeing multiple threads continually being spawned for the client's http simple server (port 6062). Please let me know if you need more from me. Thanks, Ted From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 9:37 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Thanks Amila. I appreciate the input. I am using Dual channel since it appeared to be required per this thread: http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/% [EMAIL PROTECTED] Is this the case? I am using Sandesha2 1.1 with Axis2 1.1.1. I have verified your points outlined below. Everything appears correct. Martin - I will put together a reproducible test case and post ASAP. Thanks for your assistance. Ted From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 12:25 AM To: axis-user@ws.apache.org; Martin Gainty Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Are you using the Dual chanel mode or single chanel? if you set the setUseSeparateListener your request comes in a different http chanel than you send the request. Otherwise it comes in the same chanel. In the dual chanel model, What happens is your client starts a simple http server on your machine and set the ReplyTo addressing header to point to the stated server. So you have to make sure these things. 1. you must have engage the Addressing. (otherwise server won't be able to find the reply location) 2. client uses the port and the host name you have specified in the axis2.xml to start its simple http server and set this address to replyTo filed. So you have to use two seperate axis2.xml files for client and the server with different port numbers if you run them both in one machine. 3. if your server is in out side your firewall, the host name you specify in the client axis2.xml should be able to access from the out side the firewall. On 5/10/07, Martin Gainty [EMAIL PROTECTED] wrote: Good Evening if you publish your wsdl we can run the client code 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: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, May 09, 2007 7:10 PM Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning So, I'm guessing that the message is never reaching the server. Which may explain why there is no logging? I can see in debug where the Sandesha2 logic is hit and the message is sent but I never see any sequences or other message traffic and my client is left polling forever waiting for the callback to complete. Any other thoughts on what might be happening here or where else I can look? Thanks, Ted -Original
RE: How does axis decide the endpoint URL?
Hi dims, Has there been any consideration given to dynamically generating the endpoint's host/port based on where the service is deployed? Thanks, Ted -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, May 18, 2007 2:11 PM To: axis-user@ws.apache.org Subject: Re: How does axis decide the endpoint URL? Please look into your axis2.xml under WEB-INF/conf there is a setting there for hard-coding the url. thanks, dims On 5/18/07, Jeremy Smith [EMAIL PROTECTED] wrote: My server has a bit of a complicated networking setup. It is behind a firewall with an external address, and it only knows about its internal addresses. The problem is that in the wsdl that axis2 generates, it directs clients to the internal URL and they can't connect. How does axis2 decide what the URL will be? Is there any way I can override this? Example: Axis generates this: wsdl:service name=MyService wsdl:port name=MyServiceSOAP11port_http binding=axis2:MyServiceSOAP11Binding soap:address location=http://10.x.x.x:80/axis2/services/MyService/ /wsdl:port wsdl:port name=MyServiceSOAP12port_http binding=axis2:MyServiceSOAP12Binding soap12:address location=http://10.x.x.x:80/axis2/services/MyService/ /wsdl:port wsdl:port name=MyServiceHttpport binding=axis2:MyServiceHttpBinding http:address location=http://10.x.x.x:80/axis2/services/MyService/ /wsdl:port /wsdl:service where 10.x.x.x is an inaccessible internal IP address. Thanks, Jeremy - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How does axis decide the endpoint URL?
To clarify, I am referring to user provided WSDL here, not Axis2 generated WSDL. Thanks, Ted -Original Message- From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, May 18, 2007 3:04 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: How does axis decide the endpoint URL? Hi dims, Has there been any consideration given to dynamically generating the endpoint's host/port based on where the service is deployed? Thanks, Ted -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, May 18, 2007 2:11 PM To: axis-user@ws.apache.org Subject: Re: How does axis decide the endpoint URL? Please look into your axis2.xml under WEB-INF/conf there is a setting there for hard-coding the url. thanks, dims On 5/18/07, Jeremy Smith [EMAIL PROTECTED] wrote: My server has a bit of a complicated networking setup. It is behind a firewall with an external address, and it only knows about its internal addresses. The problem is that in the wsdl that axis2 generates, it directs clients to the internal URL and they can't connect. How does axis2 decide what the URL will be? Is there any way I can override this? Example: Axis generates this: wsdl:service name=MyService wsdl:port name=MyServiceSOAP11port_http binding=axis2:MyServiceSOAP11Binding soap:address location=http://10.x.x.x:80/axis2/services/MyService/ /wsdl:port wsdl:port name=MyServiceSOAP12port_http binding=axis2:MyServiceSOAP12Binding soap12:address location=http://10.x.x.x:80/axis2/services/MyService/ /wsdl:port wsdl:port name=MyServiceHttpport binding=axis2:MyServiceHttpBinding http:address location=http://10.x.x.x:80/axis2/services/MyService/ /wsdl:port /wsdl:service where 10.x.x.x is an inaccessible internal IP address. Thanks, Jeremy - 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] - 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] SAML/Rampart Question
Thanks Dimuthu. That's better than nothing. :-) Any plans to add documentation/examples in the future? Anyone else have a working implementation of Rampart with SAML they could share? Specifically adding the SAML assertion to the WS-Security header. Thanks, Ted -Original Message- From: Dimuthu Leelaratne [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 16, 2007 10:28 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] SAML/Rampart Question Hi Ted, Unforutunately we don't have a sample, but we have some TestCases where Rampart talks to a Security Token Service and recieves a SAML token. Look inside /trunk/java/modules/rampart-integration/src/test/java/org/apache/rahas Regards, Dimuthu On 5/17/07, Ted Jones [EMAIL PROTECTED] wrote: I'm just digging into SAML, so please bare with me. There does not seem to be a lot of documentation or examples for adding SAML assertions to a WS-Security header in Rampart, maybe someone could point me to some? :-) Does Rampart/OpenSAML integrate with an existing SAML server(s), provide it's own, or neither? Is it possible for a web service client just to accept a SAML token and add it to the WS-Security header? That is really what I am looking for. TIA, Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] How do I deploy my webservice in a separate war file other than axis2.war?
Raghu, I've seen that one before. Believe it or not that is due to *some* missing class or classes. To resolve it make sure all the Axis2 distribution jars are in your war's lib and make sure they are all from the same release. You likely won't need them all but you can whittle them down after you get everything working. Regards, Ted From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 3:23 PM To: axis-user@ws.apache.org Cc: [EMAIL PROTECTED] Subject: RE: [Axis2] How do I deploy my webservice in a separate war file other than axis2.war? Hi Michael, Your solution kind of worked partially, but deployment failed. I received the following exception. Please let me know if you know the solution. For this java.lang.ExceptionInInitializerError at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:555) at org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilde r.java:93) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigB uilder.java:76) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(D eploymentEngine.java:640) at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxis Configurator.java:136) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle t.java:486) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:406) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav a:1091) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.j ava:3880) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4141 ) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja va:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:804) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:693) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:31 0) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:680) at org.apache.catalina.startup.Catalina.start(Catalina.java:536) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: java.lang.IllegalStateException: No valid ObjectCreator found. at org.apache.axiom.om.util.StAXUtils$Pool.init(StAXUtils.java:44) at org.apache.axiom.om.util.StAXUtils.clinit(StAXUtils.java:68) ... 33 more Thanks Raghu -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 12:35 PM To: axis-user@ws.apache.org Subject: RE: [Axis2] How do I deploy my webservice in a separate war file other than axis2.war? Hi, I've got a similar setup working. One trick is this: your aar file should only have services.xml, no class or library files. The service class (or classes) should be in WEB-INF/classes. The contents of my aar are just: META-INF/ META-INF/MANIFEST.MF lib/ META-INF/Authenticate.wsdl META-INF/services.xml I've attached a dump of the contents of my war file so you can see how I put it together. I've also got a webwork application bundled up with it (an admin application to maintain a database), and it's using Spring and Hibernate (both for the web app and the web service), and so far it's working. Good luck, Michael -Original Message- From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 3:11 PM To: axis-user@ws.apache.org Subject: [Axis2] How do I deploy my webservice in a separate war file other than axis2.war? Hi, I've used Axis2 and
[Axis2] SAML/Rampart Question
I'm just digging into SAML, so please bare with me. There does not seem to be a lot of documentation or examples for adding SAML assertions to a WS-Security header in Rampart, maybe someone could point me to some? :-) Does Rampart/OpenSAML integrate with an existing SAML server(s), provide it's own, or neither? Is it possible for a web service client just to accept a SAML token and add it to the WS-Security header? That is really what I am looking for. TIA, Ted
RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
Hi Paul, Any luck with your machine (or my issue)? ;-) Thanks for your help, Ted -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 11:24 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Ted My machine has gone haywire and I'm just rebuilding it (well actually just backing everything up before rebuilding it). I'll debug this as soon as I get running. Paul On 5/11/07, Ted Jones [EMAIL PROTECTED] wrote: In case you have problems accessing the files via these links, you can get to them here: http://jonested.tripod.com/ and use 'Save As to download them. Thanks, Ted From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 7:17 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Martin, Paul, Amila, anybody I missed, Here are links to the service aar, wsdl, test client, and the client and server config files. Hopefully there is some glaring mistake I have made. ;-) http://jonested.tripod.com/echoClient.java http://jonested.tripod.com/client_axis2.xml http://jonested.tripod.com/server_axis2.xml http://jonested.tripod.com/echo.wsdl http://jonested.tripod.com/echo.aar I am running the client and server on the same machine. For what it's worth, in debug I am seeing multiple threads continually being spawned for the client's http simple server (port 6062). Please let me know if you need more from me. Thanks, Ted From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 9:37 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Thanks Amila. I appreciate the input. I am using Dual channel since it appeared to be required per this thread: http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/% [EMAIL PROTECTED] Is this the case? I am using Sandesha2 1.1 with Axis2 1.1.1. I have verified your points outlined below. Everything appears correct. Martin - I will put together a reproducible test case and post ASAP. Thanks for your assistance. Ted From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 12:25 AM To: axis-user@ws.apache.org; Martin Gainty Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Are you using the Dual chanel mode or single chanel? if you set the setUseSeparateListener your request comes in a different http chanel than you send the request. Otherwise it comes in the same chanel. In the dual chanel model, What happens is your client starts a simple http server on your machine and set the ReplyTo addressing header to point to the stated server. So you have to make sure these things. 1. you must have engage the Addressing. (otherwise server won't be able to find the reply location) 2. client uses the port and the host name you have specified in the axis2.xml to start its simple http server and set this address to replyTo filed. So you have to use two seperate axis2.xml files for client and the server with different port numbers if you run them both in one machine. 3. if your server is in out side your firewall, the host name you specify in the client axis2.xml should be able to access from the out side the firewall. On 5/10/07, Martin Gainty [EMAIL PROTECTED] wrote: Good Evening if you publish your wsdl we can run the client code 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: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, May 09, 2007 7:10 PM Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning So, I'm guessing that the message is never reaching the server. Which may explain why there is no logging? I can see in debug where the Sandesha2 logic is hit and the message is sent but I never see any sequences or other message traffic and my client is left polling forever waiting for the callback to complete. Any other thoughts on what might be happening here or where else I can look? Thanks, Ted -Original Message- From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 09, 2007 10:27 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Thanks for all the responses. This is a great mailing list. I am not seeing any messages in TCPMON or in the logs. :-( Question: How can you configure TCPMON to capture messages
RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
Martin, Paul, Amila, anybody I missed, Here are links to the service aar, wsdl, test client, and the client and server config files. Hopefully there is some glaring mistake I have made. ;-) http://jonested.tripod.com/echoClient.java http://jonested.tripod.com/client_axis2.xml http://jonested.tripod.com/server_axis2.xml http://jonested.tripod.com/echo.wsdl http://jonested.tripod.com/echo.aar I am running the client and server on the same machine. For what it's worth, in debug I am seeing multiple threads continually being spawned for the client's http simple server (port 6062). Please let me know if you need more from me. Thanks, Ted From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 9:37 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Thanks Amila. I appreciate the input. I am using Dual channel since it appeared to be required per this thread: http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/%3C [EMAIL PROTECTED] Is this the case? I am using Sandesha2 1.1 with Axis2 1.1.1. I have verified your points outlined below. Everything appears correct. Martin - I will put together a reproducible test case and post ASAP. Thanks for your assistance. Ted From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 12:25 AM To: axis-user@ws.apache.org; Martin Gainty Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Are you using the Dual chanel mode or single chanel? if you set the setUseSeparateListener your request comes in a different http chanel than you send the request. Otherwise it comes in the same chanel. In the dual chanel model, What happens is your client starts a simple http server on your machine and set the ReplyTo addressing header to point to the stated server. So you have to make sure these things. 1. you must have engage the Addressing. (otherwise server won't be able to find the reply location) 2. client uses the port and the host name you have specified in the axis2.xml to start its simple http server and set this address to replyTo filed. So you have to use two seperate axis2.xml files for client and the server with different port numbers if you run them both in one machine. 3. if your server is in out side your firewall, the host name you specify in the client axis2.xml should be able to access from the out side the firewall. On 5/10/07, Martin Gainty [EMAIL PROTECTED] wrote: Good Evening if you publish your wsdl we can run the client code 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: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, May 09, 2007 7:10 PM Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning So, I'm guessing that the message is never reaching the server. Which may explain why there is no logging? I can see in debug where the Sandesha2 logic is hit and the message is sent but I never see any sequences or other message traffic and my client is left polling forever waiting for the callback to complete. Any other thoughts on what might be happening here or where else I can look? Thanks, Ted -Original Message- From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 09, 2007 10:27 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Thanks for all the responses. This is a great mailing list. I am not seeing any messages in TCPMON or in the logs. :-( Question: How can you configure TCPMON to capture messages sent to SimpleHTTPServer? I get a port bind exception. Also, I cannot seems to get logging working with Sandesha2. If anyone has it working, I would really appreciate a peek at their log4j.properties. Thanks! Ted -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 11:12 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Ted Jones wrote: I am using Sandesha2 with an asynch Axis2 client. Using the example that comes with Sandesha2
RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
Thanks Amila. I appreciate the input. I am using Dual channel since it appeared to be required per this thread: http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/%3C [EMAIL PROTECTED] Is this the case? I am using Sandesha2 1.1 with Axis2 1.1.1. I have verified your points outlined below. Everything appears correct. Martin - I will put together a reproducible test case and post ASAP. Thanks for your assistance. Ted From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 12:25 AM To: axis-user@ws.apache.org; Martin Gainty Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Are you using the Dual chanel mode or single chanel? if you set the setUseSeparateListener your request comes in a different http chanel than you send the request. Otherwise it comes in the same chanel. In the dual chanel model, What happens is your client starts a simple http server on your machine and set the ReplyTo addressing header to point to the stated server. So you have to make sure these things. 1. you must have engage the Addressing. (otherwise server won't be able to find the reply location) 2. client uses the port and the host name you have specified in the axis2.xml to start its simple http server and set this address to replyTo filed. So you have to use two seperate axis2.xml files for client and the server with different port numbers if you run them both in one machine. 3. if your server is in out side your firewall, the host name you specify in the client axis2.xml should be able to access from the out side the firewall. On 5/10/07, Martin Gainty [EMAIL PROTECTED] wrote: Good Evening if you publish your wsdl we can run the client code 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: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, May 09, 2007 7:10 PM Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning So, I'm guessing that the message is never reaching the server. Which may explain why there is no logging? I can see in debug where the Sandesha2 logic is hit and the message is sent but I never see any sequences or other message traffic and my client is left polling forever waiting for the callback to complete. Any other thoughts on what might be happening here or where else I can look? Thanks, Ted -Original Message- From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 09, 2007 10:27 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Thanks for all the responses. This is a great mailing list. I am not seeing any messages in TCPMON or in the logs. :-( Question: How can you configure TCPMON to capture messages sent to SimpleHTTPServer? I get a port bind exception. Also, I cannot seems to get logging working with Sandesha2. If anyone has it working, I would really appreciate a peek at their log4j.properties. Thanks! Ted -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 11:12 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Ted Jones wrote: I am using Sandesha2 with an asynch Axis2 client. Using the example that comes with Sandesha2 (the asynch echo client), the onComplete() method of my callback is never hit. It appears the response is not returning. Any ideas? Did you try capturing message sequences with TCPMON and chek the message sequence? Also, have a look into the server and client logs. Samisa... - 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] WS-RM and Axis2 Asynch Client not Returning
That's good to know. Thanks Paul. -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 10:00 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Ted FYI The latest Sandesha builds (and the upcoming 1.2 release) support RM 1.0 without a separate listener. There has been a lot of work to support this. Paul On 5/10/07, Ted Jones [EMAIL PROTECTED] wrote: Thanks Amila. I appreciate the input. I am using Dual channel since it appeared to be required per this thread: http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/% [EMAIL PROTECTED] Is this the case? I am using Sandesha2 1.1 with Axis2 1.1.1. I have verified your points outlined below. Everything appears correct. Martin - I will put together a reproducible test case and post ASAP. Thanks for your assistance. Ted From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 12:25 AM To: axis-user@ws.apache.org; Martin Gainty Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Are you using the Dual chanel mode or single chanel? if you set the setUseSeparateListener your request comes in a different http chanel than you send the request. Otherwise it comes in the same chanel. In the dual chanel model, What happens is your client starts a simple http server on your machine and set the ReplyTo addressing header to point to the stated server. So you have to make sure these things. 1. you must have engage the Addressing. (otherwise server won't be able to find the reply location) 2. client uses the port and the host name you have specified in the axis2.xml to start its simple http server and set this address to replyTo filed. So you have to use two seperate axis2.xml files for client and the server with different port numbers if you run them both in one machine. 3. if your server is in out side your firewall, the host name you specify in the client axis2.xml should be able to access from the out side the firewall. On 5/10/07, Martin Gainty [EMAIL PROTECTED] wrote: Good Evening if you publish your wsdl we can run the client code 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: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, May 09, 2007 7:10 PM Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning So, I'm guessing that the message is never reaching the server. Which may explain why there is no logging? I can see in debug where the Sandesha2 logic is hit and the message is sent but I never see any sequences or other message traffic and my client is left polling forever waiting for the callback to complete. Any other thoughts on what might be happening here or where else I can look? Thanks, Ted -Original Message- From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 09, 2007 10:27 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Thanks for all the responses. This is a great mailing list. I am not seeing any messages in TCPMON or in the logs. :-( Question: How can you configure TCPMON to capture messages sent to SimpleHTTPServer? I get a port bind exception. Also, I cannot seems to get logging working with Sandesha2. If anyone has it working, I would really appreciate a peek at their log4j.properties. Thanks! Ted -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 11:12 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Ted Jones wrote: I am using Sandesha2 with an asynch Axis2 client. Using the example that comes with Sandesha2 (the asynch echo client), the onComplete() method of my callback is never hit. It appears the response is not returning. Any ideas? Did you try capturing message sequences with TCPMON and chek the message sequence? Also, have a look into the server and client logs. Samisa... - 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] WS-RM and Axis2 Asynch Client not Returning
Thanks for all the responses. This is a great mailing list. I am not seeing any messages in TCPMON or in the logs. :-( Question: How can you configure TCPMON to capture messages sent to SimpleHTTPServer? I get a port bind exception. Also, I cannot seems to get logging working with Sandesha2. If anyone has it working, I would really appreciate a peek at their log4j.properties. Thanks! Ted -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 11:12 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Ted Jones wrote: I am using Sandesha2 with an asynch Axis2 client. Using the example that comes with Sandesha2 (the asynch echo client), the onComplete() method of my callback is never hit. It appears the response is not returning. Any ideas? Did you try capturing message sequences with TCPMON and chek the message sequence? Also, have a look into the server and client logs. Samisa... - 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] WS-RM and Axis2 Asynch Client not Returning
So, I'm guessing that the message is never reaching the server. Which may explain why there is no logging? I can see in debug where the Sandesha2 logic is hit and the message is sent but I never see any sequences or other message traffic and my client is left polling forever waiting for the callback to complete. Any other thoughts on what might be happening here or where else I can look? Thanks, Ted -Original Message- From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 09, 2007 10:27 AM To: axis-user@ws.apache.org Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning Thanks for all the responses. This is a great mailing list. I am not seeing any messages in TCPMON or in the logs. :-( Question: How can you configure TCPMON to capture messages sent to SimpleHTTPServer? I get a port bind exception. Also, I cannot seems to get logging working with Sandesha2. If anyone has it working, I would really appreciate a peek at their log4j.properties. Thanks! Ted -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 11:12 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Ted Jones wrote: I am using Sandesha2 with an asynch Axis2 client. Using the example that comes with Sandesha2 (the asynch echo client), the onComplete() method of my callback is never hit. It appears the response is not returning. Any ideas? Did you try capturing message sequences with TCPMON and chek the message sequence? Also, have a look into the server and client logs. Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] MessageReceiver is Null in Axis2 Operation using WS-RM
Hi Chamikara,
Upon further review, I don't believe this is a Sandesha2 issue. The
operation is generated without a CallbackReceiver value set in the ADB
generated stub. If I set a default CallbackReceiver in my client code,
everything works fine. Maybe the operation should have a default
instance of CallbackReceiver set on it OR the ADB generated stub code
should set one on the operation when it is created?
Thanks,
Ted
From: Chamikara Jayalath [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 01, 2007 10:51 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] MessageReceiver is Null in Axis2 Operation using
WS-RM
Hi Ted,
Could u please add JIRA (in Sandesha2) and attach whatever the files
necessary to reproduce the error. I just did a test with
Axis21.1.1/Sandesha2 1.1 and it ran without trouble.
Chamikara
On 5/2/07, Ted Jones [EMAIL PROTECTED] wrote:
I am using Sandesha2 1.1 with Axis2 1.1.1 and am running into an
error where the MessageReceiver is null for the Axis operation and is
causing a NPE. The following code in the OutInAxisOperation class is
where the exception occurs:
if (options.isUseSeparateListener()) {
CallbackReceiver callbackReceiver =
(CallbackReceiver) axisOp
.getMessageReceiver();
callbackReceiver.addCallback(mc.getMessageID(),
callback);
I have the message receivers defined in my client axis2.xml and
server axis.xml. I even have the message receivers defined in the
service.xml for good measure.
I have set the following options in the Axis2 client:
clientOptions.setTransportInProtocol(org.apache.axis2.Constants.TRANSPOR
T_HTTP);
clientOptions.setProperty(AddressingConstants.WS_ADDRESSING_VERSION,org.
apache.axis2.addressing.AddressingConstants.Final.WSA_NAMESPACE );
clientOptions.setUseSeparateListener(true);
The client/service works without Sandesha2 since I am not using
a separate listener in that case.
Is there anything else I need to add the the Axis2.xml or client
code to get the receiver set on the operation?
TIA,
Ted
--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs
[Axis2] MessageReceiver is Null in Axis2 Operation using WS-RM
I am using Sandesha2 1.1 with Axis2 1.1.1 and am running into an error
where the MessageReceiver is null for the Axis operation and is causing
a NPE. The following code in the OutInAxisOperation class is where the
exception occurs:
if (options.isUseSeparateListener()) {
CallbackReceiver callbackReceiver = (CallbackReceiver)
axisOp
.getMessageReceiver();
callbackReceiver.addCallback(mc.getMessageID(), callback);
I have the message receivers defined in my client axis2.xml and server
axis.xml. I even have the message receivers defined in the service.xml
for good measure.
I have set the following options in the Axis2 client:
clientOptions.setTransportInProtocol(org.apache.axis2.Constants.TRANSPOR
T_HTTP);
clientOptions.setProperty(AddressingConstants.WS_ADDRESSING_VERSION,org.
apache.axis2.addressing.AddressingConstants.Final.WSA_NAMESPACE);
clientOptions.setUseSeparateListener(true);
The client/service works without Sandesha2 since I am not using a
separate listener in that case.
Is there anything else I need to add the the Axis2.xml or client code to
get the receiver set on the operation?
TIA,
Ted
[Axis2] WS-Security Headers not Generated in SOAP Request
I have a webapp that has an Axis2 client/stub in it and is calling a web service that is using Rampart. When I create the ConfigurationContext using ConfigurationContextFactory.createConfigurationContextFromFileSystem(), all works as expected. However, when I create the ConfigurationContext using ConfigurationContextFactory.createConfigurationContextFromURIs(), the WS-Security headers are not added to the SOAP Request and I get an org.apache.axis2.AxisFault: WSDoAllReceiver: Incoming message does not contain required Security header message. I can see in debug that the modules are engaged and loaded in the context. Are there any known issues regarding creating a ConfigurationContext via URIs that might explain this behavior? Thanks, Ted
RE: [Axix2] java.lang.RuntimeException: Unexpected subelement value
Thanks Amila. I'll add that to the JIRA.
Ted
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 03, 2007 9:20 AM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
On 3/31/07, Ted Jones [EMAIL PROTECTED] wrote:
That is how Axis2 generated the schema in my wsdl. I have a POJO
(Cell)
which has a field (Value) of type Object. Here is the schema
generated
by Axis2 that seems to be causing the issue:
xs:element name=Cell type=ax21:Cell /
xs:complexType name=Cell
xs:sequence
xs:element name=value type=xs:anyType /
/xs:sequence
/xs:complexType
see your wsdl and its schema declaration
it has
elementFormDefault=qualified
targetNamespace=http://helper.mywebservice.soap.widget.com/xsd
so the value element should be in the
http://helper.mywebservice.soap.widget.com/xsd
namespace.
this means your response is invalid according to the wsdl file.
This cell element is used in the response and the stub tries to
compare
it's namespace (http://helper.mywebservice.soap.widget.com/xsd)
to
create a QName to compare to the value element which uses the
http://www.w3.org/2001/XMLSchema; namespace and causes the
Unexpected
subelement value exception.
Here is my POJO:
public class Cell {
protected java.lang.Object value;
public java.lang.Object getValue() {
return value;
}
public void setValue(java.lang.Object value) {
this.value = value;
}
}
I have also attached my full wsdl.
Thanks for your help,
Ted
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] ]
Sent: Saturday, March 31, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected
subelement
value
Why do you have an element in your message in the
http://www.w3.org/2001/XMLSchema; namespace? Does your message
include
a schema? If so, have you defined a xs:schema element as an
element
within your message structure? Or did you perhaps specify
http://www.w3.org/2001/XMLSchema; as the targetNamespace for
your
schema?
An example would help us identify the problem.
Anne
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for your response Amila. The SOAP response looks
correct when
validating against the wsdl. The issue seems to be in the
generated
stub code when a check is done comparing the QName of the
element. The
WSDL targetnamespace
http://helper.webservice.soap.test.com/xsd
is used to compare against an element that has
http://www.w3.org/2001/XMLSchema as it's namespace so they
don't match
up and consequently the java.lang.RuntimeException:
Unexpected
subelement value exception is thrown.
Here is the line I am referring to:
if (reader.isStartElement() new
javax.xml.namespace.QName(http://helper.mywebservice.soap.widget.com/xs
d
,value).equals(reader.getName())){
Is this a limitation of ADB, an error in the stub generation,
an error
in the wsdl generation, or something I can control in my stub
generation?
Thanks for any insight you can offer.
Ted
From: Amila Suriarachchi [mailto: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ]
Sent: Thursday, March 29, 2007 11:48 PM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected
subelement
value
we have discussed this senario in many times.
First thing you have to do is to check the received soap
message using
the tcp mon.
then validate the that received response message with the
generated
wsdl (wsdl you used to generate the code)
Amila.
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
I am receiving the following exception in my ADB generated
stub
while
processing my soap response: java.lang.RuntimeException:
Unexpected
subelement value
The WSDL used to generate my stub is auto generated (Axis2
1.1.1).
Any ideas?
TIA,
Ted
RE: [Axix2] java.lang.RuntimeException: Unexpected subelement value
Logged: https://issues.apache.org/jira/browse/AXIS2-2464
I added a link to this thread as well (via Nabble):
http://www.nabble.com/-Axix2--java.lang.RuntimeException:-Unexpected-sub
element-value-t3489089.html
Thanks,
Ted
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 03, 2007 9:42 AM
To: axis-user@ws.apache.org
Subject: RE: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
Thanks Amila. I'll add that to the JIRA.
Ted
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 03, 2007 9:20 AM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
On 3/31/07, Ted Jones [EMAIL PROTECTED] wrote:
That is how Axis2 generated the schema in my wsdl. I have a POJO
(Cell)
which has a field (Value) of type Object. Here is the schema
generated
by Axis2 that seems to be causing the issue:
xs:element name=Cell type=ax21:Cell /
xs:complexType name=Cell
xs:sequence
xs:element name=value type=xs:anyType /
/xs:sequence
/xs:complexType
see your wsdl and its schema declaration
it has
elementFormDefault=qualified
targetNamespace=http://helper.mywebservice.soap.widget.com/xsd
so the value element should be in the
http://helper.mywebservice.soap.widget.com/xsd
namespace.
this means your response is invalid according to the wsdl file.
This cell element is used in the response and the stub tries to
compare
it's namespace (http://helper.mywebservice.soap.widget.com/xsd)
to
create a QName to compare to the value element which uses the
http://www.w3.org/2001/XMLSchema; namespace and causes the
Unexpected
subelement value exception.
Here is my POJO:
public class Cell {
protected java.lang.Object value;
public java.lang.Object getValue() {
return value;
}
public void setValue(java.lang.Object value) {
this.value = value;
}
}
I have also attached my full wsdl.
Thanks for your help,
Ted
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] ]
Sent: Saturday, March 31, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected
subelement
value
Why do you have an element in your message in the
http://www.w3.org/2001/XMLSchema; namespace? Does your message
include
a schema? If so, have you defined a xs:schema element as an
element
within your message structure? Or did you perhaps specify
http://www.w3.org/2001/XMLSchema; as the targetNamespace for
your
schema?
An example would help us identify the problem.
Anne
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for your response Amila. The SOAP response looks
correct when
validating against the wsdl. The issue seems to be in the
generated
stub code when a check is done comparing the QName of the
element. The
WSDL targetnamespace
http://helper.webservice.soap.test.com/xsd
is used to compare against an element that has
http://www.w3.org/2001/XMLSchema as it's namespace so they
don't match
up and consequently the java.lang.RuntimeException:
Unexpected
subelement value exception is thrown.
Here is the line I am referring to:
if (reader.isStartElement() new
javax.xml.namespace.QName(http://helper.mywebservice.soap.widget.com/xs
d
,value).equals(reader.getName())){
Is this a limitation of ADB, an error in the stub generation,
an error
in the wsdl generation, or something I can control in my stub
generation?
Thanks for any insight you can offer.
Ted
From: Amila Suriarachchi [mailto: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ]
Sent: Thursday, March 29, 2007 11:48 PM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected
subelement
value
we have discussed this senario in many times.
First thing you have to do is to check the received soap
message using
the tcp mon.
then validate the that received response message with the
generated
wsdl (wsdl you used to generate the code)
Amila.
On 3/30/07
RE: [Axix2] java.lang.RuntimeException: Unexpected subelement value
More info...
The cell element is returned as part of an array. Not sure if this makes
any difference or not.
Thanks,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 31, 2007 11:56 AM
To: axis-user@ws.apache.org
Subject: RE: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
That is how Axis2 generated the schema in my wsdl. I have a POJO (Cell)
which has a field (Value) of type Object. Here is the schema generated
by Axis2 that seems to be causing the issue:
xs:element name=Cell type=ax21:Cell / xs:complexType name=Cell
xs:sequence xs:element name=value type=xs:anyType /
/xs:sequence /xs:complexType
This cell element is used in the response and the stub tries to compare
it's namespace (http://helper.mywebservice.soap.widget.com/xsd) to
create a QName to compare to the value element which uses the
http://www.w3.org/2001/XMLSchema; namespace and causes the Unexpected
subelement value exception.
Here is my POJO:
public class Cell {
protected java.lang.Object value;
public java.lang.Object getValue() {
return value;
}
public void setValue(java.lang.Object value) {
this.value = value;
}
}
I have also attached my full wsdl.
Thanks for your help,
Ted
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 31, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
Why do you have an element in your message in the
http://www.w3.org/2001/XMLSchema; namespace? Does your message include
a schema? If so, have you defined a xs:schema element as an element
within your message structure? Or did you perhaps specify
http://www.w3.org/2001/XMLSchema; as the targetNamespace for your
schema?
An example would help us identify the problem.
Anne
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for your response Amila. The SOAP response looks correct when
validating against the wsdl. The issue seems to be in the generated
stub code when a check is done comparing the QName of the element. The
WSDL targetnamespace http://helper.webservice.soap.test.com/xsd
is used to compare against an element that has
http://www.w3.org/2001/XMLSchema as it's namespace so they don't match
up and consequently the java.lang.RuntimeException: Unexpected
subelement value exception is thrown.
Here is the line I am referring to:
if (reader.isStartElement() new
javax.xml.namespace.QName(http://helper.mywebservice.soap.widget.com/xs
d
,value).equals(reader.getName())){
Is this a limitation of ADB, an error in the stub generation, an error
in the wsdl generation, or something I can control in my stub
generation?
Thanks for any insight you can offer.
Ted
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 11:48 PM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
we have discussed this senario in many times.
First thing you have to do is to check the received soap message using
the tcp mon.
then validate the that received response message with the generated
wsdl (wsdl you used to generate the code)
Amila.
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
I am receiving the following exception in my ADB generated stub
while
processing my soap response: java.lang.RuntimeException: Unexpected
subelement value
The WSDL used to generate my stub is auto generated (Axis2 1.1.1).
Any ideas?
TIA,
Ted
--
Amila Suriarachchi,
WSO2 Inc.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] ClassNotFoundException when executing axis2server.bat on W2K - %AXIS2_CLASS_PATH% cut off ?
You could extract all the jars and create a single Axis2.jar. An ANT script would be the way to go if you chose this route. Good luck, Ted -Original Message- From: Heiko Korndorf [mailto:[EMAIL PROTECTED] Sent: Monday, April 02, 2007 10:09 AM To: axis-user@ws.apache.org Subject: [Axis2] ClassNotFoundException when executing axis2server.bat on W2K - %AXIS2_CLASS_PATH% cut off ? Hi, I have downloaded Axis2 1.1.1 (standard binary distribution) and I can start the Axis2 Standalone Server (axis2server.bat) without a problem on my WinXP machine. When I execute the same procedure on my Win2000 computer, startup of axis2server.bat fails with a ClassNotFoundException, though. The reason seems to be that the %AXIS2_CLASS_PATH% only contains the last 7 jar files in %AXIS2_HOME%\lib, instead of all of the 43 jar files in the lib folder. The FOR loop in axis2server.bat which concatenates all the lib/*.jar files into %AXIS2_HOME% seems to work fine, but I suspect that under Win2000 there is a length constraint for windows environment variables which causes the rest of the string to be cut off. Any hints on how to resolve that issue ? Thanks Best regards, Heiko Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 - 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: [Axix2] java.lang.RuntimeException: Unexpected subelement value
Further analysis of the soap response leads me to believe the array of
cells may be the culprit here. Here is a snippet from the response that
shows an array of cells:
rows xmlns=http://helper.mywebservice.soap.widget.com/xsd;
cells
xs:value xmlns:xs=http://www.w3.org/2001/XMLSchema;value1/xs:value
/cells
cells
xs:value xmlns:xs=http://www.w3.org/2001/XMLSchema;value2/xs:value
/cells
cells
xs:value xmlns:xs=http://www.w3.org/2001/XMLSchema;value3/xs:value
/cells
cellsxs:value
xmlns:xs=http://www.w3.org/2001/XMLSchema;value4/xs:value/cells
/rows
The elements rows and cells share the same namespace and the stub
handles them just fine. The value element uses the XMLSchema namespace
though and the stub bombs out since it is expecting the parent namespace
from the rows element. This seems like a valid schema though so that
would place the error in the generated stub code. Right?
Thanks,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 3:05 PM
To: axis-user@ws.apache.org
Subject: RE: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
More info...
The cell element is returned as part of an array. Not sure if this makes
any difference or not.
Thanks,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 31, 2007 11:56 AM
To: axis-user@ws.apache.org
Subject: RE: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
That is how Axis2 generated the schema in my wsdl. I have a POJO (Cell)
which has a field (Value) of type Object. Here is the schema generated
by Axis2 that seems to be causing the issue:
xs:element name=Cell type=ax21:Cell / xs:complexType name=Cell
xs:sequence xs:element name=value type=xs:anyType /
/xs:sequence /xs:complexType
This cell element is used in the response and the stub tries to compare
it's namespace (http://helper.mywebservice.soap.widget.com/xsd) to
create a QName to compare to the value element which uses the
http://www.w3.org/2001/XMLSchema; namespace and causes the Unexpected
subelement value exception.
Here is my POJO:
public class Cell {
protected java.lang.Object value;
public java.lang.Object getValue() {
return value;
}
public void setValue(java.lang.Object value) {
this.value = value;
}
}
I have also attached my full wsdl.
Thanks for your help,
Ted
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 31, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
Why do you have an element in your message in the
http://www.w3.org/2001/XMLSchema; namespace? Does your message include
a schema? If so, have you defined a xs:schema element as an element
within your message structure? Or did you perhaps specify
http://www.w3.org/2001/XMLSchema; as the targetNamespace for your
schema?
An example would help us identify the problem.
Anne
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for your response Amila. The SOAP response looks correct when
validating against the wsdl. The issue seems to be in the generated
stub code when a check is done comparing the QName of the element. The
WSDL targetnamespace http://helper.webservice.soap.test.com/xsd
is used to compare against an element that has
http://www.w3.org/2001/XMLSchema as it's namespace so they don't match
up and consequently the java.lang.RuntimeException: Unexpected
subelement value exception is thrown.
Here is the line I am referring to:
if (reader.isStartElement() new
javax.xml.namespace.QName(http://helper.mywebservice.soap.widget.com/xs
d
,value).equals(reader.getName())){
Is this a limitation of ADB, an error in the stub generation, an error
in the wsdl generation, or something I can control in my stub
generation?
Thanks for any insight you can offer.
Ted
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 11:48 PM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
we have discussed this senario in many times.
First thing you have to do is to check the received soap message using
the tcp mon.
then validate the that received response message with the generated
wsdl (wsdl you used to generate the code)
Amila.
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
I am receiving the following exception in my ADB generated stub
while
processing my soap response: java.lang.RuntimeException: Unexpected
subelement value
The WSDL used to generate my stub is auto generated (Axis2 1.1.1).
Any ideas?
TIA,
Ted
--
Amila Suriarachchi,
WSO2 Inc.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
RE: [Axix2] java.lang.RuntimeException: Unexpected subelement value
Thanks for the feedback Anne. It is much appreciated. I'm using the ADB. I'll
log a JIRA on it and switch to a schema first approach.
Thanks again,
Ted
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Mon 4/2/2007 7:01 PM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement value
But why is Axis2 putting the value element in the xsd namespace.
Your schema specifies that it should be in the
http://helper.mywebservice.soap.widget.com/xsd; namespace. Which
databinding are you using? Can you give us more information on how the
message is being generated? You might want to file a JIRA on this one.
Meanwhile, if you can avoid it, you should not use an element of type
xs:anyType in your schema. Your first mistake was in letting Axis2
generate your schema. (it's a common mistake, though). When designing
interoperable web services, you should define your schema first, then
map the schema to your code.
But let's assume for the moment that you avoid my advice and continue
down the treacherous code-first development approach...
If you have an interface that includes an undefined Object, Axis2 has
no way of deciphering the expected type, so it defines it as
xs:anyType. You should do your best to define the structures that you
plan to expose through the interface. As a general rule, never expose
Java Collections. Only expose simple types, beans, and arrays. As long
as you follow these basic rules, things typically work reasonably
well.
Anne
On 4/2/07, Ted Jones [EMAIL PROTECTED] wrote:
Further analysis of the soap response leads me to believe the array of
cells may be the culprit here. Here is a snippet from the response that
shows an array of cells:
rows xmlns=http://helper.mywebservice.soap.widget.com/xsd;
cells
xs:value xmlns:xs=http://www.w3.org/2001/XMLSchema;value1/xs:value
/cells
cells
xs:value xmlns:xs=http://www.w3.org/2001/XMLSchema;value2/xs:value
/cells
cells
xs:value xmlns:xs=http://www.w3.org/2001/XMLSchema;value3/xs:value
/cells
cellsxs:value
xmlns:xs=http://www.w3.org/2001/XMLSchema;value4/xs:value/cells
/rows
The elements rows and cells share the same namespace and the stub
handles them just fine. The value element uses the XMLSchema namespace
though and the stub bombs out since it is expecting the parent namespace
from the rows element. This seems like a valid schema though so that
would place the error in the generated stub code. Right?
Thanks,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 3:05 PM
To: axis-user@ws.apache.org
Subject: RE: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
More info...
The cell element is returned as part of an array. Not sure if this makes
any difference or not.
Thanks,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 31, 2007 11:56 AM
To: axis-user@ws.apache.org
Subject: RE: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
That is how Axis2 generated the schema in my wsdl. I have a POJO (Cell)
which has a field (Value) of type Object. Here is the schema generated
by Axis2 that seems to be causing the issue:
xs:element name=Cell type=ax21:Cell / xs:complexType name=Cell
xs:sequence xs:element name=value type=xs:anyType /
/xs:sequence /xs:complexType
This cell element is used in the response and the stub tries to compare
it's namespace (http://helper.mywebservice.soap.widget.com/xsd) to
create a QName to compare to the value element which uses the
http://www.w3.org/2001/XMLSchema; namespace and causes the Unexpected
subelement value exception.
Here is my POJO:
public class Cell {
protected java.lang.Object value;
public java.lang.Object getValue() {
return value;
}
public void setValue(java.lang.Object value) {
this.value = value;
}
}
I have also attached my full wsdl.
Thanks for your help,
Ted
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 31, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
Why do you have an element in your message in the
http://www.w3.org/2001/XMLSchema; namespace? Does your message include
a schema? If so, have you defined a xs:schema element as an element
within your message structure? Or did you perhaps specify
http://www.w3.org/2001/XMLSchema; as the targetNamespace for your
schema?
An example would help us identify the problem.
Anne
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for your response Amila. The SOAP response looks correct when
validating against the wsdl. The issue seems to be in the generated
stub code when a check is done comparing the QName of the element. The
WSDL targetnamespace http
RE: [Axix2] java.lang.RuntimeException: Unexpected subelement value
That is how Axis2 generated the schema in my wsdl. I have a POJO (Cell)
which has a field (Value) of type Object. Here is the schema generated
by Axis2 that seems to be causing the issue:
xs:element name=Cell type=ax21:Cell /
xs:complexType name=Cell
xs:sequence
xs:element name=value type=xs:anyType /
/xs:sequence
/xs:complexType
This cell element is used in the response and the stub tries to compare
it's namespace (http://helper.mywebservice.soap.widget.com/xsd) to
create a QName to compare to the value element which uses the
http://www.w3.org/2001/XMLSchema; namespace and causes the Unexpected
subelement value exception.
Here is my POJO:
public class Cell {
protected java.lang.Object value;
public java.lang.Object getValue() {
return value;
}
public void setValue(java.lang.Object value) {
this.value = value;
}
}
I have also attached my full wsdl.
Thanks for your help,
Ted
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 31, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
Why do you have an element in your message in the
http://www.w3.org/2001/XMLSchema; namespace? Does your message include
a schema? If so, have you defined a xs:schema element as an element
within your message structure? Or did you perhaps specify
http://www.w3.org/2001/XMLSchema; as the targetNamespace for your
schema?
An example would help us identify the problem.
Anne
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for your response Amila. The SOAP response looks correct when
validating against the wsdl. The issue seems to be in the generated
stub code when a check is done comparing the QName of the element. The
WSDL targetnamespace http://helper.webservice.soap.test.com/xsd
is used to compare against an element that has
http://www.w3.org/2001/XMLSchema as it's namespace so they don't match
up and consequently the java.lang.RuntimeException: Unexpected
subelement value exception is thrown.
Here is the line I am referring to:
if (reader.isStartElement() new
javax.xml.namespace.QName(http://helper.mywebservice.soap.widget.com/xs
d
,value).equals(reader.getName())){
Is this a limitation of ADB, an error in the stub generation, an error
in the wsdl generation, or something I can control in my stub
generation?
Thanks for any insight you can offer.
Ted
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 11:48 PM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
we have discussed this senario in many times.
First thing you have to do is to check the received soap message using
the tcp mon.
then validate the that received response message with the generated
wsdl (wsdl you used to generate the code)
Amila.
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
I am receiving the following exception in my ADB generated stub
while
processing my soap response: java.lang.RuntimeException: Unexpected
subelement value
The WSDL used to generate my stub is auto generated (Axis2 1.1.1).
Any ideas?
TIA,
Ted
--
Amila Suriarachchi,
WSO2 Inc.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
MyWebService.wsdl
Description: MyWebService.wsdl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axix2] java.lang.RuntimeException: Unexpected subelement value
Thanks for your response Amila. The SOAP response looks correct when
validating against the wsdl. The issue seems to be in the generated stub
code when a check is done comparing the QName of the element. The WSDL
targetnamespace http://helper.webservice.soap.test.com/xsd
http://helper.webservice.soap.test.com/xsd is used to compare against
an element that has http://www.w3.org/2001/XMLSchema
http://www.w3.org/2001/XMLSchema as it's namespace so they don't
match up and consequently the java.lang.RuntimeException: Unexpected
subelement value exception is thrown.
Here is the line I am referring to:
if (reader.isStartElement() new
javax.xml.namespace.QName(http://helper.webservice.soap.test.com/xsd,;
value).equals(reader.getName
http://helper.webservice.soap.test.com/xsd,value;).equals(reader.getN
ame ())){
Is this a limitation of ADB, an error in the stub generation, an error
in the wsdl generation, or something I can control in my stub
generation?
Thanks for any insight you can offer.
Ted
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 11:48 PM
To: axis-user@ws.apache.org
Subject: Re: [Axix2] java.lang.RuntimeException: Unexpected subelement
value
we have discussed this senario in many times.
First thing you have to do is to check the received soap message using
the tcp mon.
then validate the that received response message with the generated wsdl
(wsdl you used to generate the code)
Amila.
On 3/30/07, Ted Jones [EMAIL PROTECTED] wrote:
I am receiving the following exception in my ADB generated stub
while processing my soap response: java.lang.RuntimeException:
Unexpected subelement value
The WSDL used to generate my stub is auto generated (Axis2
1.1.1).
Any ideas?
TIA,
Ted
--
Amila Suriarachchi,
WSO2 Inc.
RE: Axis2 Client Stub not Generating WS-Security Headers
Thanks for your assistance Ruchith. I was able to get it working. Thanks, Ted -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 2:34 AM To: axis-user@ws.apache.org Subject: Re: Axis2 Client Stub not Generating WS-Security Headers Hi Ted, On 3/28/07, Ted Jones [EMAIL PROTECTED] wrote: Thank you for the reply Ruchith. I am following these instructions with the exception of the service invocation since I am using my generated client stub. Does the client repository location need to be included in order to generate the proper stub logic for inserting the WS-Security headers? When you codegen the stub will *not* contain any logic related to rampart. Also, the code sample links are broken on the link you gave me. The link is now fixed. Thanks, Ruchith Thanks, Ted -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 11:04 PM To: axis-user@ws.apache.org Subject: Re: Axis2 Client Stub not Generating WS-Security Headers Hi Ted, Please see this : http://www.wso2.org/library/240 Thanks, Ruchith On 3/28/07, Ted Jones [EMAIL PROTECTED] wrote: I have an Axis2 1.1.1 ADB generated client stub that is instantiated using a client axis2.xml config and pointing to a client repository that has the rampart and addressing mar files. The config file and repository location are loaded via URL. In debug, I can see the rampart and addressing modules are engaged. In my client code, I have added the following properties to the serviceclient's options instance: options.setProperty(WSConstants.WSSE_NS , WSConstants.USERNAME_TOKEN_LN); options.setProperty(WSConstants.USERNAME_LN,getConnectionProperties(). getUserid()); options.setProperty(WSConstants.PASSWORD_LN,getConnectionProperties(). getPassword()); options.setProperty(WSConstants.PASSWORD_TYPE_ATTR, WSConstants.PASSWORD_TEXT); The WS-Security headers are never inserted into the soap request and I receive the ever-popular org.apache.axis2.AxisFault: WSDoAllReceiver: Incoming message does not contain required Security header. This web service and the ws-security logic works using soapUI (a great *free* tool by the way). Is there some other property I need to set in the options or something else I need to be doing? Thanks Ted -- www.ruchith.org www.wso2.org - 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] -- www.ruchith.org www.wso2.org - 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 Client Stub not Generating WS-Security Headers
Thank you for the reply Ruchith. I am following these instructions with the exception of the service invocation since I am using my generated client stub. Does the client repository location need to be included in order to generate the proper stub logic for inserting the WS-Security headers? Also, the code sample links are broken on the link you gave me. Thanks, Ted -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 11:04 PM To: axis-user@ws.apache.org Subject: Re: Axis2 Client Stub not Generating WS-Security Headers Hi Ted, Please see this : http://www.wso2.org/library/240 Thanks, Ruchith On 3/28/07, Ted Jones [EMAIL PROTECTED] wrote: I have an Axis2 1.1.1 ADB generated client stub that is instantiated using a client axis2.xml config and pointing to a client repository that has the rampart and addressing mar files. The config file and repository location are loaded via URL. In debug, I can see the rampart and addressing modules are engaged. In my client code, I have added the following properties to the serviceclient's options instance: options.setProperty(WSConstants.WSSE_NS , WSConstants.USERNAME_TOKEN_LN); options.setProperty(WSConstants.USERNAME_LN,getConnectionProperties(). getUserid()); options.setProperty(WSConstants.PASSWORD_LN,getConnectionProperties(). getPassword()); options.setProperty(WSConstants.PASSWORD_TYPE_ATTR, WSConstants.PASSWORD_TEXT); The WS-Security headers are never inserted into the soap request and I receive the ever-popular org.apache.axis2.AxisFault: WSDoAllReceiver: Incoming message does not contain required Security header. This web service and the ws-security logic works using soapUI (a great *free* tool by the way). Is there some other property I need to set in the options or something else I need to be doing? Thanks Ted -- www.ruchith.org www.wso2.org - 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 Client Stub not Generating WS-Security Headers
I'm thinking this is due to not using the -r in my WSDL2JAVA command to include my client repository? I added this and now I am getting the following: java.lang.IllegalStateException: No valid ObjectCreator found. Threads I have come across indicate that this error is caused by an incorrect version of the STAX jar, but it is the one that came with Axis2 1.1.1. My classpath does not include any jars that are not part of the Axis2 1.1.1 distribution. Any ideas? Thanks, Ted From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 3:04 PM To: axis-user@ws.apache.org Subject: Axis2 Client Stub not Generating WS-Security Headers I have an Axis2 1.1.1 ADB generated client stub that is instantiated using a client axis2.xml config and pointing to a client repository that has the rampart and addressing mar files. The config file and repository location are loaded via URL. In debug, I can see the rampart and addressing modules are engaged. In my client code, I have added the following properties to the serviceclient's options instance: options.setProperty(WSConstants.WSSE_NS , WSConstants.USERNAME_TOKEN_LN); options.setProperty(WSConstants.USERNAME_LN,getConnectionProperties().ge tUserid()); options.setProperty(WSConstants.PASSWORD_LN,getConnectionProperties().ge tPassword()); options.setProperty(WSConstants.PASSWORD_TYPE_ATTR, WSConstants.PASSWORD_TEXT); The WS-Security headers are never inserted into the soap request and I receive the ever-popular org.apache.axis2.AxisFault: WSDoAllReceiver: Incoming message does not contain required Security header. This web service and the ws-security logic works using soapUI (a great *free* tool by the way). Is there some other property I need to set in the options or something else I need to be doing? Thanks Ted
RE: HTTPS WSDL
Thank you for the reply Deepal. Do you know if this is a temporary workaround, or is it a permanent solution for HTTPS endpoints? Also, do you know if it is possible to use custom wsdl and just have the host and port replaced dynamically? Thanks, Ted -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Thu 2/15/2007 11:03 PM To: axis-user@ws.apache.org Subject: Re: HTTPS WSDL To solve the issue , you need to pass the portName when you generate code -pn PortName Note : Here the PortName is the name of the port which has HTTPS address on it. Thanks Deepal Ted Jones wrote: I am letting Axis2 generate my WSDL for a service. When accessing the WSDL via HTTPS, the endpoints are still being generated with HTTP. Is this a known issue or is there a way to force HTTPS for the endpoints? Thanks, Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] winmail.dat- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HTTPS WSDL
I am letting Axis2 generate my WSDL for a service. When accessing the WSDL via HTTPS, the endpoints are still being generated with HTTP. Is this a known issue or is there a way to force HTTPS for the endpoints? Thanks, Ted
RE: [Axis2] java.lang.IllegalArgumentException: null rcl
Perhaps this is a bug? I removed my custom wsdl and let Axis2 generate
it for me. I am seeing the same issue while trying to get the class
loader for the java.lang.Boolean class. I suspect since this class is in
the boot class loader, null is returned from getClassloader() call? Can
anyone suggest a workaround to force the Boolean class into the webapp
class loader?
If this IS a bug, should I log a JIRA, or is it a KI?
Thanks,
Ted
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 6:00 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] java.lang.IllegalArgumentException: null rcl
More info...
In debug, I can see the issue is spawning from the following call to the
constructor of ReflectClassBuilder in the JamServiceFactoryImpl class
(from the annogen jar):
public ReflectClassBuilder(ClassLoader rcl) {
if (rcl == null) throw new IllegalArgumentException(null rcl);
mLoader = rcl;
}
There is a class loader array with two values: a null and a system class
loader. The null class loader is being passed in this case for a class
of type java Boolean. The java object arrays seem to process fine prior
to this point. Any ideas?
I am using Axis2 1.1.1.
Thanks,
Ted
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 2:05 PM
To: axis-user@ws.apache.org
Subject: [Axis2] java.lang.IllegalArgumentException: null rcl
I am encountering the following exception in the Stax parser of Axis2
while rendering the results from my web service:
org.apache.axiom.om.OMException: java.lang.IllegalArgumentException:
null rcl
I have read some threads indicating there issues related to java
collections returned in Axis2. I have arrays of java objects being
returned. Does anyone know if this is indeed an issue and if there is a
workaround?
Thanks,
Ted
RE: [Axis2] java.lang.IllegalArgumentException: null rcl
I was able to resolve this issue with a minor change to the
getPullParser(Object, QName, TypeTable, boolean) method of
org.apache.axis2.databinding.utils.BeanUtils.
Changing:
jam_service_parms.addClassLoader(beanObject.getClass().getClassLoader())
;
to:
ClassLoader cl = beanObject.getClass().getClassLoader();
if (cl!=null){
jam_service_parms.addClassLoader(cl);
}else{
jam_service_parms.addClassLoader(Thread.currentThread().getContextClassL
oader());
}
averted the null class loader and properly deserialized my java Boolean.
This seems like a solid resolution and may fix another (seemingly
related?) JIRA I came across:
https://issues.apache.org/jira/browse/AXIS2-2054?page=com.atlassian.jira
.plugin.system.issuetabpanels:all-tabpanel
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February 12, 2007 10:20 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] java.lang.IllegalArgumentException: null rcl
Perhaps this is a bug? I removed my custom wsdl and let Axis2 generate
it for me. I am seeing the same issue while trying to get the class
loader for the java.lang.Boolean class. I suspect since this class is in
the boot class loader, null is returned from getClassloader() call? Can
anyone suggest a workaround to force the Boolean class into the webapp
class loader?
If this IS a bug, should I log a JIRA, or is it a KI?
Thanks,
Ted
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 6:00 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] java.lang.IllegalArgumentException: null rcl
More info...
In debug, I can see the issue is spawning from the following call to the
constructor of ReflectClassBuilder in the JamServiceFactoryImpl class
(from the annogen jar):
public ReflectClassBuilder(ClassLoader rcl) {
if (rcl == null) throw new IllegalArgumentException(null rcl);
mLoader = rcl;
}
There is a class loader array with two values: a null and a system class
loader. The null class loader is being passed in this case for a class
of type java Boolean. The java object arrays seem to process fine prior
to this point. Any ideas?
I am using Axis2 1.1.1.
Thanks,
Ted
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 2:05 PM
To: axis-user@ws.apache.org
Subject: [Axis2] java.lang.IllegalArgumentException: null rcl
I am encountering the following exception in the Stax parser of Axis2
while rendering the results from my web service:
org.apache.axiom.om.OMException: java.lang.IllegalArgumentException:
null rcl
I have read some threads indicating there issues related to java
collections returned in Axis2. I have arrays of java objects being
returned. Does anyone know if this is indeed an issue and if there is a
workaround?
Thanks,
Ted
[Axis2] java.lang.IllegalArgumentException: null rcl
I am encountering the following exception in the Stax parser of Axis2 while rendering the results from my web service: org.apache.axiom.om.OMException: java.lang.IllegalArgumentException: null rcl I have read some threads indicating there issues related to java collections returned in Axis2. I have arrays of java objects being returned. Does anyone know if this is indeed an issue and if there is a workaround? Thanks, Ted
RE: [Axis2] java.lang.IllegalArgumentException: null rcl
More info...
In debug, I can see the issue is spawning from the following call to the
constructor of ReflectClassBuilder in the JamServiceFactoryImpl class
(from the annogen jar):
public ReflectClassBuilder(ClassLoader rcl) {
if (rcl == null) throw new IllegalArgumentException(null rcl);
mLoader = rcl;
}
There is a class loader array with two values: a null and a system class
loader. The null class loader is being passed in this case for a class
of type java Boolean. The java object arrays seem to process fine prior
to this point. Any ideas?
I am using Axis2 1.1.1.
Thanks,
Ted
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 2:05 PM
To: axis-user@ws.apache.org
Subject: [Axis2] java.lang.IllegalArgumentException: null rcl
I am encountering the following exception in the Stax parser of Axis2
while rendering the results from my web service:
org.apache.axiom.om.OMException: java.lang.IllegalArgumentException:
null rcl
I have read some threads indicating there issues related to java
collections returned in Axis2. I have arrays of java objects being
returned. Does anyone know if this is indeed an issue and if there is a
workaround?
Thanks,
Ted
Axis2 Parameter to Operation is always null
Whenever I invoke an operation for a particular web service, the parameter is always null. I am passing the correct values in the soap request, but they never seem to make to the invoked operation. The parameter is a java object and defined as a complex type in my schema. Do I need to somehow map the java object type to the parameter in my wsdl? Has anyone else encountered this before? TIA, Ted
RE: WS-Security in Axis2
Thanks for the reply Slim. Did you have to configure the gSOAP client with the client.axis2.xml file? From: zze-Basic DRISS S ext RD-MAPS-ISS [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 23, 2007 10:46 AM To: axis-user@ws.apache.org Subject: RE: WS-Security in Axis2 Hi, Yes I've used a gSOAP 2.7 client to access an Axis2 service through a UsernameToken authentication with Rampart 1.1. Regards, Slim De : Ted Jones [mailto:[EMAIL PROTECTED] Envoyé : lundi 15 janvier 2007 22:00 À : axis-user@ws.apache.org Objet : WS-Security in Axis2 Is there any way to use Rampart in Axis2 with a non-Axis2 client, or is that a pre-requisite? Has anyone used any other WS-Security providers with Axis2. Thanks, Ted Jones
WS-Security in Axis2
Is there any way to use Rampart in Axis2 with a non-Axis2 client, or is that a pre-requisite? Has anyone used any other WS-Security providers with Axis2. Thanks, Ted Jones
RE: WSDL2Java Question
If you want Axis 1.* stubs, then AXIS_HOME should point to your Axis 1.* location (not Axis2). From: Gul Onural [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:38 PM To: axis-user@ws.apache.org Subject: RE: WSDL2Java Question Most probably... What I have defined to get wsdl2Java working : AXIS2_HOME environment variable pointing to axis2 installation directory and %AXIS2_HOME%\bin in my PATH From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:33 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Yes, both AXIS_HOME and JAVA_HOME point to their correct directories. However they are defined in /etc/profile and not in my local profile. Could that be it? Thanx Gul Onural wrote: Have you defined AXIS_HOME environment variable pointing to your axis2 installation ? From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:23 PM To: Axis User Subject: WSDL2Java Question The examples below are straight from http://ws.apache.org/axis/java/reference.html#WSDL2JavaReference and neither obviously works (for me). I can't even get --help to work. [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help http://appsrv:8080/axis2/services/wsVendor Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java http://appsrv:8080/axis2/services/wsVendor?wsdl Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java Here's a snippet from the web site instructions: Usage: java org.apache.axis.wsdl.WSDL2Java [options] WSDL-URI Options: -h, --help print this message and exit What am I doing wrong? Thanx, Garth - 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: WSDL2Java Question
Judging by your error message you are trying to execute the Axis 1.* WSDL2JAVA and your classpath is pointing to Axis2. Here are the instructions for the Axis2 WSDL2JAVA tool: http://ws.apache.org/axis2/1_0/userguide2.html#WSDL2Java_Tool If you prefer to use the Axis 1.* WSDL2JAVA, make sure you point to the Axis 1.* installation. From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:47 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Pertinent env vars: JAVA_HOME=/usr/dev/jdk1.5.0_10 JAR_HOME=/usr/dev/jars LANG=en_US.UTF-8 GDMSESSION=default JUNIT_HOME=/usr/dev/junit4.1 HISTCONTROL=ignoredups AXIS_LIBRARIES=/usr/dev/axis2-1.1.1/lib XERCES_HOME=/usr/dev/xerces-2_9_0 JAVAMAIL_HOME=/usr/dev/javamail-1.4 JAVA_ENDORSED_DIRS=/usr/dev/jwsdp-2.0/jaxp/lib:/usr/dev/jwsdp-2.0/jaxp/l ib/endorsed:/usr/dev/apache-tomcat-5.5.20/bin:/usr/dev/apache-tomcat-5.5 .20/common/lib:/usr/dev/apache-tomcat-5.5.20/webapps/axis2/WEB-INF/lib SOAP_HOME=/usr/dev/soap-2_3_1 PATH=/usr/dev/jdk1.5.0_10/bin:/usr/dev/apache-ant-1.6.5/bin:/usr/dev/axi s2-1.1.1/bin:/usr/dev/jwsdp-2.0:/usr/dev/jwsdp-2.0/jaxrpc/bin:/usr/dev/m aven-2.0.4:/usr/dev/maven-2.0.4/bin:/usr/local/sbin:/usr/local/bin:/usr/ sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games Do I need more/less/different? Thanx Gul Onural wrote: Most probably... What I have defined to get wsdl2Java working : AXIS2_HOME environment variable pointing to axis2 installation directory and %AXIS2_HOME%\bin in my PATH From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:33 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Yes, both AXIS_HOME and JAVA_HOME point to their correct directories. However they are defined in /etc/profile and not in my local profile. Could that be it? Thanx Gul Onural wrote: Have you defined AXIS_HOME environment variable pointing to your axis2 installation ? From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:23 PM To: Axis User Subject: WSDL2Java Question The examples below are straight from http://ws.apache.org/axis/java/reference.html#WSDL2JavaReference and neither obviously works (for me). I can't even get --help to work. [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help http://appsrv:8080/axis2/services/wsVendor Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java http://appsrv:8080/axis2/services/wsVendor?wsdl Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java Here's a snippet from the web site instructions: Usage: java org.apache.axis.wsdl.WSDL2Java [options] WSDL-URI Options: -h, --help print this message and exit What am I doing wrong? Thanx, Garth - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL2Java Question
There are some schema support limitations with Axis2 code generation that have forced us to use the Axis 1.3 WSDL2JAVA tool against our Axis2 service. Your schema may not have the same issues, so the Axis2 WSDL2JAVA may be sufficient for your needs. From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:55 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question I use AXIS2 v1.1.1. Dumb Q but do I want Axis 1.* stubs? I've never gotten far enough with the tool to see what it produces. Thanx, Garth Ted Jones wrote: If you want Axis 1.* stubs, then AXIS_HOME should point to your Axis 1.* location (not Axis2). From: Gul Onural [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:38 PM To: axis-user@ws.apache.org Subject: RE: WSDL2Java Question Most probably... What I have defined to get wsdl2Java working : AXIS2_HOME environment variable pointing to axis2 installation directory and %AXIS2_HOME%\bin in my PATH From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:33 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Yes, both AXIS_HOME and JAVA_HOME point to their correct directories. However they are defined in /etc/profile and not in my local profile. Could that be it? Thanx Gul Onural wrote: Have you defined AXIS_HOME environment variable pointing to your axis2 installation ? From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:23 PM To: Axis User Subject: WSDL2Java Question The examples below are straight from http://ws.apache.org/axis/java/reference.html#WSDL2JavaReference and neither obviously works (for me). I can't even get --help to work. [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help http://appsrv:8080/axis2/services/wsVendor Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java http://appsrv:8080/axis2/services/wsVendor?wsdl Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java Here's a snippet from the web site instructions: Usage: java org.apache.axis.wsdl.WSDL2Java [options] WSDL-URI Options: -h, --help print this message and exit What am I doing wrong? Thanx, Garth - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL2Java Question
The manual is referring to the class and not the .sh script file. Try: wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:08 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question If I take those instructions literally, here's what I get: [EMAIL PROTECTED]:~$ WSDL2Java -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide bash: WSDL2Java: command not found I have searched my Ubuntu edgy box and can not find any file of that name (or even close). If I look in the AXIS2_HOME/bin dir, all I find is wsdl2java.sh and (for Windows) .bat. Am I missing something (no sarcasm please:-)? Thanx Ted Jones wrote: Judging by your error message you are trying to execute the Axis 1.* WSDL2JAVA and your classpath is pointing to Axis2. Here are the instructions for the Axis2 WSDL2JAVA tool: http://ws.apache.org/axis2/1_0/userguide2.html#WSDL2Java_Tool If you prefer to use the Axis 1.* WSDL2JAVA, make sure you point to the Axis 1.* installation. From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:47 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Pertinent env vars: JAVA_HOME=/usr/dev/jdk1.5.0_10 JAR_HOME=/usr/dev/jars LANG=en_US.UTF-8 GDMSESSION=default JUNIT_HOME=/usr/dev/junit4.1 HISTCONTROL=ignoredups AXIS_LIBRARIES=/usr/dev/axis2-1.1.1/lib XERCES_HOME=/usr/dev/xerces-2_9_0 JAVAMAIL_HOME=/usr/dev/javamail-1.4 JAVA_ENDORSED_DIRS=/usr/dev/jwsdp-2.0/jaxp/lib:/usr/dev/jwsdp-2.0/jaxp/l ib/endorsed:/usr/dev/apache-tomcat-5.5.20/bin:/usr/dev/apache-tomcat-5.5 .20/common/lib:/usr/dev/apache-tomcat-5.5.20/webapps/axis2/WEB-INF/lib SOAP_HOME=/usr/dev/soap-2_3_1 PATH=/usr/dev/jdk1.5.0_10/bin:/usr/dev/apache-ant-1.6.5/bin:/usr/dev/axi s2-1.1.1/bin:/usr/dev/jwsdp-2.0:/usr/dev/jwsdp-2.0/jaxrpc/bin:/usr/dev/m aven-2.0.4:/usr/dev/maven-2.0.4/bin:/usr/local/sbin:/usr/local/bin:/usr/ sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games Do I need more/less/different? Thanx Gul Onural wrote: Most probably... What I have defined to get wsdl2Java working : AXIS2_HOME environment variable pointing to axis2 installation directory and %AXIS2_HOME%\bin in my PATH From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:33 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Yes, both AXIS_HOME and JAVA_HOME point to their correct directories. However they are defined in /etc/profile and not in my local profile. Could that be it? Thanx Gul Onural wrote: Have you defined AXIS_HOME environment variable pointing to your axis2 installation ? From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:23 PM To: Axis User Subject: WSDL2Java Question The examples below are straight from http://ws.apache.org/axis/java/reference.html#WSDL2JavaReference and neither obviously works (for me). I can't even get --help to work. [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help http://appsrv:8080/axis2/services/wsVendor Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java http://appsrv:8080/axis2/services/wsVendor?wsdl Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java Here's a snippet from the web site instructions: Usage: java org.apache.axis.wsdl.WSDL2Java [options] WSDL-URI Options: -h, --help print
RE: WSDL2Java Question
Hmmm... not sure about that one. Can you try setting JAVA_HOME to a 1.4 JDK and see if that makes a difference? From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:30 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question I really appreciate your patience... Here's what I get: [EMAIL PROTECTED]:~$ wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide Using AXIS2_HOME: /usr/dev/axis2-1.1.1 Using JAVA_HOME: /usr/dev/jdk1.5.0_10 Unrecognized option: -uri Could not create the Java virtual machine. Ted Jones wrote: The manual is referring to the class and not the .sh script file. Try: wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:08 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question If I take those instructions literally, here's what I get: [EMAIL PROTECTED]:~$ WSDL2Java -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide bash: WSDL2Java: command not found I have searched my Ubuntu edgy box and can not find any file of that name (or even close). If I look in the AXIS2_HOME/bin dir, all I find is wsdl2java.sh and (for Windows) .bat. Am I missing something (no sarcasm please:-)? Thanx Ted Jones wrote: Judging by your error message you are trying to execute the Axis 1.* WSDL2JAVA and your classpath is pointing to Axis2. Here are the instructions for the Axis2 WSDL2JAVA tool: http://ws.apache.org/axis2/1_0/userguide2.html#WSDL2Java_Tool If you prefer to use the Axis 1.* WSDL2JAVA, make sure you point to the Axis 1.* installation. From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:47 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Pertinent env vars: JAVA_HOME=/usr/dev/jdk1.5.0_10 JAR_HOME=/usr/dev/jars LANG=en_US.UTF-8 GDMSESSION=default JUNIT_HOME=/usr/dev/junit4.1 HISTCONTROL=ignoredups AXIS_LIBRARIES=/usr/dev/axis2-1.1.1/lib XERCES_HOME=/usr/dev/xerces-2_9_0 JAVAMAIL_HOME=/usr/dev/javamail-1.4 JAVA_ENDORSED_DIRS=/usr/dev/jwsdp-2.0/jaxp/lib:/usr/dev/jwsdp-2.0/jaxp/l ib/endorsed:/usr/dev/apache-tomcat-5.5.20/bin:/usr/dev/apache-tomcat-5.5 .20/common/lib:/usr/dev/apache-tomcat-5.5.20/webapps/axis2/WEB-INF/lib SOAP_HOME=/usr/dev/soap-2_3_1 PATH=/usr/dev/jdk1.5.0_10/bin:/usr/dev/apache-ant-1.6.5/bin:/usr/dev/axi s2-1.1.1/bin:/usr/dev/jwsdp-2.0:/usr/dev/jwsdp-2.0/jaxrpc/bin:/usr/dev/m aven-2.0.4:/usr/dev/maven-2.0.4/bin:/usr/local/sbin:/usr/local/bin:/usr/ sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games Do I need more/less/different? Thanx Gul Onural wrote: Most probably... What I have defined to get wsdl2Java working : AXIS2_HOME environment variable pointing to axis2 installation directory and %AXIS2_HOME%\bin in my PATH From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:33 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Yes, both AXIS_HOME and JAVA_HOME point to their correct directories. However they are defined in /etc/profile and not in my local profile. Could that be it? Thanx Gul Onural wrote: Have you defined AXIS_HOME environment variable pointing to your axis2 installation ? From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:23 PM To: Axis User Subject: WSDL2Java Question
RE: WSDL2Java Question
No. They are mutually exclusive events. From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 5:17 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question I tried but Sun's download servers are offline for system upgrades. So it'll have to wait for awhile. BTW, I install Axis2-1.1.1 from the binary distro and install it into /usr/dev/axis2-1.1.1 which is where AXIS2_HOME points. I deploy Axis2 using the war file distro and simply drop it into Tomcat;s webapps folder. Should this make any diff? Ted Jones wrote: Hmmm... not sure about that one. Can you try setting JAVA_HOME to a 1.4 JDK and see if that makes a difference? From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:30 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question I really appreciate your patience... Here's what I get: [EMAIL PROTECTED]:~$ wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide Using AXIS2_HOME: /usr/dev/axis2-1.1.1 Using JAVA_HOME: /usr/dev/jdk1.5.0_10 Unrecognized option: -uri Could not create the Java virtual machine. Ted Jones wrote: The manual is referring to the class and not the .sh script file. Try: wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:08 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question If I take those instructions literally, here's what I get: [EMAIL PROTECTED]:~$ WSDL2Java -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide bash: WSDL2Java: command not found I have searched my Ubuntu edgy box and can not find any file of that name (or even close). If I look in the AXIS2_HOME/bin dir, all I find is wsdl2java.sh and (for Windows) .bat. Am I missing something (no sarcasm please:-)? Thanx Ted Jones wrote: Judging by your error message you are trying to execute the Axis 1.* WSDL2JAVA and your classpath is pointing to Axis2. Here are the instructions for the Axis2 WSDL2JAVA tool: http://ws.apache.org/axis2/1_0/userguide2.html#WSDL2Java_Tool If you prefer to use the Axis 1.* WSDL2JAVA, make sure you point to the Axis 1.* installation. From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:47 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Pertinent env vars: JAVA_HOME=/usr/dev/jdk1.5.0_10 JAR_HOME=/usr/dev/jars LANG=en_US.UTF-8 GDMSESSION=default JUNIT_HOME=/usr/dev/junit4.1 HISTCONTROL=ignoredups AXIS_LIBRARIES=/usr/dev/axis2-1.1.1/lib XERCES_HOME=/usr/dev/xerces-2_9_0 JAVAMAIL_HOME=/usr/dev/javamail-1.4 JAVA_ENDORSED_DIRS=/usr/dev/jwsdp-2.0/jaxp/lib:/usr/dev/jwsdp-2.0/jaxp/l ib/endorsed:/usr/dev/apache-tomcat-5.5.20/bin:/usr/dev/apache-tomcat-5.5 .20/common/lib:/usr/dev/apache-tomcat-5.5.20/webapps/axis2/WEB-INF/lib SOAP_HOME=/usr/dev/soap-2_3_1 PATH=/usr/dev/jdk1.5.0_10/bin:/usr/dev/apache-ant-1.6.5/bin:/usr/dev/axi s2-1.1.1/bin:/usr/dev/jwsdp-2.0:/usr/dev/jwsdp-2.0/jaxrpc/bin:/usr/dev/m aven-2.0.4:/usr/dev/maven-2.0.4/bin:/usr/local/sbin:/usr/local/bin:/usr/ sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games Do I need more/less/different? Thanx Gul Onural wrote: Most probably... What I have defined to get wsdl2Java working : AXIS2_HOME environment variable pointing to axis2
RE: WSDL2Java Question
Seems like you would get a better error if the wsdl was not resolvable (at least you do on Windows). Worth a shot though. -Original Message- From: ChadDavis [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 5:25 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question What directory did you execute this command from? It looks like its from your home directory, which would mean that your uri is pointing somewhere up into the /home/ directory, which seems unlikely. Am I missing something? If I'm reading this right, you just need to move to the right directory so that your relative path to the wsdl resolves correctly. On 1/10/07, Garth Keesler [EMAIL PROTECTED] wrote: I really appreciate your patience... Here's what I get: [EMAIL PROTECTED]:~$ wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide Using AXIS2_HOME: /usr/dev/axis2-1.1.1 Using JAVA_HOME: /usr/dev/jdk1.5.0_10 Unrecognized option: -uri Could not create the Java virtual machine. Ted Jones wrote: The manual is referring to the class and not the .sh script file. Try: wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:08 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question If I take those instructions literally, here's what I get: [EMAIL PROTECTED]:~$ WSDL2Java -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide bash: WSDL2Java: command not found I have searched my Ubuntu edgy box and can not find any file of that name (or even close). If I look in the AXIS2_HOME/bin dir, all I find is wsdl2java.sh and (for Windows) .bat. Am I missing something (no sarcasm please:-)? Thanx Ted Jones wrote: Judging by your error message you are trying to execute the Axis 1.* WSDL2JAVA and your classpath is pointing to Axis2. Here are the instructions for the Axis2 WSDL2JAVA tool: http://ws.apache.org/axis2/1_0/userguide2.html#WSDL2Java_Tool If you prefer to use the Axis 1.* WSDL2JAVA, make sure you point to the Axis 1.* installation. From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:47 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Pertinent env vars: JAVA_HOME=/usr/dev/jdk1.5.0_10 JAR_HOME=/usr/dev/jars LANG=en_US.UTF-8 GDMSESSION=default JUNIT_HOME=/usr/dev/junit4.1 HISTCONTROL=ignoredups AXIS_LIBRARIES=/usr/dev/axis2-1.1.1/lib XERCES_HOME=/usr/dev/xerces-2_9_0 JAVAMAIL_HOME=/usr/dev/javamail-1.4 JAVA_ENDORSED_DIRS=/usr/dev/jwsdp-2.0/jaxp/lib:/usr/dev/jwsdp-2.0/jaxp /lib/endorsed:/usr/dev/apache-tomcat-5.5.20/bin:/usr/dev/apache-tomcat -5.5.20/common/lib:/usr/dev/apache-tomcat-5.5.20/webapps/axis2/WEB-INF /lib SOAP_HOME=/usr/dev/soap-2_3_1 PATH=/usr/dev/jdk1.5.0_10/bin:/usr/dev/apache-ant-1.6.5/bin:/usr/dev/a xis2-1.1.1/bin:/usr/dev/jwsdp-2.0:/usr/dev/jwsdp-2.0/jaxrpc/bin:/usr/d ev/maven-2.0.4:/usr/dev/maven-2.0.4/bin:/usr/local/sbin:/usr/local/bin :/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games Do I need more/less/different? Thanx Gul Onural wrote: Most probably... What I have defined to get wsdl2Java working : AXIS2_HOME environment variable pointing to axis2 installation directory and %AXIS2_HOME%\bin in my PATH From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:33 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Yes, both AXIS_HOME and JAVA_HOME point to their correct directories. However they are defined in /etc/profile and not in my local profile. Could that be it? Thanx Gul Onural wrote: Have you defined AXIS_HOME environment variable pointing to your axis2 installation ? From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:23 PM To: Axis User Subject: WSDL2Java Question The examples below are straight from http://ws.apache.org/axis/java/reference.html#WSDL2JavaReference and neither obviously works (for me). I can't even get --help to work. [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java --help http://appsrv:8080/axis2/services/wsVendor Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java [EMAIL PROTECTED]:~$ java org.apache.axis.wsdl.WSDL2Java http://appsrv:8080/axis2/services/wsVendor?wsdl Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/wsdl/WSDL2Java Here's
RE: Soap Over JMS using Embedded Axis2 Engine
Hi Ali, Please see responses inline... Thanks very much, Ted From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 03, 2007 5:36 PM To: axis-user@ws.apache.org Subject: Re: Soap Over JMS using Embedded Axis2 Engine Hi Ted, I'm needing the following information: - Do you successfully send the message? The message is sent by the producer in JMSSender. - Does the listener get the message successfully? No. - Do you call an in-only service? The service is in-out (accepts and returns an OMElement). - Is it possible that you call an in-only service with sendReceive()? No. Regards, Ali Sadik Kumlali - Original Message From: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org; [EMAIL PROTECTED] Sent: Wednesday, January 3, 2007 11:14:03 PM Subject: RE: Soap Over JMS using Embedded Axis2 Engine Thanks again Ali. After applying the changes you recommended, I am still getting the same org.apache.axis2.AxisFault: Incoming message input stream is null exception. Stepping through debug, the JMSSender is getting a null reply back from the Message reply = consumer.receive(timeout) call and the reply value is used for the input stream (thus the fault). Does that make any sense to you? Thanks, Ted From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 03, 2007 1:13 PM To: axis-user@ws.apache.org Subject: Re: Soap Over JMS using Embedded Axis2 Engine Hi Ted, It seems that you have problems with MEP (message exchange pattern). According to the Writing Web Services Using Axis2's Primary APIs tutorial[1], every operation must map to a corresponding MessageReceiver class.. But in JMS tutorial[2], services.xml doesn't map a particular operation to a corresponding MessageReceiver. I'm not sure whether it works in this way. Therefore could you please try the following structure: service name=service description My Web Service /description transports transportjms/transport /transports parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/parameter parameter name=allowedMethods locked=falseexecuteDataservice/parameter parameter name=transport.jms.ConnectionFactory locked=trueQueueConnectionFactory/parameter parameter name=transport.jms.Destination locked=truemyservice/parameter operation name=yourInOutMethodName messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ actionMappingurn:yourInOutMethodName/actionMapping /operation operation name=yourInOnlyMethodName messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ actionMappingurn:yourInOnlyMethodName/actionMapping /operation /service You should select RawXMLINOutMessageReceiver or RawXMLINOnlyMessageReceiver according to your operation(method) type. If your operation returns a result, then you should use RawXMLINOutMessageReceiver. Otherwise use RawXMLINOnlyMessageReceiver. Please also consider that RawXML*MessageReceiver expects your operation accepts OMElement and optionally returns and OMElement. Regards, Ali Sadik Kumlali [1] http://ws.apache.org/axis2/1_1/xmlbased-server.html [2] http://ws.apache.org/axis2/1_1/jms-transport.html - Original Message From: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org; [EMAIL PROTECTED] Sent: Wednesday, January 3, 2007 5:22:13 PM Subject: RE: Soap Over JMS using Embedded Axis2 Engine (email with exception included, sorry about that) Thanks very much Ali. That seems to be the issue with the timeout. I started the JMSListener from my test client and it is picking up the message now. I am now getting the following exception: org.apache.axis2.AxisFault: Incoming message input stream is null at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:64) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:381) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:295) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508) Any thoughts? Thanks, Ted From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 02, 2007 4:57 PM To: axis-user@ws.apache.org Subject: Re: Soap Over JMS using Embedded Axis2 Engine Hi Ted, War distribution(AxisServlet actually) doesn't initialize JMS listener. Please look at followings: 1) http://www.mail-archive.com/axis-user@ws.apache.org/msg21464.html 2) https://issues.apache.org/jira/browse/AXIS2-1488 Regards, Ali Sadik Kumlali - Original Message From: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org; [EMAIL PROTECTED] Sent: Tuesday, January 2, 2007 9:35:14 PM Subject: RE
RE: Soap Over JMS using Embedded Axis2 Engine
Thanks very much Ali. That seems to be the issue with the timeout. I started the JMSListener from my test client and it is picking up the message now. I am now getting the following exception: From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 02, 2007 4:57 PM To: axis-user@ws.apache.org Subject: Re: Soap Over JMS using Embedded Axis2 Engine Hi Ted, War distribution(AxisServlet actually) doesn't initialize JMS listener. Please look at followings: 1) http://www.mail-archive.com/axis-user@ws.apache.org/msg21464.html 2) https://issues.apache.org/jira/browse/AXIS2-1488 Regards, Ali Sadik Kumlali - Original Message From: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org; [EMAIL PROTECTED] Sent: Tuesday, January 2, 2007 9:35:14 PM Subject: RE: Soap Over JMS using Embedded Axis2 Engine Thanks for the reply Brennan. I believe I have everything configured as per the link below, but I keep timing out while waiting for the server to send the response. I am seeing this in my ActiveMQ console: myservice - No subscriptions registered, will not dispatch message at this time. myservice is the destination I am dynamically adding in my client code and that matches with the destination in my services.xml. Here is my services.xml: service name=service description My Web Service /description transports transportjms/transport /transports parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/parameter parameter name=allowedMethods locked=falseexecuteDataservice/parameter parameter name=transport.jms.ConnectionFactory locked=trueQueueConnectionFactory/parameter parameter name=transport.jms.Destination locked=truemyservice/parameter messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers /service Thanks for your help, Ted From: Brennan Spies [mailto:[EMAIL PROTECTED] Sent: Friday, December 29, 2006 10:19 PM To: axis-user@ws.apache.org Subject: RE: Soap Over JMS using Embedded Axis2 Engine Ted, Did you uncomment/configure the appropriate entries in your axis2.xml as well as your .aar’s service.xml? http://ws.apache.org/axis2/1_1/jms-transport.html From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, December 29, 2006 3:36 PM To: axis-user@ws.apache.org Subject: Soap Over JMS using Embedded Axis2 Engine I am attempting to execute a web service via ActiveMQ. The web service is deployed to an Axis2 engine that is embedded in a web app running on Tomcat 5.5. Are there any known *gotchas* here? I cannot seem to communicate with the service via JMS as it keeps timing out. When I change my endpoint in the client call from the JMS endpoint to the web service endpoint, it finds it. Thanks, Ted __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: Soap Over JMS using Embedded Axis2 Engine
(email with exception included, sorry about that) Thanks very much Ali. That seems to be the issue with the timeout. I started the JMSListener from my test client and it is picking up the message now. I am now getting the following exception: org.apache.axis2.AxisFault: Incoming message input stream is null at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:64) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:381) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:295) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508) Any thoughts? Thanks, Ted From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 02, 2007 4:57 PM To: axis-user@ws.apache.org Subject: Re: Soap Over JMS using Embedded Axis2 Engine Hi Ted, War distribution(AxisServlet actually) doesn't initialize JMS listener. Please look at followings: 1) http://www.mail-archive.com/axis-user@ws.apache.org/msg21464.html 2) https://issues.apache.org/jira/browse/AXIS2-1488 Regards, Ali Sadik Kumlali - Original Message From: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org; [EMAIL PROTECTED] Sent: Tuesday, January 2, 2007 9:35:14 PM Subject: RE: Soap Over JMS using Embedded Axis2 Engine Thanks for the reply Brennan. I believe I have everything configured as per the link below, but I keep timing out while waiting for the server to send the response. I am seeing this in my ActiveMQ console: myservice - No subscriptions registered, will not dispatch message at this time. myservice is the destination I am dynamically adding in my client code and that matches with the destination in my services.xml. Here is my services.xml: service name=service description My Web Service /description transports transportjms/transport /transports parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/parameter parameter name=allowedMethods locked=falseexecuteDataservice/parameter parameter name=transport.jms.ConnectionFactory locked=trueQueueConnectionFactory/parameter parameter name=transport.jms.Destination locked=truemyservice/parameter messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers /service Thanks for your help, Ted From: Brennan Spies [mailto:[EMAIL PROTECTED] Sent: Friday, December 29, 2006 10:19 PM To: axis-user@ws.apache.org Subject: RE: Soap Over JMS using Embedded Axis2 Engine Ted, Did you uncomment/configure the appropriate entries in your axis2.xml as well as your .aar’s service.xml? http://ws.apache.org/axis2/1_1/jms-transport.html From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, December 29, 2006 3:36 PM To: axis-user@ws.apache.org Subject: Soap Over JMS using Embedded Axis2 Engine I am attempting to execute a web service via ActiveMQ. The web service is deployed to an Axis2 engine that is embedded in a web app running on Tomcat 5.5. Are there any known *gotchas* here? I cannot seem to communicate with the service via JMS as it keeps timing out. When I change my endpoint in the client call from the JMS endpoint to the web service endpoint, it finds it. Thanks, Ted __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: Soap Over JMS using Embedded Axis2 Engine
Thanks again Ali. After applying the changes you recommended, I am still getting the same org.apache.axis2.AxisFault: Incoming message input stream is null exception. Stepping through debug, the JMSSender is getting a null reply back from the Message reply = consumer.receive(timeout) call and the reply value is used for the input stream (thus the fault). Does that make any sense to you? Thanks, Ted From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 03, 2007 1:13 PM To: axis-user@ws.apache.org Subject: Re: Soap Over JMS using Embedded Axis2 Engine Hi Ted, It seems that you have problems with MEP (message exchange pattern). According to the Writing Web Services Using Axis2's Primary APIs tutorial[1], every operation must map to a corresponding MessageReceiver class.. But in JMS tutorial[2], services.xml doesn't map a particular operation to a corresponding MessageReceiver. I'm not sure whether it works in this way. Therefore could you please try the following structure: service name=service description My Web Service /description transports transportjms/transport /transports parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/parameter parameter name=allowedMethods locked=falseexecuteDataservice/parameter parameter name=transport.jms.ConnectionFactory locked=trueQueueConnectionFactory/parameter parameter name=transport.jms.Destination locked=truemyservice/parameter operation name=yourInOutMethodName messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ actionMappingurn:yourInOutMethodName/actionMapping /operation operation name=yourInOnlyMethodName messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ actionMappingurn:yourInOnlyMethodName/actionMapping /operation /service You should select RawXMLINOutMessageReceiver or RawXMLINOnlyMessageReceiver according to your operation(method) type. If your operation returns a result, then you should use RawXMLINOutMessageReceiver. Otherwise use RawXMLINOnlyMessageReceiver. Please also consider that RawXML*MessageReceiver expects your operation accepts OMElement and optionally returns and OMElement. Regards, Ali Sadik Kumlali [1] http://ws.apache.org/axis2/1_1/xmlbased-server.html [2] http://ws.apache.org/axis2/1_1/jms-transport.html - Original Message From: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org; [EMAIL PROTECTED] Sent: Wednesday, January 3, 2007 5:22:13 PM Subject: RE: Soap Over JMS using Embedded Axis2 Engine (email with exception included, sorry about that) Thanks very much Ali. That seems to be the issue with the timeout. I started the JMSListener from my test client and it is picking up the message now. I am now getting the following exception: org.apache.axis2.AxisFault: Incoming message input stream is null at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:64) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:381) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:295) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508) Any thoughts? Thanks, Ted From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 02, 2007 4:57 PM To: axis-user@ws.apache.org Subject: Re: Soap Over JMS using Embedded Axis2 Engine Hi Ted, War distribution(AxisServlet actually) doesn't initialize JMS listener. Please look at followings: 1) http://www.mail-archive.com/axis-user@ws.apache.org/msg21464.html 2) https://issues.apache.org/jira/browse/AXIS2-1488 Regards, Ali Sadik Kumlali - Original Message From: Ted Jones [EMAIL PROTECTED] To: axis-user@ws.apache.org; [EMAIL PROTECTED] Sent: Tuesday, January 2, 2007 9:35:14 PM Subject: RE: Soap Over JMS using Embedded Axis2 Engine Thanks for the reply Brennan. I believe I have everything configured as per the link below, but I keep timing out while waiting for the server to send the response. I am seeing this in my ActiveMQ console: myservice - No subscriptions registered, will not dispatch message at this time. myservice is the destination I am dynamically adding in my client code and that matches with the destination in my services.xml. Here is my services.xml: service name=service description My Web Service /description transports transportjms/transport /transports parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/parameter parameter name=allowedMethods locked=falseexecuteDataservice/parameter parameter name=transport.jms.ConnectionFactory locked
RE: Soap Over JMS using Embedded Axis2 Engine
Thanks for the reply Brennan. I believe I have everything configured as per the link below, but I keep timing out while waiting for the server to send the response. I am seeing this in my ActiveMQ console: myservice - No subscriptions registered, will not dispatch message at this time. myservice is the destination I am dynamically adding in my client code and that matches with the destination in my services.xml. Here is my services.xml: service name=service description My Web Service /description transports transportjms/transport /transports parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/paramete r parameter name=allowedMethods locked=falseexecuteDataservice/parameter parameter name=transport.jms.ConnectionFactory locked=trueQueueConnectionFactory/parameter parameter name=transport.jms.Destination locked=truemyservice/parameter messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers /service Thanks for your help, Ted From: Brennan Spies [mailto:[EMAIL PROTECTED] Sent: Friday, December 29, 2006 10:19 PM To: axis-user@ws.apache.org Subject: RE: Soap Over JMS using Embedded Axis2 Engine Ted, Did you uncomment/configure the appropriate entries in your axis2.xml as well as your .aar's service.xml? http://ws.apache.org/axis2/1_1/jms-transport.html From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: Friday, December 29, 2006 3:36 PM To: axis-user@ws.apache.org Subject: Soap Over JMS using Embedded Axis2 Engine I am attempting to execute a web service via ActiveMQ. The web service is deployed to an Axis2 engine that is embedded in a web app running on Tomcat 5.5. Are there any known *gotchas* here? I cannot seem to communicate with the service via JMS as it keeps timing out. When I change my endpoint in the client call from the JMS endpoint to the web service endpoint, it finds it. Thanks, Ted
Soap Over JMS using Embedded Axis2 Engine
I am attempting to execute a web service via ActiveMQ. The web service is deployed to an Axis2 engine that is embedded in a web app running on Tomcat 5.5. Are there any known *gotchas* here? I cannot seem to communicate with the service via JMS as it keeps timing out. When I change my endpoint in the client call from the JMS endpoint to the web service endpoint, it finds it. Thanks, Ted
[AXIS2-1.1] Unsupported content Simple Type Union
When running wsdl2java with wsdl that imports a schema with the
following simple type definition:
xsd:simpleType name=BookEdition
xsd:annotation
xsd:documentation
Book edition, which can be an integer (1,2, ...) or nothing.
/xsd:documentation
/xsd:annotation
xsd:union memberTypes=xsd:nonNegativeInteger
xsd:simpleType
xsd:restriction base=xsd:string
xsd:enumeration value=/
/xsd:restriction
/xsd:simpleType
/xsd:union
/xsd:simpleType
I receive the following exception:
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException
: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:224)
at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetExcepti
on
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp
leDBExtension.java:52)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:177)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp
leDBExtension.java:49)
... 3 more
Caused by: org.apache.axis2.schema.SchemaCompilationException:
Unsupported conte
nt Simple Type Union in
{http://www.test.com/XMLSchema/DataSets/Books/Book
Datatypes}BookEdition !
at
org.apache.axis2.schema.SchemaCompiler.processSimpleType(SchemaCompil
er.java:1794)
at
org.apache.axis2.schema.SchemaCompiler.processSimpleSchemaType(Schema
Compiler.java:1747)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.j
ava:870)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:527)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:489)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:14
88)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler
.java:1450)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompi
ler.java:950)
at
org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(
SchemaCompiler.java:909)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.j
ava:864)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:527)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:489)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:14
88)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler
.java:1450)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompi
ler.java:950)
at
org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(
SchemaCompiler.java:909)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.j
ava:864)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:527)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:499)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:33
6)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:31
8)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:24
8)
at
org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java
:72)
I see there is a KI with with regards to ADB and support for
xs:union inside xs:simpleType (AXIS2-1093). Does this apply to wsdl2java
as well?
Thanks,
Ted Jones
I
RE: [AXIS2-1.1] Unsupported content Simple Type Union
Ah... ADB is used for code generation. Any idea when a fix will be
available for this?
Thanks,
Ted
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 19, 2006 10:21 AM
To: axis-user@ws.apache.org
Subject: [AXIS2-1.1] Unsupported content Simple Type Union
When running wsdl2java with wsdl that imports a schema with the
following simple type definition:
xsd:simpleType name=BookEdition
xsd:annotation
xsd:documentation
Book edition, which can be an integer (1,2, ...) or nothing.
/xsd:documentation
/xsd:annotation
xsd:union memberTypes=xsd:nonNegativeInteger
xsd:simpleType
xsd:restriction base=xsd:string
xsd:enumeration value=/
/xsd:restriction
/xsd:simpleType
/xsd:union
/xsd:simpleType
I receive the following exception:
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException
: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:224)
at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetExcepti
on
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp
leDBExtension.java:52)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:177)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp
leDBExtension.java:49)
... 3 more
Caused by: org.apache.axis2.schema.SchemaCompilationException:
Unsupported conte
nt Simple Type Union in
{http://www.test.com/XMLSchema/DataSets/Books/Book
Datatypes}BookEdition !
at
org.apache.axis2.schema.SchemaCompiler.processSimpleType(SchemaCompil
er.java:1794)
at
org.apache.axis2.schema.SchemaCompiler.processSimpleSchemaType(Schema
Compiler.java:1747)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.j
ava:870)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:527)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:489)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:14
88)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler
.java:1450)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompi
ler.java:950)
at
org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(
SchemaCompiler.java:909)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.j
ava:864)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:527)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:489)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:14
88)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler
.java:1450)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompi
ler.java:950)
at
org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(
SchemaCompiler.java:909)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.j
ava:864)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:527)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:499)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:33
6)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:31
8)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:24
8)
at
org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java
:72)
I see there is a KI with with regards to ADB and support for
xs:union inside xs:simpleType (AXIS2-1093). Does this apply to wsdl2java
as well
RE: Axis 1.* to Axis2 Migration Question
To be more specific as to what Axis 1.3 logic I am trying to convert,
the java:msg provider in Axis 1.3 specifies that the service class
contains the
following method signature (among others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the request,
execute our business logic, and return the results in the SOAP response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say that
there is no parallel Axis2 form of a service that uses a message
provider and will default to an method based on it's signature? Does
the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and response
envelopes as arguments. What is the parallel implementation for Axis2?
TIA,
Ted Jones
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis 1.* to Axis2 Migration Question
Thanks for the response dims. The Axis 1.* implementation is such that
it does not matter what the method name is, as long as the signature
matches one if the expected method signatures. If the method name was
specified in the allowableMethods property, it would be executed. So the
operation name did not have to match the method name. Is this still the
case? The reason I ask is because I am getting an Operation not found
exception.
Thanks for your help,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to convert,
the java:msg provider in Axis 1.3 specifies that the service class
contains the following method signature (among others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the request,
execute our business logic, and return the results in the SOAP
response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say
that there is no parallel Axis2 form of a service that uses a message
provider and will default to an method based on it's signature? Does
the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and response
envelopes as arguments. What is the parallel implementation for
Axis2?
TIA,
Ted Jones
-
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://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis 1.* to Axis2 Migration Question
.
- Original Message -
From: Ted Jones [EMAIL PROTECTED]
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 2:10 PM
Subject: RE: Axis 1.* to Axis2 Migration Question
Thanks for the response dims. The Axis 1.* implementation is such that
it does not matter what the method name is, as long as the signature
matches one if the expected method signatures. If the method name was
specified in the allowableMethods property, it would be executed. So the
operation name did not have to match the method name. Is this still the
case? The reason I ask is because I am getting an Operation not found
exception.
Thanks for your help,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to convert,
the java:msg provider in Axis 1.3 specifies that the service class
contains the following method signature (among others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the request,
execute our business logic, and return the results in the SOAP
response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say
that there is no parallel Axis2 form of a service that uses a message
provider and will default to an method based on it's signature? Does
the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and response
envelopes as arguments. What is the parallel implementation for
Axis2?
TIA,
Ted Jones
-
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://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis 1.* to Axis2 Migration Question
The soap action is set. Is this value being used to determine which
operation to execute? Is there a way to force it to pick the method
specified in the service.xml that uses the OMElement
methodName(OMElement element) signature?
Thanks,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 1:50 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
make sure you set the soap action correctly.
-- dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for the response dims. The Axis 1.* implementation is such that
it does not matter what the method name is, as long as the signature
matches one if the expected method signatures. If the method name was
specified in the allowableMethods property, it would be executed. So
the operation name did not have to match the method name. Is this
still the case? The reason I ask is because I am getting an Operation
not found exception.
Thanks for your help,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to
convert, the java:msg provider in Axis 1.3 specifies that the
service class contains the following method signature (among
others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the
request,
execute our business logic, and return the results in the SOAP
response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say
that there is no parallel Axis2 form of a service that uses a
message provider and will default to an method based on it's
signature? Does the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the
following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className
value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and
response envelopes as arguments. What is the parallel
implementation for
Axis2?
TIA,
Ted Jones
- 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://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis 1.* to Axis2 Migration Question
Hmmm... I get this when trying to get to the Axis2 generated WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Here is my service.xml for the deployed service: service name=service description Test Web Service /description parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/paramete r parameter name=allowedMethods locked=falseexecuteDataservice/parameter operation name=executeDataservice messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service FYI - The WSDL is generated dynamically from a servlet, it is not in the META-INF directory. Thanks, Ted -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, December 14, 2006 2:41 PM To: axis-user@ws.apache.org Cc: Martin Gainty Subject: Re: Axis 1.* to Axis2 Migration Question can you paste the autogenerated wsdl when you point your browse to ?wsdl thanks, dims On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote: My WSDL is pasted in below. This same WSDL works in Axis 1.3. When I execute the getBookCollection operation, it really accesses a method in the service that grabs the SOAP Action value and uses that to query against the database, gets a value and updates the SOAP response. This allows a dynamic behavior that does not require us to recreate the web service to accommodate a specific operation name. Here is a snippet from the userguide for Axis 1.2 that lead us down this path: snippet __ Message services Finally, we arrive at Message style services, which should be used when you want Axis to step back and let your code at the actual XML instead of turning it into Java objects. There are four valid signatures for your message-style service methods: public Element [] method(Element [] bodies); public SOAPBodyElement [] method (SOAPBodyElement [] bodies); public Document method(Document body); public void method(SOAPEnvelope req, SOAPEnvelope resp); The first two will pass your method arrays of either DOM Elements or SOAPBodyElements - the arrays will contain one element for each XML element inside the soap:body in the envelope. The third signature will pass you a DOM Document representing the soap:body, and expects the same in return. The fourth signature passes you two SOAPEnvelope objects representing the request and response messages. This is the signature to use if you need to look at or modify headers in your service method. Whatever you put into the response envelope will automatically be sent back to the caller when you return. Note that the response envelope may already contain headers which have been inserted by other Handlers. ___ /snippet It is the fourth signature that we were able to utilize. The method name was not the operation name, but an arbitrary value we defined. Here is my WSDL: definitions name=Books targetNamespace=http://com.test/BooksWebService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://com.test/BooksWebService; xmlns:schema1=http://test.com/books/input; xmlns:schema2=http://www.test.com/XMLSchema/DataSets/Books; types xsd:schema targetNamespace=http://com.test/BooksWebService; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xsd:import namespace=http://test.com/books/input; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service /B ooksWebService/BooksInput.xsd / xsd:import namespace=http://www.test.com/XMLSchema/DataSets/Books; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service /B ooksWebService/Books.xsd / /xsd:schema /types message name=Books_getBookCollection_getBookCollectionInput documentationInput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionInput element=schema1:getBookCollectionByTitleRequest / /message message name=Books_getBookCollection_getBookCollectionOutput documentationOutput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionOutput element=schema2:bookCollection / /message portType name=Books operation name=getBookCollection input message
Axis 1.* to Axis2 Migration Question
I have a web service in Axis 1.3 that is defined using the following deployment descriptor: service name=myservice provider=java:MSG parameter name=allowedMethods value=executeMyService/ parameter name=className value=com.soap.service.MyWebService/ /service The method (executeMyService) accepts the soap request and response envelopes as arguments. What is the parallel implementation for Axis2? TIA, Ted Jones
RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say that there is no parallel Axis2 form of a service that uses a message provider and will default to an method based on it's signature? Does the operation need to be specified now? Thanks -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 13, 2006 2:42 PM To: axis-user@ws.apache.org Subject: Re: Axis 1.* to Axis2 Migration Question This is a good place to start: http://ws.apache.org/axis2/1_1/migration.html HTH, Robert On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote: I have a web service in Axis 1.3 that is defined using the following deployment descriptor: service name=myservice provider=java:MSG parameter name=allowedMethods value=executeMyService/ parameter name=className value=com.soap.service.MyWebService/ /service The method (executeMyService) accepts the soap request and response envelopes as arguments. What is the parallel implementation for Axis2? TIA, Ted Jones - 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: Evaluating SOAP-Server
We have used the Systinet SOAP Server successfully. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Oliver Hirschi Sent: Monday, July 31, 2006 5:35 AM To: axis-user@ws.apache.org Subject: Evaluating SOAP-Server Hi, I'd like to change our application-server from corba to soap. The main job of this application server is to interact with java-clients to make database-queries. Additionally there are a few jobs which takes a lot of time, so they should be done on server, not on client. In the future its possible, that we devlope also a java-web-client to the server. This client should then also use the same soap-interfaces of the server. Is axis the right soap-server due to my requirements? By googleing about soap there comes ever Apache Axis. Is this the one and only soap-server or are there others? Great thank kind regards, -- Oliver Hirschi http://www.FamilyHirschi.ch - 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 1.0] WSDL2Java: WSDL for operations without params
Try this: message name=getMembershipInfo /message portType name=ClubInfoPortType operation name=getMembershipInfo input message=tns:getMembershipInfo name=getMembershipInfo/ /operation /portType -Ted -Original Message- From: Nirmit Desai [mailto:[EMAIL PROTECTED] Sent: Friday, July 28, 2006 2:35 PM To: axis-user@ws.apache.org Subject: RE: [Axis2 1.0] WSDL2Java: WSDL for operations without params Hi William, it creates a getScheduledReports.java in data bindings and puts that as the parameter type of the method. I suspect it is impossible to have it generate an empty parameter list for methods in WSDL2Java. Maybe this is a bug. -Nirmit William Ferguson William.Ferguson To @contractorsoluti axis-user@ws.apache.org ons.com.au cc 07/27/2006 07:20 Subject PMRE: [Axis2 1.0] WSDL2Java: WSDL for operations without params Please respond to [EMAIL PROTECTED] he.org Try xs:element name=getScheduledReports xs:complexType/ /xs:element wsdl:message name=getScheduledReportsMessage wsdl:part element=ns0:getScheduledReports name=part1/ /wsdl:message William -Original Message- From: Nirmit Desai [mailto:[EMAIL PROTECTED] Sent: Friday, 28 July 2006 3:40 AM To: axis-user@ws.apache.org Subject: [Axis2 1.0] WSDL2Java: WSDL for operations without params Hi all, I was wondering what is the right way to write a WSDL for a service operation taking no parameters. I tried this as the parameter type: complexType name=Void/ element name=getMembershipInfoParam type=xsd1:Void/ message name=getMembershipInfo part element=xsd1:getMembershipInfoParam name=in/ /message portType name=ClubInfoPortType operation name=getMembershipInfo input message=tns:getMembershipInfo name=getMembershipInfo / /operation /portType But WSDL2Java generates a Void.Java and specifies Void as the type of the operation parameter. How to write it such that the generated operation takes no parameters? Thanks, -Nirmit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis] Load Web Service on Startup
I don't know of any Axis settings to do this, but you could invokethe Web Servicefrom a servlet that loads on startup. Ted From: Patel, Ronak (US SSA) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 27, 2006 1:56 PMTo: axis-user@ws.apache.orgSubject: RE: [Axis] Load Web Service on Startup Hello All, I am interested in finding out how I can force Apache Axis to load and run my Web Service (by calling its init() method) when the Web Server starts. Is there a configuration parameter that I need to set somewhere? I am interested in finding this out in both Axis2 and Axis1.x. Any help would be greatly appreciated. Ronak Patel Software Engineer BAE Systems CNIR 450 Pulaski Road Greenlawn, NY 11740 (631) 262 - 8230 [EMAIL PROTECTED]
RE: WSDD reference or examples
Here is an example of wsdd for what you describe: deployment name="test" xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" !-- note that either style="message" OR provider="java:MSG" both work -- service name="serviceName" provider="java:MSG" parameter name="className" value="com.test.service.MyWebService" / parameter name="allowedMethods" value="MyMethodName" / /service/deployment From: Andrew Morrison [mailto:[EMAIL PROTECTED] Sent: Thursday, July 20, 2006 7:11 AMTo: axis-user@ws.apache.orgSubject: WSDD reference or examples Hi, Can anyone point me to a reference for creating a *.wsdd? I am trying to create a WSDD for a Message style web service. The intention is that the Axis generated WSDL will specify a user-defined XML schema (wsdlInputSchema) and assert that the input and output for the web service should be an XML document as defined by the schema. If anyone knows where I could see an example that would be great I am finding snippets of info on the web, but am having difficulty finding a detailed listing of the options etc. All the best, Andrew. The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you.
RE: [1.3] Handling large values
Have you tried increasing the heap size on your server? From: Simon McMahon [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 27, 2006 7:52 PMTo: axis-user@ws.apache.orgSubject: [1.3] Handling large values Hi, Axis throws various faults, including out-of-memory, when I pass a large value through a web service - e.g. a 5 Mb String. I dont have many alternatives because the firewall only allows http. Otherwise I would just use FTP. Any suggestions on how to get Axis 1.xto handle large messages? I dont want to try Axis 2 (again) because I already tried this some time agoand it required too many changes to my application. Regards, Simon. Simon McMahon Work: (07) 31311420Mobile: (043) 2294180*This email, including any attachments sent with it, isconfidential and for the sole use of the intended recipient(s).This confidentiality is not waived or lost, if you receive it andyou are not the intended recipient(s), or if it is transmitted/received in error.Any unauthorised use, alteration, disclosure, distribution orreview of this email is strictly prohibited. The informationcontained in this email, including any attachment sent withit, may be subject to a statutory duty of confidentiality if itrelates to health service matters.If you are not the intended recipient(s), or if you havereceived this email in error, you are asked to immediatelynotify the sender by telephone collect on Australia+61 1800 198 175 or by return email. You should alsodelete this email, and any copies, from your computersystem network and destroy any hard copies produced.If not an intended recipient of this email, you must not copy,distribute or take any action(s) that relies on it; any form ofdisclosure, modification, distribution and/or publication of thisemail is also prohibited.Although Queensland Health takes all reasonable steps toensure this email does not contain malicious software,Queensland Health does not accept responsibility for theconsequences if any person's computer inadvertently suffersany disruption to services, loss of information, harm or isinfected with a virus, other malicious computer programme orcode that may occur as a consequence of receiving thisemail.Unless stated otherwise, this email represents only the viewsof the sender and not the views of the Queensland Government.
RE: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)
I just added it. Thanks, Ted From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, June 23, 2006 6:19 PMTo: axis-user@ws.apache.orgSubject: Re: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681) Dims just filed a JIRA about this issue a day or two ago. http://issues.apache.org/jira/browse/AXIS2-837 Please add your use cases to the JIRA.Thanks,Anne On 6/23/06, Ted Jones [EMAIL PROTECTED] wrote: Martin, Here is the WSDL:definitions name="widgetServices" targetNamespace="http://com.widgets/test" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://com.widgets/test" xmlns:schema1="http://www.widgets.com/bqt_Output" types xsd:schema targetNamespace="http://com.widgets/test" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xsd:import namespace="http://www.widgets.com/bqt_Output" schemaLocation="http://chicago:8080/test/servlet/ArtifactDocumentService/test/bqt_Output.xsd" / /xsd:schema /types message name="bqt_SMALLA_getSMALLA_Input" documentationInput message for operation bqt_SMALLA/getSMALLA./documentation /message message name="bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" documentationOutput message for operation bqt_SMALLA/getSMALLA./documentation part name="bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" element="schema1:SMALLA_Output" / /message portType name="bqt_SMALLA" operation name="getSMALLA" input name="Input" message="tns:bqt_SMALLA_getSMALLA_Input" / output name="SMALLA_OutputMsg" message="tns:bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" / /operation /portType binding name="bqt_SMALLA" type="tns:bqt_SMALLA" soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" / operation name="getSMALLA" soap:operation style="document" soapAction="bqt_WS.bqt_SMALLA.getSMALLA" / input name="Input" soap:body use="literal" / /input output name="SMALLA_OutputMsg" soap:body use="literal" / /output /operation /binding service name="widgetsDataServices" port name="bqt_SMALLA" binding="tns:bqt_SMALLA" soap:address location="http://chicago:8080/test/services/service" / /port /service/definitions Here is the WSDD: deployment name="test" xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" !-- note that either style="message" OR provider="java:MSG" both work -- service name="service" provider="java:MSG" parameter name="className" value="com.widgets.soap.lds.service.DataServiceWebService" / parameter name="allowedMethods" value="executeDataservice" / /service/deployment I am executing a web service with no input parametersso the SOAP body is empty like so: soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" soapenv:Body//soapenv:Envelope I am getting an NPE returned before I even hit my Web Service, so I am assuming the exception is happening in Axis somewhere (I'm not seeing a stack trace). Here is the response: ?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/ /soapenv:Fault/soapenv:Body/soapenv:Envelope I get this using Coral and Systinet as my clients. When I generate an Axis client, I do not get an NPE but I get a node added to my body with the operation name in it (which I don't want to seeas my logic depends on the body to be empty when no inputs are provided). Any help would be greatly appreciated! Thanks,Ted Jones-Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] ]Sent: Friday, June 23, 2006 2:20 PMTo: axis-user@ws.apache.org Subject: Re: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)Good Afternoon Ted-Could we see the WSDL?Thanks,MartinThis 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
RE: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)
IP VP, I encountered the same thing (or something very similar) with Axis 1.3. I was hoping an upgrade to Axis2 would fix my problem. Have you had any luck resolving? Thanks, Ted Jones -Original Message- From: ip vp [mailto:[EMAIL PROTECTED] Sent: Thursday, June 22, 2006 4:28 PM To: axis-user@ws.apache.org Subject: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681) Importance: High Hi all, I am trying to call a comercial partner webservice thats return a string and do not need input parameters. Based on User guide ( Client for echoVoid Operation) I am doing the followig: - generating java code based on wsdl, using ecplise plugin. - did a very simple client whit the following code: GeneratedStubClass myStub = new GeneratedStubClass(); System.out.println(myStub.MethodWithOperationName()); I am getting the following error: java.lang.NullPointerException at org.apache.axis2.context.MessageContext.setEnvelope(MessageContext.java:681) This error occurs with all variants of WSDL2JAVA configuration: with and without databinds, using get, using post, using soap... What am I doing wrong ? thanks in advance IP VP _ Você sabe em qual Copa o Pelé vestiu a camisa 10 pela 1a. vez? http://copa.br.msn.com/extra/curiosidades/1958/ - 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: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)
Martin, Here is the WSDL:definitions name="widgetServices" targetNamespace="http://com.widgets/test" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://com.widgets/test" xmlns:schema1="http://www.widgets.com/bqt_Output" types xsd:schema targetNamespace="http://com.widgets/test" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xsd:import namespace="http://www.widgets.com/bqt_Output" schemaLocation="http://chicago:8080/test/servlet/ArtifactDocumentService/test/bqt_Output.xsd" / /xsd:schema /types message name="bqt_SMALLA_getSMALLA_Input" documentationInput message for operation bqt_SMALLA/getSMALLA./documentation /message message name="bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" documentationOutput message for operation bqt_SMALLA/getSMALLA./documentation part name="bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" element="schema1:SMALLA_Output" / /message portType name="bqt_SMALLA" operation name="getSMALLA" input name="Input" message="tns:bqt_SMALLA_getSMALLA_Input" / output name="SMALLA_OutputMsg" message="tns:bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" / /operation /portType binding name="bqt_SMALLA" type="tns:bqt_SMALLA" soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" / operation name="getSMALLA" soap:operation style="document" soapAction="bqt_WS.bqt_SMALLA.getSMALLA" / input name="Input" soap:body use="literal" / /input output name="SMALLA_OutputMsg" soap:body use="literal" / /output /operation /binding service name="widgetsDataServices" port name="bqt_SMALLA" binding="tns:bqt_SMALLA" soap:address location="http://chicago:8080/test/services/service" / /port /service/definitionsHere is the WSDD:deployment name="test" xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" !-- note that either style="message" OR provider="java:MSG" both work -- service name="service" provider="java:MSG" parameter name="className" value="com.widgets.soap.lds.service.DataServiceWebService" / parameter name="allowedMethods" value="executeDataservice" / /service/deployment I am executing a web service with no input parametersso the SOAP body is empty like so: soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" soapenv:Body//soapenv:Envelope I am getting an NPE returned before I even hit my Web Service, so I am assuming the exception is happening in Axis somewhere (I'm not seeing a stack trace). Here is the response: ?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/ /soapenv:Fault/soapenv:Body/soapenv:Envelope I get this using Coral and Systinet as my clients. When I generate an Axis client, I do not get an NPE but I get a node added to my body with the operation name in it (which I don't want to seeas my logic depends on the body to be empty when no inputs are provided). Any help would be greatly appreciated!Thanks,Ted Jones-Original Message-From: Martin Gainty [mailto:[EMAIL PROTECTED]]Sent: Friday, June 23, 2006 2:20 PMTo: axis-user@ws.apache.orgSubject: Re: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)Good Afternoon Ted-Could we see the WSDL?Thanks,MartinThis 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: "Ted Jones" [EMAIL PROTECTED]To: axis-user@ws.apache.orgSent: Friday, June 23, 2006 2:30 PMSubject: RE: NullPointerException inMessageContext.setEnvelope(MessageContext.java:681)IP VP,I encountered the same thing (or something very similar) with Axis 1.3. I was hoping an upgrade to Axis2 would fix my problem. Have you had any luck resolving?Thanks,Ted Jones-Original Message-From: ip vp [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 22, 2006 4:28 PMTo: axis-user@ws.apache.org
RE: Dynamic Proxy
Thanks for the reply Martin. I am trying to avoid generating stubs (not an option for me). I want to execute dynamically at runtime for a given wsdl. Is this possible with Axis2? I know you can do it with Systinet. Thanks, Ted From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 21, 2006 5:48 PMTo: axis-user@ws.apache.orgSubject: Re: Dynamic Proxy Good Evening Ted- If you already have the WSDL then you can run the Java2WSDL utility to generate the required stubs e.g. org.apache.axis.wsdl.WSDL2Java Whatever.wsdl HTH,Martin *This email message and any files transmitted with it contain confidentialinformation intended only for the person(s) to whom this email message isaddressed. If you have received this email message in error, please notifythe sender immediately by telephone or email and destroy the originalmessage without making a copy. Thank you. - Original Message - From: Ted Jones To: axis-user@ws.apache.org Sent: Wednesday, June 21, 2006 5:25 PM Subject: Dynamic Proxy Can someone please point me to some example code for a dynamic proxy in Axis2? I have a wsdl url and just want to set the operation and parameters via code. Thanks, Ted Jones
