Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.) Date of First Response: 2009-03-16 06:36:58 project_key: SOA Document the outcome of SOA-1217
Link: Added: This issue is related to SOA-1217
Trevor wrote: We had a long discussion about this (and every other time that scout/jira has come up). Whatever we do to scout/juddi will break something, when this problem came up the first time it was ocumented that the TCK stuff would be affected and that the scout/juddi stuff should be used via esb. So customers shouldn't be relying on this. We think that we should bite the bullet and just document that the sar has gone, unless of course you find that it's absence breaks some SOA functionality. Yes it should really have been done at GA but at that point we thought we would get a fix from EAP in a reasonable time scale.
It looks like SOA-1217 has been pushed back to 4.3.CP02 I imagine we want this documented as a known issue. Could you supply some more concrete details please, I'm not familiar with jUDDI. Thanks.
hang on, is this just the removal of juddi-service.sar ?
I can't tell you how stupid I feel having just read my last comment. :-| If I read the title of the JIRA it must have gone right out of my head and I went straight to SOA-1217 to see what happened. Since SOA-1217 has been set to CP02 , I assume that juddi-service.sar will still be in the final CP01 ?
Release Note: Previous versions of JBoss Enterprise SOA Platform shipped with two different versions of the jUDDI and Scout jars. juddi-service.sar has been removed to avoid conflicts with the version contained in jbossesb.sar
In the release note - page 12, section 10.2
Link: Added: This issue is related to SOA-1298