You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2010/06/29 17:56:50 UTC
[jira] Issue Comment Edited: (JUDDI-397) new self-registering web
service removes present ws
[ https://issues.apache.org/jira/browse/JUDDI-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883593#action_12883593 ]
Kurt T Stam edited comment on JUDDI-397 at 6/29/10 11:55 AM:
-------------------------------------------------------------
Hi Gunnlaugur,
This is by design, and will happen if you use the same serviceKey. I did not notice before that in your example you use the same key: "serviceKey="uddi:${keyDomain}:services-hello${department}"
This issue will not occur if you use different keys. The key is unique to the sevice.
--Kurt
was (Author: kurtstam):
Hi Gunnlauger,
This is by design, and will happen if you use the same serviceKey. I did not notice before that in your example you use the same key: "serviceKey="uddi:${keyDomain}:services-hello${department}"
--Kurt
> 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.
Re: [jira] Issue Comment Edited: (JUDDI-397) new self-registering web
service removes present ws
Posted by Gunnlaugur Sigurðsson <gu...@gmail.com>.
Hi Kurt.
Thanks for this information.
I'll have to take a look at my service keys.
Thats a nother mail
http://mail-archives.apache.org/mod_mbox/ws-juddi-user/201006.mbox/%3CAANLkTikwfSTqipLQc3Ppw_Qr5CCdpuheKpthwIBNcwBH@mail.gmail.com%3E
Thanks.
-Gunnlaugur
On Tue, Jun 29, 2010 at 3:56 PM, Kurt T Stam (JIRA)
<ju...@ws.apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/JUDDI-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883593#action_12883593 ]
>
> Kurt T Stam edited comment on JUDDI-397 at 6/29/10 11:55 AM:
> -------------------------------------------------------------
>
> Hi Gunnlaugur,
>
> This is by design, and will happen if you use the same serviceKey. I did not notice before that in your example you use the same key: "serviceKey="uddi:${keyDomain}:services-hello${department}"
>
> This issue will not occur if you use different keys. The key is unique to the sevice.
>
> --Kurt
>
> was (Author: kurtstam):
> Hi Gunnlauger,
>
> This is by design, and will happen if you use the same serviceKey. I did not notice before that in your example you use the same key: "serviceKey="uddi:${keyDomain}:services-hello${department}"
>
> --Kurt
>
>> 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.
>
>
--
Kveðja/Regards
Gunnlaugur Sigurðsson
gunnlaugursig@gmail.com
Mobile: (+354) 896-7963
Home: (+354) 565-5229