I'll add to that...I've found something very interesting while surveying the
marketplace of EJB containers. Basically, jBoss is as good as it gets for less
than $10,000 per CPU. And of course jBoss is $0 per CPU. WebLogic and iPlanet
are both awesome, in that they completely implement the J2EE spec, and support
advanced features such as clustering. But unless you have a deployment budget
of about $100k or more, forget about them.
I screwed around with Allaire JRun, and though I was impressed by the web-based
configuration manager, the EJB support is very bad. I would go so far as to
say that their claim of "EJB 1.1 support" is simply a lie. From what I could
tell, they don't even support the ejb-jar.xml deployment descriptor! You can't
get much less spec-compliant than that. jBoss is clearly superior to JRun,
which ranges from $2000-$5000 per CPU.
Thad Humphries wrote:
> Aaron,
>
> SUCCESS!! I did some digging around the various *.policy files I have in
> Java and finally hit upon creating a .java.policy file in my home directory
> containing
>
> grant {
> permission java.security.AllPermission;
> permission java.net.SocketPermission "localhost:1024-",
> "accept,listen,connect,resolve";
> };
>
> With this, the client application ran exactly as described in
> Monsoon-Haefel's book, Client_1.java from Ch 4 of "Enterprise Java Beans,
> 2d" (O'Reilly:2000).
>
> Please allow me a brief testimonial: I have had more success these past 4
> days with jBoss than I had in *twice* the time with Allaire's JRun (the
> single developer license). Hands down, jBoss is easier to use. For
> example, beans deploy themselves, even on updates. In JRun, you have to
> uninstall the bean, restart the server, install the new bean, restart the
> server. In jBoss, configuration changes were easy, if not always well
> documented. As for tech support, I was able to get clear, understandable
> answers from this new group whereas scores of messages were of no help on
> Allaire's message board. Finally, from the way I read it, jBoss
> ***actually complies with the EJB spec***! JRun, OTOH, *requires* me to
> write my own ejbFindByPrimaryKey() method in the ProgramBean.java
> file. (In fact, jBoss seems to go extra mile by writing other finders for
> me as well.)
>
> Now it's on to adding TomCat!
>
> At 11:43 9/28/2000 -0400, you wrote:
> > The problem you are having now is not related to databases. You
> >are getting a security exception when you try to perform a JNDI lookup.
> >The port 1099 is where the jBoss JNDI server listens (there's a section in
> >the manual on default ports). Is you client an applet or something? Do
> >you have a security manager in your client? Does it allow network access?
> >Is the client running on the same machine as the server? The exception
> >indicates that the client is trying to connect to "localhost", so if it's
> >really on a different machine, look at the section in the manual on
> >"clients on a different machine".
> >
> >Aaron
>
> --------------------------------------------------------------------------
> Thad Humphries "'Open Systems' means no fences. And
> Web Development Manager no fences means no need for Gates."
> Phone: 540/675-3015, ext. 225 - Sun Microsystems
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
