| Summary: | jUDDI v3 sample code referenced in user guide, not included in ER4 build | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Documentation, Distribution, jUDDI - within SOA | Assignee: | Kurt Stam <kurt.stam> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 ER4 | ||
| Target Milestone: | --- | ||
| Target Release: | FUTURE | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1663 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-08 20:00:29 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
Len DiMaggio
2009-12-03 03:04:12 UTC
Happy to work on this but I maybe more an ESB task since they integrate jUDDI? Could we simply add links to the maven artifacts, rather then shipping it? We have no interest in the juddi documentation, examples nor uddi-console, definitely not an ESB task. For the SOA jUDDI docs we have decided to link to the project example code. A disclaimer is going to be added to the text in the doc specifying that although the use-cases described by the code are supported, the example code itself is not & has not been QE'd or tested. Are you aware of any issues that could complicate this, Kurt? quick question: I can't find juddi-client-3.0.0.jar The closest I can find is jboss-soa-p.5.0.0/jboss-as/server/production/deployers/esb.deployer/lib/juddi-client-3.0.0.aop.jar I suspect that this is not the jar I'm looking for. It actually is the jar you are looking for + some aop fixed, which we are currently trying to roll in, so that we don't need the aop stuff anymore. Kurt is correct, the aop version allows ESB to workaround some issues in that version of juddi. The intent is to remove as many, if not all, of these workarounds with the upcoming 3.0.1 release of juddi at which point this should be called juddi-client-3.0.1.jar. If we still need the aop version then we will also have to add the aop jars/configuration to the documentation. Link: Added: This issue related SOA-1657 Affects: Added: [Release Notes] OK, I'll update the docs to indicate that JAR file Also: what is the best URL (for this version of jUDDI) to direct people to for the sample code? Is this URL ok for the example code? http://svn.apache.org/repos/asf/webservices/juddi/tags/juddi-3.0.0/juddiv3-samples/ http://svn.apache.org/repos/asf/webservices/juddi/tags/juddi-3.0.1/docs/examples/ http://svn.apache.org/repos/asf/webservices/juddi/tags/juddi-3.0.1/juddiv3-samples/ I think we may want to consider adding the relevant code as an appendix. One of the things I will do this week is set up a jboss soa-p instance with the latest code to make sure it all works. --Kurt re: including code as an appendix I've thought about that, for it to be worthwhile you need to include the code for the complete complete project & all the details of directory structure, maven pom etc. ie. everything that someone would need to build it. It's generally better to include snippets of relevant code & then direct users to where the complete projects are available. Could the jUDDI samples could be zipped up for separate download on ws.apache.org/juddi ? PM team decided this is a nice to have for SOA 5.1.0. Not a blocker. Writer: Added: Darrin Release Notes Docs Status: Added: Not Yet Documented |