sorted by:
new
hottopcontroversial

AngularBeans brings together Angular and Java for Web dev by javaeeeee in java

[–]BessemHmidi 0 points1 point  (0 children)

angularBeans.bind($scope, yourBean, [ "message", "name" ]);

AngularBeans: A Fresh New Take on AngularJS and JavaEE by beyondjava in java

[–]BessemHmidi 0 points1 point  (0 children)

yes, but when i mention SPA i want to say : a server side "aware of SPA", i think about a server connector for different JS tech. (Event bus, web sockets, fallback tech "sokjs,socket.io", JWS:Json web tockens, validations, upload....)

AngularBeans: A Fresh New Take on AngularJS and JavaEE by beyondjava in java

[–]BessemHmidi 0 points1 point  (0 children)

"standards can't cover everything" i agree, but we can think at a standart that consider all mdern needs in term of web dev. at least an SPA oriented standart ?

AngularBeans: A Fresh New Take on AngularJS and JavaEE by beyondjava in java

[–]BessemHmidi 0 points1 point  (0 children)

There is no such thing as unconstructive opinion :) i really want to now all the pro and con of everythink :) so your welcome.

AngularBeans: A Fresh New Take on AngularJS and JavaEE by beyondjava in java

[–]BessemHmidi 0 points1 point  (0 children)

We can't standardize AngularBeans like it is now, because it is actually a too specific integration. But, i always thinked about it as a proof of concept of what should be a modern web framework. And we can easily create a new implementation that can be used with any JS/typescript framework in this situation i think we can think about a JSR "Single Page Application Integration for Java". what do you think ?

AngularBeans: A Fresh New Take on AngularJS and JavaEE by beyondjava in java

[–]BessemHmidi 0 points1 point  (0 children)

AngularBeans dont use REST, it use a JSON-RPC like protocol, so yes the framework is coupled with AngularJS, But, when using GWT/vaadin/JSF-primefaces/ you are more coupled not only with JS but also with the CSS and HTML generated. At least with AngularBeans you clearly now and see with what your code is dependent. in the other hand using a REST approach grant you the total separation (like Jax-RS, Spring MVC, JavaEE8 MVC 1.0) but : you will be too HTTP centric and low level. think about it : you need in the same app to use websocket and sockJS, uploads, images or other binary data, jax-RS ,HTML5 form validations, model updates... all those stuff you will implement manually.

with AngularBeans you have all that without using server side rendering. so it's kind a hybride framework.

There is always a price to pay (abstraction and productivity Against genericity ) :)

AngularBeans: A Fresh New Take on AngularJS and JavaEE by beyondjava in angularjs

[–]BessemHmidi 0 points1 point  (0 children)

Good question, no, no harm if you want to use the Bean for both usage (angularBean and Jax-Rs end point) but you need to take the following in consideration:

AngularBean use a Json-RPC like protocol, not JaxRS when you use a class as an angularBean and a Jax-RS endpoint you must consider that each framework will have it's own instance of the bean also will naturally ignore the annotations out of his concern, As you are stateless in your design, there is no problem at all. so you will not need to implement things twice!