[jbossws-issues] [JBoss JIRA] Commented: (JBWS-3233) jbossws/services web view shows wrong port

[Darran Lofthouse (JIRA)]

    [ https://issues.jboss.org/browse/JBWS-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628791#comment-12628791 ] 

Darran Lofthouse commented on JBWS-3233:
----------------------------------------

"it seems wrong"

For something that seems wrong I would suggest opening a support case through the customer portal to discuss with a support engineer.

However reading the description it does seem that the web service may be missing a transport guarantee setting of CONFIDENTIAL as that is the trigger to switch to using the 8443 address.  

> jbossws/services web view shows wrong port
> ------------------------------------------
>
>                 Key: JBWS-3233
>                 URL: https://issues.jboss.org/browse/JBWS-3233
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: productivity
>         Environment: JBoss 4.3.0 CP08 running on RHEL 5 (5.6) - kernel version 2.6.18-238.1.1.el5
>            Reporter: Steve Cassidy
>            Priority: Minor
>
> We have a JBoss installation where we have disabled port 8080 for security reasons (in jboss-web.deployer/server.xml). We listen on port 8443 on SSL and 8009 for AJP.
> However if I look at the web view of Web services (jbossws/services context path in a web browser) this shows the WSDLs of the services but the links are still showing ":8080" as the listening port (even though JBoss is not listening on port 8080).
> I undersdtand that it is possible to have JBoss listeing on multiple ports so hence it would not be clear what would be put here instead but for a simple example where Jboss is listening on port 8443 and not 8080 it seems wrong that 8080 is shown and not 8443.
> I understand that this is not the highetst priority issue ever but to make the product consistent could you please look at this.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira