10 comments

We've published the preliminary EJB 3 support feature list, considered
for inclusion into next IDEA version:

http://www.jetbrains.net/confluence/display/IDEADEV/EJB3Support

All your thoughts and ideas are welcome.

The feature list looks pretty long considering that here's only about EJB 3. Do you
plan to implement all these for Demetra?

The "Conversion" part looks very interesting.
- you could add "Convert Hibernate 2 to clean 3.0 Bean" :).
I the conversion is smooth and correct, I can imagine many projects using IntelliJ just
to make a riskless and easy conversion/upgrade :).

The "Persistence Support"/"Model Diagram" and
the "Persistence Support"/"Visual mapping editor" would be also something very interesting :).

Ahmed.

0

The "Conversion" part looks very interesting.
- you could add "Convert Hibernate 2 to clean 3.0
0 Bean" :).


+1

0

> - you could add "Convert Hibernate 2 to clean 3.0 Bean" :).

There's no problem at conversion Hibernate beans. The problem is that we
wouldn't be able to convert client code - too many API differences.
That's why we're going to provide support only for 3.0 Bean generation,
not conversion.

0

> The feature list looks pretty long considering that here's only about
> EJB 3. Do you
> plan to implement all these for Demetra?

This is just a list of features we're considering to be implemented.

0

The par concept is gone, ejb archives are the same as any other archive, and persistence classes can be in any jar file, so there is no par module type needed anymore.

The one thing I don't see there is intelligent query support. For example, if I rename my class, any queries using it should be likewise renamed, similarly for fields/properties. I should also be able to do the renaming from within the query ,for example:

"select o from Document o". If I ctrl-w on Document, I should be able to refactor -> rename.

Also, find usages for a particular NamedQuery, and safe delete of query (show unused queries too in editor, same as unused anything else).

The conversion stuff, while handy, i think could be very easily done with a plugin from the community (hell, if there is enough demand, I can probably knock up an ejb2+xdoclet entity to ejb3 plugin within a couple of days), so I wouldn't say it's crucial for core.

Under creation, why is there no entity? Creating an entity is as easy as creating a state(less/ful) bean (in all cases, it's just one annotation).

0

What about my post in
http://www.intellij.net/forums/thread.jsp?forum=22&thread=169554 (msg
#4939613, search for "Messi"), i.e. the packaging-related things (ok,
according to Hani PAR is gone)?

regards,

Messi

Mike Aizatsky (JetBrains) wrote:

Hi,

We've published the preliminary EJB 3 support feature list, considered
for inclusion into next IDEA version:

http://www.jetbrains.net/confluence/display/IDEADEV/EJB3Support

All your thoughts and ideas are welcome.

0

Hani,

The par concept is gone, ejb archives are the same as any other archive, and persistence classes can be in any jar file, so there is no par module type needed anymore.


What do you mean? They're still in the latest available JSR draft.

0

The one thing I don't see there is intelligent query support. For example, if I rename my class, any queries using it should be likewise renamed, similarly for fields/properties. I should also be able to do the renaming from within the query ,for example:

"select o from Document o". If I ctrl-w on Document, I should be able to refactor -> rename.


That's under "Full support of query language: completion, error
highlighting". I'll add "references" to it too.

Also, find usages for a particular NamedQuery, and safe delete of query (show unused queries too in editor, same as unused anything else).


Added.

The conversion stuff, while handy, i think could be very easily done with a plugin from the community (hell, if there is enough demand, I can probably knock up an ejb2+xdoclet entity to ejb3 plugin within a couple of days), so I wouldn't say it's crucial for core.


These are not plans (yet). Just a set of unprioritized ideas.

Under creation, why is there no entity? Creating an entity is as easy as creating a state(less/ful) bean (in all cases, it's just one annotation).

Fixed. Just lost.

0

Even though this thread is quite old: Here's a feature that I haven't seen mentioned:
JSF Form CRUD Generation
Already implemented in Netbeans 5.5 Early Access, so hurry up ;)
http://blogs.sun.com/roller/page/pavel?entry=next_step_generate_simple_jsf

0

I haven't taken a close look at it yet, but I have heard and read that it is also available
from the JBossSeamIDE Eclipse plugin: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSeamIDE

0

Please sign in to leave a comment.