[EMAIL PROTECTED] wrote:
>
> Didn't mean to rant. I really do like what you guys are doing with jBoss!
> Just making my head swim a little remembering the list of packages
> going in there: EJB, JDBC, JNDI, JMX, JMS, JAAS, Jini, ...
>
All of the above packages seem to fit into jBoss very well, and will also do be
there in most other EJB servers, except _maybe_ JMX and Jini (if I didn't know
what the idea is with using that I would perhaps wonder, but I do :).
> I totally agree that jBoss should take advantage of these kinds of packages
> where appropriate and not reinvent the wheel. But, I was thinking that it is
> somewhat intimidating for would-be contributors to get a handle on all
> this stuff...
>
Well, you don't have to get a handle on it all. EJB (of course) and JNDI are
very likely that you must at least know they are used. JMX probably in order to
plug in your stuff next to jBoss' core. JAAS perhaps if you are deep down in the
container invocation handling. JDBC and JMS only if you are in that particular
field. Jini not likely unless you want to do clustering with Rickard :)
> BTW, is there a list of the min hardware requirements for jBoss? I
> realize this will vary somewhat by platform, but I would think that some
> of you would have a general idea. I would try to find it on the website,
> but can't get there...
>
I guess the requirements would be the same (or less?) as the ones for J2EE in
general. Probably the JRE sets most limits, jBoss will probably just run slower
or faster depending on your system (memory is always good, as well as processing
power).
/Kalle
--
Karl-Fredrik Blixt
Computer Science student at LiTH, Sweden
Homepage: http://www-und.ida.liu.se/~karbl058
Telephone: +46-(0)13-17 99 29
Cellular: +46-(0)739-87 11 03
UIN: 4744258
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
