Bug 779154 (SOA-1549)

Summary:	Backwards incompatibility in deployment
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Lukáš Petrovický <lpetrovi>
Component:	JBossAS, Compatibility	Assignee:	trev <tkirby>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0.0 ER1	CC:	dlesage
Target Milestone:	---
Target Release:	5.0.2
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1549
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-05-31 13:29:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Lukáš Petrovický 2009-10-26 07:28:47 UTC

Affects: Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes
Date of First Response: 2010-02-08 14:50:20
project_key: SOA

See JBPAPP-3002.

Comment 1 Lukáš Petrovický 2009-10-26 07:29:40 UTC

Link: Added: This issue depends JBESB-2910

Comment 2 Lukáš Petrovický 2009-10-26 11:24:11 UTC

Link: Removed: This issue depends JBAS-7403

Comment 3 Lukáš Petrovický 2009-10-26 11:25:48 UTC

Link: Added: This issue depends JBPAPP-3002

Comment 4 Len DiMaggio 2010-02-08 19:50:20 UTC

This fix will not be in 5.0 at GA.

Comment 5 Len DiMaggio 2010-02-08 19:51:06 UTC

Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes]

Comment 6 trev 2010-05-19 14:18:50 UTC

fixed in EAP 5.0.1 which is included in this release

Comment 7 Pavel Macik 2010-05-31 13:29:25 UTC

Verified in 5.0.2.CR1 - wsdl's URL from http://localhost:8080/jbossws/services is accessable.

Comment 8 David Le Sage 2010-06-16 05:19:14 UTC

Draft text for Release Notes states:


https://jira.jboss.org/jira/browse/SOA-1549

    An Invalid End-Point Address error would occur if the user tried to access http://
    localhost:8080/jbossws/services whilst a WAR file was embedded in a JAR archive. This occurred
    because the web service inside the ESB archive was deployed in such a way that the WAR did
    not contain the WEB-INF/jboss-web.xml file, meaning that the web service's WSDL would be
    inaccessible.


    This was a backwards-compatibility issue. It has been fixed by adding jboss-web.xml and
     specifying a context root. As a result, the error no longer occurs.