oasp / oasp4js

OASP4JS deprecated repository
Apache License 2.0
9 stars 161 forks source link

After login no content is available #69

Closed ksola closed 8 years ago

ksola commented 8 years ago

In the sample application I logging as waiter and no tables are available. image The same happen when the user is logged into cook image

hohwille commented 8 years ago

The debugger seems to reveal that the content has been received from the server. Did you observe this problem on the latest code from the develop branch when locally starting with "gulp serve"?

dumbNickname commented 8 years ago

I have just checked the application from commit # 7db90439b52273814987cb13c0a9c6045fee3623 (currently the head of development branch) and the tables are being displayed properly in my local environment. I can already say that you are using development branch as Error Log is present in the navigation bar. I will try to clean my env and reproduce your problem. I will let you know if I face similar problems.

ksola commented 8 years ago

Yes, I have checked it on the latest code from develop branch when starting with "gulp serve"

dumbNickname commented 8 years ago

I have asked @ksola to check if application works properly when oasp4j server is taken from stable master branch (instead of development) as I have also faced some problems with websockets when using server from development branch. Now we wait for some (hopefully) good news :P

MarcoRose commented 8 years ago

Norbert Klein reportet the same with his local installation, but definitely saw the data being transferred on the network to the browser.

dumbNickname commented 8 years ago

Problem should be solved by https://github.com/oasp/oasp4js/pull/71. I would kindly ask one of the admins to have a look at that pull request and merge it if everything is fine (btw. some other pull requests are hanging). My write access to the main repository is missing for some reason, so I cannot do it on my own : )

tomaszwawrzyniakit commented 8 years ago

I also had this problem. After the merger with #71 everything works fine.

maybeec commented 8 years ago

will be fixed with #79 without reverting to instable dependency resolution.

jkokoszk commented 8 years ago

Fixed with PR #71