Bug 779648 (SOA-2017) - WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
Summary: WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2017
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.0.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0.2
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-29 00:18 UTC by Len DiMaggio
Modified: 2010-06-08 03:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-28 12:36:38 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2017 0 None None None Never

Description Len DiMaggio 2010-03-29 00:18:38 UTC 
Date of First Response: 2010-04-06 03:45:45
project_key: SOA

Platform JIRA for JBoss ESB project JIRA:  https://jira.jboss.org/jira/browse/JBESB-3255
Comment 1 Len DiMaggio 2010-03-29 00:19:27 UTC 
Link: Added: This issue depends JBESB-3255
Comment 2 David Ward 2010-04-06 07:45:45 UTC 
JBESB-3255 has been closed.
Comment 3 Kevin Conner 2010-04-06 09:48:11 UTC 
Link: Removed: This issue depends JBESB-3255
Comment 4 Kevin Conner 2010-04-06 09:48:47 UTC 
Link: Added: This issue depends JBESB-3257
Comment 5 Kevin Conner 2010-04-06 09:49:15 UTC 
JBESB-3257 is the platform related issue.
Comment 6 David Ward 2010-04-16 16:32:06 UTC 
JBESB-3257 has been closed.
Comment 7 Kevin Conner 2010-04-26 09:04:44 UTC 
Updated in ESB, will be in next merge.
Comment 8 Jiri Pechanec 2010-05-28 12:36:38 UTC 
Verified in CR1
Comment 9 Dana Mison 2010-06-08 03:35:10 UTC 
Added to the 5.0.2 release notes as resolved:

JBESB-3257
The Contract JSP application was not showing the WSDL for ESB archives that were deployed when the server launched.
This was because the collection of the service contracts at launch time occurred too early.  This has been resolved 
and the collection now occurs at the correct time.
Note You need to log in before you can comment on or make changes to this bug.