Bug 778583 (SOA-1057) - typo in jUDDI related code sample
Summary: typo in jUDDI related code sample
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1057
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.3 GA,4.2 CP02
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP03
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-02 02:39 UTC by Dana Mison
Modified: 2009-01-12 19:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-12 19:26:54 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778619 0 high CLOSED typo in jUDDI related code sample 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1057 0 None None None Never

Internal Links: 778619

Description Dana Mison 2008-12-02 02:39:28 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2008-12-15 06:39:16
project_key: SOA

This section is from the 4.3 Services Guide & the 4.2 Registry Guide.  I assume that the String factoryInitial = ... line is missing either a ); and or some arguments.  This is the same in the ESB source doc.


Where the hostname of the queryManagerURI and lifeCycleManagerURI need to point to the hostname on which jUDDI is running (which would be where application1 is running). Obviously application1 needs to have access to a naming service. To do the registration process you need to do something like:

//Getting the JNDI setting from the config
String factoryInitial = Config.getStringProperty(
Properties env = new Properties();
env.setProperty(RegistryEngine.PROPNAME_JAVA_NAMING_FACTORY_INITIAL,factoryInitial);
env.setProperty(RegistryEngine.PROPNAME_JAVA_NAMING_PROVIDER_URL, providerURL);
env.setProperty(RegistryEngine.PROPNAME_JAVA_NAMING_FACTORY_URL_PKGS, factoryURLPkgs); 

InitialContext context = new InitialContext(env);
Inquiry inquiry = new InquiryService();
log.info("Setting " + INQUIRY_SERVICE + ", " + inquiry.getClass().getName());
mInquery = inquiry;
context.bind(INQUIRY_SERVICE, inquiry);
Publish publish = new PublishService();
log.info("Setting " + PUBLISH_SERVICE + ", " + publish.getClass().getName());
mPublish = publish;
context.bind(PUBLISH_SERVICE, publish);

Comment 1 nwallace 2008-12-15 11:39:16 UTC
I've emailed Kev to see if he can help.

Comment 2 tcunning 2008-12-19 14:48:54 UTC
My suggestion is just to remove the String factoryInitial = Config.getStringProperty line and leave the value of factoryInitial to be assumed.      In the code sample, neither providerURL and factoryURLPkgs are set.       It'd probably more consistent to just assume that the user has set all three previously then to set one and leave the other two assumed.

load_generator/src/org/jboss/soa/esb/samples/quickstart/jmx/JMXAttributeFinder.java seems like a decent example of where this is used.

Comment 3 Mark Little 2008-12-22 04:19:48 UTC
Link: Added: This issue is a dependency of JBESB-2247


Comment 4 Mark Little 2008-12-22 04:23:32 UTC
Changes made to project docs.

Comment 5 Mark Little 2008-12-22 04:25:46 UTC
Link: Added: This issue is a dependency of JBESB-2248


Comment 6 Mark Little 2008-12-22 04:32:30 UTC
Link: Added: This issue related SOA-1098


Comment 7 Dana Mison 2008-12-22 05:03:18 UTC
updated 4.2.CP03 Registry Guide

Comment 8 Dana Mison 2008-12-22 05:10:31 UTC
updated in 4.3.CP01 Services Guide

Comment 9 Len DiMaggio 2009-01-12 19:26:54 UTC
Verified fixed here:

https://svn.corp.jboss.com/repos/soa/branches/4.2.0/build-tools/docs/esb/services/


Note You need to log in before you can comment on or make changes to this bug.