The prediction that an EJB can not work as a CORBA client is absolutely wrong.
You can use an MDB to receive the message from another process and then use a
Java CORBA client to call a remote CORBA server even located in another
company. The only requirement is the interoperability of the CORBA
I have deployed a web/ejb application in jboss (size of EAR 1.5MB) and I'm
using Apache 2.0 with Ajp13 before. The previous version (EAR 1.4MB) works fine
for several weeks in production. Now I've added some new features and we face a
very strange behaviour of the Jboss server.
After two round
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820769#3820769
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820769
Hi gort,
I have the same problem, like some other guys too.
I found a brand new 70 euros problem
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820328#3820328
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820328
Hello JBoss Experts,
i am developing a J2EE application with JBoss 2.4.4 and a mySQL 4.1 database wi