I am planning to migrate to the Struts 2 with the Struts 1 code base. I am not getting any good source to proceed on this migration. Could you please help on this approach?
S1 with S2 it will overkill. Both frameworks are complicated, so the maintenance costs increase twice or more time. So, the strategy is to migrate completely to S2.
Both frameworks are implemented MVC pattern. Divide the application on three parts that should migrate separately: Model, Controller, and View. The order is not important, but logically is implied to follow the MCV order. The Model you'd probably not change, the Controller part requires to rewrite the configuration, the View is most difficult part, you have to rewrite S1 tags to S2 tags.
Migrating Struts 1.x to Struts 2.x:
You can use Struts1 actions under the struts1 plugin. Also consider to read the existing migration guide, solutions, and strategy that might help you in the migration process. Mapping actions could be easily done via convention plugin. You can't use Struts1 JSP tags with Struts2, but you can use it in Struts1 if you are running both frameworks with the same application.
Integrate Struts with Spring:
The right and up-to-date approach is to migrate to Struts2. If you
concern the things why Struts is deprecated, you might read this
article: Is Struts Dead? Part III: I can't kill Struts (Struts is
Deprecated) David Geary.
InfoQ Migration Guide:
Migrating Struts Apps to Struts 2 - Part I
Migrating to Struts 2 - Part II
Migrating to Struts 2 - Part III
Related
I am planning to migrate to the Struts 2 with the Struts 1 code base. I am not getting any good source to proceed on this migration. Could you please help on this approach?
S1 with S2 it will overkill. Both frameworks are complicated, so the maintenance costs increase twice or more time. So, the strategy is to migrate completely to S2.
Both frameworks are implemented MVC pattern. Divide the application on three parts that should migrate separately: Model, Controller, and View. The order is not important, but logically is implied to follow the MCV order. The Model you'd probably not change, the Controller part requires to rewrite the configuration, the View is most difficult part, you have to rewrite S1 tags to S2 tags.
Migrating Struts 1.x to Struts 2.x:
You can use Struts1 actions under the struts1 plugin. Also consider to read the existing migration guide, solutions, and strategy that might help you in the migration process. Mapping actions could be easily done via convention plugin. You can't use Struts1 JSP tags with Struts2, but you can use it in Struts1 if you are running both frameworks with the same application.
Integrate Struts with Spring:
The right and up-to-date approach is to migrate to Struts2. If you
concern the things why Struts is deprecated, you might read this
article: Is Struts Dead? Part III: I can't kill Struts (Struts is
Deprecated) David Geary.
InfoQ Migration Guide:
Migrating Struts Apps to Struts 2 - Part I
Migrating to Struts 2 - Part II
Migrating to Struts 2 - Part III
I am planning to migrate to the Struts 2 with the Struts 1 code base. I am not getting any good source to proceed on this migration. Could you please help on this approach?
S1 with S2 it will overkill. Both frameworks are complicated, so the maintenance costs increase twice or more time. So, the strategy is to migrate completely to S2.
Both frameworks are implemented MVC pattern. Divide the application on three parts that should migrate separately: Model, Controller, and View. The order is not important, but logically is implied to follow the MCV order. The Model you'd probably not change, the Controller part requires to rewrite the configuration, the View is most difficult part, you have to rewrite S1 tags to S2 tags.
Migrating Struts 1.x to Struts 2.x:
You can use Struts1 actions under the struts1 plugin. Also consider to read the existing migration guide, solutions, and strategy that might help you in the migration process. Mapping actions could be easily done via convention plugin. You can't use Struts1 JSP tags with Struts2, but you can use it in Struts1 if you are running both frameworks with the same application.
Integrate Struts with Spring:
The right and up-to-date approach is to migrate to Struts2. If you
concern the things why Struts is deprecated, you might read this
article: Is Struts Dead? Part III: I can't kill Struts (Struts is
Deprecated) David Geary.
InfoQ Migration Guide:
Migrating Struts Apps to Struts 2 - Part I
Migrating to Struts 2 - Part II
Migrating to Struts 2 - Part III
One of the things I love about Grails is the ability to generate controllers and scaffolded views.
I've decided to build a new project without Grails, on Java using spring-boot. I was wondering if there was some sort of tool that will do the equivalent of the Grails 'generate-all' command that is something that will generate the controllers and views from my model so I can get a head start with my development.
I'd preferably want to create my views with thymeleaf, although I know that might be asking a bit much.
For the last few years I have been a Symfony developer and one of the things I enjoy the most is the fact that I don't have to write/maintain entities by hand.
Through Doctrine (the integrated ORM) I can extract the table metadata and relations through
php app/console doctrine:mapping:import SomeBundle yaml
And then I can generate the ORM entity classes
php app/console generate:doctrine:entities SomeBundle
And I'm friggin' done.
Need to migrate?, no problem. Use this command to create a migration:
doctrine:migrations:diff
And the following to migrate to it:
doctrine:migrations:migrate
For Grails, it seems that there is no straight forward way, unless I go and download the Hibernate tools and a tool like Liquibase.
There seem to be a couple of plugins that did this, but the one for reverse engineering from a database does not seem supported for Grails 3 (db-reverse-engineer) and the one for migrations I tried, but does not seem stable enough (database-migration).
Am I just looking in the wrong place?, if not, how do you as a professional Grails developer solve these needs?
No there is not a straight forward way to make a "round-trip" as you describe in Grails 3.x.
Most plugins aren't going to be 3.x ready yet. 3.x is still quite new.
That said, the reverse engineering plugin isn't designed to be a fully automated one-shot handles everything type of plugin. It's suppose to be a running start that you take the last bit by hand.
The migration plugin on the other hand is fully production ready and very stable in 2.x.
I'm working on a PHP project and evaluating Symfony 2 + Doctrine ORM. Coming back to PHP from Ruby on Rails, I'm wondering if there are parallels for the acts_as-style ActiveRecord plugins that are available all over GitHub for common behaviours in Rails.
Doctrine itself only has a few standard extensions for Translatable, Tree, Sluggable, and Timestampable. I was able to find a few other items on GitHub.
I'm looking for things like sortable lists, some implementation of soft-delete, state machines, file attachments (images), and so on. Is anything similar available or is it a roll-your-own ecosystem? Where can I find more resources?
You can look at https://github.com/l3pp4rd/DoctrineExtensions, there's some awesome extensions!