Hi,

I'm a beginner and I've looked at jBoss and looked at ozone and thought: why
should I care about the ejbSpec? I could write simple java classes (and use
inheritance and interfaces as i like) and they would be persistent and
transactional, which is all I need. I don't need servlets and JSP for my
current project. Why should I use jBoss? What are the main advantages of an
ejbServer to an oodbms? Please tell me what I missed...

Let's say you convinced me - jBoss can do more than ozone. Will ozone be
integrated in jBoss as backend-storage instead of an relational-db which I
wouldn't use anyway? (As I will only write CMP-Beans I should be able to
switch from Hypersonic to Ozone whithout having to change the code?)

Can I build class hierarchies with EJB 1.1? Can I have a manager bean which
somehow extends a person bean? Is there a book like "applying design
patterns to ejb"? Should I do so? I seemed to me as if this was impossible.

Another thing:
I would be GREAT to have releases (i don't mind alpha beta or whatever) more
often and to have a list which tell's me what should be working and what
still has to be implemented.

Thanks in advance,

regards

david




--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to