A fiend of mine was evaluating jBoss for use as a part of his development environment.
He is going to check back in a couple months. Anyway, he thought that this feedback
may be helpful.
- jeremiah
---
Hello,
I have been evaluating JBoss for use in development. I am very impressed with some of
the functionality, but my impression is that it is not quite ready. Here are remarks,
criticisms and
suggestions for improvement:
1. Documentation. The "Beginning EJB programming using jBoss (Windows)" is
excellent. But this only covers a stateless session bean. Could this be expanded to
show how to use all the standard types?
2. Stateful session beans. These do not seem to be supported. The "Default Stateful
SessionBean" configuration is not part of the jboss.xml files. Can you include an
example that demonstrates usage including Synchronization? I was trying to modify the
"sb" example from Jonas to work with JBoss but I gave up.
3. Connection pools. The Minerva documentation looks very good. But it mentions a
file called
jboss.jcml which is not in the standard distribution, so it seems like this isn't
quite integrated. Could you include an example of how this works with a standard
database such as oracle?
4. Container managed persistence. This creates a table with the same name as the
bean. But the reality is, in most cases the table will already be created. How do
you use a different table name than the bean name? The documentation mentions that
this can be changed in "jaws.xml" but it doesn't say how.
5. Bean managed persistence. Examples and documentation on this area also need to be
improved. This is related to Minerva because usually you would specify the
"<resource-ref>" in the ejb-jar.xml file, and then in the bean get the datasource from
the context.
6. Transaction support. How do you change the transaction attribute type? In
weblogic, this is set in the ejb-jar.xml file in the "<assembly-descriptor>
<container-transaction> <trans-attribute>" section. I think this is also part of the
dtd.
7. EJX. This is very nice-looking but doesn't seem to do much. You really need a
nice gui tool to help configure these XML files, similar to Weblogic's GUI tool.
Conclusion: At this point, JBoss isn't ready for development. I wish it were as I
really like the concept.
Next I will be evaluating Orionserver, which seems very impressive but it isn't
open-source.
I would like to help with development and I will look at the different projects to see
where I can add
value.
Keep up the good work.
Nathan Vanderhoofven
Senior Software Engineer
Global Commerce Systems
[EMAIL PROTECTED]
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
