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.
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 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 Lindgren
Michael Mok 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.
I am aware that adding server specific functionality could lead to a bloatware. Can I suggest providing them as an optional plugins which would really help web application developers and EJB developer in terms of debugging and deploying their applications. This concept is similar to developing PHP and Tomcat plug ins for Apache web server.
I would hope to see an optional plug that will allow you to run, debug and deploy J2EE war files. A Tomcat 4 plug in will eliminate the need to configure Tomcat server.xml whenever you develop a new webapplication. For the moment, I have three webapplications running on the same Tomcat installation 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 in the same output console (ie println message from all three web applications), and Tomcat starts up, it starts up the three applications. The plug in will dynamically setup the classpath and libraries as required by 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 to describe the J2EE server integration, as I have not yet develop any EJBs but I would figure (if we take Sun's J2EE RI) that it will dynically startup the J2EE server, deploy your EJBs and allows you to run and debug your EJBs.
+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>
JWS, builds on the above for web services. From BEA. I think Apache AXIS and BEA Weblogic Workshop (from 7.0) have an implementation of this. <http://www.jcp.org/jsr/detail/181.jsp>
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/>
--pete
Fredrik Lindgren wrote:
-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 Lindgren
Michael Mok 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" <cdr@intellij.com> wrote in message >> news:afekvi$gns$1@is.intellij.net... >> >>> 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!" >>> >>> >>> >>> >>> >> >>
I use Jboss/Jetty, so in here lies the problem, how do you support most configurations under the sun without having to add so much to the editor? I can't stand Tomcat personally, and prefer Orion or Jboss.
This is something no other IDE has managed to resolve effectively except to shove everyone in either Tomcat, Weblogic or Websphere which I think is ridiculous. Just because Tomcat is the 'reference implementation' doesn't mean it's a good thing to develop in.
I don't know how much is involved, and how much time the JetBrains folks have, but a plugin architecture would be wonderful. I would like to have the option of adding a plugin that will give us the full support of the app server of our choice either provided by default from JetBrains, or something that another developer writes and sells to those who want to use it. I was thinking something along the lines of having a standard interface for IDEA which would run 80% of the code, and then 20% of the rest which would usually be app server specific needs to be written by a developer or the vendor.
I think that app servers support from within IDEA should come out of the gate with plugins for: Tomcat Jboss/Jetty Orion Resin Servletexec
And of course provide way to run none so you can keep debugging the way you do right now, remotely.
All of those app server offer at least free development fees and are widely used. Let the poor souls who like to spend zillions on the expensive app servers write their own damn plugins and spend their own money on expensive useless solutions.
I am aware that adding server specific functionality could lead to a bloatware. Can I suggest providing them as an optional plugins which would really help web application developers and EJB developer in terms of debugging and deploying their applications. This concept is similar to developing PHP and Tomcat plug ins for Apache web server.
I would hope to see an optional plug that will allow you to run, debug and deploy J2EE war files. A Tomcat 4 plug in will eliminate the need to configure Tomcat server.xml whenever you develop a new webapplication. For the moment, I have three webapplications running on the same Tomcat installation 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 in the same output console (ie println message from all three web applications), and Tomcat starts up, it starts up the three applications. The plug in will dynamically setup the classpath and libraries as required by 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 to describe the J2EE server integration, as I have not yet develop any EJBs but I would figure (if we take Sun's J2EE RI) that it will dynically startup the J2EE server, deploy your EJBs and allows you to run and debug your EJBs.
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" <cdr@intellij.com> wrote in message
news:afekvi$gns$1@is.intellij.net...
>
>
>
>
>
-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 Lindgren
Michael 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 Software
http://www.intellij.com
"Develop with pleasure!"
Mike
I am aware that adding server specific functionality could lead to a
bloatware. Can I suggest providing them as an optional plugins which would
really help web application developers and EJB developer in terms of
debugging and deploying their applications. This concept is similar to
developing PHP and Tomcat plug ins for Apache web server.
I would hope to see an optional plug that will allow you to run, debug and
deploy J2EE war files. A Tomcat 4 plug in will eliminate the need to
configure Tomcat server.xml whenever you develop a new webapplication. For
the moment, I have three webapplications running on the same Tomcat
installation 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 in
the same output console (ie println message from all three web
applications), and Tomcat starts up, it starts up the three applications.
The plug in will dynamically setup the classpath and libraries as required
by 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 to
describe the J2EE server integration, as I have not yet develop any EJBs but
I would figure (if we take Sun's J2EE RI) that it will dynically startup the
J2EE server, deploy your EJBs and allows you to run and debug your EJBs.
Regards
Michael Mok
"Mike Aizatsky" <mike@intellij.com> wrote in message
news:afp8dp$jid$1@is.intellij.net...
>
>
>
>
>
+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:
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/>
--pete
Fredrik 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" <cdr@intellij.com> wrote in message
>> news:afekvi$gns$1@is.intellij.net...
>>
>>> 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 most
configurations under the sun without having to add so much to the editor? I
can't stand Tomcat personally, and prefer Orion or Jboss.
This is something no other IDE has managed to resolve effectively except to
shove everyone in either Tomcat, Weblogic or Websphere which I think is
ridiculous. Just because Tomcat is the 'reference implementation' doesn't
mean it's a good thing to develop in.
I don't know how much is involved, and how much time the JetBrains folks
have, but a plugin architecture would be wonderful. I would like to have
the option of adding a plugin that will give us the full support of the app
server of our choice either provided by default from JetBrains, or something
that another developer writes and sells to those who want to use it. I was
thinking something along the lines of having a standard interface for IDEA
which would run 80% of the code, and then 20% of the rest which would
usually be app server specific needs to be written by a developer or the
vendor.
I think that app servers support from within IDEA should come out of the
gate with plugins for:
Tomcat
Jboss/Jetty
Orion
Resin
Servletexec
And of course provide way to run none so you can keep debugging the way you
do right now, remotely.
All of those app server offer at least free development fees and are widely
used. Let the poor souls who like to spend zillions on the expensive app
servers write their own damn plugins and spend their own money on expensive
useless solutions.
Just my 2 cents.
R
On 7/1/02 10:05 AM, in article afpmc9$2lp$1@is.intellij.net, "Michael Mok"
<moktc@hotmail.com> 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