Fix for Java demos, WSS issues 571, 972 & 973#14
Merged
dpwspoon merged 5 commits intokaazing:developfrom Mar 14, 2017
Merged
Conversation
…dup the projects, also added functionality for starting the pogram with a user inputed URI, username and password.
zahariaca
changed the title
zahariaca
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixed problem with connecting to wss in all 3 j2se demos, also cleaned up the projects, also added functionality for starting the program with a user inputed URI, username and password.
The JMS, AMQP and WS where not running OOTB because they where setup with a
wss://sandbox.kaazing.net/*. This would cause a problem because it could not find the certificate in the Java cacert and the connection could never be established and the apps would either crash or just not function at all.Also because the URI was hard coded in the app, it was not user friendly. I made changes to the app so that it will start with
ws://sandbox.kaazing.net/*by default, but now the user can also give arguments to the programs to start them with their own URI, username and passwords. I decided to change the URI fromWSStoWSbecause using actual SSL connection in java is hard, the user would have to addsandbox.kaazing.netcertificate into their local java cacert. The user could still use aWSSif they would input it theWSSURI as a command line argument and if they would import the appropriate certificate in java cacert.Added a guide for starting each app inside the appropriate README.md and in the actual program in case someone inputs the wrong number of command line arguments.
Also all the demos had all they're functionality inside the class constructor, so I changed that to better reflect Java best practices.