Bug 779385 (SOA-1775) - juddiv3.war doesn't get deployed
Summary: juddiv3.war doesn't get deployed
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1775
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.0.0 ER6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.0.0 GA,5.0.0 ER7
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-06 15:42 UTC by Jiri Locker
Modified: 2010-01-28 10:24 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-28 10:24:34 UTC
Type: Bug


Attachments (Terms of Use)
server.log (90.88 KB, text/plain)
2010-01-06 16:43 UTC, Jiri Locker
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779239 0 high CLOSED 5.0 ER4 build - default server config profile does not include juddi.war 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1775 0 None None None Never

Internal Links: 779239

Description Jiri Locker 2010-01-06 15:42:33 UTC
Date of First Response: 2010-01-06 18:08:45
project_key: SOA

juddiv3.war inside jbossesb-registry.sar doesn't get deployed.

Comment 1 Jiri Locker 2010-01-06 15:55:58 UTC
Link: Added: This issue is related to JBESB-2983


Comment 2 Jiri Locker 2010-01-06 15:55:58 UTC
Link: Added: This issue is related to SOA-1625


Comment 3 Jiri Locker 2010-01-06 15:55:58 UTC
Link: Added: This issue is related to SOA-1632


Comment 4 Jiri Locker 2010-01-06 15:55:58 UTC
Link: Added: This issue is related to JBPAPP-3291


Comment 5 Jiri Locker 2010-01-06 16:43:53 UTC
Attachment: Added: server.log


Comment 6 Kevin Conner 2010-01-06 17:06:51 UTC
Link: Removed: This issue is related to SOA-1632 


Comment 7 Kevin Conner 2010-01-06 17:06:59 UTC
Link: Removed: This issue is related to JBESB-2983 


Comment 8 Kevin Conner 2010-01-06 17:07:05 UTC
Link: Removed: This issue is related to JBPAPP-3291 


Comment 9 Kevin Conner 2010-01-06 23:08:45 UTC
There are two issues that need fixing in the integration

- deployment of the war file
- correction of the jbossws-entities file

For the first, change the war jboss-web.xml to the following and then place it in the deploy directory (no longer in the jbossesb-registry.sar directory)

<jboss-web>
    <class-loading>
        <loader-repository>jboss.esb:loader=jbossesb-registry.sar</loader-repository>
    </class-loading>
    <context-root>/juddiv3</context-root>
    <depends>jboss.esb:service=JuddiRMI</depends>
</jboss-web>

For the second, edit the jbossws-entities.properties file and remove the trailing space from the xmldsig entry.

With both of these done, the services are once again deployed and can be seen through the http://localhost:8080/jbossws/services console.

This should have been picked up as part of the evaluation of SOA-1625 but was missed.

Comment 10 Kevin Conner 2010-01-07 07:56:29 UTC
Link: Added: This issue depends JBESB-3101


Comment 11 Kevin Conner 2010-01-07 07:59:00 UTC
Trev, assigning to you as there are a couple of integration tasks

- war should now be placed in deploy directory (explicit scoping information is now included in the war)
- need to remove the space from the property file.

Kev

Comment 12 Kevin Conner 2010-01-07 08:53:07 UTC
Sorry, correct issue should have been SOA-1632 and not SOA-1625.

Comment 13 Kevin Conner 2010-01-07 08:53:20 UTC
Link: Removed: This issue is related to SOA-1625 


Comment 14 Kevin Conner 2010-01-07 08:53:41 UTC
Link: Added: This issue is related to SOA-1632


Comment 15 trev 2010-01-07 15:21:07 UTC
build fixes checked in r4685
esb war fix will be in next merge, leaving open until merge happens

Comment 17 Martin Vecera 2010-01-28 10:24:34 UTC
Verified in ER7.


Note You need to log in before you can comment on or make changes to this bug.