Re: Axis2 Deployment Model Deficiency
Dims, I tried the latest nightly from 06-15. It still does not work. I simply took the axis2.war, renamed addressing-SNAPSHOT.mar inside it to addressing.mar, and deployed it in WebLogic 9.1. It gave me the following error on startup about not being able to load the referenced addressing module. I then removed the addressing module reference from axis2.xml and tried it again. It came up fine now, but I still don't see the Version service, which is part of Axis2.war, in the Axis admin console. I took a peek at the source code in WarBasedAxisConfigurator. I don't see any code that handles the case when getServletContext().getRealPath() == null. So it looks like this is not yet implemented. Here's the error about not being able to load the addressing module: Jun 15, 2006 11:38:32 AM EDT Error HTTP BEA-101216 Servlet: AxisServlet failed to preload on startup in Web application: axis2.war. org.apache.axis2.deployment.DeploymentException: Trying to engage a module which is not available : addressing; nested exception is: org.apache.axis2.AxisFault: Trying to engage a module which is not available : addressing at org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:147) at org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon figurator.java:213) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura tionContextFactory.java:56) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:235) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:203) Truncated. see log file for complete stacktrace org.apache.axis2.AxisFault: Trying to engage a module which is not available : addressing at org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:301) at org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:766) at org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:143) at org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon figurator.java:213) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura tionContextFactory.java:56) Thanks, Junaid Davanum Srinivas [EMAIL PROTECTED] To maxis-user@ws.apache.org cc 06/14/2006 11:43 AMSubject Re: Axis2 Deployment Model Deficiency Please respond to [EMAIL PROTECTED] he.org Junaid, Did you try latest nightly? I believe this is fixed. thanks, dims On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Here's my scenario which I believe might be a common requirement for a lot of enterprise applications. I'm trying to bundle Axis2 webapp as part of a bigger EAR application and deploy in an application server such as WebLogic. I would like to package up all of the Web Services inside of the webapp/EAR file. The problem is that Axis2 cannot seem to load the services from within the EAR file in WebLogic.. The issue arises due to the fact that Axis2 relies on the concept of a repository, which MUST be a folder on the file system. On certain application servers like WebSphere, this is not an issue since they internally explode the EAR when you deploy it and Axis2 does not seem to have a problem. However application servers like WebLogic do NOT explode the EAR, hence Axis2 cannot find/load the services from the repository. Here is the offending code in WarBasedAxisConfigurator: repository = config.getServletContext().getRealPath(/WEB-INF); --- this returns null in Weblogic axis2Steram = new FileInputStream(repository + /conf/axis2.xml); There are 2 work-arounds as I understand it: 1) Always deploy the application in an exploded format (WebLogic provides this feature). However this is not
Re: Axis2 Deployment Model Deficiency
Done. http://issues.apache.org/jira/browse/AXIS2-822 Thanks, Junaid Davanum Srinivas [EMAIL PROTECTED] To maxis-user@ws.apache.org cc 06/15/2006 12:20 PMSubject Re: Axis2 Deployment Model Deficiency Please respond to [EMAIL PROTECTED] he.org Could u please log a bug so that we can track it? thanks, dims On 6/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Dims, I tried the latest nightly from 06-15. It still does not work. I simply took the axis2.war, renamed addressing-SNAPSHOT.mar inside it to addressing.mar, and deployed it in WebLogic 9.1. It gave me the following error on startup about not being able to load the referenced addressing module. I then removed the addressing module reference from axis2.xml and tried it again. It came up fine now, but I still don't see the Version service, which is part of Axis2.war, in the Axis admin console. I took a peek at the source code in WarBasedAxisConfigurator. I don't see any code that handles the case when getServletContext().getRealPath() == null. So it looks like this is not yet implemented. Here's the error about not being able to load the addressing module: Jun 15, 2006 11:38:32 AM EDT Error HTTP BEA-101216 Servlet: AxisServlet failed to preload on startup in Web application: axis2.war. org.apache.axis2.deployment.DeploymentException: Trying to engage a module which is not available : addressing; nested exception is: org.apache.axis2.AxisFault: Trying to engage a module which is not available : addressing at org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:147) at org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon figurator.java:213) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura tionContextFactory.java:56) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:235) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:203) Truncated. see log file for complete stacktrace org.apache.axis2.AxisFault: Trying to engage a module which is not available : addressing at org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:301) at org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:766) at org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:143) at org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon figurator.java:213) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura tionContextFactory.java:56) Thanks, Junaid Davanum Srinivas [EMAIL PROTECTED] To maxis-user@ws.apache.org cc 06/14/2006 11:43 AM Subject Re: Axis2 Deployment Model Deficiency Please respond to [EMAIL PROTECTED] he.org Junaid, Did you try latest nightly? I believe this is fixed. thanks, dims On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Here's my scenario which I believe might be a common requirement for a lot of enterprise applications. I'm trying to bundle Axis2 webapp as part of a bigger EAR application and deploy in an application server such as WebLogic. I would like to package up all of the Web Services inside of the webapp/EAR file. The problem is that Axis2 cannot seem to load the services from within the EAR file in WebLogic.. The issue arises due to the fact that Axis2 relies on the concept of a repository, which MUST be a folder on the file system. On certain application servers like
Re: How to load custom configuration (EngineConfiguration)
You can use the following system property to specify the EngineConfigurationFactory. This EngineConfigurationFactory should return an instance of your custom configuration. -Daxis.EngineConfigFactory=your_engineConfigFactory_Classname - Junaid Nicolas-Viet Nguyen [EMAIL PROTECTED] To il.com axis-user axis-user@ws.apache.org cc 06/15/2006 08:44 PMSubject How to load custom configuration (EngineConfiguration) Please respond to [EMAIL PROTECTED] he.org Hello All, If I write my own Configuration to load my handlers, say MyClientConfig, how can I enable axis to load this configuration instead of using the default FileProvider as start up? I am using axis1.4 Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 Deployment Model Deficiency
Hi, Here's my scenario which I believe might be a common requirement for a lot of enterprise applications. I'm trying to bundle Axis2 webapp as part of a bigger EAR application and deploy in an application server such as WebLogic. I would like to package up all of the Web Services inside of the webapp/EAR file. The problem is that Axis2 cannot seem to load the services from within the EAR file in WebLogic.. The issue arises due to the fact that Axis2 relies on the concept of a repository, which MUST be a folder on the file system. On certain application servers like WebSphere, this is not an issue since they internally explode the EAR when you deploy it and Axis2 does not seem to have a problem. However application servers like WebLogic do NOT explode the EAR, hence Axis2 cannot find/load the services from the repository. Here is the offending code in WarBasedAxisConfigurator: repository = config.getServletContext().getRealPath(/WEB-INF); --- this returns null in Weblogic axis2Steram = new FileInputStream(repository + /conf/axis2.xml); There are 2 work-arounds as I understand it: 1) Always deploy the application in an exploded format (WebLogic provides this feature). However this is not an option for us. 2) Use a repository folder OUTSIDE of the EAR by specifiying the axis2.xml.path in web.xml. However this option also poses a problem in a cluster scenario where you need to have a common accessible folder, which will serve as the repository and EVERY machine in the cluster must be mapped to this common folder. It's a setup maintenance headache. I worked previously with Axis 1.x and it did not have a problem loading services from within the EAR file. Ofcourse any changes you make to the configuration while it was running would be lost on a server re-start (since server-config.wsdd was read-only). But it still worked. I believe this is a critical change that is needed and should be addressed in the next version, unless I'm missing something here. Let me know if I should open up an enhancement request JIRA. Thanks, Junaid - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Deployment Model Deficiency
Dims, I haven't tried the latest nightly. I'll give it a shot. Thanks, Junaid Davanum Srinivas [EMAIL PROTECTED] To maxis-user@ws.apache.org cc 06/14/2006 11:43 AMSubject Re: Axis2 Deployment Model Deficiency Please respond to [EMAIL PROTECTED] he.org Junaid, Did you try latest nightly? I believe this is fixed. thanks, dims On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Here's my scenario which I believe might be a common requirement for a lot of enterprise applications. I'm trying to bundle Axis2 webapp as part of a bigger EAR application and deploy in an application server such as WebLogic. I would like to package up all of the Web Services inside of the webapp/EAR file. The problem is that Axis2 cannot seem to load the services from within the EAR file in WebLogic.. The issue arises due to the fact that Axis2 relies on the concept of a repository, which MUST be a folder on the file system. On certain application servers like WebSphere, this is not an issue since they internally explode the EAR when you deploy it and Axis2 does not seem to have a problem. However application servers like WebLogic do NOT explode the EAR, hence Axis2 cannot find/load the services from the repository. Here is the offending code in WarBasedAxisConfigurator: repository = config.getServletContext().getRealPath(/WEB-INF); --- this returns null in Weblogic axis2Steram = new FileInputStream(repository + /conf/axis2.xml); There are 2 work-arounds as I understand it: 1) Always deploy the application in an exploded format (WebLogic provides this feature). However this is not an option for us. 2) Use a repository folder OUTSIDE of the EAR by specifiying the axis2.xml.path in web.xml. However this option also poses a problem in a cluster scenario where you need to have a common accessible folder, which will serve as the repository and EVERY machine in the cluster must be mapped to this common folder. It's a setup maintenance headache. I worked previously with Axis 1.x and it did not have a problem loading services from within the EAR file. Ofcourse any changes you make to the configuration while it was running would be lost on a server re-start (since server-config.wsdd was read-only). But it still worked. I believe this is a critical change that is needed and should be addressed in the next version, unless I'm missing something here. Let me know if I should open up an enhancement request JIRA. Thanks, Junaid - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://wso2.com/blogs/ - 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 2 example web service fails
The first child element of SOAP Body (echo) is not namespace qualified. - Junaid Scudder, Jeffrey W Jeffrey.W.Scudde To [EMAIL PROTECTED] axis-user@ws.apache.org cc 06/01/2006 01:58 PMSubject Axis 2 example web service fails Please respond to [EMAIL PROTECTED] he.org Hello all, I sent out an email a week ago and am resubmitting my question. I am getting an exception in Tomcat when running Axis2 1.0 with the example service from the user's guide. I had previously followed the example for Axis 0.95 and everything worked perfectly. With 1.0 I had to change the libraries used in my code and I eventually started from a clean slate trying to track down the cause of this problem. I wrote a web service in java, packaged into an .aar and dropped it into Axis2. I have also written a simple client which sends a SOAP:Envelope to invoke the echo service. When I send the following xml: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:BodyechotestHello Axis2/test/echo /soapenv:Body /soapenv:Envelope I receive the following response from the server: Error reading response from service provider: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/axis2/services/JeffService A peek into the Tomcat logs reveals the following exception stack trace: - Servlet.service() for servlet AxisServlet threw exception org.apache.axiom.om.OMException: SOAPEnvelope must contain a body element which is either first or second child element of the SOAPEnvelope. at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getBody(SOAPEnvelopeImp l.java:142) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.addChild(SOAPEnvelopeIm pl.java:103) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeI mpl.java:82) at org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine. java:183) at org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java :168) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1 48) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86 9) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc essConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint .java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow erWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:684) at java.lang.Thread.run(Unknown Source) - Servlet.service() for servlet jsp threw exception java.lang.IllegalStateException: getOutputStream() has already been called for this response at org.apache.catalina.connector.Response.getWriter(Response.java:599) at
RE: Axis 2 example web service fails
Can you post the WSDL? Did you try and see if the namespace that you are using matches the one in the WSDL? - Junaid Scudder, Jeffrey W Jeffrey.W.Scudde To [EMAIL PROTECTED] axis-user@ws.apache.org cc 06/01/2006 05:07 PMSubject RE: Axis 2 example web service fails Please respond to [EMAIL PROTECTED] he.org Since the test service I wrote was in the following package: package scudder.jeff I modified the message sent from the client to add a namespace. It is now: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Bodyjst:echo xmlns:jst=http://jeff.scudder;Hello Axis2/jst:echo /soapenv:Body /soapenv:Envelope But I still get exactly the same error from the client and the same error in the tomcat logs. The first line of tomcat's exception stack says: SOAPEnvelope must contain a body element which is either first or second child element of the SOAPEnvelope. Which makes me think that the problem occurs before the contents of the soap body are ever examined. Thank you, Jeff Scudder -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 11:09 AM To: axis-user@ws.apache.org Subject: Re: Axis 2 example web service fails The first child element of SOAP Body (echo) is not namespace qualified. - Junaid Scudder, Jeffrey W Jeffrey.W.Scudde To [EMAIL PROTECTED] axis-user@ws.apache.org cc 06/01/2006 01:58 PM Subject Axis 2 example web service fails Please respond to [EMAIL PROTECTED] he.org Hello all, I sent out an email a week ago and am resubmitting my question. I am getting an exception in Tomcat when running Axis2 1.0 with the example service from the user's guide. I had previously followed the example for Axis 0.95 and everything worked perfectly. With 1.0 I had to change the libraries used in my code and I eventually started from a clean slate trying to track down the cause of this problem. I wrote a web service in java, packaged into an .aar and dropped it into Axis2. I have also written a simple client which sends a SOAP:Envelope to invoke the echo service. When I send the following xml: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:BodyechotestHello Axis2/test/echo /soapenv:Body /soapenv:Envelope I receive the following response from the server: Error reading response from service provider: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/axis2/services/JeffService A peek into the Tomcat logs reveals the following exception stack trace: - Servlet.service() for servlet AxisServlet threw exception org.apache.axiom.om.OMException: SOAPEnvelope must contain a body element which is either first or second child element of the SOAPEnvelope. at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getBody(SOAPEnvelopeImp l.java:142) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.addChild(SOAPEnvelopeIm pl.java:103) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeI mpl.java:82) at org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine. java:183) at org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java :168) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:252) at
Re: Axis2[1.0] war in Weblogic 9.1
If you are interested in distributing Axis2 with a set of fixed pre-deployed services/modules, you can try to put those services/modules directly within the war, and deploy the modified war. I doubt if this will work in all containers since Axis2 relies on the repository being a regular folder on the file system. As you said, it's up to the container to explode the war internally (I believe WebSphere explodes it while WebLogic 9.1 does not). There are basically 2 options as I understand: 1)Deploy as an exploded war 2)Deploy as a war/ear and specifiy the paths to Axis2 repository and axis2.xml via the following properties in web.xml: init-param param-nameaxis2.xml.path/param-name param-valueC:\Axis2\repository\axis2.xml/param-value /init-param init-param param-nameaxis2.repository.path/param-name param-valueC:\Axis2\repository/param-value /init-param -Junaid Rodrigo Ruiz [EMAIL PROTECTED] s.com To axis-user@ws.apache.org 05/26/2006 04:38 cc AM Subject Re: Axis2[1.0] war in Weblogic 9.1 Please respond to [EMAIL PROTECTED] he.org Hi, The behaviour you describe is perfectly normal with regard to the Servlet Specification. When deploying Axis 2 as a war, the container is not creating a read-write directory structure, and peforms all accesses directly through the war archive, instead of unpacking it. Whether to unpack the WAR or not is up to the container implementation, and the specification allows both options. If you are interested in distributing Axis 2 with a set of fixed pre-deployed services/modules, you can try to put those services/modules directly within the war, and deploy the modified war. I am not sure at all if this will work in the current version as, AFAIK, Axis 2 uses custom classloaders for isolating services that might not work in this mode. Anyway, I don't see any technical reason why this should not be possible. In any case, deploying it as an exploded war is the correct way to prevent those errors. Hope this helps, Rodrigo Ruiz Ali Sadik Kumlali wrote: Hi Gopal, The same problem exists with WL8.1 SP4. What I saw there, when the war is uploaded by using console application, war is not totally extracted. Only some of subfolders and the files are extracted. May be the same extraction problem exists on WL9.1, too. I don't know why this happens, though. Regards, Ali Sadik Kumlali */Gopal Patwa [EMAIL PROTECTED]/* wrote: I tried axis2.war deploying on weblogic 9.1 as war, deployment was sucessful but unable to load version service. But if I use exploded war it works.. Any idea why it's happening, did any one had success runing axis2.war under weblogic 9.1 Thanks Gopal -- View this message in context: http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4571990 Sent from the Axis - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call rates. http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.7.1/348 - Release Date: 25/05/2006 http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com -- --- GRIDSYSTEMSRodrigo Ruiz Aguayo Parc Bit - Son Espanyol 07120 Palma de Mallorca
Re: Mentioning namespace for the SOAP Message
Suyog, The WSDL generation has apparently been fixed as per: http://issues.apache.org/jira/browse/AXIS2-721 Check if this also fixes your original problem of namespace mismatch for the Response returned from the Web Service invocation. - Junaid Anne Thomas Manes [EMAIL PROTECTED] To maxis-user@ws.apache.org cc 05/25/2006 08:54 AMSubject Re: Mentioning namespace for the SOAP Message Please respond to [EMAIL PROTECTED] he.org It's a bug. I believe it's been fixed in the latest build. Anne On 5/24/06, Suyog Gandhi [EMAIL PROTECTED] wrote: This WSDL is created by Axis2 upon the deploy of .aar file. How do I avoid that namespace attribute? Is there some kind of setting in some file? On Wed, 24 May 2006 20:39:14 -0400 Anne Thomas Manes [EMAIL PROTECTED] wrote: You must remove the namespace attributes from your binding definitions, e.g., body definitions should be: soap:body use=literal / Make sure you're using the latest build of Axis2. Anne On 5/24/06, Suyog Gandhi [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Can somebody tell me how to set the namespace for the soap message on server side? I wrote my java file, created service.xml and deployed the .aar. Please find atached wsdl file. I am getting 2 different namesspaces for request and response, due to which I am getting Data Binding Error on the client side. SOAP Request: Note the name space for getDimensionNames ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body getDimensionNames xmlns= http://webs.shared.clemenza.vistaar.com/xsd http://webs.shared.clemenza.vistaar.com/xsd/ /soapenv:Body /soapenv:Envelope SOAP Reply (Upon successful server side execution) : Note the name space for getDimensioNamesResponse ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/ soapenv:Header / soapenv:Body ns:getDimensionNamesResponse xmlns:ns= http://org.apache.axis2/xsd http://org.apache.axis2/xsd returnPart/return returnKit/return returnCustomer/return returnTime/return returnSales Type/return returnCampaign/return returnDiscount Table/return returnDiscount Code/return returnCurrency/return returnVersion/return returnEngine/return returnWhatIf/return returnMeasures/return /ns:getDimensionNamesResponse /soapenv:Body /soapenv:Envelope - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[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: Buggy .aar deployment
Jeff,
You are using the RawXMLINOutMessageReceiver. I believe in Axis2 1.0,
automatic WSDL generation only happens when you use the RPCMessageReceiver.
If you need to use RawXMLINOutMessageReceiver, then you have generate the
WSDL yourself and drop it in the META-INF folder.
- Junaid
robert lazarski
[EMAIL PROTECTED]
mail.com To
axis-user@ws.apache.org
05/25/2006 01:15 cc
PM
Subject
Re: Buggy .aar deployment
Please respond to
[EMAIL PROTECTED]
he.org
Post the stack trace for the 500 error and maybe we can help. The rules
changed for displaying a wsdl in the 1.0 release - search the forums with
the message for more info.
HTH,
Robert
http://www.braziloutsource.com/
On 5/24/06, Scudder, Jeffrey W [EMAIL PROTECTED] wrote:
Hi all,
I had previously deployed a web service as a .aar file in Axis2 version
0.95 and the service broke when I upgraded to 1.0
I rewrote the code for version 1.0 (libraries changed from 0.95 to 1.0)
changed services.xml to fit the new example on the Axis2 website, and
redeployed the .aar. Unfortunately the service I created does not work.
When I attempt to view the WSDL on localhost:8080/axis2 I get the
following message:
error
descriptionUnable to generate WSDL for this service/description
−
reason
Either user has not dropped the wsdl into META-INF or operations use
message receivers other than RPC.
/reason
/error
The same message appears when I attempt to view WSDLs for most of the
example web services which come with the Axis2 download. When I attempt
to use my service, I receive an HTTP 500 error code.
I am using Tomcat 5.5.17 and the services.xml and code I am using are
copied below. Is there something I am doing wrong, are there unresolved
version compatibility issues? Any help is greatly appreciated
Thank you,
Jeff Scudder
services.xml
service
description
This is Jeff's sample Web Service with two operations, echo and
ping.
/description
parameter name=ServiceClass locked=falseJeffService/parameter
operation name=echo
messageReceiver class=
org.apache.axis2.receivers.RawXMLINOutMessageReceiver/
actionMappingurn:echo/actionMapping
/operation
operation name=ping
messageReceiver class=
org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/
actionMappingurn:ping/actionMapping
/operation
/service
JeffService.java
import org.apache.axiom.om.*;
public class JeffService {
public void ping(OMElement element){
return;
}
public OMElement echo(OMElement element){
return element;
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Providing custom WSDL
Deepal, I have already created JIRAs for both of these issues last week. http://issues.apache.org/jira/browse/AXIS2-721 http://issues.apache.org/jira/browse/AXIS2-722 Thanks, Junaid Deepal Jayasinghe [EMAIL PROTECTED] e.lk To axis-user@ws.apache.org 05/21/2006 02:16 cc PM Subject Re: [Axis2] Providing custom WSDL Please respond to [EMAIL PROTECTED] he.org Hi Junaid pls see my comments below; [EMAIL PROTECTED] wrote: Hi all, I'm deploying my Web Service using the RawXMLINOutMessageReceiver and providing my own WSDL in the META-INF folder. However the WSDL that is returned from the ?wsdl URL is different than the original one, specifically the wsdl:binding and wsdl:service portions are changed. What is the rationale behind this? I can see that 2 additional bindings have been added, SOAP12 as well as REST. However I see a couple of problems: At the deploy time Axis2 read original wsdl and ignore its wsdl:binding and wsdl:service . At the runtime it generate them. 1) The soap:body element specifies a namespace even though it is a doc/literal binding. This is disallowed explicitly by the WS-I Basic Profile 1.1 http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Namespaces_for_soapbind_Elements hmm, need to fix this. Can you please create a JIRA so that we will definitely fix that before next release. 2) The bigger issue though is the endpoint addresses. I'm integrating Axis2 webapp within my larger application (EAR) and would like to use a different webapp context than 'axis2'. However the endpoint addresses in the generated WSDL have axis2 hard-coded in them are of the form http://machine:80/axis2/services/MyService There are few JIRAs on this issue , we will definitely fix them before next release. even though my Web Service is deployed at a different URL and the original WSDL that I provided had the correct endpoint address http://machine:80/mywebapp/services/MyService - Junaid -- Thanks, Deepal ~Future is Open~ - 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] Providing custom WSDL
Hi all, I'm deploying my Web Service using the RawXMLINOutMessageReceiver and providing my own WSDL in the META-INF folder. However the WSDL that is returned from the ?wsdl URL is different than the original one, specifically the wsdl:binding and wsdl:service portions are changed. What is the rationale behind this? I can see that 2 additional bindings have been added, SOAP12 as well as REST. However I see a couple of problems: 1) The soap:body element specifies a namespace even though it is a doc/literal binding. This is disallowed explicitly by the WS-I Basic Profile 1.1 http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Namespaces_for_soapbind_Elements 2) The bigger issue though is the endpoint addresses. I'm integrating Axis2 webapp within my larger application (EAR) and would like to use a different webapp context than 'axis2'. However the endpoint addresses in the generated WSDL have axis2 hard-coded in them are of the form http://machine:80/axis2/services/MyService even though my Web Service is deployed at a different URL and the original WSDL that I provided had the correct endpoint address http://machine:80/mywebapp/services/MyService - Junaid
Re: [Axis2] Providing custom WSDL
Done. http://issues.apache.org/jira/browse/AXIS2-721 http://issues.apache.org/jira/browse/AXIS2-722 Thanks, Junaid Davanum Srinivas [EMAIL PROTECTED] To maxis-user@ws.apache.org cc 05/12/2006 12:22 PMSubject Re: [Axis2] Providing custom WSDL Please respond to [EMAIL PROTECTED] he.org Junaid, wsdl:binding and wsdl:service are changed on purpose as the details are specific to the server in which the service is deployed. Please do however log separate bugs for #1 and #2 below thanks, dims On 5/12/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi all, I'm deploying my Web Service using the RawXMLINOutMessageReceiver and providing my own WSDL in the META-INF folder. However the WSDL that is returned from the ?wsdl URL is different than the original one, specifically the wsdl:binding and wsdl:service portions are changed. What is the rationale behind this? I can see that 2 additional bindings have been added, SOAP12 as well as REST. However I see a couple of problems: 1) The soap:body element specifies a namespace even though it is a doc/literal binding. This is disallowed explicitly by the WS-I Basic Profile 1.1 http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Namespaces_for_soapbind_Elements 2) The bigger issue though is the endpoint addresses. I'm integrating Axis2 webapp within my larger application (EAR) and would like to use a different webapp context than 'axis2'. However the endpoint addresses in the generated WSDL have axis2 hard-coded in them are of the form http://machine:80/axis2/services/MyService even though my Web Service is deployed at a different URL and the original WSDL that I provided had the correct endpoint address http://machine:80/mywebapp/services/MyService - Junaid -- Davanum Srinivas : http://wso2.com/blogs/
Re: Problem deploying axis
You can work around this problem by setting the following property for AdminService in server-config.wsdd to enable remote deployment. parameter name=enableRemoteAdmin value=true/ - Junaid Santunu Podder [EMAIL PROTECTED] com To axis-user@ws.apache.org 04/27/2006 05:49 cc AM Subject Problem deploying axis Please respond to [EMAIL PROTECTED] he.org Hi there, I am facing a problem deploying Axis on a linux server having a dual IP address. This is due to Axis's restriction of only allowing deployment from localhost. The server, I am trying to deploy on has 2 IP addresses and this is confusing AXIS into thinking that its a remote deployment. Has anyone faced this issue and if could let me know a probably solution. Thanks in advance, Santunu This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.
Re: Making operations with no output type synchronous
Define the WSDL operation with both input and output messages. Define the output message as being empty with no parts: message name=MyOutputMessage / - Junaid Stefan Freyr Stefansson [EMAIL PROTECTED] To is axis-user@ws.apache.org cc 04/06/2006 09:30 AMSubject Making operations with no output type synchronous Please respond to [EMAIL PROTECTED] he.org Hello. I've been trying to run a single JUnit method that calls an Axis web service operation. The operation receives one input parameter but there's no output defined. The JUnit test case uses the classes generated by wsdl2java to lookup the service and call the operation like so: MyClass_ServiceLocator locator = new MyClass_ServiceLocator(); MyClass_PortType service = locator.getMyClass(new URL(SERVICE_URL)); MyOperationRequest request = new MyOperationRequest(Some data...); service.myOperation(request); For some reason this didn't work and I got no error out on the screen. I later found out that this was because the JUnit test case called the myOperation asynchronously and managed to finish and kill the JVM before the stuff behind it (the stuff Axis generates) managed to actually even send out a request. So my question is: Can I define a void operation in WSDL without Axis generating code that calls it asynchronously? Kind regards, Stefan Freyr. p.s. I'm using Axis 1.2.1 (See attached file: att26p98.dat) att26p98.dat Description: Binary data
Junaid Bhatra is out of the office.
I will be out of the office starting 03/22/2006 and will not return until 03/24/2006. I will respond to your message when I return.
Re: Axis 1.3 document literal and no parts in the message
As per your WSDL (message with no parts), for doc/literal style, the correct SOAP message should be an empty SOAP body, with no child elements. However that being said, if this is an input message, I'm not sure if it makes much sense to send an empty SOAP message to the server, since the server can only dispatch based on the QName of SOAP body child element (not sure if the server has the ability to dispatch based on an empty QName). But if this were an output message, then it's fine to expect an empty SOAP body, which would model a void return type from your service method. Regardless, this does look like a bug if you are using doc/literal style. Maybe Anne (or someone else) can comment further on this. - Junaid Lars Torunski [EMAIL PROTECTED] ne.de To axis-user@ws.apache.org 03/16/2006 03:56 cc PM Subject Axis 1.3 document literal and no Please respond to parts in the message [EMAIL PROTECTED] he.org I got stuck in a discussion between two consultants if Axis 1.3 fulfills the WSDL 1.1 specification for document/literal correctly. Consultant 1: Taken from http://www.w3.org/TR/wsdl#_messages (2.3 Messages) the message is defined by Messages consist of one or more logical parts.. Consultant 2: On the other hand the WSDL schema definition in http://www.w3.org/TR/wsdl#A4.1 defines wsdl:part with element ref=wsdl:part minOccurs=0 maxOccurs=unbounded/ Consultant 1: This maybe contradictory, but this is because WSDL may use either by rpc or document styles. Per RPC, of course, message may be without any part. Unfortunately, this is not the case with document style. For document style only the message part are sent. No other leading information is used. Thus, the inner message-parts in this case are must. One MUST NOT discard message-parts when document style is used. Me: We have a message getAllSectors defined as wsdl:message name=getAllSectorsRequest /wsdl:message Thus, no part is defined. Axis 1.3 create the following http request: ?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:BodygetAllSectors xmlns=urn:remote.ws.mycompany.org//soapenv:Body/soapenv:Envelope What do you think? Is there a problem in our wsdl file or is this a bug in Axis 1.3 by using document/literal?
Re: How to Deploy Axis1.3 webservice on HTTPS enabled Tomcat server
See the section on Security in the Axis Wiki http://wiki.apache.org/ws/FrontPage/Axis It has a section on deploying and accessing Web Services over SSL - Junaid Rhimbo [EMAIL PROTECTED] To axis-user@ws.apache.org 03/11/2006 04:49 cc PM Subject Re: How to Deploy Axis1.3 Please respond to webservice on HTTPS enabled Tomcat [EMAIL PROTECTED] server he.org Hi Mohit, I don't really know the answer to your question but I did see something on this page: http://ws.apache.org/axis/java/building-axis.html Under Building with JSEE it says this: This is needed for https support. 1. Download the required Class libraries (jsse.jar, jnet.jar,jcert.jar) to $(axis.home)/java/lib. You can download this from http://java.sun.com/products/jsse/ Recommended version : 1.0.3 I don't know if this helps. Sorry. Vartan --- Mohit_Goyal [EMAIL PROTECTED] wrote: Hi all... i have developed a webservice which needs to be deployed over https on Tomcat 5 server. I tried using the same stepa which we follow for a regular deployment over http but i keep getting exceptions when running the java org.apache.axis.client.AdminClient -lhttps://domain:443/axis/services/Servicename deploy.wsdd Can anyone who has done deployment over Tomcat or faced similar problem tell me what steps to follow to deploy the service over https Thanks a lot in advance Mohit DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: Ploblem in deploying Axis1.3 document based web service over HTTPS
The AdminClient internally makes a Web Service call to the AdminService (on
the server) for the purposes of deployment/undelpoyment. So you still need
to worry about the SSL certificate if you use the https URL for deployment.
Alternatively you could use the regular http URL for deployment first, then
worry about setting up the certificate later.
- Junaid
Mohit_Goyal
[EMAIL PROTECTED]
am.comTo
axis-user@ws.apache.org
03/09/2006 02:19 cc
PM
Subject
RE: Ploblem in deploying Axis1.3
Please respond to document based web service over
[EMAIL PROTECTED] HTTPS
he.org
Thanks for the reply.. but rite now am not concerned about the client... i
currently want to deploy my service on the server first...
From: [EMAIL PROTECTED] on behalf of Cyrille Le Clerc
Sent: Thu 3/9/2006 11:30 PM
To: axis-user@ws.apache.org
Subject: Re: Ploblem in deploying Axis1.3 document based web service over
HTTPS
Hi Mohit,
It looks like the SSL certificate of your server is not trusted by
your client. For instance, this occurs with self-signed certificates.
Connecting to a non-trusted SSL server from an Axis client is
described in Axis wiki. You have to use the SunFakeTrustSocketFactory
:
http://wiki.apache.org/ws/FrontPage/Axis/AxisClientConfiguration/Ssl
Hope this helps,
Cyrille
--
Cyrille Le Clerc
[EMAIL PROTECTED]
[EMAIL PROTECTED]
On 3/9/06, Mohit_Goyal [EMAIL PROTECTED] wrote:
Hi all,
I developed a document based web service using Axis1.3 and it was working
fine when I deployed it on simple http endpoint on tomcat 5. But when I
regenerated the wsdl for https endpoint address and tried to deploy it
using the following commands, it throws an AxisFault. I have tried
deploying it using the following commands:
java org.apache.axis.client.AdminClient deploy.wsdd
Exception: AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection refused
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException:
Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
java org.apache.axis.client.AdminClient
-lhttps://address:443/axis/services/Servicename deploy.wsdd
Exception: AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: javax.net.ssl.SSLHandshakeException:
sun.security.validator.Valida
torException: No trusted certificate found
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: No trusted certificate found
I also tried running it with the following options:
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol
-Dhttps.proxyHost=hostname -Dhttps.proxyPort=443
But I received the following exception:
Exception: AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException: Unexpected EOF from proxy
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.io.IOException:
Unexpected EOF from proxy
at
org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:156)
at
org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
Plz help...
I am stuck because of this for many days... I tried to implement the
steps for creating keystore and modifying the server.xml file for TOMCAT
but nothing worked.
Thanks,
Mohit
DISCLAIMER:
This email (including any attachments) is intended for the sole use of
the intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or
Re: Fwd: WSDD2Java + Admin util for deployment = Undescribably strange error...
If you find a good all-in-one checking tool, please let me know. You can try the Eclipse WTP project. It has a WSDL/XML Schema editor/validator which seems to work well and doesn't choke on WSDL/XSD imports. http://www.eclipse.org/webtools/ - Junaid Dies Koper [EMAIL PROTECTED] com To axis-user@ws.apache.org 03/02/2006 07:53 cc PM Subject Re: Fwd: WSDD2Java + Admin util for Please respond to deployment = Undescribably strange [EMAIL PROTECTED] error... he.org Hello Scott, There are still a bunch of errors in your WSDL and XSD files. Maybe they are not related to the problems you are encountering, but it is also possible that Axis is choking on them and generates incorrect files. #The first problem I noticed was that you put attributes before sequence in complexTypes. Why don't you google for a WSDL and an XML validator and sort them out first? On the WS-I web site there is also a Java-based tool to check whether your WSDL is WS-I BP compliant (it does not check everything, though). I believe the WS-I test tool does not XML validate files. I sometimes use Cape Clear's SOA editor for validating WSDL files, but never got it to check imported WSDL/XSD files. If you find a good all-in-one checking tool, please let me know. Regards, Dies Scott McCoy wrote: -- Forwarded message -- From: Scott McCoy [EMAIL PROTECTED] Date: Mar 2, 2006 11:33 AM Subject: Re: WSDD2Java + Admin util for deployment = Undescribably strange error... To: [EMAIL PROTECTED] I've discovered that relying on the SOAPAction header does not comply with WS-I Standards, but when trying to move to the wrapped document literal syntax, where I have a different document element for each method, I suddenly am not able to properly include my soap header elements. I tried using your suggestion here, attached is a little stub where I tried to do so, using what seems to be your suggestions here. Using another form I was able to get the header element included but that does not unwrap my createAccount method, and I'm unsure as to if it will properly map to the correct method. When trying to simply omit the soapaction attribute from the operation definitions in my previous binding, axis just sort of stops working. Any input would be appreciated, Thanks, Scott S. McCoy On 2/22/06, Anne Thomas Manes [EMAIL PROTECTED] wrote: Scott, there are a bunch of errors in your WSDL. I've corrected a few of them (including notes about the corrections in comments): wsdl:definitions name=urn:Account targetNamespace= http://plm.marchex.com/service/account; xmlns:tns= http://plm.marchex.com/service/account xmlns:typens=http://plm.marchex.com/service/account; xmlns:authns= http://plm.marchex.com/credentials !-- wrong version of XML Schema xmlns:xsd= http://www.w3.org/1999/XMLSchema -- xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/ xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; wsdl:types !-- Use xsd:import or xsd:include to import xsd definitions -- xsd:schema targetNamespace= http://plm.marchex.com/services/account xsd:include schemaLocation=account.xsd/ xsd:import namespace= http://plm.marchex.com/credentials schemaLocation=credentials.xsd/ /xsd:schema /wsdl:types !-- Use wsdl:import only to import wsdl files wsdl:import namespace= http://plm.marchex.com/service/account; location=account.xsd/ wsdl:import namespace= http://plm.marchex.com/credentials; location=credentials.xsd/ -- !-- If you want to use the wrapped convention, then you must define a different set of request and response messages for each operation. The element referenced by the input message part must be a wrapper element
Re: Bug in dateTime handling with Axis 1.2.1?
I faced this bug in Axis 1.1. However this was fixed in 1.2.1 and I don't have this problem anymore (I'm talking client, not the server). Can you check the generated stubs to see if it's using the CalendarSerializer class? CalendarSerializer does generate the correct Schema dateTime representation. Can you post your WSDL as well? - Junaid Ebert, Chris [EMAIL PROTECTED] omTo axis-user@ws.apache.org 02/16/2006 05:56 cc PM Subject Bug in dateTime handling with Axis Please respond to 1.2.1? [EMAIL PROTECTED] he.org Hi all, I have an input that has type xs:dateTime. Axis is serializing the Calendar object to something like Thu Oct 27 17:00:00 PDT 2005. This isn't the format specified in http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime-lexical-rep r, which would look more like 2005-10-27T17:00:00-08:00. My *server* isn't Axis, only the client, and the server doesn't like it. I think this is a bug in Axis -- has it been fixed in some version? Is there some subtlety in the wsdl declaration? Or am I all wet? Chris
Re: generating server-config.wsdd with AdminService's enableRemoteAdmin=true?
Check server-config.wsdd in axis.jar. I believe Axis uses that to create server-config.wsdd first time. Maybe you can modify update this server-config.wsdd with the parameter to true in axis.jar? Thanks, Junaid Nikita Tovstoles Nikita.Tovstoles @Sun.COM To Sent by: axis-user@ws.apache.org Nikita.Tovstoles@ cc Sun.COM Subject generating server-config.wsdd with 11/10/2005 02:08 AdminService's PMenableRemoteAdmin=true? Please respond to [EMAIL PROTECTED] he.org I'm trying to remotely deploy a WAR with axis 1.2.1 embedded onto Sun's SJAS 8.1, and then register a web service using remote call to AdminService. Web service registration fails with a 401, because server-config.wsdd, generated at deploy-time in service AdminService sets: parameter name=enableRemoteAdmin value=false/. Is there anyway to make axis generated server-config.wsdd with the above param set to true? I am not including a pre-created server-config.wsdd, because the value of attachments.Directory property in globalConfiguration seems to be dependent on WAR's deploy directory within app server - that directory is created dynamically at each deployment by SJAS, every time with a different name. thanks -nikita [attachment Nikita.Tovstoles.vcf deleted by Junaid Bhatra/MRO]
Re: SOAPMonitor active/complete status
I believe this is a known bug.See http://issues.apache.org/jira/browse/AXIS-1551- Junaid-"Jarmo Doc" [EMAIL PROTECTED] wrote: -To: axis-user@ws.apache.orgFrom: "Jarmo Doc" [EMAIL PROTECTED]Date: 11/10/2005 05:14PMSubject: SOAPMonitor active/complete statusTypically SOAPMonitor shows all of my service requests with matching responses and a status of 'Complete'. If, however, an operation throws a user-defined exception then SOAPMonitor does not show any response and it shows a status that is permanently 'Active', even if subsequent operations complete normally.Is this a bug in the monitor? Or is it likely that my service is throwing exceptions in the wrong way?PS the client does receive an AxisFault and this does contain the user-defined exception that was thrown by the service so it seems (to me) to be doing the right thing.Thanks._FREE pop-up blocking with the new MSN Toolbar – get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
