You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Alexander Wagner <al...@inside-m2m.de> on 2014/07/25 15:12:32 UTC
TomEE OpenEJB IDE Support
Hello TomEE/OpenEJB-Comunity,
I would like to know which ways you prefer for developing
JEE-Applications with TomEE and maybe standalone OpenEJB Server in
combination with a good IDE-Support. The main question is about: use a
War-Project and be happy with the great Eclipse WTP Connector support
and do not waste time to try anything else like EARs or plain ejb-jars.
Maybe you could give a better answer with some background information
about our requirements and environments.
In our company we are using Eclipse for Java-Development. We are using
plain Tomcat for Web-Development (mainly JSF) and for now in some
projects already TomEE. Historically we have also server parts which are
running from a Java Main Method without any container. A plan might be
in the future to get also this servers to the JEE world. As a footnote:
we are most time project driven, so for now we have no real products
where we can put a lot of efforts in refactoring until everything is as
nice as it could.
In the projects where we used TomEE we created two or more
War-Applications to separate development and robustness of the different
parts of the whole system. For example we defined a portal.war, a
notification-service.war and reporting-service.war. Every
War-Apllication has its own Business and Persistency-Layer where only
the things are modeled which are needed e.g. JPA-EntityBeans. The portal
has naturally also a UI-Layer in this case a JSF. If there is some
inter-application communication needed the War-Applications talk over
some Remote-Interfaces and/or JMS with each other, depending on the use
cases.
Currently our big question is if the War-File approach for applications
without any UI-layer is the right one. It feels a little bit that this
is not the nature of War-Files;-) The other way we could imagine is to
create ejb-jars out of the notification- and reporting-service applications.
At this point our big question is the IDE Support. The Eclipse Support
for Tomcat/TomEE over the WTP-Connector is excellent, but it covers only
War-Projects. So I tried the OpenEJB Eclipse Plugin
(https://openejb.apache.org/openejb-eclipse-plugin.html). First of all,
it seems to work, but nevertheless it seems also a little bit outdated.
Does someone has some real experiences with it, especially with
debugging, workspace maven dependency resolution?
We have also some doubts about using EAR-Files, we could not imagine how
the development process should work, running only certain parts for
development in container for better startup time etc. And our real big
problem with it is, that we do not see any IDE-Support. Do you have some
other experiences in this field?
And maybe in the end, is this all about ideology and don't waste your
time for thinking about misusage of War-Applications!?
Thank you in advance for your answers!
Best regards,
Alexander Wagner
Re: TomEE OpenEJB IDE Support
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
About connectors: eclipse integration is surely a bit old and best one is
the wtp connector for wars only. Note that Intellij Idea has a tomee
connector supporting even ears and ejbmodules.
About wars or war: depend the lifecycle and the development team
responsability. If a single team and all wars redeployed together then use
a single one ;)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-07-25 15:12 GMT+02:00 Alexander Wagner <al...@inside-m2m.de>
:
> Hello TomEE/OpenEJB-Comunity,
>
> I would like to know which ways you prefer for developing JEE-Applications
> with TomEE and maybe standalone OpenEJB Server in combination with a good
> IDE-Support. The main question is about: use a War-Project and be happy
> with the great Eclipse WTP Connector support and do not waste time to try
> anything else like EARs or plain ejb-jars. Maybe you could give a better
> answer with some background information about our requirements and
> environments.
>
> In our company we are using Eclipse for Java-Development. We are using
> plain Tomcat for Web-Development (mainly JSF) and for now in some projects
> already TomEE. Historically we have also server parts which are running
> from a Java Main Method without any container. A plan might be in the
> future to get also this servers to the JEE world. As a footnote: we are
> most time project driven, so for now we have no real products where we can
> put a lot of efforts in refactoring until everything is as nice as it could.
>
> In the projects where we used TomEE we created two or more
> War-Applications to separate development and robustness of the different
> parts of the whole system. For example we defined a portal.war, a
> notification-service.war and reporting-service.war. Every War-Apllication
> has its own Business and Persistency-Layer where only the things are
> modeled which are needed e.g. JPA-EntityBeans. The portal has naturally
> also a UI-Layer in this case a JSF. If there is some inter-application
> communication needed the War-Applications talk over some Remote-Interfaces
> and/or JMS with each other, depending on the use cases.
>
> Currently our big question is if the War-File approach for applications
> without any UI-layer is the right one. It feels a little bit that this is
> not the nature of War-Files;-) The other way we could imagine is to create
> ejb-jars out of the notification- and reporting-service applications.
>
> At this point our big question is the IDE Support. The Eclipse Support for
> Tomcat/TomEE over the WTP-Connector is excellent, but it covers only
> War-Projects. So I tried the OpenEJB Eclipse Plugin (
> https://openejb.apache.org/openejb-eclipse-plugin.html). First of all, it
> seems to work, but nevertheless it seems also a little bit outdated. Does
> someone has some real experiences with it, especially with debugging,
> workspace maven dependency resolution?
>
> We have also some doubts about using EAR-Files, we could not imagine how
> the development process should work, running only certain parts for
> development in container for better startup time etc. And our real big
> problem with it is, that we do not see any IDE-Support. Do you have some
> other experiences in this field?
>
> And maybe in the end, is this all about ideology and don't waste your time
> for thinking about misusage of War-Applications!?
>
> Thank you in advance for your answers!
>
> Best regards,
> Alexander Wagner
>
>
Re: TomEE OpenEJB IDE Support
Posted by Alexander Wagner <al...@inside-m2m.de>.
Sorry I didn't mentioned that we use maven for the projects and also m2e
in Eclipse. Without theses tools the build process might be not so
comfortable.
The DCEVM is really great stuff, I used it already, too. I need to
install it again after a new eclipse installation. Sometimes I had the
felling that the debugger gets more often out of sync and didn't
recognized than any changes, but this might be only a personal feeling.
The m2e conntectors are a good advice, we are using mostly the ignore
feature of eclipse to exclude unsupported lifecycles:-D
So in the end we wouldn't be alone if we use war-files over ears or
ejb-jar. For the moment satisfying :-)
Am 25.07.2014 um 16:37 schrieb Anthony Fryer:
> Alexander Wagner wrote
>> At this point our big question is the IDE Support. The Eclipse Support
>> for Tomcat/TomEE over the WTP-Connector is excellent, but it covers only
>> War-Projects. So I tried the OpenEJB Eclipse Plugin
>> (https://openejb.apache.org/openejb-eclipse-plugin.html). First of all,
>> it seems to work, but nevertheless it seems also a little bit outdated.
>> Does someone has some real experiences with it, especially with
>> debugging, workspace maven dependency resolution?
>
> I use eclipse with tomEE almost everyday. It has taken time to get eclipse
> working well, but now for me it is a great tool for developing applications.
>
> Eclipse maven support, m2e, takes some time to get used to, but when you do
> and you work out which additional m2e plugins you need, you can get eclipse
> to perform automatic builds using the maven build plugins. An example of
> some m2e plugins i use are...
>
> m2e connector for jaxws
> m2e connector for OpenJPA
> m2e connector for XML Transform
>
> I decided ages ago that packaging my applications in war files instead of
> ears wasn't a big deal. I wanted to use tomEE from eclipse and use the
> eclipse wtp to automatically publish my war into tomee. I could repackage
> into ear files later if i want to deploy into a different container that
> doesn't support skinny ears (ie. wars).
>
> I also setup my servers configed in eclipse to use a Dynamic Code Evolution
> VM (DCEVM) so class changes are just deployed into a running tomee instance
> automatically and debugging can be performed immediately after a code change
> is made (no need to redeploy the app and restart tomee and no need to pay
> for jrebel). Some info about this can be found here...
>
> http://javainformed.blogspot.com.au/2014/01/jrebel-free-alternative.html
>
> So in summary
>
> * I have a multi module maven pom project (I have 23 projects in my eclipse
> workspace all pure maven projects, no eclipse specific info in the pom.xml
> files).
>
> * My projects are all built automatically by eclipse when a code change is
> made because i installed the necessary m2e plugins. This includes changes
> to wsdl files, xsd files and jpa entities.
>
> * The classes generated by the eclipse maven builder are automatically
> published to my tomee server by eclipse wtp.
>
> * DCEVM automatically loads those classes into an already running server.
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/TomEE-OpenEJB-IDE-Support-tp4670731p4670733.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Re: TomEE OpenEJB IDE Support
Posted by Anthony Fryer <ap...@hotmail.com>.
Alexander Wagner wrote
> At this point our big question is the IDE Support. The Eclipse Support
> for Tomcat/TomEE over the WTP-Connector is excellent, but it covers only
> War-Projects. So I tried the OpenEJB Eclipse Plugin
> (https://openejb.apache.org/openejb-eclipse-plugin.html). First of all,
> it seems to work, but nevertheless it seems also a little bit outdated.
> Does someone has some real experiences with it, especially with
> debugging, workspace maven dependency resolution?
I use eclipse with tomEE almost everyday. It has taken time to get eclipse
working well, but now for me it is a great tool for developing applications.
Eclipse maven support, m2e, takes some time to get used to, but when you do
and you work out which additional m2e plugins you need, you can get eclipse
to perform automatic builds using the maven build plugins. An example of
some m2e plugins i use are...
m2e connector for jaxws
m2e connector for OpenJPA
m2e connector for XML Transform
I decided ages ago that packaging my applications in war files instead of
ears wasn't a big deal. I wanted to use tomEE from eclipse and use the
eclipse wtp to automatically publish my war into tomee. I could repackage
into ear files later if i want to deploy into a different container that
doesn't support skinny ears (ie. wars).
I also setup my servers configed in eclipse to use a Dynamic Code Evolution
VM (DCEVM) so class changes are just deployed into a running tomee instance
automatically and debugging can be performed immediately after a code change
is made (no need to redeploy the app and restart tomee and no need to pay
for jrebel). Some info about this can be found here...
http://javainformed.blogspot.com.au/2014/01/jrebel-free-alternative.html
So in summary
* I have a multi module maven pom project (I have 23 projects in my eclipse
workspace all pure maven projects, no eclipse specific info in the pom.xml
files).
* My projects are all built automatically by eclipse when a code change is
made because i installed the necessary m2e plugins. This includes changes
to wsdl files, xsd files and jpa entities.
* The classes generated by the eclipse maven builder are automatically
published to my tomee server by eclipse wtp.
* DCEVM automatically loads those classes into an already running server.
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/TomEE-OpenEJB-IDE-Support-tp4670731p4670733.html
Sent from the TomEE Users mailing list archive at Nabble.com.