Self-Taught IT?

I love the premise of this article: Just because you are a Self-Taught Developer/IT Guy doesn’t make you any less authentic in your field than someone with a BS or an MS.

Planning vs. Acting is procrastination.  Just go after it.

via @DZone: 

With the high cost and low quality of College courses these days, it has surpassed the threshold of not being with the value it once offered.


IntelliJ importing Maven Project: No Route to Localhost

I will NOT be the only person to encounter this problem.
So here is my quick blog.

Using Intellij on Mac OSX Yosemite 10.10.1:

  • When trying to create a new project from existing maven sources
    the IDE would not switch to the “Select a profile” view.
  • The IDE did not give me a message.  It just wouldn’t advance. This forced me to review the logs

The logs live in :  MacintoshHD ▸ Users ▸ {user-name} ▸ Library ▸ Logs ▸ IntelliJIdea14

I could look at the logs directly through the Finder (open in a text editor) or use the convenient Console application in the application Launchpad.

I was getting this problem:  java.rmi.ConnectIOException: Exception creating connection to: localhost; nested exception is:

It was buried among an unending stack:

2015-07-05 21:40:41,304 [12622480]  ERROR - agnostic.FrequentEventDetector - IntelliJ IDEA 14.1.3  Build #IU-141.1010.3 
2015-07-05 21:40:41,304 [12622480]  ERROR - agnostic.FrequentEventDetector - JDK: 1.6.0_65 
2015-07-05 21:40:41,304 [12622480]  ERROR - agnostic.FrequentEventDetector - VM: Java HotSpot(TM) 64-Bit Server VM 
2015-07-05 21:40:41,304 [12622480]  ERROR - agnostic.FrequentEventDetector - Vendor: Apple Inc. 
2015-07-05 21:40:41,304 [12622480]  ERROR - agnostic.FrequentEventDetector - OS: Mac OS X 
2015-07-05 21:40:41,304 [12622480]  ERROR - agnostic.FrequentEventDetector - Last Action: ImportProject 
2015-07-05 21:40:41,314 [12622490]   INFO - agnostic.FrequentEventDetector - Too many events posted
    at com.intellij.openapi.diagnostic.FrequentEventDetector.eventHappened(
    at com.intellij.ide.IdeEventQueue.postEvent(
    at java.awt.EventQueue.invokeLater(
    at javax.swing.SwingUtilities.invokeLater(
    at com.intellij.openapi.application.impl.LaterInvocator.b(
    at com.intellij.openapi.application.impl.LaterInvocator.invokeLater(
    at com.intellij.openapi.application.impl.ModalityInvokatorImpl.invokeLater(
    at com.intellij.openapi.application.impl.ModalityInvokatorImpl.invokeLater(
    at com.intellij.openapi.application.impl.ApplicationImpl.invokeLater(
    at com.intellij.openapi.vfs.newvfs.RefreshQueueImpl$
    at java.util.concurrent.Executors$
    at java.util.concurrent.FutureTask$Sync.innerRun(
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
    at java.util.concurrent.ThreadPoolExecutor$
2015-07-05 21:40:41,325 [12622501]  ERROR - agnostic.FrequentEventDetector - Too many events posted
    at com.intellij.openapi.diagnostic.FrequentEventDetector.eventHappened(

This problem is driven my maven itself.

Context:  I work for a very large Enterprise with a burdensome amount of rules to access anything either in or out of the network.

Sifting through the code I eventually found the “no route to localhost” error line.

From past experience Maven proxy settings are unable to route to certain internal IPs through the proxy.

I have a “settings.xml” file sitting under my /Users/{user-name}/.m2 directory to enforce usage of certain repos and setting proxy values.  So I had to ensure my <nonProxyHosts> were set correctly:


My initial mistake was using a “,” comma for a separator.  This is not correct for Maven.  It needs a Pipe {“|”}.

I corrected this and my project import problems have been resolved.

Happy coding.

Reference to the maven proxy settings:

Angular.js Select tag via ‘ng-control’

Subtitle:  Don’t Trust Your Eyes

My project has been bouncing technologies like basketballs against the backboard. The latest techno-basketball to sink is Angular.js.  I don’t intend to do a thorough review of this technology here since it is well documented in the Google/Stackoverflow community.  But I have been having fun with populating a <Select> tag’s options using the built in angular directives.

First here are some links I found useful in my quest to resolve this issue:

Basically I am replacing this code block (originally coded to work in a Dust.js format:

<!-- Year -->
  <label for="yearID">Year:</label>
    <select id="yearID" name="year"
      value="{{ academicRecords[0].completionYear }}"
      title="Please select the completion year"></select>

… with the Angular directive code below:

   ng-options="y.value as y.option for y in yearList" 
     <option style="display:none" " 
             title="Please select the completion year">

First thing i have to do is create a $scope.yearList (my name) variable to populate the list:

$scope.yearList = $scope.getYearList();

And here is $scope.getYearList() function and the other supporting variable/function to populate this list:

$scope.getYearList = function () {
   var min = 50 ;  // Number of years to reach back to
   var year = new Date().getFullYear();
   var yearArray = [];

   do {
     // yearID.add( new Option(year,year), null );
   } while (min>0);
   return yearArray;
// Create individual JSON Array objects to populate list
$scope.yearObject = function (year) {
 return {
   option: ""+year ,  value : ""+year }

Assign the appropriate function call to the <select>’s ng-option:

ng-options="y.value group by y.option for y in yearList"

$scope.yearList as entry point fulfills this request (fills out my list.)

With everything setup I have a beautiful (auto-populated) Select List of Option Labels appropriately populating. My head scratcher at this point is controlling which values goe into the ‘Value=”” ‘ tag.  It is being generated as a 0 based list.  {0-49 in this case}


But the option value is correct (see 2012) above. So it *can’t* (famous last words) be a monumental effort get the correct values in “value=” as well.

So I Google search the following:  angular ng-option value.  

And here is what I come up with:

  • Using a case where the year comes back as 1984, submitting the form I see the following result (from Google Chrome Dev Mode):

$dirty: false
$error: Object
$formatters: Array[0]
$invalid: false
$modelValue: “1984”
$name: “YearCompleted”
$parsers: Array[0]
$pristine: true
$render: function render()
{ $setPristine: function ()
{ $setValidity: function (validationErrorKey, isValid)
{ $setViewValue: function (value)
{ $valid: true $viewChangeListeners: Array[0]
$viewValue: “1984”

Despite the <option value=”0″>2013</option>  not being the value=”” we may intuitively KNOW should be present (via standard HTML processing,)  the 2-way binding correct delivers the correctly selected value upon submit.An astute developer should rightly note my example’s values and text are the same :

<option value=2013>2013</option>

So I ran a quick test in which I changed the JSON populating the target select tag

$scope.yearObject = function (year) {
  return {
    value: 'Pass Me! Pass Me!'+year ,
    text : ''+year

Notice for the “value : ” JSON element I added:

'Pass Me! Pass Me!'+year ,

GIVEN: none of the above code populating the SELECT tag was modified

RESULT: refreshing browser, choosing year 2001:

Despite choosing ‘2001’, it still shows ‘2013’ selected.

We will see this is an auto-magical mind bender at this point.

I Click [SUBMIT] and the Chrome DevConsole reveals to me the submitted values (via 2 way binding) are the following:

$valid: true
YearCompleted: Constructor
$dirty: true
$error: Object
$formatters: Array[0]
$invalid: false
$modelValue: "Pass Me! Pass Me!2001"
$name: "YearCompleted"
$parsers: Array[0]
$pristine: false
$render: function render() {
$setPristine: function () {
$setValidity: function (validationErrorKey, isValid) {
$setViewValue: function (value) {
$valid: true
$viewChangeListeners: Array[0]
$viewValue: "Pass Me! Pass Me!2001"

Intuitively any Web Developer will expect the “Value” property of an <Option> tag to get picked up and passed to the 2-way binding (causing us to see the list Id’s in the
“value” property as a problem.)  But (beyond the scope of my research tonight) Angular is tracking the values elsewhere, so upon submit, the appropriate value  {probably keyed to the Id’ values} is bound to the variable/object.  This is why I subtitled this blog post Don’t Trust Your Eyes.

Hopefully this will be found helpful to those who initially have this same question as you start working with Angular.  Happy Coding!