Search Results

Search found 134 results on 6 pages for 'axis2'.

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

Page 2/6 | < Previous Page | 1 2 3 4 5 6  | Next Page >

  • JBoss 6 error deploying Axis2

    - by manasouza
    I tried to deploy Axis2 war file (versions 1.6.1 and 1.5.6) on JBoss 6.0.0 and got the following error: ` DEPLOYMENTS IN ERROR: Deployment "vfs:///C:/Desenvolvimento/jboss-6.0.0.Final/server/default/deploy/ axis2.war" is in error due to the following reason(s): java.lang.ClassNotFoundEx ception: 1.0.com.sun.codemodel.JConditional at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(Dep loyersImpl.java:1228) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainD eployerImpl.java:905) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.c heckComplete(MainDeployerPlugin.java:87) [:6.0.0.Final] at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.che ckAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceB ootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceB ootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(A bstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.r un(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] ` Thanks in advance

    Read the article

  • Axis2 webservice (aar archive) properties file

    - by XpiritO
    Hi there, guys. I'm currently developing a set of SOAP webservices over Axis2, deployed over a clustered WebLogic 10.3.2 environment. My webservices use some user settings that I want to be editable without the need for recompiling and regenerating the AAR archive. With this in mind, I chose to put them into a properties file that is loaded and consumed in runtime. Unfortunately, I'm having some questions about this: As far as I know, to achieve what I want, the only option is to put the properties file into the ../axis2/WEB-INF/classes directory of each one of the deployments (on each WebLogic instance) I currently have on my clustered configuration, and then load the file, as follows (or equivalent, this has not been verified for optimization): InputStreamReader fMainProp = new InputStreamReader(this.getClass().getResourceAsStream("myfile.properties")); Properties mainProp = new Properties(); mainProp.load(fMainProp); This is not as practical as I wanted it to be, because each time I want to alter some setting on the properties file, I have to edit each one of the files (deployed over different WebLogic instances) and there is a high probability of modifying one of these files without modifying the others. What I would like to know is if there is any (better) alternative to accomplish what I want, minimizing the potential conflict of configuration that is created by distributing and replicating the properties file through multiple WebLogic instances.

    Read the article

  • Steps in creating a web service using Axis2 - The client code

    - by zengr
    I am trying to create a web service, my tools of trade are: ** Axis2, Eclipse, Tomcat, Ant ** I need to create a web service from Code, i.e. Write a basic java class which will have the methods to be declared in the WSDL. Then use java2WSDL.sh to create my WSDL. So, is this approach correct: Write my Java class with actual business logic package packageNamel; public class Hello{ public void World(String name) { SOP("Hello" + name); } } Now, when I pass this Hello.java to java2WSDL.sh, this will give me the WSDL. Finally, I will write the services.xml file, and create the Hello.aar with following dir structure: Hello.aar packageName Hello.class META-INF services.xml MANIFEST.MF Hello.WSDL Now, I assume, my service will be deployed when I put the aar in tomcat1/webapps/axis2/WEB-INF/services But, here comes my problem, HOW DO I ACCESS THE METHOD World(String name)???!!, i.e. I am clueless about the client code! Please enlighten me on making a very basic web service and calling the method. The above described 3 steps might be wrong. It's a community wiki, feel free to edit. Thanks

    Read the article

  • How can I setup dependencies for Axis2 / Axiom on Maven2

    - by ronaldocpontes
    I've tried the following settings on pom.xml to use Axis2 wsdl2code: <dependencies> <dependency> <groupId>org.apache.axis2</groupId> <artifactId>axis2</artifactId> <version>1.5.1</version> </dependency> </dependencies> ... <build> <plugins> <plugin> <groupId>org.apache.axis2</groupId> <artifactId>axis2-wsdl2code-maven-plugin</artifactId> <version>1.5.1</version> <executions> <execution> <goals> <goal>wsdl2code</goal> </goals> <configuration> <packageName>com.site.package</packageName> <wsdlFile>http://www.site.com/api/v2_soap?wsdl=1</wsdlFile> <databindingName>xmlbeans</databindingName> </configuration> </execution> </executions> </plugin> ... </plugins> ... </build> Whenever I run mvn clean, I get the following warnings with a ClassNotFoundException showing no signs of org.apache.axiom. [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.codehaus.plexus:plexus-utils:pom:1.4.9:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.codehaus.plexus:plexus-utils at C:\Users\Ronaldo.m2\repository\org\codehaus\plexus\plexus-utils\1.4.9\plexus-utils-1.4.9.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.maven:maven-plugin-api:pom:2.0.7:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.maven:maven-plugin-api at C:\Users\Ronaldo.m2\repository\org\apache\maven\maven-plugin-api\2.0.7\maven-plugin-api-2.0.7.pom [WARNING] POM for 'org.apache.maven:maven-artifact:pom:2.0.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.maven:maven-artifact at C:\Users\Ronaldo.m2\repository\org\apache\maven\maven-artifact\2.0.8\maven-artifact-2.0.8.pom [WARNING] POM for 'org.apache.maven:maven-project:pom:2.0.7:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.maven:maven-project at C:\Users\Ronaldo.m2\repository\org\apache\maven\maven-project\2.0.7\maven-project-2.0.7.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.geronimo.specs:geronimo-stax-api_1.0_spec at C:\Users\Ronaldo.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.pom [WARNING] POM for 'commons-io:commons-io:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-io:commons-io at C:\Users\Ronaldo.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-api:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-api at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.8\axiom-api-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-impl:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-impl at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.8\axiom-impl-1.2.8.pom [WARNING] POM for 'org.apache.ws.commons.axiom:axiom-dom:pom:1.2.8:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.ws.commons.axiom:axiom-dom at C:\Users\Ronaldo.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.8\axiom-dom-1.2.8.pom [WARNING] POM for 'javax.mail:mail:pom:1.4:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project javax.mail:mail at C:\Users\Ronaldo.m2\repository\javax\mail\mail\1.4\mail-1.4.pom [WARNING] POM for 'xalan:xalan:pom:2.7.0:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project xalan:xalan at C:\Users\Ronaldo.m2\repository\xalan\xalan\2.7.0\xalan-2.7.0.pom [WARNING] POM for 'org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:pom:1.0.1:runtime' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache

    Read the article

  • Axis2 Web Service Client Generation - Types without modifying the client

    - by sstarcher
    Is it possible with Axis2 and Eclipse to generate a Web Service client and have it use java types that you already have in packages instead of creating it's own types. Reason being of course if I have type A already created and it creates it's own Type A I can't just assign variable of type A to variable of type B. The wsdl is being generated from a Web Service deployed to an application server. If it's not possible to generate it from that would it be possible to generate a client from the already existing java files.

    Read the article

  • Log axis2 client requests and responses

    - by Manuel Darveau
    I would like to log all requests/responses made by an axis2 client. I tried to create a file called client-config.wsdd as describer in http://code.google.com/support/bin/answer.py?hl=en&answer=15137 but without success (I don't get a log file). Requests are made over https and I am not sure if it matters. I tried <transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/> and <transport name="https" pivot="java:org.apache.axis.transport.http.HTTPSender"/> without success.

    Read the article

  • SOAP: JWSDP Webservice and Axis2 Client?

    - by Sophomore
    Just a plain simple question to which I could'nt find a straight answer... I'm building a SOAP webservice which is supposed to deliver some data to a client. (Actually it's RDF parsed/stripped to XML)... I'd like to use JWSDP which will generate WDSL specification. Are there any downfalls when the client is using axis2 instead of JWSDP? My intention was, that this shouldn't matter, as this is what WSDL is meant for, but I wanted to check before there arise any incompatibilities or problems...

    Read the article

  • How to use log4j for a axis2 webservice

    - by KItis
    I have created a simple axis2 webservice to understand logging functionality in a webservice. in this sample webservice, when a client calls this webservice, first it reads the log4j.property file. then i can see the logs being printed on console. but i have included file appender too into the property file. but i can not file the log file any where in my sample webapplication. i am using tomcat to run the webservice. following is webservice interface method called by client. package test; import java.io.IOException; import java.io.InputStream; import java.util.Properties; import org.apache.log4j.BasicConfigurator; import org.apache.log4j.Logger; import org.apache.log4j.PropertyConfigurator; public class WSInterface { static final Logger logger = Logger.getLogger(WSInterface.class); public String log4jTest(String input){ InputStream inputStream = this.getClass().getClassLoader() .getResourceAsStream(input); Properties properties = new Properties(); System.out.println("InputStream is: " + inputStream); //load the inputStream using the Properties try { properties.load(inputStream); } catch (IOException e) { // TODO Auto-generated catch block e.printStackTrace(); } PropertyConfigurator.configure(properties); logger.debug("Hello World!"); Class myclass = WSInterface.class; String url = myclass.getResource("WSInterface.class").toString(); String output = ""; return url; } }

    Read the article

  • Use a non-coalescing parser in Axis2

    - by Nathan
    Does anyone know how I can get Axis2 to use a non-coalescing XMLStreamReader when it parses a SOAP message? I am writing code that reads a large base64 binary text element. Coalescing is the default behaviour, and this causes the default XMLStreamReader to load the entire text into memory rather than returning multiple CHARACTERS events. The upshot of this is that I run out of heap space when running the following code: reader = element.getTextAsStream( true ); The OutOfMemory error occurs in com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next: java.lang.OutOfMemoryError: Java heap space at com.sun.org.apache.xerces.internal.util.XMLStringBuffer.append(XMLStringBuffer.java:208) at com.sun.org.apache.xerces.internal.util.XMLStringBuffer.append(XMLStringBuffer.java:226) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanContent(XMLDocumentFragmentScannerImpl.java:1552) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2864) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:558) at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225) at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34) at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225) at org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.next(SJSXPStreamReaderWrapper.java:138) at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:668) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214) at org.apache.axiom.om.impl.llom.SwitchingWrapper.updateNextNode(SwitchingWrapper.java:1098) at org.apache.axiom.om.impl.llom.SwitchingWrapper.<init>(SwitchingWrapper.java:198) at org.apache.axiom.om.impl.llom.OMStAXWrapper.<init>(OMStAXWrapper.java:73) at org.apache.axiom.om.impl.llom.OMContainerHelper.getXMLStreamReader(OMContainerHelper.java:67) at org.apache.axiom.om.impl.llom.OMContainerHelper.getXMLStreamReader(OMContainerHelper.java:40) at org.apache.axiom.om.impl.llom.OMElementImpl.getXMLStreamReader(OMElementImpl.java:790) at org.apache.axiom.om.impl.llom.OMElementImplUtil.getTextAsStream(OMElementImplUtil.java:114) at org.apache.axiom.om.impl.llom.OMElementImpl.getTextAsStream(OMElementImpl.java:826) at org.example.UploadFileParser.invokeBusinessLogic(UploadFileParser.java:160)

    Read the article

  • Axis2 SOAP Envelope Header Information

    - by BigZig
    I'm consuming a web service that places an authentication token in the SOAP envelope header. It appears (through looking at the samples that came with the WS WSDL) that if the stub is generated in .NET, this header information is exposed through a member variable in the stub class. However, when I generate my Axis2 java stub using WSDL2Java it doesn't appear to be exposed anywhere. What is the correct way to extract this information from the SOAP envelope header? WSDL: http://www.vbar.com/zangelo/SecurityService.wsdl C# Sample: using System; using SignInSample.Security; // web service using SignInSample.Document; // web service namespace SignInSample { class SignInSampleClass { [STAThread] static void Main(string[] args) { // login to the Vault and set up the document service SecurityService secSvc = new SecurityService(); secSvc.Url = "http://localhost/AutodeskDM/Services/SecurityService.asmx"; secSvc.SecurityHeaderValue = new SignInSample.Security.SecurityHeader(); secSvc.SignIn("Administrator", "", "Vault"); DocumentServiceWse docSvc = new DocumentServiceWse(); docSvc.Url = "http://localhost/AutodeskDM/Services/DocumentService.asmx"; docSvc.SecurityHeaderValue = new SignInSample.Document.SecurityHeader(); docSvc.SecurityHeaderValue.Ticket = secSvc.SecurityHeaderValue.Ticket; docSvc.SecurityHeaderValue.UserId = secSvc.SecurityHeaderValue.UserId; } } } The sample illustrates what I'd like to do. Notice how the secSvc instance has a SecurityHeaderValue member variable that is populated after a successful secSvc.SignIn() invocation. Here's some relevant API documentation regarding the SignIn method: Although there is no return value, a successful sign in will populate the SecurityHeaderValue of the security service. The SecurityHeaderValue information is then used for other web service calls.

    Read the article

  • How to tell axis2 to use an existing object as a service?

    - by Christian Hausknecht
    I am trying to expose some methods of a running application as a webservice. The core idea is to use an embedded web-server and send the soap messages to the apache axis2 framework in order to invoke the services. The problem is, that axis2's createService methods only accept Classes as parameter, not existing objects. So I believe that axis2 itself creates an object of the service class and then uses it to call methods when an external service call arrives. But I need to pass an existing object for being used as a service, because I need to call methods of other objects of the running application within the service methods. So the "standard" way that axis2 creates a new instance of the service class and calls then its methods is obviously no sulution for me. So is there a way to realize this? Or is there another solution? Perhaps you can pass objects later on to the allready created service object by axis2? If there is another solution without axis2 I might consider that one. Basically I am only interested in exposing some functionality of a runnning application as a webservice.

    Read the article

  • Axis2 and WSDL2Java: SOAP header is missing

    - by lasombra
    I've generated the java code from wsdl using WSDL2Java. I create a SOAP requestand I send it to the server, which answers with an AxisFault. If I have a look in the soap request there is now header tag . Why not? Does the follwing line in the stub not add a header? // adding SOAP soap_headers _serviceClient.addHeadersToEnvelope(env); What would be the solution to add a header, so that the SOAP request looks like that: <?xml version='1.0' encoding='UTF-8'?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header/> <soapenv:Body> ... </soapenv:Body> </soapenv:Envelope>

    Read the article

  • Apache Axis2 1.5.1 and NTLM Authentication

    - by arcticpenguin
    I've browsed all of the discussions here on StackOverflow regarding NTLM and Java, and I can't seem to find the answer. I'll try and be much more specific. Here's some code that returns a client stub that (I hope) is configured for NTLM authentication: ServiceStub getService() { try { ServiceStub stub = new ServiceStub( "http://myserver/some/path/to/webservices.asmx"); // this service is hosted on IIS List<String> ntlmPreferences = new ArrayList<String>(1); ntlmPreferences.add(HttpTransportProperties.Authenticator.NTLM); HttpTransportProperties.Authenticator ntlmAuthenticator = new HttpTransportProperties.Authenticator(); ntlmAuthenticator.setPreemptiveAuthentication(true); ntlmAuthenticator.setAuthSchemes(ntlmPreferences); ntlmAuthenticator.setUsername("me"); ntlmAuthenticator.setHost("localhost"); ntlmAuthenticator.setDomain("mydomain"); Options options = stub._getServiceClient().getOptions(); options.setProperty(HTTPConstants.AUTHENTICATE, ntlmAuthenticator); options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, "true"); stub._getServiceClient().setOptions(options); return stub; } catch (AxisFault e) { e.printStackTrace(); } return null; } This returns a valid SerivceStub object. When I try to invoke a call on the stub, I see the following in my log: Jun 9, 2010 12:12:22 PM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: NTLM authentication scheme selected Jun 9, 2010 12:12:22 PM org.apache.commons.httpclient.HttpMethodDirector authenticate SEVERE: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials Does anyone have a solution to this issue?

    Read the article

  • Embedded AXIS2: Serving a custom WSDL

    - by Maik
    I am using a console app that starts several axis instances without using a packages archive. Like this: AxisService axisService2 = AxisService.createService( new Myclass.getClass().getName(), axisConfigurationContext.getAxisConfiguration()); axisService2.addParameter(new Parameter("useOriginalwsdl", "true")); axisConfigurationContext.getAxisConfiguration().addService(axisService2); Now, I need to serve a custom WSDL. I tried adding a META-INF folder to the bin-root, and in various other places, but with no success. How do I specify in this case the location of a custom WSDL? Thanks!

    Read the article

  • How to Setup Eclipse to Start Writing Web Services using Axis2

    - by Mubashar Ahmad
    Dear Gurus I am a .net Developer but now a days i want to setup Eclipse to write a sample web services to test the capacity of Java/Axis over WCF/BasicHttpBindings. I found a couple of articles regarding the setup procedures but they are too old or their wording is may be for java or eclipse experts. Can anyone please give me detailed instruction on how can I get to work quickly. I tried my best but i can't even setup TomCat properly its not starting and throwing exception when i try to start it from eclipse servers windows. Please some one give me a latest and novice level article. Regards

    Read the article

  • running jar in a terminal using axis2

    - by Emilio
    I'm trying to run in the command line a java application distributed in a jar file. It call an axis2 web service, so the jar contains a /axis2client directory with rampart.mar security module. It works fine while I run it in netbeans, but it throws an exception if I try to run it in a terminal using this command: java -jar myfile.jar The Exception: org.apache.axis2.AxisFault: invalid url: //file:/home/xxx/Desktop/myfile.jar!/axis2client/ (java.net.MalformedURLException: no protocol: //file:/home/xxx/Desktop/myfile.jar) As you can see, it's trying to use the /axis2client directory inside the jar, as when I run it in Netbeans, but It fails with a MalformedURLException. I think it's something about the protocol 'file:', probably '//file:/' must be 'file:///'. The problem is that I cannot change this call to the directory because the method that loads the /axis2client directory it's not mine, it's from another library that use my project and include all the axis2 support. So, any idea?? Thanks in advance lads!

    Read the article

  • where are the log files saved in axis2 webservice

    - by KItis
    i have put log4j.properties file into WEB-INF/classes folder in my axis 2 webservice. now i can see logs been printed on console. but i have also put file appender. but i can not find the log file anywhere. could someone help me to find a solution for this problem. log4j.rootLogger=DEBUG, CA, FA #Console Appender log4j.appender.CA=org.apache.log4j.ConsoleAppender log4j.appender.CA.layout=org.apache.log4j.PatternLayout log4j.appender.CA.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n #File Appender log4j.appender.FA=org.apache.log4j.FileAppender log4j.appender.FA.File=ws.log log4j.appender.FA.layout=org.apache.log4j.PatternLayout log4j.appender.FA.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n # Set the logger level of File Appender to WARN log4j.appender.FA.Threshold = WARN

    Read the article

  • Can I make Axis2 generate a WSDL with 'unwrapped' types?

    - by Bedwyr Humphreys
    I'm trying to consume a hello world AXIS2 SOAP web service using a PHP client. The Java class is written in Netbeans and the AXIS2 aar file is generated using the Netbeans AXIS2 plugin. You've all seen it before but here's the java class: public class SOAPHello { public String sayHello(String username) { return "Hello, "+username; } } The wsdl genereated by AXIS2 seems to wrap all the parameters so that when I consume the service i have to use a crazy PHP script like this: $client = new SoapClient("http://myhost:8080/axis2/services/SOAPHello?wsdl"); $parameters["username"] = "Dave"; $response = $client->sayHello($parameters)->return; echo $response."!"; When all I really want to do is echo $client->sayHello("Dave")."!"; My question is two-fold: why is this happening? and what can I do to stop it? :) Here's are the types, message and porttype sections of the generated wsdl: <wsdl:types> <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://soap.axis2.myhost.co.uk"> <xs:element name="sayHello"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="username" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="sayHelloResponse"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> </wsdl:types> <wsdl:message name="sayHelloRequest"> <wsdl:part name="parameters" element="ns:sayHello"/> </wsdl:message> <wsdl:message name="sayHelloResponse"> <wsdl:part name="parameters" element="ns:sayHelloResponse"/> </wsdl:message> <wsdl:portType name="SOAPHelloPortType"> <wsdl:operation name="sayHello"> <wsdl:input message="ns:sayHelloRequest" wsaw:Action="urn:sayHello"/> <wsdl:output message="ns:sayHelloResponse" wsaw:Action="urn:sayHelloResponse"/> </wsdl:operation> </wsdl:portType>

    Read the article

  • Can/should one disable namespace validation in Axis2 clients using ADB databinding?

    - by RJCantrell
    I have an document/literal Axis 1 service which I'm consuming with an Axis 2 client (ADB databinding, generated from WSDL2Java). It receives a valid XML response, but in parsing that XML, I get the error "Unexpected Subelement" for any type which doesn't have a namespace defined in the response. I can resolve the error by manually changing the (auto-generated by Axis2) type-validation line to only check the type name and not the namespace as well, but is there a non-manual way to skip this? This service is consumed properly by other Axis 1 clients. Here's the response, with bits in ALL CAPS having been anonymized. Some types have namespaces, some have empty-string namespaces, and some have none at all. Can I control this via the service's WSDL, or in Axis2's WSDL2Java handling of the WSDL? Is there a fundamental mismatch between Axis 1 and Axis2? The response below looks correct, except perhaps for where that type (anonymized as TWO below) is nested within itself. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <SERVICENAMEResponse xmlns="http://service.PROJECT.COMPANY.com"> <SERVICENAMEReturn xmlns=""> <ONE></ONE> <TWO><TWO> <THREE>2</THREE> <FOUR>-10</FOUR> <FIVE>6</FIVE> <SIX>1</SIX> </TWO></TWO> <fileName></fileName> </SERVICENAMEReturn></SERVICENAMEResponse> </soapenv:Body></soapenv:Envelope> I did not have to modify the validation of the "SERVICENAMEResponse" object because it has the correct namespace specified, but I have to so for all its subelements. The manual modification that I can make (one per type) to fix this is to change: if (reader.isStartElement() && new javax.xml.namespace.QName("http://dto.PROJECT.COMPANY.com","ONE").equals(reader.getName())){ to: if (reader.isStartElement() && new javax.xml.namespace.QName("ONE").equals(reader.getName())){

    Read the article

  • Axis error about runtime location

    - by Ayrad
    The error is: Exception occurred while reading or writing file {0}The Axis2 facets cannot be installed since the Axis2 runtime location has not been set. Go to the Web Services preference page and set the Axis2 runtime location under Axis2 Preferences. In the preferences mentioned, the location is set correctly and in fact, it says "Axis2 runtime loaded successfully" after loadign the correct runtime location. So what's going on? Any solutions other than re-installing eclipse or creating a new workspace? I am using Axis2 1.4.1 and eclipse.

    Read the article

  • How i can convert client for Axis 1.4 to Axis2 in JAVA ?

    - by dahevos
    Hello, First of all i success to programming a client for an Axis 1.2 web service, but for Axis2 i don't know how i can do, and the tutorial in Apache don't really help me. Here my code : import java.net.URL; import javax.xml.namespace.QName; import org.apache.axis.client.Call; import org.apache.axis.client.Service; public class EmployeClient { public static void main(String [] args) throws Exception { Service service = new Service(); Call call = (Call)service.createCall(); String endpoint = "http://localhost:8080/axis/services/EmployeService"; call.setTargetEndpointAddress(new URL(endpoint)); call.setOperationName(new QName("getCurrentID")); String dept = "marketing"; String name = "sacha"; String position = (String)call.invoke(new Object [] {new String(dept), new String(name)}); System.out.println("Résultat de la recherche : " + position ); } } So how can i do for convert this code in Axis2 ? Thanks you very much. ps : i'm french, sorry for my bad english !

    Read the article

  • Connection to webservice times out first time

    - by Neo
    My application needs to connect to a web service. The WSDL file given by the client was converted to java using the wsdl2java utility in axis 2-1.5.2. The problem occurs during the first connection to the webservice. It gives me java.net.SocketTimeoutException: Read timed out at jrockit.net.SocketNativeIO.readBytesPinned(Native Method) at jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:46) at java.net.SocketInputStream.socketRead0(SocketInputStream.java) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:747) at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:238) at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78) at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106) at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413) at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1974) at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1100) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:438) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:230) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:166) at com.jmango.webservice.talker.WCFServiceStub.addSaleSupportRequest(WCFServiceStub.java:270) at com.jmango.domain.salessystem.talkerimp.RequestServiceInfoImp.addanewServiceRequest(RequestServiceInfoImp.java:58) at com.jmango.mobilenexus.service.MobileServiceImp.sendQueryforServiceInfo(MobileServiceImp.java:358) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.remoting.support.RemoteInvocationTraceInterceptor.invoke(RemoteInvocationTraceInterceptor.java:77) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy8.sendQueryforServiceInfo(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.caucho.hessian.server.HessianSkeleton.invoke(HessianSkeleton.java:180) at com.caucho.hessian.server.HessianSkeleton.invoke(HessianSkeleton.java:110) at org.springframework.remoting.caucho.Hessian2SkeletonInvoker.invoke(Hessian2SkeletonInvoker.java:94) at org.springframework.remoting.caucho.HessianExporter.invoke(HessianExporter.java:142) at org.springframework.remoting.caucho.HessianServiceExporter.handleRequest(HessianServiceExporter.java:70) at org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter.handle(HttpRequestHandlerAdapter.java:50) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:807) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:512) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:718) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:111) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:776) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:705) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:899) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:619) I tried searching the web for answers though there was one place which mentions it could be the firewall at the webservice end that is blocking, I wasnt able to find a valid solution. Any help will be much appreciated. Running: Apache Tomcat 6.0 Axis2 1.5.2

    Read the article

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

< Previous Page | 1 2 3 4 5 6  | Next Page >