[jira] [Commented] (LENS-549) Lens client doesn't come-up if the lens server is not available

["Rajat Khandelwal (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LENS-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547616#comment-14547616 ] 

Rajat Khandelwal commented on LENS-549:
---------------------------------------

LensClientSingletonWrapper is what is sounds like: a singleton wrapper for Lens Client. The setClient method is not useful IMO. It was designed as a utility class for users of lens-client module(e.g. lens-cli module), providing the credential prompt code. So users of lens client don't need to write their own code for credential prompting.

Please suggest if you have an alternative design in mind. The case you have mentioned should be handled in LensClient#connectToLensServer. That method should make sure all required parameters are there. 

> Lens client doesn't come-up if the lens server is not available
> ---------------------------------------------------------------
>
>                 Key: LENS-549
>                 URL: https://issues.apache.org/jira/browse/LENS-549
>             Project: Apache Lens
>          Issue Type: Bug
>            Reporter: Pranav Kumar Agarwal
>            Assignee: Pranav Kumar Agarwal
>
> LensClientSingletonWrapper constructor fails if the lens.server.base.url is unavailable. atm, since its in static path it fails with ExceptionInInitializerError, thus unable to use LensClientSingletonWrapper.setClient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)