AlexeyThe list is very impressive, cant wait to check it out when the next releaseis available. I have three requests to add but do not know how to add toyour J2EE feature request list.1) Integration with Tomcat 4.02) Integration with JBoss3) Integration with Sun J2EE RIItem 2 and 3 will allow developers to run and testing their Entity andSession beans without the need to pay big dollars for a J2EE server.RegardsMichael Mok"Alexey Kudravtsev" <email@example.com> wrote in messagenews:firstname.lastname@example.org...
There you'll find already implemented and most anticipated EJB featureslists.--regards,Alexey Kudravtsev.JetBrains, Inc / IntelliJ Softwarehttp://www.intellij.com"Develop with pleasure!"
-1 for specific container integration into the core functionality of IDEA. This is the kind of thing that bloat is made of.In the longer perspective, support for the new deployment API could be a good thing though./Fredrik LindgrenMichael Mok wrote:
>>http://www.intellij.org/twiki/bin/view/Main/J2EESupport>>>>There you'll find already implemented and most anticipated EJB features>>lists.>>-->>regards,>>Alexey Kudravtsev.>>JetBrains, Inc / IntelliJ Software>>http://www.intellij.com>>"Develop with pleasure!">>>>>>>>>>
Michael,What do you mean when you speak about J2EE server integration?--Best regards,Mike Aizatsky.-
JetBrains, Inc / IntelliJ Softwarehttp://www.intellij.com"Develop with pleasure!"
MikeI am aware that adding server specific functionality could lead to abloatware. Can I suggest providing them as an optional plugins which wouldreally help web application developers and EJB developer in terms ofdebugging and deploying their applications. This concept is similar todeveloping PHP and Tomcat plug ins for Apache web server.I would hope to see an optional plug that will allow you to run, debug anddeploy J2EE war files. A Tomcat 4 plug in will eliminate the need toconfigure Tomcat server.xml whenever you develop a new webapplication. Forthe moment, I have three webapplications running on the same Tomcatinstallation and I used IDEA to connect to Tomcat to debug any one of them.However it is a hassle as any System.out.println message get displayed inthe same output console (ie println message from all three webapplications), and Tomcat starts up, it starts up the three applications.The plug in will dynamically setup the classpath and libraries as requiredby Tomcat and will startup Tomcat running only one web application at a time(ie the web application of your current project). I do not know how todescribe the J2EE server integration, as I have not yet develop any EJBs butI would figure (if we take Sun's J2EE RI) that it will dynically startup theJ2EE server, deploy your EJBs and allows you to run and debug your EJBs.RegardsMichael Mok"Mike Aizatsky" <email@example.com> wrote in messagenews:firstname.lastname@example.org...
What do you mean when you speak about J2EE server integration?
--Best regards,Mike Aizatsky.------------------------------JetBrains, Inc / IntelliJ Softwarehttp://www.intellij.com"Develop with pleasure!"
+1 for Tomcat(because it would be a good example, and everyone uses it. Even resin guys, like myself. ;o), everything else should prob be a plugin.While we're adding j2ee things that would be nice here's a repost from the features group:
Here are some interesting JSRs from the JCP. The only reason I mention these is for the intellij team to be aware of them. More and more java standards tend to have generated files (RMI, EJB, Web Services, JDO, etc.), and this seems like an effort to standarize a way of defining them, similiar to existing ad-hoc efforts (XDoclet, EJen, EJBgen, Javadoc). Probably not a request for this release, but just a development to be aware of. This JSR is aimed primarily at deployment and development tools, and who is the best development team out there? ;o)The best outcome, of course, would be for Jetbrains to join the expert group and help drive this effort. <hint, hint>Metadata for java, led by Joshua Bloch, of Effective Java fame.<http://www.jcp.org/jsr/detail/175.jsp>JWS, builds on the above for web services. From BEA. I think Apache AXISand BEA Weblogic Workshop (from 7.0) have an implementation of this.<http://www.jcp.org/jsr/detail/181.jsp>An article with a bit of info, examples of JWS.<http://www.onjava.com/pub/a/onjava/2002/05/08/jws.html>
Finally, here's something that just got approved through the JCP. Still can't quite figure out what it does...<http://java.sun.com/products/jmi/>--peteFredrik Lindgren wrote:
>> Alexey>>>> The list is very impressive, cant wait to check it out when the next >> release>> is available. I have three requests to add but do not know how to add to>> your J2EE feature request list.>>>> 1) Integration with Tomcat 4.0>> 2) Integration with JBoss>> 3) Integration with Sun J2EE RI>>>> Item 2 and 3 will allow developers to run and testing their Entity and>> Session beans without the need to pay big dollars for a J2EE server.>>>> Regards>>>> Michael Mok>>>> "Alexey Kudravtsev" <email@example.com> wrote in message>> news:firstname.lastname@example.org...>>>>> http://www.intellij.org/twiki/bin/view/Main/J2EESupport>>>>>> There you'll find already implemented and most anticipated EJB features>>> lists.>>> -->>> regards,>>> Alexey Kudravtsev.>>> JetBrains, Inc / IntelliJ Software>>> http://www.intellij.com>>> "Develop with pleasure!">>>>>>>>>>>>>>>>>>>
+1 with a caveat...I use Jboss/Jetty, so in here lies the problem, how do you support mostconfigurations under the sun without having to add so much to the editor? Ican't stand Tomcat personally, and prefer Orion or Jboss.This is something no other IDE has managed to resolve effectively except toshove everyone in either Tomcat, Weblogic or Websphere which I think isridiculous. Just because Tomcat is the 'reference implementation' doesn'tmean it's a good thing to develop in.I don't know how much is involved, and how much time the JetBrains folkshave, but a plugin architecture would be wonderful. I would like to havethe option of adding a plugin that will give us the full support of the appserver of our choice either provided by default from JetBrains, or somethingthat another developer writes and sells to those who want to use it. I wasthinking something along the lines of having a standard interface for IDEAwhich would run 80% of the code, and then 20% of the rest which wouldusually be app server specific needs to be written by a developer or thevendor.I think that app servers support from within IDEA should come out of thegate with plugins for:TomcatJboss/JettyOrionResinServletexecAnd of course provide way to run none so you can keep debugging the way youdo right now, remotely.All of those app server offer at least free development fees and are widelyused. Let the poor souls who like to spend zillions on the expensive appservers write their own damn plugins and spend their own money on expensiveuseless solutions.Just my 2 cents.ROn 7/1/02 10:05 AM, in article email@example.com, "Michael Mok"<firstname.lastname@example.org> wrote:
>> Michael,>> >> What do you mean when you speak about J2EE server integration?>> >> -->> Best regards,>> Mike Aizatsky.>> -
>> JetBrains, Inc / IntelliJ Software>> http://www.intellij.com>> "Develop with pleasure!">> >> >>
I completely agree with Robert. App server specific stuff should not be included in IDEA core piece. It should come as plug-ins.My additional 2 cent,Nilesh
Please sign in to leave a comment.