| Summary: | jUDDI tables are dropped at ESB shutdown | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Martin Vecera <mvecera> |
| Component: | JBossESB | Assignee: | trev <tkirby> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 IR5 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.2 CR3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-129 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
soa-standalone
|
|
| Last Closed: | 2008-02-11 14:57:18 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
Martin Vecera
2007-11-12 10:01:33 UTC
Link: Added: This issue is duplicated by JBESB-1323 Link: Added: This issue depends JBESB-1323 Link: Removed: This issue is duplicated by JBESB-1323 I'm now deploying the juddi.was by default to the jbossesb.sar (see changes for JBESB-1323) So in the SOA-P where I guess you are using the 'all' profile you should now try to simply remove the juddi.sar that ships with jbossas. (try == make sure that it does not break jbossas, which it shouldn't). See also http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4104506#4104506 This is a SOA-P issue. Please track at SOA-129 JBoss Forum Reference: Added: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4104506#4104506 Trevor asked me to try SOA-P IR8 without juddi-service.sar. It seems like the server is able to start and shutdown cleanly. It is also possible to deploy and undeploy simple hello world quickstart example. We definitely have to run whole AS's test suite before saying "it works". But I prefer fixing it as Thomas suggests in the linked forum because deleting juddi-service.sar makes applying EAP & SOA patches very complicated later... Both versions of the juddi.war still exist but the version in EAP no longer drops the tables It's not clear whether your suggestion was implemented, can you confirm that it is it safe to delete the juddi.war from the esb variant? It is not save to simply delete the juddi.war. What we need is an update of the jboss jaxr project as described in the forum thread. I'm happy for you to update the JAXR project Thomas, but it will require an EAP update. So it needs to be done now because EAP 4.3 is going GA very soon. Link: Added: This issue depends JBWS-1942 Link: Added: This issue depends JBPAPP-507 See Marks comment I believe Kurt should own that project since he already owns the juddi code base. Link: Added: This issue related JBQA-1268 Link: Added: This issue related JBQA-1267 Kurt is busy at the moment Thomas. So I'd appreciate it if you could get this done for now and then we can figure out later where it should be done. Kurt, could you please update https://svn.jboss.org/repos/jbossas/projects/jaxr/trunk/pom.xml with the versions that you need. I can then run the install target for you and do the release. Thomas, please use anonsvn http://anonsvn.labs.jboss.com/labs/jbossesb/branches/JBESB_4_2_1_GA_CP/product/lib/ext/ to get the jars you need. Kurt is fully committed to other things at the moment and we need help from your team. http://repository.jboss.org/jboss/jboss-juddi/2.0.0.RC5/ This is installed in jbossas/trunk and jbossas/branches/Branch_4_2 Will need to get this into the platform release after Beta1. Link: Added: This issue is related to JBAS-5094 This will not be in the EAP 4.3 release, so we will patch EAP as we've been doing when you install into it for this release. This is fixed in CR3, Trevor you can close this issue I think... |