| Summary: | juddi service deployed in two locations | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Rajesh Rajasekaran <rajesh.rajasekaran> |
| Component: | Configuration | Assignee: | trev <tkirby> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 Beta 1 | CC: | andres.pereiro, asoldano, mageshbk, mrostan |
| Target Milestone: | --- | ||
| Target Release: | 4.3 CP02 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-353 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-09-15 18:46:55 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: | |
| Bug Depends On: | 777827 | ||
| Bug Blocks: | 778631 | ||
|
Description
Rajesh Rajasekaran
2008-01-22 23:22:03 UTC
removed deploy/juddi-service.sar and eap still works Link: Added: This issue is a dependency of JBESB-1599 In the GA build, the file is here: [ldimaggi@ldimaggi GA]$ find . -name juddi-service.sar -print./jboss-soa-p.4.2.0/jboss-as/server/production/deploy/juddi-service.sar ./jboss-soa-p.4.2.0/jboss-as/server/all/deploy/juddi-service.sar Link: Removed: This issue is a dependency of JBESB-1599 ESB is laying down these jars : ./jboss-as/server/production/deploy/jbossesb.sar/lib/juddi-2.0rc5.jar ./jboss-as/server/production/deploy/jbossesb.sar/lib/juddi-client-2.0rc5.jar ./jboss-as/server/all/deploy/jbossesb.sar/lib/juddi-2.0rc5.jar ./jboss-as/server/all/deploy/jbossesb.sar/lib/juddi-client-2.0rc5.jar ./jboss-as/server/production/deploy/jbossesb.sar/lib/scout-1.0rc1.jar ./jboss-as/server/all/deploy/jbossesb.sar/lib/scout-1.0rc1.jar I've asked Alessio and Kevin to comment, I'm dubious about the first comment Well, speaking of the first comment ("removed deploy/juddi-service.sar and eap still works" ), that depends on what is tested to prove that EAP works. i can say for sure removing juddi-service without doing anything else makes the registry related tests of the jbossws testsuite fail, as well as the jaxr module's tests of the TCK.
The scout library installed by jbossesb, instead, makes some TCK tests fail because of missing dependency on Apache's stuff (xmlbeans being the first thing).
Link: Added: This issue depends JBPAPP-937 Link: Added: This issue is duplicated by SOA-987 These two juddis do conflict. If you use uddibrowser in SOA-P (as described in the ESB Services Guide), it brings up juddi-service but there are errors. Remove juddi-service.sar and it will bring up ESB's juddi and you will be able to browse. I took a look at the MBean code for JUDDIService and ESB's JuddiRMIService - it looks like JUDDIService has one feature ( runScript(InputStream stream)) that JuddRMIService doesn't have. There's a few properties in jboss-service.xml as well. Is this related to the other duplicate jUDDI issues (currently assigned to Julian)? Yes, this is .If Julians fix works, then probably all scout juddi issues can be closed. Link: Added: This issue is a dependency of SOA-1107 In 4.3 CP02 CR3, juddi-service.sar is not present. Can this JIRA be closed? The file is not in 4.3 CP02: [ldimaggi@ldimaggi jboss-as]$ pwd /opt/local/43_CP02_CR3/jboss-soa-p.4.3.0/jboss-as [ldimaggi@ldimaggi jboss-as]$ find -name juddi-service.sar -print |