Re: Naming of parameters and exceptions
Hello everybody! Amila Suriarachchi wrote: On Tue, Sep 22, 2009 at 12:16 PM, Sebastian Schneider mailto:schnei...@dvz.fh-aachen.de>> wrote: I still do not have found out why sometimes the word "Exception" is added to custom Exception classes and sometimes it is not?? If I have an Exception-class called MyException in the service implementation I sometimes find an inner class in the service stub which is called MyExceptionException instead of MyException if there is an wsd:fault message for an operation it generates an exception class for that which has the sufix 'Exception'. But if you have a schema element with the name MyException it generates an ADB class for that and does not add a sufix. I appreciate the answer very much but for my specific case what is the conclusion if I want to use my own exception classes leaving their names untouched? Do I really need to name my exception classes in the service implementation without the suffix Exception to afterwards just have one Exception-suffix in the generated code? Or does this mean I just have to tweak the configuration? Thanks a lot for any help Sebastian -- Mit freundlichen Grüßen / Best regards / meilleures salutations Sebastian Schneider Tel. 0 24 05 / 45 28 95 9
Re: Axis2 (1.5) - java2wsdl throws error JAVA_HOME environment variable is not defined correctly
JAVA_HOME should point to the home directory of your JDK-installation: In my case, for example JAVA_HOME is set to C:\Programme\Java\jdk1.6.0_16
Re: Problem with serialization of class Date
Hello Amila! > this[1] may help as well > > thanks, > Amila. > > [1] > http://amilachinthaka.blogspot.com/2009/09/handling-date-and-datetime-with-axis2.html Thanks a lot. Looks this explains a lot and will help me. Sebastian
Re: Problem with serialization of class Date
Hello Upul! > I think for Date it only keeps the date portion. You could try it with > Calendar type. > > Upul The class Date in Java also keeps the time. Or do you mean Axis2 is ignoring the time portion? What do you mean with using the Calendar type? AFAIK it's an Java interface to do conversions regarding to times and dates not to store dates. > On Fri, Sep 25, 2009 at 4:51 PM, Sebastian Schneider > wrote: > > Hello axis users, > > > > I am using Axis2-1.5 and I have a method in my service > > implementation which returns an object with an Date-attribute. The > > problem I'm facing now is that the time is wrong or gets lost. > > > > For example on the server side the date in question is Fri Sep 25 > > 13:14:44 CEST 2009. When I call my webservice and check the returned date > > in the > > member variable it is Fri Sep 25 01:00:00 CEST 2009. > > > > I am generating the service archive with the plugin for Eclipse and > > I did not make any manual changes to the services.xml which is > > generated by the wizard. Is this a bug or do I need to specify some > > options for the serialization of the Date class? > > > > Any hint is highly appreciated. > > > > Thanks, > > Sebastian Regards, Sebastian
Problem with serialization of class Date
Hello axis users, I am using Axis2-1.5 and I have a method in my service implementation which returns an object with an Date-attribute. The problem I'm facing now is that the time is wrong or gets lost. For example on the server side the date in question is Fri Sep 25 13:14:44 CEST 2009. When I call my webservice and check the returned date in the member variable it is Fri Sep 25 01:00:00 CEST 2009. I am generating the service archive with the plugin for Eclipse and I did not make any manual changes to the services.xml which is generated by the wizard. Is this a bug or do I need to specify some options for the serialization of the Date class? Any hint is highly appreciated. Thanks, Sebastian
Re: Naming of parameters and exceptions
Hello Amila, hello everybody first of all thank you for your answer. > > I got a question regarding the naming of parameters and exceptions > > in the generated stub code for the client. Why are numbers added to the > > parameter > > names? > this is a technique done to avoid any possible compilation issues. And there is no way to disable this? I chose my parameter and method names carefully to ease things for the developers using my webservice. I do not see how compilation issues could arise from parameter names. > > I still do not have found out why sometimes the word "Exception" is > added to custom Exception classes and sometimes it is not?? If I have an > > Exception-class called MyException in the service implementation I sometimes > > find an inner class in the service stub which is called MyExceptionException > > instead of MyException > if there is an wsd:fault message for an operation it generates an exception > class for that which has the sufix 'Exception'. But if you have a schema > element with the name MyException it generates an ADB class for that and > does not add a sufix. I am still new to Axis/Axis2. I created an interface and afterwards an implementation of this interface. Then I used the Eclipse's Webservice wizard selecting the Bottom-Up-Method pointing the wizard to my implementation. Finally I used the Service Archiver to export my webservice. My service implementation includes exception classes I created and since they are Exceptions they are all named in this way: MyFirstCustomException, MySecondException. Is it necessary to create a schema to avoid this behaviour? If yes, how do I start? Best regards and thank you for your help, Sebastian
Naming of parameters and exceptions
Hello everybody, I got a question regarding the naming of parameters and exceptions in the generated stub code for the client. Why are numbers added to the parameter names? For example, if my service method looked like findUserByName(String name) after generating the stub client from the WSDL file I would find a method findUserByName(String name12) or something in the stub. What is the reason for this and can this behaviour be disabled? I still do not have found out why sometimes the word "Exception" is added to custom Exception classes and sometimes it is not?? If I have an Exception-class called MyException in the service implementation I sometimes find an inner class in the service stub which is called MyExceptionException instead of MyException I am using Axis2-1.5. Data binding is done by ADB. Thank your for any hints and explainations regarding this. Best regards, Sebastian
Downloading Axis2-1.4.1
Hello! On http://ws.apache.org/axis2/download.cgi downloading Axis2-1.4.1 is not possible. The download link points to the 1.5 download and changing the path manually to 1.4.1 produces a 404 error. So how can I download 1.4.1? Sebastian -- Mit freundlichen Grüßen / Best regards / Cordialement Sebastian Schneider, schnei...@dvz.fh-aachen.de
Non-Committer Checkout not working
Hello, I am trying to do a non-committer checkout of the source code but I always get the error 501: Not implemented. I am using TortoiseSVN for Windows and I tried to just check out the HEAD version: Checkout from http://svn.apache.org/repos/asf/webservices/axis2/trunk/java, revision HEAD, Fully recursive, Externals excluded Server sent unexpected return value (501 Not Implemented) in response to OPTIONS request for 'http://svn.apache.org/repos/asf/webservices/axis2/trunk/java' Anything special to consider? Thanks for your help, Sebastian -- Mit freundlichen Grüßen / Best regards / Cordialement Sebastian Schneider, schnei...@dvz.fh-aachen.de
Generate service.xml on the command line
Hello Axis2 users! I have used Eclipse with WTP to create my webservice and a WSDL-file was generated. However a service.xml is missing. Since reported in my previous mail the Service Archiver which offered a way to generate a service.xml is not working. I did not find the information how to generate a service.xml on the command line. Can anyone help? I've got way too many methods to write the service.xml manually. Thank you for your hints, Sebastian -- Mit freundlichen Grüßen / Best regards / Cordialement Sebastian Schneider, schnei...@dvz.fh-aachen.de
Service Archive Wizard - Eclipse Plug-in
Hello folks, I was using the service archive wizard a couple of times and it worked. But now I have encountered the following error. The wizard shows up but all the elements of the forms are missing. No way to select class files or to give any other input for the wizard. I deleted and reinstalled the plugin but the problem persists. Is this a bug which I should report in JIRA? By the way: Is 1.4.1 the latest version of the plugin? So there isn't a plugin for Axis2-1.5? I am using the latest version of Eclipse Europa (3.5.0). Best regards Sebastian -- Mit freundlichen Grüßen / Best regards / Cordialement Sebastian Schneider, schnei...@dvz.fh-aachen.de
Re: [Axis2] Deploying Axis2-1.5 on JBoss 5.0.0
Hello Robert, thank you for your help. I finally deleted the xerces.jar and the xm-apis.jar. Afterwards deploying worked without problems. Bye Sebastian -- Mit freundlichen Grüßen / Best regards / Cordialement Sebastian Schneider, schnei...@dvz.fh-aachen.de
[Axis2] Deploying Axis2-1.5 on JBoss 5.0.0
1) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) Any hints are highly appreciated. Sorry for the long stacktrace. Thank you and best regards, Sebastian -- Mit freundlichen Grüßen / Best regards / Cordialement Sebastian Schneider, schnei...@dvz.fh-aachen.de
