EJB3 Support

[bershath27]

hi,
i'm disappointed with the removal of the EJB3 project/component creation module, on the latest version.

on JBossIDE-Beta2, it was included and i don't understand the reason why you have dropped it. can i know what's going on pls ?

thanks
Tyronne Wickramarathne

[rob.stryker]

The EJB3-project was nothing more than a regular old java project that added certain jars to a classpath. It provided no other functionality at all other than adding jars to a classpath.

It served two purposes during its lifespan. Originally back in the old JBoss IDE, it was the only ejb3 tools implementation around. After we starated moving forward from there, it served as a stop-gap mechanism until webtools implemented an ejb3 facet in their EJB Project.

The only other purpose it served was to try to be a "module" without being a module. The goal behind it was to allow both an ejb3 module and a web module to live in the same project for what would become our seam project. That's no longer an issue, as the seam project has now been implemented in another way.

So to summarize, it's purposes were to wait for WTP to get ejb3 out, and to potentially create a seam project. As WTP now has ejb 3.0 facets available and a Seam project has been created in another way, the EJB3 project needed to go.

Your options are basically to use the WTP EJB project with a 3.0 facet, or use a plain java project but add the ejb3 libraries to your project's build path yourself. (right click on project, select build path, go to the Libraries tab, select Add Library, and there should be a jboss ejb3 library there. )

I realize this is slightly inconvenient, but the idea of keeping around a project who's entire reason for existing had disappeared was not a good one to entertain.

- Rob

[bershath27]

why do we have to go thru such a tortures route to create a project/components in EJB3 ? it would be great if we could keep it back ?? AFAIK, when we move on, with newer versions, we used to keep the existing components while adding new features.. but not removing the components, i believe, :)

thanks
Tyronne Wickramarathne

[rob.stryker]

The *only* thing the EJB project had was adding some jars to the classpath. That's all it did. It had no packaging configuration pre-made for it, the way WTP projects do. It had no interesting builders. It provided nothing but a classpath.

It is not reasonable to create a project type that does nothing but add to the classpath.

You can always create a plain java project and then add the EJB3 classpath container to your project. Right click on your project, select build path, navigate into classpath, add library, and find the JBoss EJB3 library page. It really isn't that much more work.

[maxandersen]

I think tyronne is mostly missing the *wizards*

Didn't we use to have ejb3 component wizards ?

session bean as such ?

(maybe my brain is still on vacation)

[bershath27]

>>I think tyronne is mostly missing the *wizards*
yes, exactly. :)

>>Didn't we use to have ejb3 component wizards ?
yes we had component wizards. but it's not available with the newer version.

>>session bean as such ?
yes, for both session beans as well as for MDBs. great if we could have those wizards back. for me it badly affects as i'm doing loads of JBM/JBMQ stuff with MDBs. doing things in a quicker time is the key where those wizards played a vital role.

i've been using JBossIDE since 2004, with xdoclet for the ejb2.x projects. so i have no issues adding the class libraries required for ejb3 and creating things from the scratch, but we're missing the ejb3 wizards here and that's what most concerned about.

(btw: bershath27 == xdoclet)

thanks
Tyronne Wickramarathne

[rob.stryker]

Then this will be fixed ;)

Sorry for the inconvenience

[bershath27]

hi Rob
no worries. i have created an Jira for this : http://jira.jboss.com/jira/browse/JBIDE-911
great if you can accommodate this feature on beta4 :)
thanks
Tyronne Wickramarathne

[bershath27]

Guys,

This is not fixed as expected, ie as it was in JBossIDE-2.0.0.Beta2. I'm still using the said version for this EJB3 related problem hasn't been resolved in JBDS/JBossTools.

I have noted that the EJB3 MDB/SessionBean creation are added but still EJB3 Project creation is missing.

IOW, here's how you could produce this problem:
1. Create an EJB Project (Since there's no EJB3 Project to select)
2. Create an EJB3 MDB
3 You can see that the required libraries are not getting added to the build path, which you have to add manually, where as with JBossIDE-2.0.0.Beta2, this is automated.

I will mail you with the screen dumps explaining what's exactly missing in JBDS, if needed.

Cheers
Tyronne Wickramarathne

[maxandersen]

EJB3 project is not coming back since it was a broken setup.

1) Create a EJB, EAR or WAR project and point to the designated runtime which will provide you with the required libraries.

2) Rob will have to answer this one since JBIDE-911 was about these

3) They will if you do #1

Screendumps should go in a jira if you still think there is an issue.

[bershath27]

EJB3 project is not coming back since it was a broken setup.
1) Create a EJB, EAR or WAR project and point to the designated runtime which will provide you with the required libraries.

Why do I have to go through this route when my basic requirement is just to create a .jar containing one more MDBs ? My requirement is a very basic one, I do *not* need to create an EAR or WAR, when my requirement is just to create a *.jar containing few MDBs . This is my requirement :

1. Create a simple EJB3 Project
2. Create one or more MDBs
3. Package them as a *.jar
4. Deploy it , and call the deployed MDBs from a remote JMS client

I have attached a screen dump on the Jira for you're reference on what's missing in JBossTools.

Hope this helps ;)
Cheers

[maxandersen]

Did you even *try* creating a ejb utility jar ?

There is zero difference afaik. It is one wizard that creates a jar using the actual jars that the runtime you are deploying to contains.

The ejb3 project is *not* coming back; pointing to internal jars in the plugins is broken, wrong, dangereous - you need to point to an external runtime.

If some wizards are missing besides the ejb3 project then please create *specific* jiras for what you cannot do in those 4 steps.