- This topic has 44 replies, 30 voices, and was last updated 17 years, 8 months ago by
.
-
Posts
-
It looks like EJB3 is the wave of the future. The annotation-driven design really simplifies the code and removes a lot of the barriers to developing the “J2EE way”.
As a side note, Seam shows a lot of promise in being a “Spring-killer” or at least some high-powered competition in the IOC space. It uses dependency injection to build on EJB3 and JSF/Facelets. Currently, MyEclipse allows me to do “alternative” enterprise development with Tapestry/Spring/Hibernate. It would be great if MyEclipse also supported a “standard alternative” stack with JSF/Seam/EJB3.
Eric
I herad of another initiative in this area named Dali (see http://www.eclipse.org/dali/). This is exactly the kind of thing that would help a lot. It does not seem to provide any software yet but it might be interesting to see if it can be integrated into MyEclipse.
It would be great if MyEclipse supported EJB 3.0 development. I have to use JBOSS Eclipse IDE for that right now.
EJB 3 is essential in our company.
I am personally very fond of Eclipse/MyEclipse but the lack of EJB3 features makes it difficult to sell it agaist other tools like Netbeans 5.5
The sooner we get it the better
Can you guys explain with some more specifics what kind of tooling you want to see? Do you want to see bean generation? Do you just need annotation support? etc.
We are looking at Dali as it is comming along very nicely and at some point will integrate it, last I heard from management is that they were reevaluating it’s progress as the first time we looked at it, it was too premature to integrate.
@support-rkalla wrote:
Can you guys explain with some more specifics what kind of tooling you want to see? Do you want to see bean generation? Do you just need annotation support? etc.
I think some wizards which make the bean with the default @annotations, the right includes will be great. Also a library package with the EJB3 stuff in it like you have for most things like jsf, ejb, struts etc. Also a @annotation helper so you do not have to go to a manual or webpage every time (ctrl-space).
A wizard for ejb-reference from ejb to ejb and from webproject to ejb would be helpfull.
Edwin
Since EJB3 spec is finalized and Jboss/Oracle Appservers have started support for EJB3.0, we feel the need for an IDE support from MyEclipse is very high priority. We use MyEclipse as our internal IDE, but since we have started developement of 3 projects based on EJB3 and to remove the proprietary Hibernate out of our solutions it would be of very immediate need for us. This forces us to run JBoss IDE and MyEclipse together where we are not able to make use of all the features of MyEclipse. I am seeing this trend happening in a lot of other projects as well. So we would certainly back the idea of supporting EJB3.0 in MyEclipse.
I would definitely backup the case for EJB 3.0 support in MyEclipse. And another really nice to have functionality would be a better web services support. The web services support in WTP is great and may be MyEclipse can do even better. Couldnt find anything great in the new release of WTP (1.5) though.
Rajnish
@support-rkalla wrote:
Can you guys explain with some more specifics what kind of tooling you want to see? Do you want to see bean generation? Do you just need annotation support? etc.
I’m looking more for project management, deployment, etc. With Java EE 5, the code and descriptors are relatively easy.
I’m quite attached to the current J2EE support, which asks when you create a project which spec you want to support, then manages the libraries, descriptors, deployments, etc. for you. At the very least, I would like to see existing Enterprise Java support brought up to the JEE 5 spec(s), including EJB 3.
Also, the Java Persistence API is a subset/sibling of the full EJB3 spec and can run standalone outside of a JEE container. It would be handy to be able to “Add Java Persistence Capabilities”, much like Hibernate capabilities, to any existing project (even regular Java projects).
– Eric
I am holding off on renewing until EJB 3 support is in the product. I am currently playing with NetBeans 5.5 Beta 2. It is not bad… pretty slow and has some bugs at the moment. Feature wise it is pretty nice.
MyEclipse definitly needs EJB 3.0 support. All my projects are going EJB 3.0 from Hibernate.
I ‘m tatally agree!!
MyEclipse definitly needs EJB 3.0 support. All my projects are going EJB 3.0 from Hibernate.
I ‘m totally agree!!
@support-rkalla wrote:
Can you guys explain with some more specifics what kind of tooling you want to see?…
@cybermac912 wrote:
I’m quite attached to the current J2EE support, which asks when you create a project which spec you want to support, then manages the libraries, descriptors, deployments, etc. for you. At the very least, I would like to see existing Enterprise Java support brought up to the JEE 5 spec(s), including EJB 3.
I totally agree with Eric in this point! I think, just some little(?) features would cover about 80% of EJB3 migration problem:
– extendable library sets / project templates
– configurable project validation (I’ll be really happy to get ride of “Missing ejb-jar.xml…” warning in EJB3 project)
– “Add JEE Capabilities” to any existing non-myeclipse projectPaul
I would think that ejb 3.0 support would have to be one of the very highest priority features at this point.. some of us are having to use competing tools now to support new projects because MyEclipse does not support ejb 3.0 at this time. After you get this issue taken care of, we can then discuss jsr 168 portal support, etc…. Thanks for listening (in advance!)
