[
https://issues.apache.org/jira/browse/JUDDI-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007728#comment-15007728
]
Alex O'Ree commented on JUDDI-943:
----------------------------------
I'm working on making some test cases for this and am unable to recreate the
bug. The clientName is used when you have more than one juddi config file
loaded for some reason. The client name is what you use to differentiate them.
Is that the case here?
> WebHelper class: Client name not set in servletContext after getUDDIClient is
> called
> ------------------------------------------------------------------------------------
>
> Key: JUDDI-943
> URL: https://issues.apache.org/jira/browse/JUDDI-943
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
> Affects Versions: 3.3.1
> Reporter: Matthieu Ghilain
>
> The client name is not set after the method:
> WebHelper.getUDDIClient(servletContext) is called and it seems it should be.
> Because the client name is not set a new UDDI client is returned each time
> the method is called despite the same servletContext is passed.
> The problem is here (from WebHelper class):
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " +
> client.getName() + "...");
> } else {
> throw new ConfigurationException("A client name
> needs to be specified in the client config file.");
> }
> {code}
> it should be according to me:
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " + client.getName() + "...");
> clientName = client.getName();
> } else {
> throw new ConfigurationException("A client name needs to be specified in
> the client config file.");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
