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

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

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

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:

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

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

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 /

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

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,

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

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

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.

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

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

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

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

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!

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/; /

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

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

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();

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

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

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