Just wanted to throw in a pat on the back for all the jBoss
developers. I've successfully converted about 80% of a production CORBA
application to EJBs, and run it in jBoss. It uses an Oracle back end,
though there are no entity beans yet since it's a straight translation of
the existing CORBA services. The client is a signed applet, which runs in
the Java plug-in.
The good news is that as of now (Wednesday, 5:50 EST), it runs
great in the current CVS build of jBoss. It's faster than the CORBA
version! In fact, based on the demo of the available functionality, I
think I had the company in question convinced they should switch to EJBs
immediately.
Of course, there's still room for improvement. One irritating
fact is that I had to sign the jboss-client and jnp-client JARs as well as
the main applet JAR, because the client code tries to do some wacky things
(like access /tmp on a Windows PC?) that cause security explosions. And,
sad but true, we had to back off EJBs because they have to support Mac
clients (for the next 9-ish months) which are JDK 1.1 only (as far as we
can tell 1.2 is only coming with OS X, which is not an option for the
relevant hardware). So it would be nice to have a little more leeway for
different JDKs between client and server, even if that doesn't extend to
1.1.
As for the deployment plans, it sounds like they'd like to develop
on jBoss and deploy on Weblogic. There's another product there heading
for EJBs, and it's all WebLogic pending jBoss 2.0 final. They've already
indicated their interest in switching for development, and I think if we
put out a stable, high-quality product with good tools and documentation,
they may bite for production. It remains to be seen.
So, keep up the great work, and let's put together an outstanding
2.0 release!
Aaron
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
