[GLASSFISH-6495] Web application web service deployed cluster instance returns invalid WSDl Created: 09/Oct/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: web_services
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: gmpatil Assignee: Bhakti Mehta
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: File ExtractEventService.war    
Issuezilla Id: 6,495

 Description   

Using Sun Java System Application Server 9.1_02 (build b04-fcs)

When Web application containing Web service is deployed to cluster instances,
below issues are encountered.
1) WSDL returned thru "?WSDL" on node instance http port is returned with
invalid port.
Ex:
http://host1.instance1:38080/ExtractEventService/ExtractEventService?wsdl
returns WSDL
which imports XSD's from DAS server and port 8080 where Web application is not
deployed. Even though packaged WSDL imports XSD's using relative path.
<xsd:import namespace="http://docs.oasis-open.org/wsn/b-2"
schemaLocation="http://GPATIL:8080/ExtractEventService/ExtractEventService/__container$publishing$subctx/WEB-INF/wsdl/ExtractEventService/b-2.xsd"/>

This causes Java EE Engine to fail while processing messages as it can not parse
the WSDL.

2) Not all the instances returns the WSDL using the
http://host1.instance1:38080/ExtractEventService/ExtractEventService?wsdl.



 Comments   
Comment by gmpatil [ 09/Oct/08 ]

Created an attachment (id=1946)
Web application. with WS URL /ExtractEventService/ExtractEventService

Comment by Bhakti Mehta [ 10/Oct/08 ]

Looking at this

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Fri May 29 03:43:04 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.