[jira] Commented: (JCR-2326) some jcr-client tests fail if a server runs on localhost:80

["Michael Dürig (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785922#action_12785922 ] 

Michael Dürig commented on JCR-2326:
------------------------------------

Did you run into an issue with this? I.e. did the test fail when it shouldn't? 

See my comment regarding JCR-2037. As long as we don't have that I think we either have to live with the current test or remove it entirely. IMO instantiating a full blown server for the factory test would make the test run way to slow. What we could try to do is to put up a mock server instead of the full blown server. WDYT?

OTOH there is also JCR-2362. If we are going to remove the jcr-client module entirely I think we shouldn't bother too much. 



> some jcr-client tests fail if a server runs on localhost:80 
> ------------------------------------------------------------
>
>                 Key: JCR-2326
>                 URL: https://issues.apache.org/jira/browse/JCR-2326
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-client
>    Affects Versions: 2.0.0
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Minor
>             Fix For: 2.0-beta1
>
>
> This is caused by RepositoryFactoryImplTest.testGetSpi2davRepository() and probably RepositoryFactoryImplTest.testGetSpi2davexRepository(). 
> To fix this the tests should set up the required webDav servers for the test runs. Currently the tests just try to connect to localhost:80 expecting the connection to fail in a specific way. 

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