Re[2]: [axis2-1.0] Exception-Serialisation Bug with xmlbeans databinding?
Happens also with Axis2SampleDocLit.wsdl from the examples
directory when calling a skeleton method that throws an
UnsupportedOperationException.
- Andreas
am Samstag, 6. Mai 2006 schrieb Davanum Srinivas:
DS Andreas,
DS Please open a jira bug and then upload your wsdl to the bug.
DS thanks,
DS dims
DS On 5/5/06, Andreas Hörnicke [EMAIL PROTECTED] wrote:
Is anyone else having problems with the serialisation of
exceptions when using xmlbeans databinding (worked fine with 0.94
and adb)?
The exception looks like this:
--
public class ServiceException extends AxisFault {
public ServiceException(ServiceFault f) {
super(Integer.toString(f.getCode()), new QName(...), null);
}
}
--
Throwing an instance gives me the following error:
org.apache.axiom.om.OMException
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)
at
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)
at
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)
- Andreas
DS --
DS Davanum Srinivas : http://wso2.com/blogs/
Re: ArrayOf Causing some problems
Seems like you are using databinding. If so post the wsdl and maybe we can help. A stack trace may help too. Robert http://www.braziloutsource.com/On 5/5/06, Scott Carr [EMAIL PROTECTED] wrote:I am having an issue with running a Function that returns an Array. I have a function called returnContacts that returns an array ofContact.The return type from Axis built objects is ArrayOfContacts.If I try to use the ArrayOfContact type, I get an error when I run the function saying NoSuchMethodError.If i try to set the return type to Contact[] then I get a compile error.ContactsLocator locScen = new ContactsLocator(); ContactsSoap servScen = locScen.getContactsSoap (newURL(m_strContactURL)); ArrayOfContact arrContact =servScen.returnContacts(m_ticketId.getTicketID(), Test);What am I doing wrong?Thanks--Scott CarrOpenOffice.org Documentation Co-LeadThis message was sent using IMP, the Internet Messaging Program.
Re: WSDL soap-adress not correctly set by Axis2 1.0 webapp
Let me try and understand. You have: http://localhost:8080/axis2/services/MyService But now you want to create your own webapp: http://localhost:8080/myWebApp/services/MyService Is that correct? If so, you do this via: cp axis2.war myWebApp.war ? Robert http://www.braziloutsource.com/ On 5/5/06, Sébastien Arod [EMAIL PROTECTED] wrote: When I deploy a service to Axis2 webappThe soapaddress is set by Axis2 to soap:addresslocation=http://localhost:8080/axis2/services/MyService/ that's fine. However if I changed Axis2 webapp name to a other name the soapaddressis still set to http://localhost:8080/axis2/services/MyService soobviously the client can't find the Service (404 Error). Is there a way to configure that or is it a bug ?ThanksSebastien
Further problems testing Axis2 1.0 with Oracle OC4J (9.0.4)
Hello, I have found a set of new problems using the Administration interface. My web application has the 'distributable/' flag set in the web.xml. This forces the OC4J to check whether the attributes put into the httpsession are Serializable. I get exceptions like this using the admin interface: Caused by: java.lang.IllegalArgumentException: Only java.io.Serializable, javax.ejb.EJBObject and javax.ejb.EJBHome instances can be bound to a session in a distributable web-application, not: [EMAIL PROTECTED] (class org.apache.axis2.description.AxisService) at com.evermind.server.http.EvermindHttpSession.setAttribute(EvermindHttpSession.java:97) at org.apache.axis2.transport.http.AdminAgent.processEditServicePara(AdminAgent.java:224) The same problem with Iterator, PhaseInfo, etc. It seems that the AdminAgent class puts the information into the httpsession before it sends to the view jsps. The views take it from the httpsession and then clear the session attribute. Changing the pattern AdminAgent: req.getSession().setAttribute(name, value), JSP: value = req.getSession().getAttribute(name); req.getSession().setAttribute(name, null); to AdminAgent: req.setAttribute(name, value), JSP: value = req.getAttribute(name); solves the problem. Regards, Laszlo
Re: Further problems testing Axis2 1.0 with Oracle OC4J (9.0.4)
Please create a new JIRA issue - http://issues.apache.org/jira/ thanks, dims On 5/6/06, Czeglédi László [EMAIL PROTECTED] wrote: Hello, I have found a set of new problems using the Administration interface. My web application has the 'distributable/' flag set in the web.xml. This forces the OC4J to check whether the attributes put into the httpsession are Serializable. I get exceptions like this using the admin interface: Caused by: java.lang.IllegalArgumentException: Only java.io.Serializable, javax.ejb.EJBObject and javax.ejb.EJBHome instances can be bound to a session in a distributable web-application, not: [EMAIL PROTECTED] (class org.apache.axis2.description.AxisService) at com.evermind.server.http.EvermindHttpSession.setAttribute(EvermindHttpSession.java:97) at org.apache.axis2.transport.http.AdminAgent.processEditServicePara(AdminAgent.java:224) The same problem with Iterator, PhaseInfo, etc. It seems that the AdminAgent class puts the information into the httpsession before it sends to the view jsps. The views take it from the httpsession and then clear the session attribute. Changing the pattern AdminAgent: req.getSession().setAttribute(name, value), JSP: value = req.getSession().getAttribute(name); req.getSession().setAttribute(name, null); to AdminAgent: req.setAttribute(name, value), JSP: value = req.getAttribute(name); solves the problem. Regards, Laszlo -- Davanum Srinivas : http://wso2.com/blogs/
Re: Regarding overloaded methods in a WSDL
Overloaded methods cause significant interoperability headaches and should not be used. I believe Axis decremented support for overloaded methods in V1.2.AnneOn 5/5/06, Sreedhar Chahanapally [EMAIL PROTECTED] wrote: Hi All, I have a third party WSDL which has overloaded methods. I am using apache-axis 1.2 and when trying to run WSDL2Java it complains saying, the method is overloaded. But when I use xml-axis-10 I don't get this problem and I could generate the client side stubs. May I know why is this happening? And how to generate client side code using apache-axis 1.2 Any help highly appreciated. Thanks regards, Helen.
Re: Regarding overloaded methods in a WSDL
Note also that the WS-I Basic Profile [1] disallows overloaded messages: 4.5.3 Distinctive Operations Operation name overloading in a wsdl:portType is disallowed by the Profile. R2304 A wsdl:portType in a DESCRIPTION MUST have operations with distinct values for their name attributes. Note that this requirement applies only to the wsdl:operations within a given wsdl:portType. A wsdl:portType may have wsdl:operations with names that are the same as those found in other wsdl:portTypes. [1] http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Distinctive_Operations On 5/6/06, Anne Thomas Manes [EMAIL PROTECTED] wrote: Overloaded methods cause significant interoperability headaches and should not be used. I believe Axis decremented support for overloaded methods in V1.2. AnneOn 5/5/06, Sreedhar Chahanapally [EMAIL PROTECTED] wrote: Hi All, I have a third party WSDL which has overloaded methods. I am using apache-axis 1.2 and when trying to run WSDL2Java it complains saying, the method is overloaded. But when I use xml-axis-10 I don't get this problem and I could generate the client side stubs. May I know why is this happening? And how to generate client side code using apache-axis 1.2 Any help highly appreciated. Thanks regards, Helen.
Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Joshua, A beanMapping specifies a one-to-one mapping of an XML element (defined by its qualified name) to its associated JavaBean. You should have only one beanMapping statement for each XML qname. For example, if you have the following XML element: foo:foobar xmlns:foo=urn:foo.bar foo:bazsome string/foo:baz/foo:foobarAnd you want to map it to a bean in the package com.bar.foo.foobarthen you would define a beanMapping like so:beanMapping xmlns:foo=urn: foo.barxmlns:java=http://xml.apache.org/axis/wsdd/providers/javaqname=foo:foobar languageSpecificType=java:com.bar.foo.foobar/ Note that the namespace declarations must match the prefixes that you use in the referenced qnames (foo:foobar requires that I declare the foo namespace and java:com.bar.foo.foobar requires that I declare the java namespace). These namespace declarations can (and typically are) declared in the service element rather than in each beanmapping.Anne On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Anne, I was able to get the generator to generate a client by playing around with the bean mappings. If it is not obvious to you already, I am new at this. What should my bean mappings look like? This is what I have now: beanMapping qname=java:Address xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Address / beanMapping qname=java:BaseDomainObject xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.BaseDomainObject / beanMapping qname=java:BaseDomainObjectWithHistory xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.BaseDomainObjectWithHistory / beanMapping qname=java:Case xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Case/ beanMapping qname=java:Consumer xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Consumer / beanMapping qname=java:ContactLocation xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ContactLocation / beanMapping qname=java:ContactLocationPreference xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ContactLocationPreference / beanMapping qname=java:ContactLocationType xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ContactLocationType / beanMapping qname=java:ContactMethod xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ContactMethod / beanMapping qname=java:DomainObject xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.DomainObject / beanMapping qname=java:EligibilityProfile xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.EligibilityProfile / beanMapping qname=java:Email xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Email / beanMapping qname=java:ExternalSystemKey xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ExternalSystemKey / beanMapping qname=java:GbdOccupation xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.GbdOccupation / beanMapping qname=java:Gender xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Gender / beanMapping qname=java:Party xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Party / beanMapping qname=java:Phone xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Phone / beanMapping qname=java:PhoneType xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.PhoneType / beanMapping qname=java:ReferenceObject xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ReferenceObject / beanMapping qname=java:SourceSystem xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.SourceSystem / beanMapping qname=java:State xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.State / Anne Thomas Manes [EMAIL PROTECTED] 05/05/2006 11:32 AM Please respond to axis-user To:axis-user@ws.apache.org cc: Subject:Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task Joshua, This is not a valid schema construct: complexType name=local complexContent extension base=tns2:local
Re: [Axis2 1.0] ant codegen target problems
There's some known problems AntCodegenTask. In the meantime, what I use is:
target name=wsdl2java depends=clean,prepare
delete dir=output /
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath/
arg value=-d/
arg value=xmlbeans/
arg value=-uri/
arg file=wsdl/simple.wsdl/
arg value=-ss/
arg value=-g/
arg value=-sd/
arg value=-o/
arg file=output/
arg value=-p/
arg value=org.simple.endpoint/
/java
!-- Move the schema folder to classpath--
move todir=${build.classes}
fileset dir=output/resources
include name=*schema*/**/*.class/
include name=*schema*/**/*.xsb/
/fileset
/move
/target
HTH,
Robert
http://news.google.com/
On 5/6/06, Rob Henley [EMAIL PROTECTED] wrote:
My build.xml contains
target
name=axis-init taskdef
name=codegen
classname=org.apache.axis2.tool.ant.AntCodegenTask
classpath=${axis.dist.classpath}/
/target
target name=wsdl2java
depends=axis-init codegen
wsdlfilename=my.wsdl
language=java
synconly=true
serverside=true
generateservicexml=true
/codegen /target
where axis.dist.classpath contains all the jars in
the axis2 lib directory.
Running 'ant wsdl2java' I get an error
javax.xml.stream.FactoryConfigurationError:
Provider com.bea.xml.stream.MXParserFactory not found.
Via google I managed to find a couple of additional
jars to supply missing classes: jsr173_1.0_ri.jar and jsr173_1.0_api.jar. Adding
these to my global classpath fixes the problem.
Question 1. Are the above jsr173 jars missing from
the 1.0 distribution?
Question 2. Is there a more ant-like way to control
the classpath used when the codegen tool runs? I tried the following
...
codegen
wsdlfilename=purchasing1.wsdl
language=java
synconly=true
serverside=true
generateservicexml=true
classpath refid=axis.dist.classpath/
/codegen
but that gives me a
java.lang.ExceptionInInitializerError.
Question 3. I'd like to be able to specify the
xmlbeans data binding. What is the AntCodegenTask equivalent to the command line
--databinding-method xmlbeans? This doesn't seem to be documented. I guessed
it might bedatabindingname=xmlbeans, but
when I add this to the codegen target I get the error
java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException.
Many thanks
Rob
Problems deploying with AdminClient
Dear all, I have run into a very odd problem trying to deploy my web service using AdminClient. I create my wsdl and wsdd files without any problems. I also don't get any errors when I deploy the service using: java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -l http://localhost/myURL deploy.wsdd However, the service then simply isn't there. It doesn't show up in the list of services (only AdminService and Version do). This is even more awkward, since it was working fine this morning. I had the service running, went for lunch, and it somehow undeployed itself in the meantime. So, I tried to redeploy, but without any success so far. Any idea what the problem might be? Cheers, Martin
Re: ArrayOf Causing some problems
Sorry to bother everyone with this. I believe this is an issue with Netbeans. With this particular project, I had tried the Web Service client stuff that is built into Netbeans, and got tired of using it. (There are not too many examples on how to use it.) I deleted the Web Service Client from Netbeans project, and started using the Axis Generated Objects. Netbeans seems to have not regenerated its ClassPath used to show Context Sensitive help. I created a New netbeans project with the same Axis Objects and everything worked the first time. Thanks, for the response. I really like Axis, by the way. robert lazarski wrote: Seems like you are using databinding. If so post the wsdl and maybe we can help. A stack trace may help too. Robert http://www.braziloutsource.com/ On 5/5/06, *Scott Carr* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I am having an issue with running a Function that returns an Array. I have a function called returnContacts that returns an array of Contact. The return type from Axis built objects is ArrayOfContacts. If I try to use the ArrayOfContact type, I get an error when I run the function saying NoSuchMethodError. If i try to set the return type to Contact[] then I get a compile error. ContactsLocator locScen = new ContactsLocator(); ContactsSoap servScen = locScen.getContactsSoap (new URL(m_strContactURL)); ArrayOfContact arrContact = servScen.returnContacts(m_ticketId.getTicketID(), Test); What am I doing wrong? Thanks -- Scott Carr OpenOffice.org Documentation Co-Lead This message was sent using IMP, the Internet Messaging Program.
Re: Problems deploying with AdminClient
Hello Martin.
As far as I know the AdminClient was used by Axis to deploy a service.
With Axis2 the deploying has slightly changed.
Please go through the User's Manual to see how to deploy a service.
http://ws.apache.org/axis2/1_0/userguide.html
You will see that you have some options:
1) create an aar-archive and put it in the WEB-INF/services directory of
the axis2 webapp
2) create an aar-archive and upload it through the Administration UI
3) place the content of the aar-archive unpacked into the
WEB-INF/services/${YOUR_SERVICE} directory
The third option is usefull if you have a lot jars placed in the
lib-directory of you service because the Axis2 ClassLoader is very slow
while loading jars inside aars ;-)
I hope I could help you,
Siamak Haschemi
Martin Wunderlich schrieb:
Dear all,
I have run into a very odd problem trying to deploy my web service
using AdminClient. I create my wsdl and wsdd files without any
problems. I also don't get any errors when I deploy the service using:
java -cp %AXISCLASSPATH%
org.apache.axis.client.AdminClient -l http://localhost/myURL
deploy.wsdd
However, the service then simply isn't there. It doesn't show up in
the list of services (only AdminService and Version do).
This is even
more awkward, since it was working fine this morning. I had the service
running, went for lunch, and it
somehow undeployed itself in the meantime. So, I tried to redeploy,
but without any success so far. Any idea what the problem might be?
Cheers,
Martin
Re[2]: Problems deploying with AdminClient
Hi Siamak,
Thanks a lot for the suggestion. I am still using Axis 1.3, so it
wouldn't be related to Axis 2, I guess.
Cheers,
Martin
Hello Martin.
As far as I know the AdminClient was used by Axis to deploy a service.
With Axis2 the deploying has slightly changed.
Please go through the User's Manual to see how to deploy a service.
http://ws.apache.org/axis2/1_0/userguide.html
You will see that you have some options:
1) create an aar-archive and put it in the WEB-INF/services directory of
the axis2 webapp
2) create an aar-archive and upload it through the Administration UI
3) place the content of the aar-archive unpacked into the
WEB-INF/services/${YOUR_SERVICE} directory
The third option is usefull if you have a lot jars placed in the
lib-directory of you service because the Axis2 ClassLoader is very slow
while loading jars inside aars ;-)
I hope I could help you,
Siamak Haschemi
Re: Problems deploying with AdminClient
Testing a bit more I was able to successfully deploy a different web service to a different location on the same Tomcat installation. Then I copied all the resources to a new project (in Eclipse), which I deployed to a new web-app and things seem to work there. So, at least I have the problem limited down now to the original service that I wanted to deploy. Still, it's puzzling... In the process, I happened to notice that the SOAPMonitor tool can only be used, if Tomcat is installed on port 8080. Is there a way to change the port to 80? It reverts back to 8080, even if I call the SOAPMonitor with http://localhost/ Cheers, Martin Dear all, I have run into a very odd problem trying to deploy my web service using AdminClient. I create my wsdl and wsdd files without any problems. I also don't get any errors when I deploy the service using: java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -l http://localhost/myURL deploy.wsdd However, the service then simply isn't there. It doesn't show up in the list of services (only AdminService and Version do). This is even more awkward, since it was working fine this morning. I had the service running, went for lunch, and it somehow undeployed itself in the meantime. So, I tried to redeploy, but without any success so far. Any idea what the problem might be? Cheers, Martin -- -- Martin Wunderlich, M.A. Translation/Localisation EN - DE www.martinwunderlich.com -- Free / open-source software for translation/localisation: www.martinwunderlich.com/foss-links.html -- Random aphorism: Todas las cosas tienen su misterio, y la poesía es el misterio que tienen todas la cosas. All things have their secret. And poetry is the secret that all things have. - Federico García Lorca --
Re: [Axis2] HTTP Transport Receiver
Hi, You can use the Axis2 War Distribution [1] and deploy it in Apache Tomcat. Please refer to Installing Axis2 in a Servlet Container section of the installation guide [2] to install the axis2.war. Thanks, Ruchith [1] http://www.apache.org/dyn/closer.cgi/ws/axis2/1_0/axis2.war [2] http://ws.apache.org/axis2/1_0/installationguide.html#_Toc96698086 On 5/5/06, Plater, Elizabeth [EMAIL PROTECTED] wrote: I noticed that the SimpleHTTPServer packaged with Axis2 and configured as the default Transport Receiver for http requests is not production-worthy. Do you have a standard alternative http server recommended for production use? If so, how should it be configured in the axis2.xml file?
[Axis2] Axis2's OMTutorial needs(!) to be updated :)
Hi Axis2 Team, According to the blog entry at http://blogs.cocoondev.org/dims/archives/004619.html, you also need to update OMTutorial found in Axis2's site to keep them in sync. http://ws.apache.org/commons/axiom/OMTutorial.html http://ws.apache.org/axis2/1_0/OMTutorial.html Regards, Ali Sadik Kumlali __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Interoperability with .NET
Axis 2 is tested and proven interoprability with .net. Have a look at the following news item. I was lucky enough to experience it first hand at the interop plug-fest. http://www.wso2.com/about/news/microsoftinterop/ Except for very few extreme cases WCF and Axis2 demonstrated very good interoperability :). ~Thilina On 5/5/06, GOBE HOBONA [EMAIL PROTECTED] wrote: Anne,you were right there was a problem with the SOAP message. To address theproblem I implemented a new Web Service and a MessageReceiver that builds a SOAP response from scratch. It worked.I think the problem was .NET not managing to deserialise the response fromthe RawXMLINOutMessageReceiver; hence my implementing a new class thatextends AbstractInOutSyncMessageReceiver. So if anybody asks, tell them yes, Axis2 is interoperable with .NETThanks for your help,GobeOn Thu, 4 May 2006 19:24:52 -0400 Anne Thomas Manes wrote:The envelope namespace should be http://schemas.xmlsoap.org/soap/envelope/.If your Axis endpoint is generating a SOAP message with a namespace of http://org.apache.axis2/xsd then you've done something wrong in your code.AnneOn 5/4/06, GOBE HOBONA [EMAIL PROTECTED] wrote: Hello,I am attempting to run the MyService example from a Microsoft.NET client.Iget the following SoapException from .NET when running the echo operation. Envelope namespace http://org.apache.axis2/xsd was unexpected. Expectinghttp://schemas.xmlsoap.org/soap/envelope/ Basically, has anybody successfully read-in SOAP objects from an Axis2 webservice to a .NET client?Any examples of compatibility tests or programs will be much appreciated. -- May the SourcE be with uhttp://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
Re: [Axis2] hot service undeployment
Hi Michele; I think you are using windows , because I too have this problem :) . Any way the problem is due to class loading issues . As you know in Axis2 each services get its own class loader, so how we create the class loader is using the service archive file as a url. Once we create the class loader we can not just delete the file since is it is locked by the file system . But you dont have this problem in Linux :( , Did you ever try to delete a lib file in tomcat lib directory while it is running , if you try you will get the same error , it does not allow you to delete the file. So Axis2 has the same problem , and we do not try to solve this. But you can have hot update services , I mean rather than deleting the file you can just drop the updated service into services directory , then right thing will happen (old one will be replaced by new one). Michele Mazzucco wrote: Hi Deepal, my axis2.xml has the following line parameter name=hotupdate locked=falsetrue/parameter but I can't delete any service while the server is running. Michele Deepal Jayasinghe wrote: You have that capability , but you have to edit axis2.xml file in order to have this feature. You have to change to parameter name=hotupdate locked=falsefalse/parameter following parameter name=hotupdate locked=falsefalse/parameter Michele Mazzucco wrote: Hi all, I know it's possible to deploy services while the server is running (Tomcat + Axis2), but is it possible to undeploy services while the server is on? Thanks, Michele -- Thanks, Deepal ~Future is Open~
Re: [Axis2 1.0] Service deployment problems
Hi Mochele; Your service does not have any problem and if you deploy the service then you can invoke that too. The error you are getting is not something make your service a faulty service, it is a decision that we took to reduce the number of JIRA that we may get in the future:) We can generate wsld for any given service w.o any problem , but in the mean time if some one code gen using that wsdl he should be able to invoke the service. So the wsdl we are generating is based on java reflection and that assume message receiver as RPC we can not guaranty that will work for all the message receivers. What if someone use RawXML message receiver and try to invoke the service using generated wsdl , then he will fail to do so , since the auto generated wsdl does not compatible with RawXML message receivers. To solve those problem , we no longer auto generate the wsdl. and Axis2 only print out the wsdl in the two scenarios that Ajith mentioned. Michele Mazzucco wrote: Ajith, this is non my case since I deployed my services as well services from the sample folder (that work on Axis2 RC4), all working with the Axis2 primary APIs. Michele Ajith Ranabahu wrote: Hi, The WSDL generation functionality has changed for 1.0 since the WSDL generation had a flaw. Unless you have the WSDL inside the META-INF of the aar file, the WSDL is not auto generated except for the special situation where the message receiver is the RPCInOutMessageReceiver. The reason for this is that the java2wsdl code generator assumes the service to be rpc when generating the WSDL and if the user has any custom message receiver installed everything gets screwed up! Ajith On 5/5/06, Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, it seems there are some problems to deploy services on Axis2 1.0 (or at least into the web browser console): all services but the version.aar one show a message like this error descriptionUnable to generate WSDL for this service/description reason Either user has not dropped the wsdl into META-INF or operationsuse message receivers other than RPC. /reason /error instead of the WSDL file (please try with groovyService, available into the userguide dir, for example). Michele -- Ajith Ranabahu -- Thanks, Deepal ~Future is Open~
