Thanks, I have another question, In juddi 0.9rc4, the security service is embed in publish/inquiry services. in v3 the security service is seperated from publish/inquiry services.
That means if my prevous client code is using v2 to do get_authtoken action against publish/inquiry services. It will not work in v3 because subscrioptoin/inquiry services does not contain get_authtoken now. Is there a way to make v3 be compatible to the client of previous versions ? On Fri, May 13, 2011 at 9:03 PM, Kurt T Stam <[email protected]> wrote: > Hi Shawn, > > You are right, to get the properties into the ConnectionFactory you have to > do something like we do in the tests: > > > http://svn.apache.org/repos/asf/juddi/scout/trunk/src/test/java/org/apache/ws/scout/BaseTestCase.java > > It allows you to put there setting in a properties file of your own and > then pass it down into the JAXR implementation. > > --K > > > > > On 5/13/11 5:15 AM, Shawn Jiang wrote: > > Thanks, Kurt ! > > I tried to put a scout.properties with following info but it does not work > at all. > > scout.proxy.uddiVersion=3.0 > scout.proxy.uddiNamespace=urn:uddi-org:api_v3 > > I searched the source code of scout just find there's no place to pick up > the scout.properties in the code. The best places to read the properties > are : > > org.apache.ws.scout.registry.RegistryV3Impl.init(Properties) > org.apache.ws.scout.registry.RegistryImpl.init(Properties) > > But I don't see any code to read and use the values from properties file. > Do I miss anything here ? > > > > On Thu, May 12, 2011 at 9:59 PM, Kurt T Stam <[email protected]> wrote: > >> Hi Shawn, >> >> Scout is a JAXR library to talk to a an XML registry. jUDDI is an >> implementation of such an XML based registry implementing the UDDI spec. >> jUDDI 2.x implements the UDDI v2 spec. jUDDI 3.x implements the UDDI v3 >> spec. Scout comes with its own configuration file: scout.properties. To have >> it create UDDIv3 requests use >> >> scout.proxy.uddiVersion=3.0 >> scout.proxy.uddiNamespace=urn:uddi-org:api_v3 >> >> See also: >> >> >> http://svn.apache.org/repos/asf/juddi/scout/trunk/src/test/resources/scoutv3.properties-example >> >> ad 1. The reason for defaulting it to UDDI v2 is that JAXR 1.0 only talks >> about UDDI v2, and there is no new JAXR version to deal with UDDI v3. Scout >> support UDDI v3 only where the UDDI v2 and v3 feature set overlap. >> >> ad 2. I think you are confusing the context jUDDI's webservices are >> deployed at with your webservices. You would deploy your services under a >> different context (not /juddi). You then will have to register them into >> jUDDI. You can do that by calling the jUDDI webservice API. Also we create >> annotations to do 'auto-registration' on deployment. See: >> >> http://juddi.apache.org/docs/3.0/userguide/html/chap-UDDI_annotations.html >> >> Hope that clears things up. >> >> Cheers, >> >> --Kurt >> >> >> On 5/12/11 3:36 AM, Shawn Jiang wrote: >> >>> Hi devs, >>> >>> >>> 1, There are both v2 and v3 impl classes in scout. And some of them >>> has version properties, I noticed that the default version in V3Impl is >>> 2.0. >>> >>> org.apache.ws.scout.registry.RegistryV3Impl.DEFAULT_UDDI_VERSION= "2.0"; >>> org.apache.ws.scout.registry.RegistryV3Impl.DEFAULT_UDDI_NAMESPACE = >>> "urn:uddi-org:api_v2"; >>> >>> My question is : >>> >>> What's the reason to default the V3 impl to 2.0 ? How to specify the >>> version I want to use in uddi war ? I tried juddiv3.properties but it seems >>> not working. >>> >>> >>> 2, I deploy the jaxws web services by myself and these deployed uddi >>> services are not of default v3 services/xxxxService path. >>> >>> For example, I deployed all the services to /juddi/xxxService. Where >>> can I change these URL mapping with something below ? >>> >>> juddi.proxy.inquiryURL = http://localhost:8080/juddi/UDDIInquiryService >>> juddi.proxy.publishURL = >>> http://localhost:8080/juddi/UDDIPublicationService >>> juddi.proxy.securityURL = >>> http://localhost:8080/juddi/UDDISecurityService >>> >>> >>> Thanks in advance ! >>> >>> -- >>> Shawn >>> >> >> > > > -- > Shawn > > > -- Shawn
