Hide Forgot
Affects: Release Notes Date of First Response: 2009-12-16 13:36:55 project_key: SOA In ER4, the client (for example, the juddi-client-3.0.0.jar file) is packaged in jboss-soa-p.5.0.0/jboss-as/server/production/deploy/uddi-console.war - the sample code, however is not. If we are supporting and documenting the use of the client, then we should ship all the documented code/files and not require SOA-P 5.0 customers to have to download the jUDDI project. In the new SOA-P jUDDI v3 guide, this section refers to the examples: ============= 7.7. Sample Code Sample code demonstrating how to use the UDDI Client can be found in the uddi-client module on the jUDDI v3 project. Another place to look for sample code is the docs/examples/helloword directory. A final alternative is to use annotations.
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