You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking to create a generic JavaEE to Quarkus 2 composite recipe who's primary purpose would be to move off EJBs. Planning on incrementally contributing to various parts of the upgrade. Will start with Adding Quarkus dependencies, removing JEE dependencies and converting Stateless, Stateful and Singleton EJBs to reasonable defaults on CDI. Eventually planning on upgrading Message Driven Beans to Camel Quarkus JMS/ActiveMQ, EJB Schedules to Quarkus Scheduler
What precondition(s) should be checked before applying this recipe?
That it is in-fact a JavaEE (Not JakartaEE) application to begin with
Describe the situation before applying the recipe
Working JavaEE application
Describe the situation after applying the recipe
Ideally, a fully transformed and working Quarkus 2 application
What problem are you trying to solve?
Looking to create a generic JavaEE to Quarkus 2 composite recipe who's primary purpose would be to move off EJBs. Planning on incrementally contributing to various parts of the upgrade. Will start with Adding Quarkus dependencies, removing JEE dependencies and converting Stateless, Stateful and Singleton EJBs to reasonable defaults on CDI. Eventually planning on upgrading Message Driven Beans to Camel Quarkus JMS/ActiveMQ, EJB Schedules to Quarkus Scheduler
What precondition(s) should be checked before applying this recipe?
That it is in-fact a JavaEE (Not JakartaEE) application to begin with
Describe the situation before applying the recipe
Working JavaEE application
Describe the situation after applying the recipe
Ideally, a fully transformed and working Quarkus 2 application
Are you interested in contributing this recipe to OpenRewrite?
Yes. Would be looking for feedback on best practices. I would like to stick to as many Declarative recipes as possible.
The text was updated successfully, but these errors were encountered: