Trying to setup an app with JHipster. Every tutorials I follow I have errors and failures.
Whatever options I select I got errors on my project.
Following the JHipster MiniBook procedure I have error like this on my IDE at start:
http://imgur.com/bWdek5W
And when I follow the directives to page 24 and try to run
./gradlew bootRun
I got a build failed: http://imgur.com/jFeJEQ6
I don't know what I'm doing wrong. I follow step by step the book, or other tutorials. Something must be wrong configured on my computer.
Any idea ?
Just looking at the error messages which are shown:
On the first screenshot you have configured your IDE to use Java 1.6 source code. JHipster is using Java 1.8, so the lambda expressions (which are new in Java 1.8) cannot be compiled.
On the second screenshot you have configured JHipster to use an external database. But you have not followed the documentation, which tells you to configure that external database in your application-dev.yml configuration file (and to start the database, of course!)
Related
I am trying to write a custom plugin for hawtio 2.x.
The first step that I tried building the entire project (https://github.com/hawtio/hawtio) as instructed in https://github.com/hawtio/hawtio/blob/master/BUILDING.md
Later, I tried the example (springboot sample) located at https://github.com/hawtio/hawtio/tree/master/examples/springboot
The example seems to run fine, except for the fact that I do not see a trace of the sample plugin written in this application (https://github.com/hawtio/hawtio/blob/master/examples/springboot/src/main/webapp/app/sample-plugin/js/sample-plugin.js)
Right now, I am not trying to do fancy stuffs. I am simply trying to run this sample application and see how the plugin works.
Below is the screenshot of the web console. I have also checked in the browser console. I do not see any traces of the initialization of this plugin.
Am I missing something specific?
Using this official Azure tutorial, I was able to perform all the steps until the step Browse to the app where when I browse to the app using http://myNodeJsTestApp.azurewebsites.net I get the following error:
The page cannot be displayed because an internal server error has occurred.
Please note that using same URL that tutorial asks us to use in step Set Node.js runtime of the tutorial, I was able to successfully display the exact same screen shown in that section. So the error is occurring after I got to the step Browse to the app further down. I'm using NodeJS version 8.12.0.
If you follow exactly the steps and don't modify the sample code, the only fault causing Internal server error is the node version 8.12.0.
Azure server doesn't install Node.js of all existing versions, go https://yourwebappname.scm.azurewebsites.net/api/diagnostics/runtime to check available ones.
I recommend to use 8.11.1 LTS version as the tutorial suggests, or you can choose 10.6.0 the latest on Azure.
I am implementing SignalR using dotnet core on visual studio code
on Linux debian ,and following this tutorial (working at the time of posting).
Inside the startup class I got this error message.
According to this article CookiePolicyOptions class does contain the property CheckConsentNeeded which is used to check consent policy.
I am unable to solve this please help.
looked for couple of hours, on how to solve that, but no luck.
I am using VS 2017 preview edition, and trying to open ASP.NET core 2.0 web application, that uses Angular template
when i open the site (f5 or ctrl-f5), the web-browser getting opened with the message
Cannot GET /
I don't know what causing that and how to fix that, tried to clean/rebuild/restart VS/change project port number/restart the computer, what else can I do to solve that?
Depending on what error you have in the client application, the server might not start at all. Local errors like undeclared locals are seldom a problem.
Usually, the web server does not start when a dependency of the module marked as bootstrap is missing, like, for example `entryComponents'.
Another thing that can cause the boostrap to fail, is a missing file: in this case you should have a look at templateUrl and styleUrls.
Manually compiling via ng build (or better ng build --prod) will point you to the offending code.
docdokuplm
Hi !
Just checking out your PLM, looks great! I followed your instructions:
https://github.com/docdoku/docdoku-plm/wiki/Installation-Guide
I used the nightly build.
After uploading the ear file and then using http://localhost:8080 I see the Payara server page. Was there something else I need todo or where do I start to troubleshoot? Thoughts?
Thank you!
The page displayed at 8080 is the default landing page. If you have deployed the DocDokuPLM application and configured the settings detailed within the instructions, you can open the application through Payara Server. Go to Applications -> DocDokuPLM -> Launch, and you'll get a series of links which should help you troubleshoot.
If you can't see any, run through the installation procedure again to ensure that you haven't missed a step - it seems like there's a few steps which must be configured exactly correctly for the application to work.
According to this GitHub issue, this seems like a bug with DocDokuPLM. As with most software, nightly builds are inherently risky. Looking at the source, though, it seems that the code changes fairly rarely, so you might try with the previous version of Payara Server (173), though the stack traces in the GitHub issue don't look to me like an issue with Payara.
The backend server and the UI are two separated components.
If you want to install the User Interface you have to go there :
https://github.com/docdoku/docdoku-web-front
The project which you have deployed is just for backend,inorder to interact with UI just clone the web-client from this repo https://github.com/docdoku/docdoku-web-front and in command prompt use this command npm run dev then you can use this project, make sure the port number which is mentioned in app/webapp.properties.json of web-client project is same as you have given in server-config.
Read https://github.com/docdoku/docdoku-web-front/wiki/Development-Guide for more details