[
https://issues.apache.org/jira/browse/PROTON-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610983#comment-13610983
]
Keith Wall edited comment on PROTON-276 at 3/22/13 5:48 PM:
------------------------------------------------------------
I think the problem is with our test wrapper, JythonTest, and the arrangement
of resources on the classpath (governed by the test/pom.xml). Together they
are having the affect of making the python scripts and test resources (e.g. the
test certs etc) available to python tests by two different routes.
* once by way of the Java classpath (tests/target/classes/ is on the classpath),
* and once again by way of the Python sys.path established in JythonTest#test()
It seems when the tests are run on Linux, the ssl.py finds the resources by way
of the Python sys.path and this allows SslTest#_testpath to determine an
absolute path to the certificate. However, when the tests are run on Windows
the test finds the resources by way of the Java classpath. This means
SslTest_testpath returns a filename beginning with the string "__pyclasspath__"
which then goes on to fail in BouncyCastle's PEMReader.
was (Author: k-wall):
I think the problem is with our test wrapper, JythonTest, and the
arrangement of resources on the classpath (governed by the test/pom.xml).
Together they are having the affect of making the python scripts and test
resources (e.g. the test certs etc) available to python tests by two different
routes.
* once by way of the Java classpath (tests/target/classes/ is on the classpath),
* and once again by way of the Python sys.path established in JythonTest#test()
It seems when the tests are run on Linux, the ssl.py is finds the resources by
way of the Python sys.path and this allows SslTest#_testpath to determine an
absolute path to the certificate. However, when the tests are run on Windows
the test finds the resources by way of the Java classpath. This means
SslTest_testpath returns a filename beginning with the string "__pyclasspath__"
which then goes on to fail in BouncyCastle's PEMReader.
> All ssl tests fail against proton-j on Windows
> ----------------------------------------------
>
> Key: PROTON-276
> URL: https://issues.apache.org/jira/browse/PROTON-276
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.4
> Reporter: Keith Wall
> Assignee: Keith Wall
>
> Running mvn test on Windows I see all the (Python) ssl tests fail. The error
> message is:
> java.lang.RuntimeException: Unable to read PEM object from file
> __pyclasspath__/proton_tests\ssl_db/ca-certificate.pem
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
