juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gunnlaugur Sigurðsson (JIRA) <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-397) new self-registering web service removes present ws
Date Fri, 21 May 2010 14:14:17 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869989#action_12869989
] 

Gunnlaugur Sigurðsson commented on JUDDI-397:
---------------------------------------------

Just downloaded release 3.0.2 and same problem occurred.

> new self-registering web service removes present ws
> ---------------------------------------------------
>
>                 Key: JUDDI-397
>                 URL: https://issues.apache.org/jira/browse/JUDDI-397
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 3.0.1
>         Environment: Ubuntu linux, juddi-portal-bundle-3.0.1, 
>            Reporter: Gunnlaugur Sigurðsson
>            Assignee: Kurt T Stam
>            Priority: Blocker
>             Fix For: 3.0.3
>
>         Attachments: selfregister.tar, taketwo.tar
>
>
> When I publish new self-registering web service it removes present web service.
> Description of my issue can be found in the user mailing list I posted Mon, 17 May, 13:07,
"UDDI Annotations - How do I self-register my service?"
> Prior to publishing the new service I had one service already that was able register
it self, but when I added the new service, the other one disappeared.
> There is this entry in src/main/webapp/WEB-INF/web.xml in both projects
>   <servlet>
>     <display-name>Clerk Servlet</display-name>
>     <servlet-name>UDDIClerkServlet</servlet-name>
> <servlet-class>org.apache.juddi.v3.client.config.UDDIClerkServlet</servlet-class>
>     <init-param>
>         <param-name>uddi.client.manager.name</param-name>
>         <param-value>example-manager</param-value>
>     </init-param>
>     <load-on-startup>1</load-on-startup>
>   </servlet>
> As soon as I added this to my new web service the other one disappeared when I deployed
the new service. 
> Is this causing conflict between the two?
> Name of the manager in both uddi.xml files is <manager name="example-manager">
is this not supposed to be like that?
> And the uddi.xml both have the same named clerk, but with different class entry.
>         <clerks registerOnStartup="true">
>            <clerk name="SalesCratchit" node="default" publisher="sales" password="sales">
>                 <class>is.siminn.juddi.ws.HelloWorldImpl</class>
>            </clerk>
>         </clerks>
>         <clerks registerOnStartup="true">
>            <clerk name="SalesCratchit" node="default" publisher="sales" password="sales">
>                 <class>is.siminn.juddi.ws.AppImpl</class>
>            </clerk>
>         </clerks>
> And the notations in the implementation classes are as follow.
> @UDDIService(
>         businessKey="uddi:${keyDomain}:${department}-asf",
>         serviceKey="uddi:${keyDomain}:services-hello${department}",
>         description = "Hello World test service")
> @UDDIServiceBinding(
>         bindingKey="uddi:${keyDomain}:bindings-hello${department}-wsdl",
>         description="WSDL endpoint for the hello${department} Service. This
> service is used for "
>                   + "testing the jUDDI annotation functionality",
>         accessPointType="wsdlDeployment",
>         accessPoint="http://${serverName}:${serverPort}/taketwo/app?wsdl")
> @WebService(
>         endpointInterface = "is.siminn.juddi.ws.App", serviceName = "App")
> ++++++++++++++++++++++++++++
> @UDDIService(
>         businessKey="uddi:${keyDomain}:${department}-asf",
>         serviceKey="uddi:${keyDomain}:services-hello${department}",
>         description = "Hello World test service")
> @UDDIServiceBinding(
>         bindingKey="uddi:${keyDomain}:bindings-hello${department}-wsdl",
>         description="WSDL endpoint for the hello${department} Service. This
> service is used for "
>                   + "testing the jUDDI annotation functionality",
>         accessPointType="wsdlDeployment",
>         accessPoint="http://
> ${serverName}:${serverPort}/selfregister/helloworld?wsdl")
> @WebService(
>         endpointInterface = "is.siminn.juddi.ws.HelloWorld", serviceName =
> "HelloWorld")
> I.e. tha App is the new service.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message