Our project uses the Grails stack with Grails 3.1.5, GORM and Groovy. We are trying to move away from Grails and just use Spring-Boot. We have not settled yet if we want to get rid of GORM and Groovy as well.
Our reasons are:
a lot of trouble in upgrading to Grails 3.2.2
lack of up-to-date plugins
bugs in grails and it's plugins
no community
bad documentation
mostly figuring out the magic of Grails takes up more time than writing everything on your own
Does anyone have any experience or suggestions on how to deal with a migration like this?
Thanks :)
In any case, even though you seem to have written your question in a way that is likely to create more discussion than help you out, here's my 2 cents, FWIW:
You're already in a spring boot application! You can leave all the annoying grails-y and groovy-y things behind and code your app in java, with all the boot-y annotations you want.
This is not to be facetious! It is a good methodology to slowly extract your grails artifacts and replace them, with spring-boot components, without having to break your app.
So here, from a non-existing community member of grails, good luck.
UPDATE:
After answering your question, I thought back to all the times a grails developer answered a question for me, every time I spent hours through the rabbit hole of the grails web sites, reading mind-blowing documentation and tutorials, and I thought I owed it to all these people doing this for FREE, to come back and defend them.
The grails and groovy communities are one of the friendliest I have ever come accross. You should bother to go to a conference or visit their slack community.
Some links to grails' outstanding documentation sites:
http://grails.org/documentation.html
Grails guides:
http://guides.grails.org/
Either you haven't looked or you have to tell me what your standard is.
Related
I am a completely fresher for Spring Boot. I had learn to perform Basic CRUD operations using REST API. That basic knowledge is enough to working with Spring Boot Project. Can I able to work with that?
No one is technically perfect!
Every day we are exploring new things and implement new solutions as per the new business requirements. The developer should possess a good set of problem-solving skills. That’s because it’s common for developers to come across multiple programming problems while building just about any solution.
If your lead assigned a task to you explore quarkus and implement a simple CRUD operation using go language what you will do?
"I don't know golang", Is this your answer?
Qualities of a good junior software programmer
Learn new things daily which must be useful to the growth of the company, your team and you.
Problem Solving and Logical Thinking
Written and Verbal Communication
Teamwork
Interpersonal skills
Time management
How do I search for answers from StackOverflow like a PRO? This is a very important skill set, Really, I am not joking.
Health - Health(Physical/Mental) is an important asset, don't take official things personally. Manage stress etc...
Coming to technical side
It would be good if you know at least one programming language, in your case java is fine. But if you have the listed skill sets you can learn anything very easily.
Regarding Spring boot
Do you want to become an expert in the Spring framework? Work with one big project, whatever domain.
Refer - https://www.baeldung.com/
Once you become pro - Refer - https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/
As a starter this is fine, but if your application is going to face real customers/users and want to evolve your application over time, then you would need to consider concepts like below
Login/logout security with Spring Security (if stateless then JWT is a good choice)
Evolving code and database with versions of your software (can use Liquibase to evolve and maintain DB changes ).
Handling exceptions as Aspects from Spring.
Having coded business errors so your team can resolve them and classify them accordingly.
My first post.
I have experience of basic java servlet and jsp and have got my webpage implemented in tomcat7.
Regarding Websocket, I am finding difficult to build understanding of how to implement it, i want to use tomcat8 implementation of websocket api and uplift my webpage (jsp, java, jquery, tomcat7) to use the websocket features, have not been able to find the the tutorial that can guide me through, something like hello world example. any pointers (sample codes, tutorials)?
have tried to understand tomcat8 examples but not understanding them at all
You need to understand that you don't just "add" WebSocket to an existing web application.. to make it faster, better, cheaper, more scalable, etc. Instead, you have to completely re-architect the web-layer of the application to take advantage of its capabilities.
I suggest that you first read a lot about WebSocket and what the whole idea is before you try to write any code, using Tomcat or any other WebSocket-capable server.
Nick Williams has a forthcoming book that appears to cover everything in the web application world, and as I understand it, will have a great deal of information about WebSocket-based code. You will unfortunately have to wait until March 2013 (at least) to use that particular book.
I'm sure there are similar books available, or even online tutorials to help get you started using WebSocket. Just be aware that switching to WebSocket isn't some simple configuration option: it's a very disruptive change to any existing web application.
I realize that Joomla supports LDAP but I don't want my entire database moved over to the Joomla database (for obvious reasons). I was hoping to implement SSO to maybe prevent this from happening. Is this possible? I can't find any good information on it online, after a couple of days of googling and reading different articles. I think maybe JAuthTools might be able to help me do it but even with the wiki surrounding that extension I can't find any good information on it's SSO support. If anyone knows how to do this that would be great. The users are currently stored in Active Directory.
JAuthTools as far as I'm aware isn't actively maintained anymore, and was for Joomla! 1.5.
The last SSO integration we did was with JMapMyLDAP and it seemed to work pretty well and it's last update was less than a month ago.
I completed a new MVC web application and my boss asked me to create a new version for a new custumer. Same web application but differente CSS and two new modules (for module I mean a new page used by user to interact with DB). It's not a big deal and quite easy to do, just duplicate the project in my Eclipse and modify it. Two days work and project completed. Well done, all happy but not me.
I was thinking to wordpress, it's really customizable, just create a new template and plugin and activate it. I'd like to do somenthing similar to reduce the new version deploy and the code mainteneance. My question is, how can I do something similar with Spring? or better, is it possible to create a new module and deploy it for a web application? is the Spring dynamic the right option for a MVC Spring application?
thanks,
Andrea
I don't think your approach is correct. You need to discuss with your manager whether this situation is likely to repeat. Because to me it looks like it might.
Let's imagine a scenario: you have a number of copies of your app with some minor enhancements or changes between them. A month later one customer reports about a bug that's really nasty and has to be fixed in every of your app instances. Imagine your pain.
Why don't you approach it with multi-tenancy in mind?
Implement white-labelling, so that depending on the customer your application can get different looks;
Extend the backend, so that customers don't ever see each other's data
Implement configurable features, so that one customer doesn't see extended features that your boss sold to another customer. When he does sell them - it's going to be a matter of toggling a few flags in the database/configs.
Don't want to support multi-tenancy or the product is physically deployed on different (customer) servers? Doesn't matter! If you find a bug, you fix it once and redeploy the jar-file to all the affected systems.
Granted, the above isn't two days of work, but down the road this approach may save a lot more.
As to your question, Spring allows you to customize its looks via changeable styles and layouts. I suggest you to create a sample web app with Spring Roo to see how it's done. However, if I were you I would still aim to have a shared codebase between the projects at the very least.
Have been using Savon for my webservice stuff so far, but need to talk to a more "secure" service now, needing WS Addressing and WS Security Extensions.
Have started to extend this fork of Savon to handle it, but then found WSO2 WSF/Ruby - so wondering if anyone has any experience of it, pros/cons etc. That is, is it worth my switching to it? I cant see much out there about it, besides on their own site - their forums seem awfully quiet, which does not bode well.
Currently dev on OSX/Snow Leopard, deploying on CentOS.
Thanks in advance,
Chris
It does not seem so (from the lack of replies...)