[
https://issues.apache.org/jira/browse/SCOUT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057609#comment-13057609
]
Kurt T Stam commented on SCOUT-107:
-----------------------------------
Hi Subes,
Thank you for your feedback, and I fully agree.. From a code perspective I
think we should just rip out this stuff in the RegistryImpls all together since
it seems of little value. Do you maybe have anything in the form of
documentation that can be useful for other users? We could add it as a Getting
Started Guide..
Cheers,
--Kurt
> fix constants in org.apache.ws.scout.registry.RegistryV3Impl for uddi 3
> -----------------------------------------------------------------------
>
> Key: SCOUT-107
> URL: https://issues.apache.org/jira/browse/SCOUT-107
> Project: Scout
> Issue Type: Bug
> Components: Scout Implementation
> Affects Versions: 1.2.2
> Reporter: subes
> Assignee: Kurt T Stam
> Fix For: 1.2.4
>
>
> in org.apache.ws.scout.registry.RegistryV3Impl these constants are defined:
> public static final String DEFAULT_INQUIRY_ENDPOINT =
> "http://localhost/juddi/inquiry";;
> public static final String DEFAULT_PUBLISH_ENDPOINT =
> "http://localhost/juddi/publish";;
> public static final String DEFAULT_SECURITY_ENDPOINT =
> "http://localhost/juddi/security";;
> public static final String DEFAULT_ADMIN_ENDPOINT =
> "http://localhost/juddi/admin";;
> public static final String DEFAULT_TRANSPORT_CLASS =
> "org.apache.ws.scout.transport.AxisTransport";
> public static final String DEFAULT_SECURITY_PROVIDER =
> "com.sun.net.ssl.internal.ssl.Provider";
> public static final String DEFAULT_PROTOCOL_HANDLER =
> "com.sun.net.ssl.internal.www.protocol";
> public static final String DEFAULT_UDDI_VERSION = "2.0";
> public static final String DEFAULT_UDDI_NAMESPACE = "urn:uddi-org:api_v2";
> Those are just copy-pasted from org.apache.ws.scout.registry.RegistryImpl and
> don't fit for juddi 3, but are still for juddi 2.
> Corrected those constants should be:
> public static final String DEFAULT_INQUIRY_ENDPOINT =
> "http://localhost//juddiv3/services/inquiry";;
> public static final String DEFAULT_PUBLISH_ENDPOINT =
> "http://localhost/juddiv3/services/publish";;
> public static final String DEFAULT_SECURITY_ENDPOINT =
> "http://localhost//juddiv3/services/security";;
> public static final String DEFAULT_ADMIN_ENDPOINT =
> "http://localhost/juddiv3/services/juddi-api";;
> public static final String DEFAULT_TRANSPORT_CLASS =
> "org.apache.ws.scout.transport.AxisTransport";
> public static final String DEFAULT_SECURITY_PROVIDER =
> "com.sun.net.ssl.internal.ssl.Provider";
> public static final String DEFAULT_PROTOCOL_HANDLER =
> "com.sun.net.ssl.internal.www.protocol";
> public static final String DEFAULT_UDDI_VERSION = "3.0";
> public static final String DEFAULT_UDDI_NAMESPACE = "urn:uddi-org:api_v3";
> Though, i don't know if AxisTransport has to get those values for the urls
> actually:
> public static final String DEFAULT_INQUIRY_ENDPOINT =
> "http://localhost//juddiv3/services/inquiry?wsdl";;
> public static final String DEFAULT_PUBLISH_ENDPOINT =
> "http://localhost/juddiv3/services/publish?wsdl";;
> public static final String DEFAULT_SECURITY_ENDPOINT =
> "http://localhost//juddiv3/services/security?wsdl";;
> public static final String DEFAULT_ADMIN_ENDPOINT =
> "http://localhost/juddiv3/services/juddi-api?wsdl";;
> Which are actually set in my uddi.xml for juddi-client 3.0.4. Actualy I could
> not get AxisTransport to run so i switched to LocalTransport and set the
> proper juddi-client classes as the endpoint.
> -------------------------------------------------------------
> Maybe you should make this setup with juddi-client doing the actual
> communication default for uddi 3? I got that idea from
> http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/ESB_Services_Guide/chap-the_registry.html#sect-SOA_ESB_Services_Guide-Configuring_the_Registry-Using_Scout_and_jUDDI
> (outdated because the classes are for juddi-client 2 and changed in
> juddi-client 3, though they talk about juddi-client 3 needed in the classpath
> at the end).The properties for this setup would be:
> public static final String DEFAULT_INQUIRY_ENDPOINT =
> "org.apache.juddi.v3.client.transport.wrapper.UDDIInquiryService#inquire";
> public static final String DEFAULT_PUBLISH_ENDPOINT =
> "org.apache.juddi.v3.client.transport.wrapper.UDDIPublicationService#publish";
> public static final String DEFAULT_SECURITY_ENDPOINT =
> "org.apache.juddi.v3.client.transport.wrapper.UDDISecurityService#secure";
> public static final String DEFAULT_ADMIN_ENDPOINT =
> "http://localhost/juddiv3/services/juddi-api";; //actually i dont know about
> this, because it seems it isnt even used when having juddi-client?
> public static final String DEFAULT_TRANSPORT_CLASS =
> "org.apache.ws.scout.transport.LocalTransport";
> public static final String DEFAULT_SECURITY_PROVIDER =
> "com.sun.net.ssl.internal.ssl.Provider";
> public static final String DEFAULT_PROTOCOL_HANDLER =
> "com.sun.net.ssl.internal.www.protocol";
> public static final String DEFAULT_UDDI_VERSION = "3.0";
> public static final String DEFAULT_UDDI_NAMESPACE = "urn:uddi-org:api_v3";
> If this is too much, I would be happy if you just fixed these two constants:
> public static final String DEFAULT_UDDI_VERSION = "3.0";
> public static final String DEFAULT_UDDI_NAMESPACE = "urn:uddi-org:api_v3";
> So I can use the correct constants from
> org.apache.ws.scout.registry.RegistryV3Impl for these two properties instead
> of defining them in my code as string literals.
> Finding the correct values was also quite hard :). Found them by browsing the
> scout sources
> http://svn.apache.org/viewvc/juddi/scout/trunk/src/test/resources/scoutv3.properties-example?view=markup
> ----------------------------------------------------------------
> As a benchmark, it took me as a uddi and jaxr newb three days to get this
> setup working and integrated into my software product line project. Scout is
> an important and good project, but it could be a bit more robust and user
> friendly. ;)
> Documentation on this subject at all is quite sparse, which made this quite
> hard to get done.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
