Problem with compilation of Axis2
Does the axis2-1.4.1 src build work? With what version of maven? If it does what am I doing wrong? Thanks, details follow... I am developing with axis2-1.4.1 in order to use Eclipse axis plugins. ( I de3installed 1.5.1 ) I am building on Windows Server 2008 x64. I am trying to build the axis2-1.4 source release ( outside of Eclipse ) using maven. I had problems with the latest release of maven so moved to apache-maven-2.0.10, as another post recommended this. I am still having problems. I have followed the maven install instructions and the axis build instructions. It would appear that when I run mvn install and maven attempts to download various components it is having problems; ( The following is just one set of problems relating to commons-httpclient, buit there are more with the same pattern ) Downloading: https://maven-repository.dev.java.net/nonav/repository//commons-httpclient/p oms/commons-httpclient-3.1.pom 371b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '402c45f736161f8d5a937f872c83fc014f6e5eae'; remote = '!DOCTYPE' - RETRYING Downloading: https://maven-repository.dev.java.net/nonav/repository//commons-httpclient/p oms/commons-httpclient-3.1.pom 371b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '402c45f736161f8d5a937f872c83fc014f6e5eae'; remote = '!DOCTYPE' - IGNORING [WARNING] POM for 'commons-httpclient:commons-httpclient:pom:3.1:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-httpclient:commons-httpclient at C:\Users\Administrator\.m2\repository\commons-httpclient\commons-httpclient\ 3.1\commons-httpclient-3.1.pom ... error: error reading C:\Users\Administrator\.m2\repository\commons-httpclient\commons-httpclient\ 3.1\commons-httpclient-3.1.jar; error in opening zip file ... When I look in the POMs I find... !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=http://download.java.net/maven/1/commons-httpclient/poms/commons-httpc lient-3.1.pom http://download.java.net/maven/1/commons-httpclient/poms/commons-httpclient -3.1.pom here/a./p hr addressApache Server at maven-repository.dev.java.net Port 443/address /body/html and ofcourse the accompanying zip is not valid 1K. -- This message is private and confidential. If you have received this message in error, please notify postmas...@his.co.uk and remove it from your system. Please carry out your own virus check before opening attachments. HISL Limited is a limited company registered in England and Wales. Registered Number: 3202995. VAT number: 729-6256-05. Registered Office: Chestnut Farm, Jill Lane, Sambourne, Redditch B96 6ES --
unsubscribe
From: John Francis [mailto:jfran...@his.co.uk] Sent: 10 November 2009 12:14 To: axis-user@ws.apache.org Subject: Problem with compilation of Axis2 Does the axis2-1.4.1 src build work? With what version of maven? If it does what am I doing wrong? Thanks, details follow... I am developing with axis2-1.4.1 in order to use Eclipse axis plugins. ( I de3installed 1.5.1 ) I am building on Windows Server 2008 x64. I am trying to build the axis2-1.4 source release ( outside of Eclipse ) using maven. I had problems with the latest release of maven so moved to apache-maven-2.0.10, as another post recommended this. I am still having problems. I have followed the maven install instructions and the axis build instructions. It would appear that when I run mvn install and maven attempts to download various components it is having problems; ( The following is just one set of problems relating to commons-httpclient, buit there are more with the same pattern ) Downloading: https://maven-repository.dev.java.net/nonav/repository//commons-httpclie nt/poms/commons-httpclient-3.1.pom https://maven-repository.dev.java.net/nonav/repository/commons-httpclie nt/poms/commons-httpclient-3.1.pom 371b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '402c45f736161f8d5a937f872c83fc014f6e5eae'; remote = '!DOCTYPE' - RETRYING Downloading: https://maven-repository.dev.java.net/nonav/repository//commons-httpclie nt/poms/commons-httpclient-3.1.pom https://maven-repository.dev.java.net/nonav/repository/commons-httpclie nt/poms/commons-httpclient-3.1.pom 371b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '402c45f736161f8d5a937f872c83fc014f6e5eae'; remote = '!DOCTYPE' - IGNORING [WARNING] POM for 'commons-httpclient:commons-httpclient:pom:3.1:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-httpclient:commons-httpclient at C:\Users\Administrator\.m2\repository\commons-httpclient\commons-httpcli ent\3.1\commons-httpclient-3.1.pom ... error: error reading C:\Users\Administrator\.m2\repository\commons-httpclient\commons-httpcli ent\3.1\commons-httpclient-3.1.jar; error in opening zip file ... When I look in the POMs I find... !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=http://download.java.net/maven/1/commons-httpclient/poms/commons-h ttpclient-3.1.pomhere/a./p http://download.java.net/maven/1/commons-httpclient/poms/commons-httpcl ient-3.1.pom hr addressApache Server at maven-repository.dev.java.net Port 443/address /body/html and ofcourse the accompanying zip is not valid 1K. -- This message is private and confidential. If you have received this message in error, please notify postmas...@his.co.uk and remove it from your system. Please carry out your own virus check before opening attachments. HISL Limited is a limited company registered in England and Wales. Registered Number: 3202995. VAT number: 729-6256-05. Registered Office: Chestnut Farm, Jill Lane, Sambourne, Redditch B96 6ES -- -- Scanned by iCritical.
Re: Problem with compilation of Axis2
John, As you can see the maven repo on java.net has started redirecting :( Please create a settings.xml see details on where to create the file here: http://maven.apache.org/settings.html The content of the file should be: settings mirrors mirror idjava.net.2/id namejava.net Mirror of http://repo1.maven.org/maven2//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors /settings thanks, dims On 11/10/2009 07:13 AM, John Francis wrote: Does the axis2-1.4.1 src build work? With what version of maven? If it does what am I doing wrong? Thanks, details follow... I am developing with axis2-1.4.1 in order to use Eclipse axis plugins. ( I de3installed 1.5.1 ) I am building on Windows Server 2008 x64. I am trying to build the axis2-1.4 source release ( outside of Eclipse ) using maven. I had problems with the latest release of maven so moved to apache-maven-2.0.10, as another post recommended this. I am still having problems. I have followed the maven install instructions and the axis build instructions. It would appear that when I run mvn install and maven attempts to download various components it is having problems; ( The following is just one set of problems relating to commons-httpclient, buit there are more with the same pattern ) Downloading: https://maven-repository.dev.java.net/nonav/repository//commons-httpclient/p oms/commons-httpclient-3.1.pom 371b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '402c45f736161f8d5a937f872c83fc014f6e5eae'; remote = '!DOCTYPE' - RETRYING Downloading: https://maven-repository.dev.java.net/nonav/repository//commons-httpclient/p oms/commons-httpclient-3.1.pom 371b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '402c45f736161f8d5a937f872c83fc014f6e5eae'; remote = '!DOCTYPE' - IGNORING [WARNING] POM for 'commons-httpclient:commons-httpclient:pom:3.1:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-httpclient:commons-httpclient at C:\Users\Administrator\.m2\repository\commons-httpclient\commons-httpclient\ 3.1\commons-httpclient-3.1.pom ... error: error reading C:\Users\Administrator\.m2\repository\commons-httpclient\commons-httpclient\ 3.1\commons-httpclient-3.1.jar; error in opening zip file ... When I look in the POMs I find... !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moveda href=http://download.java.net/maven/1/commons-httpclient/poms/commons-httpc lient-3.1.pom http://download.java.net/maven/1/commons-httpclient/poms/commons-httpclient -3.1.pom here/a./p hr addressApache Server at maven-repository.dev.java.net Port 443/address /body/html and ofcourse the accompanying zip is not valid 1K. -- This message is private and confidential. If you have received this message in error, please notify postmas...@his.co.uk and remove it from your system. Please carry out your own virus check before opening attachments. HISL Limited is a limited company registered in England and Wales. Registered Number: 3202995. VAT number: 729-6256-05. Registered Office: Chestnut Farm, Jill Lane, Sambourne, Redditch B96 6ES --
Re: Problem with compilation of Axis2
Oh! also nuke your .m2/repository and start fresh. thanks, dims On 11/10/2009 07:39 AM, Davanum Srinivas wrote: John, As you can see the maven repo on java.net has started redirecting :( Please create a settings.xml see details on where to create the file here: http://maven.apache.org/settings.html The content of the file should be: settings mirrors mirror idjava.net.2/id namejava.net Mirror of http://repo1.maven.org/maven2//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors /settings thanks, dims On 11/10/2009 07:13 AM, John Francis wrote: Does the axis2-1.4.1 src build work? With what version of maven? If it does what am I doing wrong? Thanks, details follow... I am developing with axis2-1.4.1 in order to use Eclipse axis plugins. ( I de3installed 1.5.1 ) I am building on Windows Server 2008 x64. I am trying to build the axis2-1.4 source release ( outside of Eclipse ) using maven. I had problems with the latest release of maven so moved to apache-maven-2.0.10, as another post recommended this. I am still having problems. I have followed the maven install instructions and the axis build instructions. It would appear that when I run mvn install and maven attempts to download various components it is having problems; ( The following is just one set of problems relating to commons-httpclient, buit there are more with the same pattern ) Downloading: https://maven-repository.dev.java.net/nonav/repository//commons-httpclient/p oms/commons-httpclient-3.1.pom 371b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '402c45f736161f8d5a937f872c83fc014f6e5eae'; remote = '!DOCTYPE' - RETRYING Downloading: https://maven-repository.dev.java.net/nonav/repository//commons-httpclient/p oms/commons-httpclient-3.1.pom 371b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '402c45f736161f8d5a937f872c83fc014f6e5eae'; remote = '!DOCTYPE' - IGNORING [WARNING] POM for 'commons-httpclient:commons-httpclient:pom:3.1:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project commons-httpclient:commons-httpclient at C:\Users\Administrator\.m2\repository\commons-httpclient\commons-httpclient\ 3.1\commons-httpclient-3.1.pom ... error: error reading C:\Users\Administrator\.m2\repository\commons-httpclient\commons-httpclient\ 3.1\commons-httpclient-3.1.jar; error in opening zip file ... When I look in the POMs I find... !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moveda href=http://download.java.net/maven/1/commons-httpclient/poms/commons-httpc lient-3.1.pom http://download.java.net/maven/1/commons-httpclient/poms/commons-httpclient -3.1.pom here/a./p hr addressApache Server at maven-repository.dev.java.net Port 443/address /body/html and ofcourse the accompanying zip is not valid 1K. -- This message is private and confidential. If you have received this message in error, please notify postmas...@his.co.uk and remove it from your system. Please carry out your own virus check before opening attachments. HISL Limited is a limited company registered in England and Wales. Registered Number: 3202995. VAT number: 729-6256-05. Registered Office: Chestnut Farm, Jill Lane, Sambourne, Redditch B96 6ES --
Axis 2: X.509, Rampart - Using credentials for authentication with no encryption/signing
Is it possible to use X509 for WS-Security authentication based on credentials from keystore, without encryption and without signature. If it is, what are the properties that you need to set in Rampart config, since it seems that you can only set the encryption and the signature keystores (and SSL keystores), but there is no property for authentication keystore. Regards, Sirish Software Engineer IBM Software Group
Re: Axis 2: X.509, Rampart - Using credentials for authentication with no encryption/signing
Can you please elaborate more on your requirement... Signing is also a way of authenticating. Thanks regards. -Prabath Sirish K Somanchi wrote: Is it possible to use X509 for WS-Security authentication based on credentials from keystore, without encryption and without signature. If it is, what are the properties that you need to set in Rampart config, since it seems that you can only set the encryption and the signature keystores (and SSL keystores), but there is no property for authentication keystore. Regards, Sirish Software Engineer IBM Software Group
Re: Axis2/Java 1.5.1 and Rampart
Please create a JIRA on the issue.
Alternatively you can attach the policy file to the client to get the
expected results.
Thanks regards.
-Prabath
SGE0 wrote:
Hi,
we have following services.xml file (part):
service name=Upload scope=application
...
module ref=rampart /
wsp:Policy wsu:Id=UsernameToken xmlns:wsu=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy;
wsp:ExactlyOne
wsp:All
sp:SupportingTokens
xmlns:sp=http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702;
wsp:Policy
sp:UsernameToken sp:IncludeToken=
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient;
wsp:Policy
sp:HashPassword/
/wsp:Policy
/sp:UsernameToken
/wsp:Policy
/sp:SupportingTokens
ramp:RampartConfig xmlns:ramp=http://ws.apache.org/rampart/policy;
ramp:passwordCallbackClass...security.PWCBHandler/ramp:passwordCallbackClass
/ramp:RampartConfig
/wsp:All
/wsp:ExactlyOne
/wsp:Policy
/service
When we generate the client stub with Java2WSDL we see that the
wsp:Policy
sp:HashPassword/
/wsp:Policy
is not correctly generated.
When we look at the populateAxisService method in the generated stub we see:
private void populateAxisService() throws org.apache.axis2.AxisFault {
...
(__operation).getMessage(org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_OUT_VALUE).getPolicySubject().attachPolicy(getPolicy(wsp:Policy
xmlns:wsp=\http://schemas.xmlsoap.org/ws/2004/09/policy\;wsp:ExactlyOnewsp:Allsp:SupportingTokens
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;wsp:Policysp:UsernameToken
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;
sp:IncludeToken=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient\;
//wsp:Policy/sp:SupportingTokenssp:SupportingTokens
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;wsp:Policysp:UsernameToken
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;
sp:IncludeToken=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient\;
//wsp:Policy/sp:SupportingTokens/wsp:All/wsp:ExactlyOne/wsp:Policy));
...
}
The result is that we can send over a plain text userid/pwd but not a hashed
password.
Anyone experiencing the same problem ?
S.
AW: OutOfMemoryError at WS call client side
Hi, I like to share the solution I have so far. I am involved in implementing a middleware which has to perform lots of web service calls, also in parallel. This means we cannot just share a service client for all our requests. I've found through debugging axis2 code that calling serviceClient.cleanup(), after I performed my web service call, removes the generated anonymous AxisService from the AxisConfiguration. I am assuming that this will prevent the OutOfMemoryError, but I could not verify it in tests yet. Can someone confirm that using the serviceClient this way is a good idea? Thank you, Matthias. -Ursprüngliche Nachricht- Von: Deepal jayasinghe [mailto:deep...@gmail.com] Gesendet: Samstag, 7. November 2009 01:42 An: axis-user@ws.apache.org Betreff: Re: OutOfMemoryError at WS call client side Hi, This is one of the common problem most of the users usually face. The reason behind this is whenever you create a serviceClient, it creates an AxisService and added to AxisConfiguration. In order to overcome this issues, create one service client and reuse that. Thanks, Deepal Dear Axis users, I currently have a memory problem when using Axis2. I implement a client for web service calls in a generic way, so that I can use my client for different types of services. My code to call the service generally looks like this: ServiceClient sender = *new* ServiceClient(/confContext/, *null*); setHeadersAndOptions(sender); //engaging modules and setting endpoint, etc. MessageContext reqMctx = createPayload(sender); //creating the request MessageContext OperationClient oc = sender.createClient(ServiceClient./ANON_OUT_IN_OP/); oc.addMessageContext(reqMctx); oc.execute(*true*); Through analyzing the heapdump I saw that inside the AxisConfiguration, a lot of AxisService instances are stored in a HashMap, around 10.000 in my case. I am using my AxisConfiguration as a static object for all calls since the Configuration does not change. Is it not a good idea to handle it thias way? I am thankful for any advise. Matthias. -- Thank you! http://blogs.deepal.org http://deepal.org
unsubscribe
unsubscribe
Kuehne + Nagel (AG Co.) KG, Geschaeftsleitung: Hans-Georg Brinkmann (Vors.), Dirk Blesius (Stellv.), Reiner Heiken (Stellv.), Bruno Mang, Alfred Manke, Christian Marnetté (Stellv.), Mark Reinhardt (Stellv.), Jens Wollesen, Rainer Wunn, Sitz: Bremen, Registergericht: Bremen, HRA 21928, USt-IdNr.: DE 812773878, Persoenlich haftende Gesellschaft: Kuehne Nagel A.G., Sitz: Contern/Luxemburg Geschaeftsfuehrender Verwaltungsrat: Klaus-Michael Kuehne
Re: Problem with compilation of Axis2
John, please add -DfailIfNoTests=false -Dtest=false when running maven. So you can ignore the errors and the artifacts you need get built. thanks, dims On 11/10/2009 09:28 AM, John Francis wrote: Thanks, I am now a lot further forward. However I do have test failures, and 2 remaining checksum errors. I did remove the old .m2 directory completely and rebuild from a fresh unzip of the axis download. Most worryingly the axis2.war is not built in the modules/webapp/target directory as described in the build instructions. Possible problems on my side; * JDK 1.6.0_13 * I am working on web apps on my eclipse tomcat install on port 8080 whilst doing this stuff. ( it has a separate axis2 env ) [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom - IGNORING [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.jar - IGNORING [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for com/sun/xml/fastinfoset/FastInfoset/1.1.8/FastInfoset-1.1.8.pom - IGNORING [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for com/sun/xml/fastinfoset/FastInfoset/1.1.8/FastInfoset-1.1.8.jar - IGNORING Are these checksum failiures ignorable? Test errors -are these failures benign?; --- Test set: org.apache.axis2.jaxws.dispatch.StringDispatchTests --- Tests run: 12, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 260.743 sec FAILURE! testSyncPayloadMode_badHostName(org.apache.axis2.jaxws.dispatch.StringDispat chTests) Time elapsed: 84.204 sec FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.apache.axis2.jaxws.dispatch.StringDispatchTests.testSyncPayloadMode_badH ostName(StringDispatchTests.java:315) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81 ) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62 ) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(Ab stractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractD irectoryTestSuite.java:165) at org.apache.maven.surefire.Surefire.run(Surefire.java:107) 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireB ooter.java:289) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:100 5) testAsyncCallbackMessageMode_badHostName(org.apache.axis2.jaxws.dispatch.Str ingDispatchTests) Time elapsed: 85.046 sec FAILURE! junit.framework.AssertionFailedError: java.net.ConnectException does not match expected type UnknownHostException at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.axis2.jaxws.dispatch.StringDispatchTests.testAsyncCallbackMessage Mode_badHostName(StringDispatchTests.java:355) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at
RE: Problem with compilation of Axis2
Thanks, I am now a lot further forward. However I do have test failures, and 2 remaining checksum errors. I did remove the old .m2 directory completely and rebuild from a fresh unzip of the axis download. Most worryingly the axis2.war is not built in the modules/webapp/target directory as described in the build instructions. Possible problems on my side; * JDK 1.6.0_13 * I am working on web apps on my eclipse tomcat install on port 8080 whilst doing this stuff. ( it has a separate axis2 env ) [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom - IGNORING [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.jar - IGNORING [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for com/sun/xml/fastinfoset/FastInfoset/1.1.8/FastInfoset-1.1.8.pom - IGNORING [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for com/sun/xml/fastinfoset/FastInfoset/1.1.8/FastInfoset-1.1.8.jar - IGNORING Are these checksum failiures ignorable? Test errors -are these failures benign?; --- Test set: org.apache.axis2.jaxws.dispatch.StringDispatchTests --- Tests run: 12, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 260.743 sec FAILURE! testSyncPayloadMode_badHostName(org.apache.axis2.jaxws.dispatch.StringDispat chTests) Time elapsed: 84.204 sec FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.apache.axis2.jaxws.dispatch.StringDispatchTests.testSyncPayloadMode_badH ostName(StringDispatchTests.java:315) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81 ) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62 ) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(Ab stractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractD irectoryTestSuite.java:165) at org.apache.maven.surefire.Surefire.run(Surefire.java:107) 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireB ooter.java:289) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:100 5) testAsyncCallbackMessageMode_badHostName(org.apache.axis2.jaxws.dispatch.Str ingDispatchTests) Time elapsed: 85.046 sec FAILURE! junit.framework.AssertionFailedError: java.net.ConnectException does not match expected type UnknownHostException at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.axis2.jaxws.dispatch.StringDispatchTests.testAsyncCallbackMessage Mode_badHostName(StringDispatchTests.java:355) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at
RuntimeException not generated correctly in the wsdl
Hi, I have my own exception SysException that externds RuntimeException However in the wsdl I don't see the RuntimeException defined well therefore when using soap ui to call myservice I get this: :0: error: src-resolve: type 'RuntimeException@ http://www.w3.org/2001/XMLSchema' not found. org.apache.xmlbeans.XmlException: .wsdl:0: error: src-resolve: type 'runtimeexcept...@http://www.w3.org/2001/XMLSchema' not found. In the generated wsdl i see: xs:complexType name=AppException xs:complexContent xs:extension base=ax22:Exception xs:sequence xs:element minOccurs=0 name=arg0 nillable=true type=xs:string/ xs:element minOccurs=0 name=arg1 nillable=true type=xs:string/ xs:element minOccurs=0 name=arg2 nillable=true type=xs:string/ xs:element minOccurs=0 name=arg3 nillable=true type=xs:string/ xs:element minOccurs=0 name=errorCode nillable=true type=xs:string/ /xs:sequence /xs:extension /xs:complexContent /xs:complexType xs:complexType name=SysException xs:complexContent xs:extension base=xs:RuntimeException xs:sequence xs:element minOccurs=0 name=arg0 nillable=true type=xs:string/ xs:element minOccurs=0 name=arg1 nillable=true type=xs:string/ xs:element minOccurs=0 name=arg2 nillable=true type=xs:string/ xs:element minOccurs=0 name=arg3 nillable=true type=xs:string/ xs:element minOccurs=0 name=errorCode nillable=true type=xs:string/ /xs:sequence /xs:extension /xs:complexContent /xs:complexType as you can see the Exception got ax22 while the RuntimeException got xs further I see this in wsdl: xs:complexType name=Exception xs:sequence xs:element minOccurs=0 name=Exception nillable=true type=xs:anyType/ /xs:sequence /xs:complexType However there is no such definition for RuntimeException. Can anyone assist me please to understand why the RuntimeException seem not to be generated well in wsdl? Note that If I add manually to wsdl a section like the Exception with RuntimeException like this: xs:complexType name=RuntimeException xs:sequence xs:element minOccurs=0 name=RuntimeException nillable=true type=xs:anyType/ /xs:sequence /xs:complexType and update also the RuntimeException from xs to ax22 I can call my service well with soap ui. Thanks
Best way to proxy soap requests...
Hi, I implemented a Web-Service, which gets all the request parameters and depending on some values it may have forward this request (with some altered values) to a second Web-Service. My question is if there is some kind of framework available, which takes care of the proxying part. To me, it seems not very scalable if I write a SOAP Client, which I instantiate and call in case I have to proxy the request. Thanks, -Reinhard
RE: Problem with compilation of Axis2
Yes, everything worked fine. A big thankyou, and kudos, dims -- This message is private and confidential. If you have received this message in error, please notify postmas...@his.co.uk and remove it from your system. Please carry out your own virus check before opening attachments. HISL Limited is a limited company registered in England and Wales. Registered Number: 3202995. VAT number: 729-6256-05. Registered Office: Chestnut Farm, Jill Lane, Sambourne, Redditch B96 6ES -- -Original Message- From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: 10 November 2009 14:35 To: axis-user@ws.apache.org Subject: Re: Problem with compilation of Axis2 John, please add -DfailIfNoTests=false -Dtest=false when running maven. So you can ignore the errors and the artifacts you need get built. thanks, dims
RE: Generated WSDL HTTPS Port not 8443
Hi, I have the same issue and very interested in finding a solution. Sanjay -Original Message- From: v2cg4ss [mailto:ssel...@datamentors.com] Sent: Monday, November 09, 2009 1:40 PM To: axis-user@ws.apache.org Subject: Re: Generated WSDL HTTPS Port not 8443 Is this in a nightly build that I can test? Will this be axis2 1.5.2? Andreas Veithen-2 wrote: On Thu, Nov 5, 2009 at 20:49, v2cg4ss ssel...@datamentors.com wrote: Thank you for the reply, is this being resolved soon. It is implemented, but the issue is not closed yet because the documentation is not up to date with the changes. I have a client using .NET and they are generating their client code from the WSDL. The programmer claims that they cannot change the endpoint in the .NET code like I can with java. MyWSStub stub = new MyWSStub(ctx, https://localhost:8443/axis2/services/MyWS;); Scott Andreas Veithen-2 wrote: Generating the correct endpoint URIs for https is something that doesn't work properly in the available Axis2 releases. See AXIS2-4465 and related issues. Andreas -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html Sent from the Axis - User mailing list archive at Nabble.com.
Nightly Build
I follow the link: http://people.apache.org/dist/axis2/nightly/ and the only folder available is the c folder. So where is the nightly build of the axis2 java? -- View this message in context: http://old.nabble.com/Nightly-Build-tp26286004p26286004.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Nightly Build
Try this one. http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/ Thanks, Deepal I follow the link: http://people.apache.org/dist/axis2/nightly/ and the only folder available is the c folder. So where is the nightly build of the axis2 java? -- Thank you! http://blogs.deepal.org http://deepal.org
RE: Generated WSDL HTTPS Port not 8443
I just tried the nightly build of 10-Nov-2009 14:33 and the endpoints look good: wsdl:service name=MyWS - wsdl:port name=MyWSHttpsSoap11Endpoint binding=ns:MyWSSoap11Binding soap:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.NetEffectWS_1HttpsSoap11Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpSoap11Endpoint binding=ns:MyWSSoap11Binding soap:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap11Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpSoap12Endpoint binding=ns:MyWSSoap12Binding soap12:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap12Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpsSoap12Endpoint binding=ns:MyWSSoap12Binding soap12:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsSoap12Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpsEndpoint binding=ns:MyWSHttpBinding http:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsEndpoint/; / /wsdl:port - wsdl:port name=MyWSHttpEndpoint binding=ns:MyWSHttpBinding http:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpEndpoint/; / /wsdl:port /wsdl:service So this is good, I also found that axis2 1.3 works as well. The problem I have now is a .NET client that is afraid to move forward with us using 1.5.1 knowing that someone on their end could refresh the endpoints via Visual Studio and blow up production. Yes, I agree that they should have test procedures in place...But I don't understand how this worked in axis2 1.3 and has been broken since 1.4.1, 1.5, and 1.5.1. I cannot download 1.4 to see if it is broken in that version but this is a major miss but someone. So I would like to vote for this issue to be resolved quickly and a 1.5.2 release be made. SanjayGupta wrote: Hi, I have the same issue and very interested in finding a solution. Sanjay -Original Message- From: v2cg4ss [mailto:ssel...@datamentors.com] Sent: Monday, November 09, 2009 1:40 PM To: axis-user@ws.apache.org Subject: Re: Generated WSDL HTTPS Port not 8443 Is this in a nightly build that I can test? Will this be axis2 1.5.2? Andreas Veithen-2 wrote: On Thu, Nov 5, 2009 at 20:49, v2cg4ss ssel...@datamentors.com wrote: Thank you for the reply, is this being resolved soon. It is implemented, but the issue is not closed yet because the documentation is not up to date with the changes. I have a client using .NET and they are generating their client code from the WSDL. The programmer claims that they cannot change the endpoint in the .NET code like I can with java. MyWSStub stub = new MyWSStub(ctx, https://localhost:8443/axis2/services/MyWS;); Scott Andreas Veithen-2 wrote: Generating the correct endpoint URIs for https is something that doesn't work properly in the available Axis2 releases. See AXIS2-4465 and related issues. Andreas -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26287344.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis 1.x to Axis2 - intercepting all messages?
Amila, Thanks very much for the article it is a great help. I see you are the author of the article and I had a question/comment about it. It says: Axis engine invokes in flow handlers for the given message, and at the end, it invokes the message receiver. Here, it should be noted that it is up to the message receiver XML info set is represented as an axiom object model and data binding (i.e converting xml info set to java objects and converting java objects to xml info set) is taken place at the message receiver. Finally, message receiver invokes service methods with Java objects. Then the article a little later says: As explained earlier axis2 data binding happens after message receiver and before the client api. Those two seem a little contradictory (at after) and I was a little concerned about that because our current Axis 1.4 implementation that extends RPCProvider doesn't handle the SOAP message and just calls the underlying service. So, I turned on Axis2 debug trace and added some additional trace calls to better understand the flow and it looks, at least in this case (below), that the order is: data binding (,837), MessageReceiver (,852), service method (,915), and then the umarshalling on the out flow (,930). Does that seem right to you, or am I misunderstanding terminology, etc.? This is the trace output, which I've edited to make it more succinct: ... ,649 axiom.soap.impl.builder.StAXSOAPModelBuilder - Starting to process SOAP 1.2 message ,649 axiom.soap.impl.builder.StAXSOAPModelBuilder - Build the OMElement Envelope by the StaxSOAPModelBuilder ,665 axiom.soap.impl.builder.StAXSOAPModelBuilder - Build the OMElement Body by the StaxSOAPModelBuilder ,665 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking pre-condition for Phase Transport ,665 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking phase Transport ,665 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking Handler 'RequestURIBasedDispatcher' in Phase 'Transport' ,665 axis2.dispatchers.RequestURIBasedServiceDispatcher - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking for Service using target endpoint address : http://localhost:8080/axis2/services/SampleService ... ,680 axis2.engine.AbstractDispatcher - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Found AxisService : SampleService ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking Handler 'SOAPActionBasedDispatcher' in Phase 'Transport' ,680 axis2.dispatchers.ActionBasedOperationDispatcher - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking for Operation using Action : urn:multipleParameters ,680 axis2.description.AxisService - getOperationBySOAPAction: Operation (org.apache.axis2.description.inoutaxisoperat...@13785d3,multipleParameters) for soapAction: urn:multipleParameters found in action map. ... ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking post-conditions for phase Transport ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking pre-condition for Phase Addressing ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking phase Addressing ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking Handler 'AddressingInHandler' in Phase 'Addressing' ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking Handler 'AddressingBasedDispatcher' in Phase 'Addressing' ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking post-conditions for phase Addressing ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking pre-condition for Phase Security ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking phase Security ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking post-conditions for phase Security ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking pre-condition for Phase PreDispatch ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking phase PreDispatch ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking post-conditions for phase PreDispatch ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Checking pre-condition for Phase Dispatch ,680 axis2.engine.Phase - [MessageContext: logID=urn:uuid:23202C4F3879831BA71257461489695] Invoking phase Dispatch ,680 axis2.engine.Phase -
Re: Generated WSDL HTTPS Port not 8443
On Tue, Nov 10, 2009 at 18:31, v2cg4ss ssel...@datamentors.com wrote: I just tried the nightly build of 10-Nov-2009 14:33 and the endpoints look good: wsdl:service name=MyWS - wsdl:port name=MyWSHttpsSoap11Endpoint binding=ns:MyWSSoap11Binding soap:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.NetEffectWS_1HttpsSoap11Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpSoap11Endpoint binding=ns:MyWSSoap11Binding soap:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap11Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpSoap12Endpoint binding=ns:MyWSSoap12Binding soap12:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap12Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpsSoap12Endpoint binding=ns:MyWSSoap12Binding soap12:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsSoap12Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpsEndpoint binding=ns:MyWSHttpBinding http:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsEndpoint/; / /wsdl:port - wsdl:port name=MyWSHttpEndpoint binding=ns:MyWSHttpBinding http:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpEndpoint/; / /wsdl:port /wsdl:service So this is good, I also found that axis2 1.3 works as well. The problem I have now is a .NET client that is afraid to move forward with us using 1.5.1 knowing that someone on their end could refresh the endpoints via Visual Studio and blow up production. Yes, I agree that they should have test procedures in place...But I don't understand how this worked in axis2 1.3 and has been broken since 1.4.1, 1.5, and 1.5.1. I cannot download 1.4 to see if it is broken in that version but this is a major miss but someone. So I would like to vote for this issue to be resolved quickly and a 1.5.2 release be made. This is very unlikely. It would mean to merge the changes from the trunk to the 1.5 branch. Technically this is not a big problem, but the code that is modified is very badly designed and there are external projects that are tightly coupled to that piece of code. I already burned my fingers with this when fixing the issue in the trunk [1] and I'm not going through this again. The fix will go into 1.6 unless somebody else volunteers to merge this into the 1.5 branch. [1] http://markmail.org/message/3gy3gnzkbh5kxt4c SanjayGupta wrote: Hi, I have the same issue and very interested in finding a solution. Sanjay -Original Message- From: v2cg4ss [mailto:ssel...@datamentors.com] Sent: Monday, November 09, 2009 1:40 PM To: axis-user@ws.apache.org Subject: Re: Generated WSDL HTTPS Port not 8443 Is this in a nightly build that I can test? Will this be axis2 1.5.2? Andreas Veithen-2 wrote: On Thu, Nov 5, 2009 at 20:49, v2cg4ss ssel...@datamentors.com wrote: Thank you for the reply, is this being resolved soon. It is implemented, but the issue is not closed yet because the documentation is not up to date with the changes. I have a client using .NET and they are generating their client code from the WSDL. The programmer claims that they cannot change the endpoint in the .NET code like I can with java. MyWSStub stub = new MyWSStub(ctx, https://localhost:8443/axis2/services/MyWS;); Scott Andreas Veithen-2 wrote: Generating the correct endpoint URIs for https is something that doesn't work properly in the available Axis2 releases. See AXIS2-4465 and related issues. Andreas -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26287344.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Axis2/Java 1.5.1 and Rampart
Hi;
Following will be helpful.
Load the policy :
StAXOMBuilder builder = new StAXOMBuilder(policy.xml);
Policy policy = PolicyEngine.getPolicy(builder.getDocumentElement());
Get the Options from the Stub :
ServiceClient client = stub._getServiceClient();
Options option = client.getOptions();
Set the policy :
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, policy);
Thanks regards.
-Prabath
stefangee...@hotmail.com wrote:
Hi,
thanks for the reply.
I'll create a JIRA on this.
Question: How can I attach the policy file to the client ? Any documentation/examples
Regards,
S.
Prabath Siriwardena-2 wrote:
Please create a JIRA on the issue.
Alternatively you can attach the policy file to the client to get the
expected results.
Thanks regards.
-Prabath
SGE0 wrote:
Hi,
we have following services.xml file (part):
service name=Upload scope=application
...
module ref=rampart /
wsp:Policy wsu:Id=UsernameToken xmlns:wsu=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy;
wsp:ExactlyOne
wsp:All
sp:SupportingTokens
xmlns:sp=http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702;
wsp:Policy
sp:UsernameToken sp:IncludeToken=
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient;
wsp:Policy
sp:HashPassword/
/wsp:Policy
/sp:UsernameToken
/wsp:Policy
/sp:SupportingTokens
ramp:RampartConfig
xmlns:ramp=http://ws.apache.org/rampart/policy;
ramp:passwordCallbackClass...security.PWCBHandler/ramp:passwordCallbackClass
/ramp:RampartConfig
/wsp:All
/wsp:ExactlyOne
/wsp:Policy
/service
When we generate the client stub with Java2WSDL we see that the
wsp:Policy
sp:HashPassword/
/wsp:Policy
is not correctly generated.
When we look at the populateAxisService method in the generated stub we
see:
private void populateAxisService() throws org.apache.axis2.AxisFault {
...
(__operation).getMessage(org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_OUT_VALUE).getPolicySubject().attachPolicy(getPolicy(wsp:Policy
xmlns:wsp=\http://schemas.xmlsoap.org/ws/2004/09/policy\;wsp:ExactlyOnewsp:Allsp:SupportingTokens
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;wsp:Policysp:UsernameToken
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;
sp:IncludeToken=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient\;
//wsp:Policy/sp:SupportingTokenssp:SupportingTokens
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;wsp:Policysp:UsernameToken
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;
sp:IncludeToken=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient\;
//wsp:Policy/sp:SupportingTokens/wsp:All/wsp:ExactlyOne/wsp:Policy));
...
}
The result is that we can send over a plain text userid/pwd but not a
hashed
password.
Anyone experiencing the same problem ?
S.
Quoted from:
http://old.nabble.com/Axis2-Java-1.5.1-and-Rampart-tp26269867p26283140.html
Remove
Remove
-Original Message-
From: Prabath Siriwardena [mailto:prab...@wso2.com]
Sent: Tuesday, November 10, 2009 10:10 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2/Java 1.5.1 and Rampart
Hi;
Following will be helpful.
Load the policy :
StAXOMBuilder builder = new StAXOMBuilder(policy.xml);
Policy policy = PolicyEngine.getPolicy(builder.getDocumentElement());
Get the Options from the Stub :
ServiceClient client = stub._getServiceClient();
Options option = client.getOptions();
Set the policy :
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, policy);
Thanks regards.
-Prabath
stefangee...@hotmail.com wrote:
Hi,
thanks for the reply.
I'll create a JIRA on this.
Question: How can I attach the policy file to the client ? Any
documentation/examples
Regards,
S.
Prabath Siriwardena-2 wrote:
Please create a JIRA on the issue.
Alternatively you can attach the policy file to the client to get the
expected results.
Thanks regards.
-Prabath
SGE0 wrote:
Hi,
we have following services.xml file (part):
service name=Upload scope=application
...
module ref=rampart /
wsp:Policy wsu:Id=UsernameToken xmlns:wsu=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
1.0.xsd
xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy;
wsp:ExactlyOne
wsp:All
sp:SupportingTokens
xmlns:sp=http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702;
wsp:Policy
sp:UsernameToken sp:IncludeToken=
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Alwa
ysToRecipient
wsp:Policy
sp:HashPassword/
/wsp:Policy
/sp:UsernameToken
/wsp:Policy
/sp:SupportingTokens
ramp:RampartConfig
xmlns:ramp=http://ws.apache.org/rampart/policy;
ramp:passwordCallbackClass...security.PWCBHandler/ramp:passwordCallbackCl
ass
/ramp:RampartConfig
/wsp:All
/wsp:ExactlyOne
/wsp:Policy
/service
When we generate the client stub with Java2WSDL we see that the
wsp:Policy
sp:HashPassword/
/wsp:Policy
is not correctly generated.
When we look at the populateAxisService method in the generated stub we
see:
private void populateAxisService() throws org.apache.axis2.AxisFault {
...
(__operation).getMessage(org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_O
UT_VALUE).getPolicySubject().attachPolicy(getPolicy(wsp:Policy
xmlns:wsp=\http://schemas.xmlsoap.org/ws/2004/09/policy\;wsp:ExactlyOne
wsp:Allsp:SupportingTokens
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;wsp:
Policysp:UsernameToken
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;
sp:IncludeToken=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/
IncludeToken/AlwaysToRecipient\
//wsp:Policy/sp:SupportingTokenssp:SupportingTokens
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;wsp:
Policysp:UsernameToken
xmlns:sp=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\;
sp:IncludeToken=\http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/
IncludeToken/AlwaysToRecipient\
//wsp:Policy/sp:SupportingTokens/wsp:All/wsp:ExactlyOne/wsp:Policy
));
...
}
The result is that we can send over a plain text userid/pwd but not a
hashed
password.
Anyone experiencing the same problem ?
S.
Quoted from:
http://old.nabble.com/Axis2-Java-1.5.1-and-Rampart-tp26269867p26283140.html
unsubscribe
unsubscribe
Re: [Axis2] Reg. parsing of MULTIREF and including MULTIREF in server responses
Hi Deepal, Thanks for the link. Unfortunately I was not able to get it working.. :( I just found some Axis2 api's such inside axis2.apache.databinding.utils - Multirefhelper and was able to get the href,attribute values from the incoming requests . Now I want to send the response processing the above values and it looks like the following ?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:Headersoapenv:Bodyns4:Response soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns4=Myservice:ResponseresponseServer href=#id0//ns4:ResponsemultiRef id=id0 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns5:Profile xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns5=http://Myservice.services.myservice.com;serviceNumbers soapenc:arrayType=ns5:ServiceNumber[2] xsi:type=soapenc:ArrayserviceNumbers href=#id1/serviceNumbers href=#id2//serviceNumbersuser href=#id3//multiRefmultiRef id=id3 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns6:User xmlns:ns6=http://dto.domain.raa.services.myservice.com; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;userSegment xsi:type=ns7:UserSegmentEnum xsi:nil=true xmlns:ns7=http://Myservice.services.myservice.com/username xsi:type=xsd:stringrag...@test.com/username/multiRefmultiRef id=id1 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns8:ServiceNumber xmlns:ns8=http://Myservice.services.myservice.com; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;serviceLinkStatus href=#id4/serviceNumber xsi:type=xsd:string00/serviceNumberserviceNumberStatus href=#id5/serviceType href=#id6//multiRefmultiRef id=id2 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns9:ServiceNumber xmlns:ns9=http://Myservice.services.myservice.com; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;serviceLinkStatus href=#id7/serviceNumber xsi:type=xsd:string01/serviceNumberserviceNumberStatus href=#id5/serviceType href=#id6//multiRefmultiRef id=id5 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns10:ServiceNumberStatusEnum xmlns:ns10=http://Myservice.services.myservice.com; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;TEST_ACTIVE/multiRefmultiRef id=id4 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns11:ServiceLinkStatusEnum xmlns:ns11=http://Myservice.services.myservice.com; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;TEST_LINKED/multiRefmultiRef id=id7 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns12:ServiceLinkStatusEnum xmlns:ns12=http://Myservice.services.myservice.com; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;TEST_INITIAL/multiRefmultiRef id=id6 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns13:ServiceTypeEnum xmlns:ns13=http://Myservice.services.myservice.com; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;TEST_MSISDN/multiRef/soapenv:Body/soapenv:Envelope I just wanted to know whether are there any APIs(such as addChild) to make it easier to add multirefs to the responses. Pl. share your thoughts on getting the above response..I am using a simple inout message receiver. Thanks for looking into it. Thanks,Raghav. --- On Mon, 11/9/09, Deepal jayasinghe deep...@gmail.com wrote: From: Deepal jayasinghe deep...@gmail.com Subject: Re: [Axis2] Reg. parsing of MULTIREF and including MULTIREF in server responses To: axis-user@ws.apache.org Date: Monday, November 9, 2009, 9:16 AM Try this, https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/rpc/RPCCallTest.java Hi Deepal, Thanks for the reply. I just had a look on the API's reg. MultiRefHelper. I have a InOutMessageReceiver already for my service.It would be great if you can share the examples(below) for starters like us to explore more.. 1. Extract Multiref values in server from incoming requests 2. Create Multiref values from server as response. Thanks, Raghav. --- On *Mon, 11/9/09, Deepal Jayasinghe /dee...@opensource.lk/* wrote: From: Deepal Jayasinghe dee...@opensource.lk Subject: Re: [Axis2] Reg. parsing of MULTIREF and including MULTIREF in server responses To: axis-user@ws.apache.org Date: Monday, November 9, 2009, 6:07 AM It is yes and no answer. In the server side when we use RPCMessageReceiver, it supports multiref. But in the client side I am not sure whether we handle it correctly, if you can try with RPCServiceClient and see whether it works. (I guess it
WSDL and XSD Design | Which design is perfect
Hi, I have a WSDL defining fault as given below 1. wsdl:message name=InvalidPINInfo wsdl:part name=parameter element=error:errorFault/ /wsdl:message . wsdl:portType name=TravelAccount wsdl:operation name=RegisterUser wsdl:input message=tns:RegisterUserRequest/ wsdl:output message=tns:RegisterUserResponse/ wsdl:fault name=InvalidPINInfo message=tns:InvalidPINInfo/ /wsdl:operation 2. I got suggestion from one of the forums to change InvalidPINInfo as follows to minimize changes in WSDL in future if fault definition needs to changed wsdl:message name=InvalidPINInfo wsdl:part name=parameter element=account:InvalidPINInfo/ /wsdl:message and then define in one of the XSDs as follows(Indirect mapping), so future change only needs XSD changes xs:element name=InvalidPINInfo type=error:errorFault/ Questions: 1. So always WSDL design needs to be taken care that it should not change often? 2. Even if it is XSD change it is a Service contract change.Not only WSDL. Is it right? Thanks, Appasamy
