Re: Static WSDL problems
We are using Axis2 bundled with our server, using AxisServlet. Where should this classes go? Do I still need a services.xml? Regards On Mon, Jan 11, 2010 at 12:49 PM, Yashvant chauhan c.yashv...@gmail.com wrote: Hi Vinicius, As per my understanding you have to do folowing things, 1) create a WSDL first with proper schema... 2) generarte server side code using the Axis2 utility wsdl2Java and update the *Impl java file your business logic 3) create a war file with whole stuff and deploy it in a webserver once you completed above three steps your service should work. Regards, Yashvant On Mon, Jan 11, 2010 at 7:19 PM, Vinicius Carvalho java.vinic...@gmail.com wrote: Hello there! We have an legacy WS built with Pojo based deployment with Axis2. I was told that in order to override a few defaults from axis (soap address, and some nillable properties on elements) one should get the generated WSDL and copy it to the same folder that the services.xml resides. Problem is: When we do that, Axis simply stop working. When I get the exact WSDL that is generated through: www.myserver.com/services/MyService?WSDL copy it to the folder of services.xml, restart tomcat. Well things get messy, and very very messy: One is that the marshalling stop working, parameters do not get converted I get lots of \n on string parameters for instance. As I said, I was told that just putting the WSDL at the services.xml folder should work, but it does not seems so. Any ideas please? Regards -- Yashvant Singh Chauhan Mobile- 09845277271 Bangalore *
Static WSDL problems
Hello there! We have an legacy WS built with Pojo based deployment with Axis2. I was told that in order to override a few defaults from axis (soap address, and some nillable properties on elements) one should get the generated WSDL and copy it to the same folder that the services.xml resides. Problem is: When we do that, Axis simply stop working. When I get the exact WSDL that is generated through: www.myserver.com/services/MyService?WSDL copy it to the folder of services.xml, restart tomcat. Well things get messy, and very very messy: One is that the marshalling stop working, parameters do not get converted I get lots of \n on string parameters for instance. As I said, I was told that just putting the WSDL at the services.xml folder should work, but it does not seems so. Any ideas please? Regards
[Axis2] Spring + Axis2 0.95 help
Hello there! I've seen some implementations of how to plug Spring + Axis2 here. I have a few questions.1st. Isn't it possible to use something like we had on Axis 1.x? I mean just a class that could have access to ServletContext? All I need is the Servlet context :( 2nd. I've seen a post taliking about using an ObjectFactory in my WebServices, but if I have a factory been instantiated by Spring Listener why bother having another one?If someone here is using Axis2+Spring would you mind sharing your solution? Best RegardsPS:Shouldn't it be a topic on the wiki?
[Axis2] Embebedding Axis2 on current WebApp
Hello, is it possible to use Axis2 administration web module on my current web application? I mean I'd like to have http://host/myapp/admin.jsp and not http://host/axis2/admin.jspIs it possible?Regards
Creating a new Log Handler
Hello there! I need to create a new Log Handler. The example on the user guides is pretty self explanatory, but I have a few questions:1st- Do I have to explicit add on each of my service to be deployed to use that handler? Isn't there a global configuration where I could add that handler to be called for ALL services (no exceptions) on my axis engine? 2nd- How can I track info about the requester (aka HTTP_REMOTE_ADDR)?Regards
Re: Remote Administration question
Could someone please give me a hand here?Best RegardsOn 2/15/06, Vinicius Carvalho [EMAIL PROTECTED] wrote:Hello There! I've deployed my App in a remote server and I'd like to publish webservices from a remote machine. From the docs I've seen that I need to provide a custom server-config.wsdd so I add this to my WEB-INF dir: deployment xmlns=http://xml.apache.org/axis/wsdd/ xmlns:java= http://xml.apache.org/axis/wsdd/providers/java service name=AdminService provider=java:MSG parameter name=className value=org.apache.axis.utils.Admin/ parameter name=allowedMethods value=*/ parameter name=enableRemoteAdmin value=true//service/deploymentWell, ok, now when I run the AdminClient task I get another error:faultString: The AXIS engine could not find a target service to invoke! targetService is null I also tried to pack inside my server-config all my services at once, well they get listed on the AxisServlet, but I can`t access the WSDL it says there's no SOAP service at the location.Could someone help me with this? What should be done to have a Axis engine that accepts remote services publishing Regards
Remote Administration question
Hello There! I've deployed my App in a remote server and I'd like to publish webservices from a remote machine. From the docs I've seen that I need to provide a custom server-config.wsdd so I add this to my WEB-INF dir: deployment xmlns=http://xml.apache.org/axis/wsdd/ xmlns:java=http://xml.apache.org/axis/wsdd/providers/java service name=AdminService provider=java:MSG parameter name=className value=org.apache.axis.utils.Admin/ parameter name=allowedMethods value=*/ parameter name=enableRemoteAdmin value=true//service/deploymentWell, ok, now when I run the AdminClient task I get another error:faultString: The AXIS engine could not find a target service to invoke! targetService is null I also tried to pack inside my server-config all my services at once, well they get listed on the AxisServlet, but I can`t access the WSDL it says there's no SOAP service at the location.Could someone help me with this? What should be done to have a Axis engine that accepts remote services publishing Regards
Help with TypeMapping
Hello there! I'm using spring + axis in my application. I've extended the org.springframework.remoting.jaxrpc.JaxRpcPortProxyFactoryBean class in order to register my Beans. Well It was working for a simpler kind of bean, but for the WSDL bellow I'm confused on how register it. 1st - I've noticed that both Assinante and AssinantePK have the same namespace, is this ok? I mean, don't I need a unique namespace for each object? 2nd - Where can I find an deep material about Serializers? 3rd - I've read the article recommend at the Axis site about the WSDL types which one use, but that explains for the SOAP envelop only, where can I find reference about differences for the type mappings? If someone cares to give me a hand here I'd be grategfull. Regards wsdl:types schema elementFormDefault=qualified targetNamespace=http://impl.alterarplano.services.cplus.way.com xmlns=http://www.w3.org/2001/XMLSchema import namespace=http://assinante.persistence.model.cplus.way.com/ import namespace=http://pacote.persistence.model.cplus.way.com/ import namespace=http://cidade.persistence.model.cplus.way.com/ element name=alterarPlano complexType sequence element name=assinante type=tns1:Assinante/ element name=novoPacote type=tns3:Pacote/ /sequence /complexType /element complexType name=ArrayOf_xsd_anyType sequence element maxOccurs=unbounded minOccurs=0 name=item type=xsd:anyType/ /sequence /complexType element name=alterarPlanoResponse complexType/ /element /schema schema elementFormDefault=qualified targetNamespace=http://cidade.persistence.model.cplus.way.com xmlns=http://www.w3.org/2001/XMLSchema import namespace=http://assinante.persistence.model.cplus.way.com/ import namespace=http://pacote.persistence.model.cplus.way.com/ import namespace=http://impl.alterarplano.services.cplus.way.com/ complexType name=Cidade sequence element name=id nillable=true type=xsd:int/ element name=nome nillable=true type=xsd:string/ /sequence /complexType /schema schema elementFormDefault=qualified targetNamespace=http://assinante.persistence.model.cplus.way.com xmlns=http://www.w3.org/2001/XMLSchema import namespace=http://pacote.persistence.model.cplus.way.com/ import namespace=http://impl.alterarplano.services.cplus.way.com/ import namespace=http://cidade.persistence.model.cplus.way.com/ complexType name=AssinantePK sequence element name=codigoCidade nillable=true type=xsd:int/ element name=contrato nillable=true type=xsd:int/ /sequence /complexType complexType name=Assinante sequence element name=cidade nillable=true type=tns2:Cidade/ element name=id nillable=true type=tns1:AssinantePK/ element name=nome nillable=true type=xsd:string/ element name=produtos nillable=true type=impl:ArrayOf_xsd_anyType/ /sequence /complexType /schema schema elementFormDefault=qualified targetNamespace=http://pacote.persistence.model.cplus.way.com xmlns=http://www.w3.org/2001/XMLSchema import namespace=http://assinante.persistence.model.cplus.way.com/ import namespace=http://impl.alterarplano.services.cplus.way.com/ import namespace=http://cidade.persistence.model.cplus.way.com/ complexType name=PacotePK sequence element name=codigoCidade nillable=true type=xsd:int/ element name=codigoProgramacao nillable=true type=xsd:int/ /sequence /complexType complexType name=Pacote sequence element name=cidade nillable=true type=tns2:Cidade/ element name=codigoReceita nillable=true type=xsd:int/ element name=id nillable=true type=tns3:PacotePK/ element name=pacote nillable=true type=xsd:string/ element name=tipoPonto nillable=true type=xsd:string/ element name=valor nillable=true type=xsd:double/ /sequence /complexType /schema /wsdl:types
Problems with CGLIB enhancements
Hello there! I've my WS configured My wsdd looks like this: service name=AlterarPlanoServiceImpl provider=java:RPC style=document use=literal parameter name=wsdlTargetNamespace value=http://impl.alterarplano.services.cplus.way.com/ parameter name=wsdlServiceElement value=AlterarPlanoServiceImplService/ parameter name=schemaQualified value=http://cidade.persistence.model.cplus.way.com,http://impl.alterarplano.services.cplus.way.com,http://pacote.persistence.model.cplus.way.com,http://assinante.persistence.model.cplus.way.com / parameter name=wsdlServicePort value=AlterarPlanoServiceImpl/ parameter name=className value=com.way.cplus.services.alterarplano.endpoint.AlterarPlanoEndPoint/ parameter name=wsdlPortType value=AlterarPlanoServiceImpl/ parameter name=typeMappingVersion value=1.2/ operation name=alterarPlano qname=alterarPlano soapAction= parameter xmlns:pns=http://impl.alterarplano.services.cplus.way.com xmlns:tns=http://assinante.persistence.model.cplus.way.com qname=pns:assinante type=tns:Assinante/ parameter xmlns:pns=http://impl.alterarplano.services.cplus.way.com xmlns:tns=http://pacote.persistence.model.cplus.way.com qname=pns:novoPacote type=tns:Pacote/ /operation parameter name=allowedMethods value=alterarPlano/ typeMapping xmlns:ns=http://assinante.persistence.model.cplus.way.com qname=ns:Assinante type=java:com.way.cplus.model.persistence.assinante.Assinante serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle=/ typeMapping xmlns:ns=http://cidade.persistence.model.cplus.way.com qname=ns:Cidade type=java:com.way.cplus.model.persistence.cidade.Cidade serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle=/ typeMapping xmlns:ns=http://pacote.persistence.model.cplus.way.com qname=ns:PacotePK type=java:com.way.cplus.model.persistence.pacote.PacotePK serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle=/ typeMapping xmlns:ns=http://pacote.persistence.model.cplus.way.com qname=ns:Pacote type=java:com.way.cplus.model.persistence.pacote.Pacote serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle=/ arrayMapping xmlns:ns=http://impl.alterarplano.services.cplus.way.com xmlns:cmp-ns=http://www.w3.org/2001/XMLSchema qname=ns:ArrayOf_xsd_anyType type=java:java.lang.Object[] innerType=cmp-ns:anyType encodingStyle=/ typeMapping xmlns:ns=http://assinante.persistence.model.cplus.way.com qname=ns:AssinantePK type=java:com.way.cplus.model.persistence.assinante.AssinantePK serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle=/ /service Well, the problem is that's not Assinante who's being transfered over the wire, but an enhanced version by CGLIB (it was loaded by Hibernate) So I end up with this: org.springframework.remoting.RemoteAccessException: Cannot access remote service [{http://impl.alterarplano.services.cplus.way.com}AlterarPlanoServiceImpl]; nested exception is org.apache.axis.AxisFault: ; nested exception is: java.io.IOException: No serializer found for class com.way.cplus.model.persistence.assinante.Assinante$$EnhancerByCGLIB$$bc19766f in registry [EMAIL PROTECTED] AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.io.IOException: No serializer found for class com.way.cplus.model.persistence.assinante.Assinante$$EnhancerByCGLIB$$bc19766f in registry [EMAIL PROTECTED] faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:java.io.IOException: No serializer found for class com.way.cplus.model.persistence.assinante.Assinante$$EnhancerByCGLIB$$bc19766f in registry [EMAIL PROTECTED] Any ideas? Regards
Help with complex bean
Hello there! I have this following Bean: public class User{ private ListCar cars; ... } Axis is generating a WSDL that contains an array of any type instead of Car and defining a qName for Car. How can I change this? Regards
Re: wath is the best style of WSDL???
if this might help http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ But, it's always a tryOn 1/26/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm developing a web service and i dont know that style is the best.WS-I recomend document/literal but all the examples (that i have found) uses RPC/encoded with axis.If I use axis and saaj, what is the best style of WSDL for myHelp me, please.
Complex bean example
How can I use a complex bean as a parameter? Where do I set the converters for it? on WSDD? is there any examples? Regards
HTTP Method POST not supported
Hello I'm running AdminClient to deploy my webservices in an embebed Axis installation on my existant web-app. Here's my ant script: java classname=org.apache.axis.client.AdminClient fork=true failonerror=true classpathref=axis.classpath classpath refid=project.class.path/ arg value=-lhttp://localhost:8080/mgjug/servlet/AdminServlet/ arg value=${wsdd.dir}/mgjug.wsdd/ /java Here's the error: Buildfile: D:\workspace\MGJUG\build.xml init: publish-webservices: [java] - Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. [java] Processing file web/wsdd/mgjug.wsdd [java] Exception: AxisFault [java] faultCode: {http://xml.apache.org/axis/}HTTP [java] faultSubcode: [java] faultString: (400)HTTP method POST is not supported by this URL [java] faultActor: [java] faultNode: [java] faultDetail: [java] {}:return code: 400 [java] lt;htmlgt;lt;headgt;lt;titlegt;Apache Tomcat/5.5.9 - Error reportlt;/titlegt;lt;stylegt;lt;!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--gt;lt;/stylegt; lt;/headgt;lt;bodygt;lt;h1gt;HTTP Status 400 - HTTP method POST is not supported by this URLlt;/h1gt;lt;HR size=quot;1quot; noshade=quot;noshadequot;gt;lt;pgt;lt;bgt;typelt;/bgt; Status reportlt;/pgt;lt;pgt;lt;bgt;messagelt;/bgt; lt;ugt;HTTP method POST is not supported by this URLlt;/ugt;lt;/pgt;lt;pgt;lt;bgt;descriptionlt;/bgt; lt;ugt;The request sent by the client was syntactically incorrect (HTTP method POST is not supported by this URL).lt;/ugt;lt;/pgt;lt;HR size=quot;1quot; noshade=quot;noshadequot;gt;lt;h3gt;Apache Tomcat/5.5.9lt;/h3gt;lt;/bodygt;lt;/htmlgt; [java] {http://xml.apache.org/axis/}HttpErrorCode:400 BUILD FAILED D:\workspace\MGJUG\build.xml:140: Java returned: 1 Regards-- Everything should be made as simple as possible, but not simpler.Albert Einstein
Re: HTTP Method POST not supported
Antoher thing is, on the default axis application (localhost:8080/axis/servlet/AdminServlet) it works :? ??On 9/20/05, Vinicius Carvalho [EMAIL PROTECTED] wrote: Hello I'm running AdminClient to deploy my webservices in an embebed Axis installation on my existant web-app. Here's my ant script: java classname=org.apache.axis.client.AdminClient fork=true failonerror=true classpathref=axis.classpath classpath refid=project.class.path/ arg value=-lhttp://localhost:8080/mgjug/servlet/AdminServlet/ arg value=${wsdd.dir}/mgjug.wsdd/ /java Here's the error: Buildfile: D:\workspace\MGJUG\build.xml init: publish-webservices: [java] - Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. [java] Processing file web/wsdd/mgjug.wsdd [java] Exception: AxisFault [java] faultCode: {http://xml.apache.org/axis/}HTTP [java] faultSubcode: [java] faultString: (400)HTTP method POST is not supported by this URL [java] faultActor: [java] faultNode: [java] faultDetail: [java] {}:return code: 400 [java] lt;htmlgt;lt;headgt;lt;titlegt;Apache Tomcat/5.5.9 - Error reportlt;/titlegt;lt;stylegt;lt;!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--gt;lt;/stylegt; lt;/headgt;lt;bodygt;lt;h1gt;HTTP Status 400 - HTTP method POST is not supported by this URLlt;/h1gt;lt;HR size=quot;1quot; noshade=quot;noshadequot;gt;lt;pgt;lt;bgt;typelt;/bgt; Status reportlt;/pgt;lt;pgt;lt;bgt;messagelt;/bgt; lt;ugt;HTTP method POST is not supported by this URLlt;/ugt;lt;/pgt;lt;pgt;lt;bgt;descriptionlt;/bgt; lt;ugt;The request sent by the client was syntactically incorrect (HTTP method POST is not supported by this URL).lt;/ugt;lt;/pgt;lt;HR size=quot;1quot; noshade=quot;noshadequot;gt;lt;h3gt;Apache Tomcat/5.5.9lt;/h3gt;lt;/bodygt;lt;/htmlgt; [java] {http://xml.apache.org/axis/}HttpErrorCode:400 BUILD FAILED D:\workspace\MGJUG\build.xml:140: Java returned: 1 Regards-- Everything should be made as simple as possible, but not simpler.Albert Einstein -- Everything should be made as simple as possible, but not simpler.Albert Einstein
Re: Deploying services to other webapps
Cristine, I'm sorry but it seems no one knows how to deal with it, I've been search the list for hours, post the same question. It only deploys to the default axis. I guess that's the price of opensource ;)On 9/20/05, Thompson, Christine [EMAIL PROTECTED] wrote: I am working with Axis 1.2.1 on Tomcat 5.0.30. I would like to use axis under a web application named something other than "axis". I wish to deploy a jar file containing the service, so I cannot use the JWS deployment. However, when I tried this, and deployed my soap service to the new webapp using AdminClient (using a classpath containing all the axis jar files from the renamed application), it still attempted to deploy to http://localhost:8080/webapps/axis, not my new application. Looking at the source code of the AdminClient class, it uses a defaultURL of http://localhost:8080/axis/services/AdminService, which presumably causes my problem. Is there a way in which I can deploy to another webapp? Or am I constrained by what appears to be a hard-coded url in the source code? Thanks, Christine === Information contained in this email message is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by email to [EMAIL PROTECTED] and destroy the original message. -- Everything should be made as simple as possible, but not simpler.Albert Einstein