I have a question about RAD & WAS Spring MVC development. So that we have a project in SVN that was created by me in STS (eclipse), but some of our team members can't retrieve & run this Spring MVC project on their RAD (ibm tool) IDE on WebSphere Application Server 7. It requires to create an EAR to run it on WAS, but in this case there're 2 projects in project explorer; EAR project & the normal one... the normal is almost an empty project, but everything from SVN is kept under EAR project. But they can't simply access index.jsp file from WebContent folder when they try to run EAR project on WAS, it says "Failed to find resource /index.jsp".
Any suggestions?
When work Spring projects over RAD we do the following approach:
We create a Dynamic Web project that contains all our Java Classes, JSP's, Spring files and some libraries that are inherent to the project. This project can be exported to a WAR and executed in containers like Apache Tomcat with no problem.
The we create an Enterprise Application Project that contains a Web Module reference to our Spring project, so we can run our application over IBM WAS as an EAR (although, WAS can work with WAR's too). This project only contains some configurations files and upper-level libraries.
Your Spring project should be imported in RAD's workspace as a Dynamic Web Project, and the EAR project must be created by the guys that uses RAD for development (an uploaded to SVN if you need it). If your "normal" -i.e Dynamic Web Project- is empty, you should check that the uploaded files are OK and the checkout process was normal.
Can you access the other resources besides index.jsp?
You got to narrow down things?
What is the context root for your web application? Is it "/"?
Post in additional information before folks can assist you
HTH
Manglu
Related
I'm building a selection of servers with .Net core 1.1 that are grouped together in an environment and I use an ARM template to create the various Azure resources I need. Currently however I have to manually deploy the actual servers, rather than having ARM deploy the artefacts for me as I'd like.
The instructions here don't work for netcore apps, but it feels like with the move to msbuild for netcore 1.1 I should be able to do this.
I've tried searching the quickstart ARM template repository, but can't find anything relevant.
The biggest stumbling block seems to be that "Web Deploy for Web Apps" needs a zip file, but dotnet.exe doesn't produce one.
you can zip the output of "dotnet publish" and use this .zip file for the deployment.
Make sure there is no root folder in the .zip. For example:
publish.zip
- bunch of .dll files
- wwwroot
- Views
...
I hope this will help you,
KirK
This is not as straight forward as I had hoped.
I created a Web Site project on my development machine using the Visual Studio C# template for a WebSite Project. (Visual studio 2010 .net 4.0). The project name is C:\Nova5\WebSite3. It consists solely of:
the Bin subdirectory
Nova.svc file
web.config file
It has been tested to run correctly by:
Setting the website as the startup project, then
Run Debug-->Start Debugging
When tested, the NovaDataService information page is correctly displayed. It also correctly works when used through my client project.
I followed the recommended procedure described at
Walkthrough: Converting a Web Site Project to a Web Application Project in Visual Studio to covert the Web Site to a Web Application.
I now have the following problems and/or difficulties:
If I use the recommended procedure for testing the web site:
-- File | Open | Web Site
-- Build Web Site -- Start Debugging
I get the Error: The type 'Nova5WCFServiceLibrary.NovaDataService', provided as the Service attribute value in the ServiceHost directive, or provided in
the configuration element system.serviceModel/serviceHostingEnvironment/serviceActivations could not be found.
Since, I think, the WebSite does work, I skipped this error and moved on to the next part of the article. The next issue (?) is there is no App_Code file in the WebSite. Is this necessary? If it is necessary, how should I create it? Or do I need to create another WebSite project from its template just to have it?
I did not copy the Nova.svc nor the web.config from the WebSite to the Web Application as none of the references I read indicated to do so. Should I copy these files to the Web Application as well?
I now used the "Convert to Web Application" on the Web Application project and recompiled the solution. Everybody is happy. No errors reported. So how do I now test the Web Application project on my development machine (which also has the client application) ?
TIA
I am deploying a spring-mvc application which uses JPA to access MySQL database. Access information is stored in persistence.xml, while creating a deployment war file I would like to replace developer persistence with the production one.
I tried to copy the production xml directly into the deployment folder (intellij settings), but it has no effect a dev. copy is always deployed.
How do I configure IDE to do that?
If your project is mavenised, then you can use the maven-war-plugin or maven-resources-plugin to customise the resources used to build the war, and the ide should honour these plugins.
I am creating a javascript webApp and i deploy it using GruntJS. this web app will be deployed in an ASP.NET MVC Web Service. I want to add the dist folder (and any files created by grunt inside the folder) programmatically inside the visual studio project, so when I build and deploy the web service I can navigate to this folder. Hope I was clear!
Yes you can. Grunt is completely independent of IDEs and texteditors and is a really helpful tool for all kinds of web development in any editor.
Grunt is described as “a node based javascript task runner with which you can automate tasks like minification, compilation, unit testing, linting and more”. You can use it for example when you do not like to be dependent on an asp.net web server doing minification and bundling for you, or you simply like to be able to use tools that are not (yet) supported by the asp.net/Visual Studio ecosystem.
Here is all you need: http://joeriks.com/2013/08/06/can-i-benefit-from-grunt-for-my-visual-studio-based-web-development/
Hope this helps!
Try to tweak WebDeploy settings in your MSBuild file (*.csproj?) so it would include files from the dist folder into your web application during publishing.
The following tutorial should be a good starting point how to do it:
http://www.asp.net/mvc/tutorials/deployment/visual-studio-web-deployment/deploying-extra-files
Also check ASP.NET Solution Template on Visual Studio Gallery
I am looking for the most straight forward way to automate the deploy of an MVC 3 application. There is a wealth of information on Stack Overflow already, but much of it seems to be old, and I am not sure what is still relevant to MVC 3.
Here is what I am trying to achieve:
Publish MVC application
Zip files
Copy zip to remote location
It is the “Publish” part of this I am having the most trouble with. Here are my main points of confusion:
How can an automated build be initiated for an MVC 3 app? Do we need to use the AspNetComiler MSBuild Task? I have seen an example of this uses in conjunction with a CSC Task. Are both really needed?
There is a “Build Deployment Package” option in Visual Studio. Can this be initiated with MSBuild? Should this be used instead?
Web Deployment Projects: where do these fit into the picture?
Thanks for any help
I am by far not specialist in application deployment so there might be better ways but here's what I do.
I use Web Deployment Projects to precompile my ASP.NET MVC 3 application
I feed the result of this project to a Setup and Deployment Project
I wrote a custom assembly which is applied to this Setup and Deplyment Project as an Install step and which based on the target IIS version creates App Pool and Virtual Directories.
I ship an MSI to the team responsible for deploying the application. All they need to do is to schedule a task which does an msiexec /u myapp.msi and then msiexec /i myapp.msi.
Remark : in my case all builds are automated in a continuous integration fashion with a Team Foundation Server Build but if you don't have a build server you could also build it manually by running the setup and deployment project which spits an MSI.