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.
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: 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: 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.
Re: Generated WSDL HTTPS Port not 8443
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.
Re: Generated WSDL HTTPS Port not 8443
Thank you for the reply, is this being resolved soon. 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.
RE: Generated WSDL HTTPS Port not 8443
There should be a setEndpoint method generated in the .NET code. That will allow them to programmatically set the endpoint. -Original Message- From: v2cg4ss [mailto:ssel...@datamentors.com] Sent: Thursday, November 05, 2009 2:49 PM To: axis-user@ws.apache.org Subject: Re: Generated WSDL HTTPS Port not 8443 Thank you for the reply, is this being resolved soon. 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-tp26208367p2621 9924.html Sent from the Axis - User mailing list archive at Nabble.com.
