I have looked around for a beginners tutorial to start creating a Spring app using the STS IDE. There seems to be nothing around, its either hand build it or the tutorial doesn't work and is many versions off the current IDE. I am very new to Spring and need to get going on this. Any links you can throw my way I would appreciate it.
STS provides Template Projects. Open File -> New -> Spring Template Project.
Now you can choose the type of application you want to create. If you want to create a web application choose Spring MVC Project. This will create a complete project with a controller, a view, maven integration and everything else you need. You can immediately run this application in tc Server.
I think the green beans series from springsource is a good start: http://blog.springsource.com/2010/11/09/green-beans-putting-the-spring-in-your-step-and-application/
Integrated in the IDE is also a task focused tutorial to learn basic steps inside the ide ( help->task focused tutorials...
I may be late, but I think this tutorial might be helpful (for those who are looking for sts tutorial like me):
http://www.giantflyingsaucer.com/blog/?p=2373
UPD:
and this one is good:
http://viralpatel.net/blogs/tutorial-spring-3-mvc-introduction-spring-mvc-framework/
Related
I chanced on Piral Framework for implementing micro-frontends and I wanted to implement it in my project.
However, my application comes as a Blazor wasm project and my aim is to use this current project as my app shell.
Is there any example on how I could implement that?
I can't really find my way around the documentation too.
Kindly note that I am a beginner. Thanks in advance.
For the app shell you cannot use Blazor.WASM. You can, however, make your app shell really lightweight (i.e., don't put almost anything in there) and have all the necessary layout parts defined in Blazor.
The idea boils down to the sample given at:
https://github.com/piral-samples/piral-distributed-layout
Now instead of having pilet(s) in React / Angular / ... you use Blazor.
For Blazor pilets (and extensions using Blazor) you can check out the documentation at the README of Piral.Blazor:
https://github.com/smapiot/Piral.Blazor/
Make sure to follow the instructions closely and use the right branch (named after the version of Blazor you are targeting).
After searching around on how to actually implement the concept of micro-frontends using Blazor WASM as my app shell, I still didn't find any solution which helped me. So I came up with a custom solution which I wrote about in a blog.
Basically, the solution makes use of the JS interop of Blazor as a medium of communicating between the other JS frameworks or libraries.
Kindly have a read: https://dev.to/xanderselorm/introduction-to-micro-frontends-using-net-blazor-wasm-part-1-lc9
I wanted to build a VB.net web application using MS Visual Studio 2015. Someone suggested me to create a Web API instead of MVC project if i'm also planning to create a mobile app later on. I may use angularjs in my project so controllers will surely be used, so what should i choose when creating the project in the first place?
Because when i created a web project: File=>New Project=>ASP.net Web Application=>Empty..there are no folders for Controllers, Model, etc. Do i have to create a Controller folder on my own?
Or should i do this: File=>New Project=>ASP.net Web Application=>Web API..? sorry if its a silly question. its just that i'm afraid that if i chose the wrong project now, it'll affect the development later on.
Answer to your question mainly depends on your choice and needs,
for example
In Case of an empty project as name defines you will have nothing else web.config.
Benefits of it:
here you can define, design your own structure. you can either make
it simple 3 tier or you can make it WEBAPI application. it's all up
to you.
however in the case of choosing Webapi template you will have a prebuilt structure which can help you out for initial understanding
https://docs.asp.net/en/latest/tutorials/first-web-api.html
benefits of it
You will get predefine template and structure.
you can utilize of webapi's which further isolate you backend logic from the frontend.
as you are also planning to create the mobile app. and using front end as angular, so in that case, webapi may come handy.
as the whole world is moving towards webapi, so i will recommend you to use it. please refer https://blogs.msdn.microsoft.com/martinkearn/2015/01/05/introduction-to-rest-and-net-web-api/
so down the line it all depend on you if you want to build you application for the stretch and take full control of it regarding structuring backend etc.. then go with empty else go with Microsoft pre-define template
Thanks,
Ajay Kotnala
Has there ever been a more confusing/difficult time to be a web developer using the Microsoft stack? That's not really my question... I know that the answer is a categorical no. :)
The single page app template that comes with VS 2013 is deplorable.
I've been working on building up a similar project template that uses Angular JS on the client, but I'm starting to spin my wheels a bit porting over the external (openId/oauth) login features.
I believe this is because of the lack of good, single-point-of-truth, and current documentation for Katana's auth/security bits and also because of how unreadable the client side code is in the S.P.A. template in visual studio 2013.
I know that I can get through it, but while I'm struggling with it, I'm wondering:
Are there any good community provided project templates or example code bases in existence that use .NET 4.5 (MVC5/Web Api 2), Angular JS, the new ASP.NET Identity stuff, and the Katana packages?
There's HotTowel.Angular, but it takes no stance on security. Besides, it's a Nuget package, which can't or shouldn't dictate as much as a proper project template can.
I agree with your observations. I have found the following setup that seems to meet your requirements and I think works very well (I don't have a template), I would suggest the following:
Create an empty WebApi2 project and adopt authentication/authorization depicted here
Use a regular index.html in the base directory as a launching point for your angular application. You can either maintain your client packages with nuget, npm, or bower.
Use whatever technique you like for organization of client code.
Personally, I would create 3 projects, One for client code, (mydomain.com) One for your api (api.mydomain.com) and one for your Model/Repository/Data Access layer.
update
Here is an open-source project that might be what you're looking for!
I want to build a demo app using SpringMVC as a backend and Flex as a fronend.
Can anyone please help me in this work.
My Questions:
1) Which tool I should use, where I can write code for both SpringMVC and Flex?
2) How to integrate this two different components?
3) I just want to build a Registration/Login demo. Please help me?
Note: I want to use free tools, plugins etc only
You can use Eclipse for both - just download the Flashbuilder plugin to allow you to develop Flex. Have a look at something like BlazeDS, which will allow you to call the spring MVC classes from Flex.
You may use Powerflasher's FDT, it is Eclipse based, last time I checked it has a free edition. Like TrueDub says, BlazeDS is worth looking at, and there is also Spring BlazeDS integration you can take advantage too.
I need to work on Action Script project. I need to generate a swiff file by creating an action script project using flex sdk . I dont know how to start this thing. I have installed flex 4.5.1 and I know how to create flex project. Can u please suggest me some tutorials for working with action script project using flex sdk.
Thanks.....
well, there are lots of free tutorials in the internet, for example on youtube. you wouldn't be able to really learn actionscript but you will understand basics, so learning will be much easier. here, take a look. also, i can strongly recommend lynda's training courses -- yes, you have to pay for them, but they've got free trial membership. also, take a look at google, you know... you don't expect someone actually to teach you personally, don't you?...