ejb support

I have just dl the new version :)


but I cant find any EJB support..is it me ? or has it been delayed ?



bye bye

0
8 comments

its not just you. i cant quite figure it out either.

btw, i dont use weblogic...i use jboss...is that problem?

0

Hi there :)

After adding the j2ee.jar to ideas lib the j2ee pane appears.

regards

Anders

"Flemming" <crap@boller.dyndns.dk> wrote in message
news:bl1v0l$1kl$1@is.intellij.net...

I have just dl the new version :)

>
>

but I cant find any EJB support..is it me ? or has it been delayed ?

>
>
>

bye bye

>


0

Hi,
where exactly should i put the j2ee.jar? i've copied it to $IDEA_HOME/lib - it didnt help.

Thanks,

0

I don't get it... Why is IntelliJ integrating with BEA WebLogic solely and not providing J2EE support in general to start with?

I think you should be able to add a EJB to a project without having defined any sort of "WebLogic" integration thing.

The EJB concept can be divided into two seperate processes. The first one being the act of actually creating the neccessary components (home, remote, ejb and the generic deployment descriptor) and the second one is the actual deploying. It's not like your VCS support where you have all the different VCS vendors provide their way of doing things from scratch... you have a common foundation that they all build upon.

The first step is what I think is most important that IDEA helps me through (the creation of the bean interfaces, class and the editing of ejb-jar.xml). The deployment is something that I should then be able to do later on with ant or a plugin in IDEA (IDEA even could provide some of the most common ones like WebLogic and JBoss... very important (for me at least)... include JBoss).

So my question is: Why the strong ties to one EJB server vendor?

...or am I misunderstanding something?

0

The things are going to move in exactly the direction you described.
First General EJB support (aka Generic application server) being available.
Then Weblogic support added
Then J2EE Open API allowing to do same things as in Weblogic integration will become available.

General EJB development will be possible without WebLogic integration in next builds.
--
regards,
Alexey Kudravtsev.
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"


"Stefan Freyr Stefansson" <stefanf@althingi.is> wrote in message news:32230740.1064929553848.JavaMail.itn@is.intellij.net...

I don't get it... Why is IntelliJ integrating with BEA WebLogic solely and not providing J2EE support in general to start with?

>

I think you should be able to add a EJB to a project without having defined any sort of "WebLogic" integration thing.

>

The EJB concept can be divided into two seperate processes. The first one being the act of actually creating the neccessary

components (home, remote, ejb and the generic deployment descriptor) and the second one is the actual deploying. It's not like your
VCS support where you have all the different VCS vendors provide their way of doing things from scratch... you have a common
foundation that they all build upon.
>

The first step is what I think is most important that IDEA helps me through (the creation of the bean interfaces, class and the

editing of ejb-jar.xml). The deployment is something that I should then be able to do later on with ant or a plugin in IDEA (IDEA
even could provide some of the most common ones like WebLogic and JBoss... very important (for me at least)... include JBoss).
>

So my question is: Why the strong ties to one EJB server vendor?

>

..or am I misunderstanding something?



0

Stefan, this is all our fault.
We were so much whining to get ANY EJB support so that they
gave us what they had currently working.
- you don't have to use weblogic, just j2ee.jar and enable j2ee
by saying "enable weblogic"
- the UI is not finished so you may have to go to the .iml files
to edit them
- the weblogic integration will be a plugin once they sort out
the needs and use cases
please, go to that j2ee page on intellij.org. it is not too bad.

r.


Stefan Freyr Stefansson wrote:

I don't get it... Why is IntelliJ integrating with BEA WebLogic solely and not providing J2EE support in general to start with?

I think you should be able to add a EJB to a project without having defined any sort of "WebLogic" integration thing.

The EJB concept can be divided into two seperate processes. The first one being the act of actually creating the neccessary components (home, remote, ejb and the generic deployment descriptor) and the second one is the actual deploying. It's not like your VCS support where you have all the different VCS vendors provide their way of doing things from scratch... you have a common foundation that they all build upon.

The first step is what I think is most important that IDEA helps me through (the creation of the bean interfaces, class and the editing of ejb-jar.xml). The deployment is something that I should then be able to do later on with ant or a plugin in IDEA (IDEA even could provide some of the most common ones like WebLogic and JBoss... very important (for me at least)... include JBoss).

So my question is: Why the strong ties to one EJB server vendor?

..or am I misunderstanding something?


0

Ok... great ;o)

I owe you an appology for my harsh tone in the previous post (didn't mean to be harsh but I just finished reading it again and it may have sounded a bit like that).

I haven't followed J2EE in Aurora at all so I was surprised to see that it was so WebLogic centric.

I'll wait patiently until the "generic" stuff comes along and then I'll start using it.

Thanks, Stefan.

0

Please sign in to leave a comment.