Yes,
also Michael Gashe will be starting a internship with Telkel pretty soon.
Michael worked at softwarebuero the company behind Ozone. :))))
there is a team :)
regards
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Shillan
> Sent: Wednesday, August 09, 2000 9:17 AM
> To: jBoss
> Subject: Re: [jBoss-User] ozone and jboss
>
>
> David,
>
> What are you trying to achieve? Persistent objects, including
> transactions?
> I can do that using any number of DBs with a JDBC driver. Ozone can do it
> to. But EJBs are not just about storing objects, are they? (Are they? :-))
>
> EJBs are there to provide scalable middleware to distance clients from the
> database, and many other things too. Search for discussions on 3-tier
> architecture for reasons why this is a good idea. Also, of course, you tie
> yourself to ozone if you use a client linked directly to it. jBoss isn't
> just EJB... it's J2EE. This can obviously do more than Ozone.. Servlets,
> JSPs, Web app hosting, JMS and the whole alphabet soup. Ozone can't do any
> of the stuff.
>
> As for plans to integrate jBoss and Ozone, yes there are. This is under
> Project Game Over on the site and I'm assigned to look at it. I
> am currently
> setting up an environment at home to do building and testing of
> such things
> and hopefully will begin next week (where "begin" = "start pestering list
> with questions about jBoss"!!)
>
> CMP is a great theory. What you say about switching from
> Hypersonic to Ozone
> (or InstantDB, PostgreSQL...) *should* be true, but I don't think
> it is just
> yet. We can all work on it though! Maybe I'm wrong, and changing
> DBs at the
> moment is already seamless!!
>
> Peter.
>
> ----- Original Message -----
> From: "David Leuschner" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, August 09, 2000 9:59 AM
> Subject: [jBoss-User] ozone and jboss
>
>
> > 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]
> >
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]