Have you tried Voyager JBoss OpenTool at http://sourceforge.net/projects/jboss-opentool/ ?
It allows you to generates all the required xml files and the deployment of the beans is really easy.
By the way, I am a little bit disappointed by Jbuilder 6. The EJB Designer. It generates randomly unwanted code and creating relationships is a mess.
I am looking at Eclipse but it seems that there's a lot of manual plumbing before I can start to focus on writing the business logic.
The Voyager OpenTool doesn't work with JBuilder 7...
I like xdoclet + ant, which I believe you can run from most IDEs.
If deploying by copying to the deploy folder is too hard, you might try the (3.0.1) ant jmx task that you can use to call MainDeployer.deploy with the url for your package. This code should be pretty easy to adapt to e.g. a JBuilder plugin if you don't like ant.
For Jbuilder6 and Jbuilder7 you can download at
Hi, how can I create web application with JBuilder 7 for JBoss3+catalina ? I'm using pluggins from http://www.protegra.com/javagroup.html. If I set up app server to jboss3 then JSP/Servlet services is disabled.
If I use multiple servers and use standart pluggin for catalina(Tomcat4.0.3) then I can't debug my JSP/Servlets.
I'm having the same problem, also using protegra's OpenTool. The effect is just the same with Jetty.
Samsonov, did you work around this problem?
I have this problem too. I then used the "multiple servers" setting and set JBoss for EJB and deploy and Tomcat (built in to JBuilder) for JSP/servlets. Then I run each one separately. Seems to be working.
Yes, I've gone this way, too.
I'm to the point of bing able to deploy the esite.jpx (WL variant) to JBoss 3.0.0, and Tomcat 4.0.3. Now the fun starts...
I can access the jndi service, but the esite fails at
Object object = context.lookup("Cart");
with "Cart not bound". Proving that I have a jndi connection, but indicating that Cart is not getting into the jndi provider at the server.
I am getting...
"esite.ejbgrpx": Unable to build:
when I build, and I've been ignoring this, until now. I surmise that something is not being added to this jar that should be, like XML descriptors of all my EJB's.
Anyone know how to determine what's causing this error?
Is is a hangover from all the WebLogic stuff that I nuked on going over to JBoss?
Replying to my own post...
Validate on the archive gives chapter and verse on what's JB thinks is wrong. Still hard to get to the bottom of the problem, and I have still not managed to deploy.