tyrus | Reference implementation of Java API | Code Editor library

jetty-websocket-client-api supports both.

Thank you BalusC.

It works!
3 weeks!

I update "3 plugin of nb-javac " from NB page and relaunch IDE.
Then my program work!!
("JAVA_HOME & PATH" remains JDK1.8)

※ At first time,
NB informed me one warning and infomation(it is about nb-javac) at bottom of IDE window.
but I coundn't install from tool -> plugin , so I left it as it was.... I'v learned. (^^;)>

Could this be the problem?

Cannot run program "git" (in directory "C:\Users\ruca\farm"): CreateProcess error=2

Do you have git installed? Can it be run from the prompt? "error=2" often refers to a missing file.

You're already using spring mvc (see your stack trace that contains spring mvc classes)

If so, probably the best option would be catching the exception at the level of Contoller Advice or any other exception handling mechanism supported by spring MVC.

Basically the stack trace is printed by spring mvc engine itself only if no-one (controller, advice or maybe service) has caught it.

From the angular standpoint there is no such a thing as an exception though. Instead you get a non 200 status with some default JSON this is a response in HTTP format, not an exception but just a response of some specific type. So I believe the best would be to establish some protocol of for messages that come to the client side and clearly the server stack trace is not something to be sent to client.

This is a kind of convention that may include:

1. HTTP status (non 200 to differentiate between errors and regular answers)
2. JSONmessage in a predefined format with:

• Exception ID
• Time on server
• Message
• Parameters to be mapped on client
• I18n related information if its relevant for your application.

Long story short:

• You create a controller advice and map the custom exception there
• The mapping method will create a "protocol" json and return it to angular.
• This mapping method will be called by spring automatically if no-one has caught the exception before.
• Since the mapping method will handle the exception, it won't be printed on console of the server which is kind of what you're trying to achieve.
• The client will get the json and will create some "infrastructure" code in angular that handles all the messages (maybe shows the message at the top of the screen, popup whatever).

There is no such thing as "synchronous websocket" as it's a whole different messaging protocol than HTTP. While HTTP is a request-response protocol, where you expect a response from the client once you sent the request, WebSocket establishes a connection using a handshake request, after which the communication becomes bidirectional where there is no concept of response to a request. You can read more about it in Wikipedia.

I think this is caused due to not having Unlimited Strength Java Cryptography Extension installed in your JRE.

Try installing(Copying JAR's) inside your JRE lib/security folder. Get it from here.

Just Download and Extract the Content. You should get two files local_policy.jar and US_export_policy.jar. Copy this to $JAVA_HOME/jre/lib/security folder.

If that resolves the issue, You should consider upgrading your Java 8 version. This issue has been addressed in Java 8u161 or later version.

Try to create a fat jar which contains all the dependencies and classes.

Update build.gradle script to this given below :

you have to use SetParamtereList method , you see some detail in this link https://stackoverflow.com/a/14296425/1838804

I have been searching a little and found 3 things (not sure this is the or even an answer at all, but it is too much to type in comments)

1. is a 'duplicate' using javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL causes viewParam to be null (unanswered but some discussion)
2. is a link that seems to be related includeViewParams=true converts null model value to empty string in query string

3. is some info from http://showcase.omnifaces.org/components/viewParam about a change in JSF 2.3 related to viewParam and null.

   In JSF 2.3, this has been fixed and has only effect when javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL context param is set to true.

This combination leads me to think that you 'were lucky' it worked in 2.2 (sure id was not '0' on postbacks?) And honestly, the 2.3 behaviour 'feels' correct.

As a solution you could also add a 'null' check in the setter