Can I declare variables of different types in the initialization of a for loop? [duplicate]

Yes, that is prohibited. Just as otherwise you cannot declare variables of differing types in one declaration statement (edit: modulo the declarator modifiers that @MrLister mentions). You can declare structs for (struct { int a = 0; short b = 0; } d; d.a < 10; ++d.a, ++d.b ) {} C++03 code: for (struct { … Read more

Angular JS resizable div directive

This question is old, but for anybody looking for a solution, I built a simple directive to handle this, for vertical and horizontal resizers. Take a look at the Plunker angular.module(‘mc.resizer’, []).directive(‘resizer’, function($document) { return function($scope, $element, $attrs) { $element.on(‘mousedown’, function(event) { event.preventDefault(); $document.on(‘mousemove’, mousemove); $document.on(‘mouseup’, mouseup); }); function mousemove(event) { if ($attrs.resizer == ‘vertical’) … Read more

I can pass a variable from a JSP scriptlet to JSTL but not from JSTL to a JSP scriptlet without an error

Scripts are raw java embedded in the page code, and if you declare variables in your scripts, then they become local variables embedded in the page. In contrast, JSTL works entirely with scoped attributes, either at page, request or session scope. You need to rework your scriptlet to fish test out as an attribute: <c:set … Read more

Limiting number of displayed results when using ngRepeat

Slightly more “Angular way” would be to use the straightforward limitTo filter, as natively provided by Angular: <ul class=”phones”> <li ng-repeat=”phone in phones | filter:query | orderBy:orderProp | limitTo:quantity”> {{}} <p>{{phone.snippet}}</p> </li> </ul> app.controller(‘PhoneListCtrl’, function($scope, $http) { $http.get(‘phones.json’).then( function(phones){ $scope.phones =; } ); $scope.orderProp = ‘age’; $scope.quantity = 5; } ); PLUNKER

what is none scope bean and when to use it?

A bean with a <managed-bean-scope> of none or a @NoneScoped annotation will be created on every single EL expression referencing the bean. It isn’t been stored by JSF anywhere. The caller has got to store the evaluated reference itself, if necessary. E.g. the following in the view <p>#{noneScopedBean.someProperty}</p> <p>#{noneScopedBean.someProperty}</p> <p>#{noneScopedBean.someProperty}</p> on a none-scoped bean will … Read more