You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by v2cg4ss <ss...@datamentors.com> on 2009/11/05 04:35:14 UTC
Generated WSDL HTTPS Port not 8443
I have looked at other posts and nothing seems to be working, I am running
Axis2 1.5.1 with Rampart 1.5 in Tomcat 6.0.20. When the WSDL is generated
by Axis2 from the services.xml I am getting the following:
<wsdl:service name="MyWS">
- <wsdl:port name="MyWSHttpSoap11Endpoint" binding="ns:MyWSSoap11Binding">
<soap:address
location="http://localhost:8080/axis2/services/MyWS.MyWSHttpSoap11Endpoint/"
/>
</wsdl:port>
- <wsdl:port name="MyWSHttpSoap12Endpoint" binding="ns:MyWSSoap12Binding">
<soap12:address
location="http://localhost:8080/axis2/services/MyWS.MyWSHttpSoap12Endpoint/"
/>
</wsdl:port>
- <wsdl:port name="MyWSHttpEndpoint" binding="ns:MyWSHttpBinding">
<http:address
location="http://localhost:8080/axis2/services/MyWS.MyWSHttpEndpoint/" />
</wsdl:port>
</wsdl:service>
In the tomcat server.xml I access the WS via HTTPS and I have had the 8080
config parameters commented out and not commented out. I have used
<parameter locked="false" name="modifyUserWSDLPortAddress">true</parameter>
and it still generates the WSDL with port 8080.
Is there a solution other than forcing the use of a WSDL file?
--
View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26208367.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: Generated WSDL HTTPS Port not 8443
Posted by Andreas Veithen <an...@gmail.com>.
On Tue, Nov 10, 2009 at 18:31, v2cg4ss <ss...@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:sselvia@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 <ss...@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
Posted by v2cg4ss <ss...@datamentors.com>.
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:sselvia@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 <ss...@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
Posted by Sanjay Gupta <Sa...@billwiseinc.com>.
Hi,
I have the same issue and very interested in finding a solution.
Sanjay
-----Original Message-----
From: v2cg4ss [mailto:sselvia@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 <ss...@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
Posted by v2cg4ss <ss...@datamentors.com>.
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 <ss...@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
Posted by Andreas Veithen <an...@gmail.com>.
On Thu, Nov 5, 2009 at 20:49, v2cg4ss <ss...@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
Posted by "Betts, Hendry" <He...@viasat.com>.
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:sselvia@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.
Re: Generated WSDL HTTPS Port not 8443
Posted by v2cg4ss <ss...@datamentors.com>.
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
Posted by Andreas Veithen <an...@gmail.com>.
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
Re: Generated WSDL HTTPS Port not 8443
Posted by v2cg4ss <ss...@datamentors.com>.
I added the <transports>... to the services.xml and I now get the following
when I start tomcat and axis2 deploys the my web service:
org.apache.axis2.deployment.DeploymentException: Service [ MyWS] is trying
to expose in a transport : <transports>
<transport>https</transport>
</transports> and which is not available in Axis2
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:150)
at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:81)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:659)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:337)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:241)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:131)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:284)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4149)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4458)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:850)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:724)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:493)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
So I added this to the axis2.xml:
<transportReceiver name="https"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8443</parameter>
</transportReceiver>
And now I get:
[WARN] Attempt number 1 of 10 to reestalish connection listener
org.apache.axis2.transport.http.server.DefaultConnectionListener@dfcb47 due
to failure
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:97)
at
org.apache.axis2.transport.http.server.DefaultConnectionListener.run(DefaultConnectionListener.java:75)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
repeated 10 times and then finally it displays:
[INFO] Listening on port 8443
[ERROR] Terminating connection listener
org.apache.axis2.transport.http.server.DefaultConnectionListener@dfcb47
after 10retries in 0 seconds.
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:97)
at
org.apache.axis2.transport.http.server.DefaultConnectionListener.run(DefaultConnectionListener.java:75)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
However, when I view the WSDL generated I do get the endpoint ports correct
but it still uses http and not https:
<wsdl:service name="MyWS">
- <wsdl:port name="MyWSHttpsSoap11Endpoint" binding="ns:MyWSSoap11Binding">
<soap:address
location="http://localhost:8443/axis2/services/MyWS.MyWSHttpsSoap11Endpoint/"
/>
</wsdl:port>
- <wsdl:port name="MyWSHttpsSoap12Endpoint" binding="ns:MyWSSoap12Binding">
<soap12:address
location="http://localhost:8443/axis2/services/MyWS.MyWSHttpsSoap12Endpoint/"
/>
</wsdl:port>
- <wsdl:port name="MyWSHttpsEndpoint" binding="ns:MyWSHttpBinding">
<http:address
location="http://localhost:8443/axis2/services/MyWS.MyWSHttpsEndpoint/" />
</wsdl:port>
</wsdl:service>
So again how can I get Axis2 to generate the correct web service endpoints?
Sagara wrote:
>
> Make sure you have only HTTPS transport define in the service.xml file.
>
> <transports>
> <transport>https</transport>
> </transports>
>
> Thanks,
>
> On Thu, Nov 5, 2009 at 9:05 AM, v2cg4ss <ss...@datamentors.com> wrote:
>>
>> I have looked at other posts and nothing seems to be working, I am
>> running
>> Axis2 1.5.1 with Rampart 1.5 in Tomcat 6.0.20. When the WSDL is
>> generated
>> by Axis2 from the services.xml I am getting the following:
>>
>> <wsdl:service name="MyWS">
>> - <wsdl:port name="MyWSHttpSoap11Endpoint"
>> binding="ns:MyWSSoap11Binding">
>> <soap:address
>> location="http://localhost:8080/axis2/services/MyWS.MyWSHttpSoap11Endpoint/"
>> />
>> </wsdl:port>
>> - <wsdl:port name="MyWSHttpSoap12Endpoint"
>> binding="ns:MyWSSoap12Binding">
>> <soap12:address
>> location="http://localhost:8080/axis2/services/MyWS.MyWSHttpSoap12Endpoint/"
>> />
>> </wsdl:port>
>> - <wsdl:port name="MyWSHttpEndpoint" binding="ns:MyWSHttpBinding">
>> <http:address
>> location="http://localhost:8080/axis2/services/MyWS.MyWSHttpEndpoint/" />
>> </wsdl:port>
>> </wsdl:service>
>>
>> In the tomcat server.xml I access the WS via HTTPS and I have had the
>> 8080
>> config parameters commented out and not commented out. I have used
>> <parameter locked="false"
>> name="modifyUserWSDLPortAddress">true</parameter>
>> and it still generates the WSDL with port 8080.
>>
>> Is there a solution other than forcing the use of a WSDL file?
>> --
>> View this message in context:
>> http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26208367.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
>
>
> -----
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://sagaras.awardspace.com/
>
--
View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26215724.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: Generated WSDL HTTPS Port not 8443
Posted by Sagara Gunathunga <sa...@gmail.com>.
Make sure you have only HTTPS transport define in the service.xml file.
<transports>
<transport>https</transport>
</transports>
Thanks,
On Thu, Nov 5, 2009 at 9:05 AM, v2cg4ss <ss...@datamentors.com> wrote:
>
> I have looked at other posts and nothing seems to be working, I am running
> Axis2 1.5.1 with Rampart 1.5 in Tomcat 6.0.20. When the WSDL is generated
> by Axis2 from the services.xml I am getting the following:
>
> <wsdl:service name="MyWS">
> - <wsdl:port name="MyWSHttpSoap11Endpoint" binding="ns:MyWSSoap11Binding">
> <soap:address
> location="http://localhost:8080/axis2/services/MyWS.MyWSHttpSoap11Endpoint/"
> />
> </wsdl:port>
> - <wsdl:port name="MyWSHttpSoap12Endpoint" binding="ns:MyWSSoap12Binding">
> <soap12:address
> location="http://localhost:8080/axis2/services/MyWS.MyWSHttpSoap12Endpoint/"
> />
> </wsdl:port>
> - <wsdl:port name="MyWSHttpEndpoint" binding="ns:MyWSHttpBinding">
> <http:address
> location="http://localhost:8080/axis2/services/MyWS.MyWSHttpEndpoint/" />
> </wsdl:port>
> </wsdl:service>
>
> In the tomcat server.xml I access the WS via HTTPS and I have had the 8080
> config parameters commented out and not commented out. I have used
> <parameter locked="false" name="modifyUserWSDLPortAddress">true</parameter>
> and it still generates the WSDL with port 8080.
>
> Is there a solution other than forcing the use of a WSDL file?
> --
> View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26208367.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/