task #8652
closed
disentangle confusion when connecting to development cdm instance fails
Added by Andreas Kohlbecker almost 5 years ago.
Updated almost 5 years ago.
Description
It can be quite cumbersome to find the cause when connecting to a development cdm instance fails.
To connect this way the following system properties are set:
-Dcdm.server.dev.port=<port>
-Dcdm.server.dev.username=<user>
-Dcdm.server.dev.password=<password>
The reasons for being confused are
- inappropriate error message
- strange and misleading code lines
- Status changed from New to Resolved
- % Done changed from 0 to 50
- Subject changed from disentangle confusion when conecting to development cdm instance fails to disentangle confusion when connecting to development cdm instance fails
- Assignee changed from Andreas Kohlbecker to Katja Luther
- Priority changed from New to Priority14
apparently these changes are not causing problems.
@Katja: I think the changes that I made to ExtReferenceSelectionDialog.java did remove the lines that came from you. I can imagine that you may want to review my changes, so I am passing this ticket to you now.
One question: Is the ExtReferenceSelectionDialog.java used at all? Non of any breakpoints that I set in there have been hit during testing.
Andreas Kohlbecker wrote:
apparently these changes are not causing problems.
@Katja: I think the changes that I made to ExtReferenceSelectionDialog.java did remove the lines that came from you. I can imagine that you may want to review my changes, so I am passing this ticket to you now.
One question: Is the ExtReferenceSelectionDialog.java used at all? Non of any breakpoints that I set in there have been hit during testing.
ExtReferenceSelectionDialog is not used at the moment, it is an example implementation for connection to a second cdm instance
- Status changed from Resolved to Closed
- Assignee changed from Katja Luther to Andreas Kohlbecker
Also available in: Atom
PDF