I found another issue, this one could be related with yours. If the UI has not being used for a while, it will redirects you to the login page automatically. Well with AngularJS apps, that is not going to be the case, because everything is Ajax behind the scenes. That means, you'll get a 401 and weird things are going to happen.

I think we should intersect all the calls through $http and if a 401 was received, redirect the whole page to the login page (like it works for "simple" pages).

I'm wondering if you disable the auto-logout in web.xml, you're still seeing the problem; I mean, uncomment the following section:

web.xml

Either way, for "creating a new requisition" I'm not able to reproduce the problem.

Hey Jesse, I'm not sure if the following is related or not, but I found a serious problem with the Requisitions ReST API in 17:

When we are back to the office, we can take a look together your issue (even knowing that I couldn't reproduce it), to see what's happening on your system, or if you're experiencing the new issue I found.

Also, the current workflow of the NewUI is pretty much the same as the old UI but faster. Besides being faster, the big improvement is, managing very-large requisitions without issues. But, I think it can be improved, like adding intelligent validations prior sending the changes back to OpenNMS, or improve workflows. I'll appreciate if we can take a look at this together.

I think it is hard to fix something that I've tried hard to reproduce without success.

Here is another successful test. This time, nothing to do with my computer.

I've used Ronny's Vagrant/Chef recipe from:

https://github.com/opennms-forge/vagrant-opennms

Then, I changed it to use latest 17 snapshot:

It works!

So, you have either an issue with your machine (or /etc/hosts, or something else), your browser or a combination of both.

I will appreciate more details about your testing environment.

Here is mine:

MacOS Running Oracle Java 8u60, and compiled latest develop like this:

./clean.pl && ./compile.pl && ./assemple.pl -p fulldir

I've cerated a clean database for my tests (running PostgreSQL 9.4.4 on my Mac), and the requisitions UI works fine. I did the following:

For each Browser/OS combination:

a) Go to Admin
b) Open the New Requisitions UI.
c) Add a requisition.
d) Verify the requisition is created (just by looking at the UI).
e) Add a node to the requisition that was created on (d) with a valid IP.
f) Synchronize the requisition
g) Verify the DB and the imports directory
h) Go to Admin -> New Requisitions UI again then: delete all the nodes, then synchronize, then delete the requisition
i) Verify that the DB is clean, and the requisitions file doesn't exist.

BTW, I tested that with Chrome 45 (MacOS, Windows10), FireFox 40 (MacOS, Windows10), Safari (MacOS) ..... It ALWAYS work as expected. I found some issues on Microsoft Edge, but that doesn't surprise me Of course, I always clear the full browser's cache before each attempt.

P.D. The smoke tests verify this whole process and it always work, so I think there is something wrong in your environment.

I'm still having the same issue with the latest build of develop.