[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ozone & EJBs
Hi Falko,
Thanks for the interesting response.
> I'm not sure if this [creating an EntityPersistanceManager ] is possible.
> Things like activation of objecs is already there in ozone. ozone is not
just a
> persistent store but also an execution environment of the objects. So it
is
> some kind of a application server itself. Do you think an
EntityPersistanceManager
> is enough to integrate the functionality of ozone into jBoss?
No, it is not enough to integrate all functionality of Ozone into JBoss but
probably enough to let JBoss use Ozone as an Object storage which would make
it possible to create EntityBeans using Ozone as the back-end database. For
the more application oriented features of Ozone one could use SessionBeans
to access those instead. Thus it should be possible to use JBoss as a
front-end to all wonders of Ozone but also allowing access to RDBMS, CORBA
systems etc. from JBoss as the application server providing a consistant
interface for your JSP's, servlets etc.
> I'm not sure again. From what I've read the connector architecture seems
to be
> a very general JDBC architecture. Like JDBC it solves some API problems
but
> doesn't bridge the gap between OO and R (or any other SQL problem). Where
do you
> think the connector architecture can help to integrate ozone into an EJB
server
> / jBoss?
You're right, my bad. I just re-read the 2.0 spec on Connectors and it seems
to have a strong focus on relational EIS. I have the impression this was
explained differently in an earlier draft of the spec which had me led
astray.
> > Do you or did Mark have any ideas on possible ways of integrating the
two?
>
> Not really. To me it seemed that Marc wasn't aware of the (EJB)
container-ish
> nature of an OODBMS. I'm still in the opinion that ozone could be an EJB
> container (not that I think that I'm able to do this) while Marc wanted
> something that just stores objects. This is more or less where we stopped
> discussion. I'm sure that there are other possibilities but I'm way to
> unfamiliar with EJB and jBoss to know them ;)
That is also an interesting possibility - to extend Ozone to incorporate EJB
container functionality and then one could use session beans in JBoss or any
other EJB server to handle the interaction with the Ozone EJB's - if a
single application server acting as a gatekeeper to presentation objects in
the application tier is wanted. I'm afraid that this will be fairly
time-consuming and difficult to do though, unless there is someone else out
there who has a clever idea of how this could be done without having to
re-write it all from scratch...
Best regards,
Per
----- Original Message -----
From: "Falko Braeutigam" <falko@smb-tec.com>
To: "Per Nyfelt" <per_nyfelt@hotmail.com>; <ozone-users@ozone-db.org>
Sent: Monday, January 08, 2001 11:46 AM
Subject: Re: Ozone & EJBs
On Fri, 05 Jan 2001, Per Nyfelt wrote:
> I've been developing EJB's using J2EE for a couple of years, mainly
> SilverStream and, recently, JBoss. It is possible to use Ozone for
> SessionBeans today but I have been thinking about trying to do something
to
> make it possible to use Ozone for Entity beans as well -maybe creating an
> EntityPersistanceManager to handle the job?
I'm not sure if this possible. Things like activation of objecs is already
there in ozone. ozone is not just a persistent store but also an execution
environment of the objects. So it is some kind of a application server
itself.
Do you think an EntityPersistanceManager is enough to integrate the
functionality of ozone into jBoss?
> Then on the other hand the connector architecture in the next version of
> J2EE (2.0) might provide another way to use Ozone together with a J2EE
> application server.
I'm not sure again. From what I've read the connector architecture seems to
be
a very general JDBC architecture. Like JDBC it solves some API problems but
doesn't bridge the gap between OO and R (or any other SQL problem). Where do
you
think the connector architecture can help to integrate ozone into an EJB
server
/ jBoss?
> I think convenience and features are more important than
> performance when considering this. It would be great if JBoss and Ozone
> could work together easily so that one could easily create an OO view of
> relational data with J2EE for the legacy systems and then use Ozone for
new
> applications and as a front end developer you would have one way of
> accessing objects and calling business methods that would combine the
power
> of EJB's with Ozone.
This would indeed be very cool and I started the dicussion with Marc exactly
for this reasons.
>
> Do you or did Mark have any ideas on possible ways of integrating the two?
Not really. To me it seemed that Marc wasn't aware of the (EJB)
container-ish
nature of an OODBMS. I'm still in the opinion that ozone could be an EJB
container (not that I think that I'm able to do this) while Marc wanted
something that just stores objects. This is more or less where we stopped
discussion. I'm sure that there are other possibilities but I'm way to
unfamiliar with EJB and jBoss to know them ;)
Falko
>
> Best regards,
> Per
>
> ----- Original Message -----
> From: "Falko Braeutigam" <falko@smb-tec.com>
> To: "Jay Abraham" <ejb700@yahoo.com>; <ozone-users@ozone-db.org>
> Sent: Friday, January 05, 2001 4:56 PM
> Subject: Re: Ozone & EJBs
>
>
> > On Fri, 05 Jan 2001, Jay Abraham wrote:
> > > How is Ozone intended to be used with Application
> > > Servers for EJB based J2EE applications? I notice
> > > that the J2EE framework seems to focus on RDBMS
> > > and ORDBMS datasources with hardly any mention of
> > > ODBMS datasources.
> >
> > I did check this with Mark Fleury of jBoss some time ago. And we did
> indeed
> > come to the conclusion that ozone is to container-ish itself to be
easily
> used
> > as a simple data source for a container. Since ozone provides RMI,
> > transactions, permissions already it seems that ozone itself could be a
> > container. But as you mentioned J2EE focuses on RDBMS. A benchmark of
EJB
> > compared to ozone could help to see if an OO container could provide any
> > advantages over a RDBMS container. Any EJB experiences out there?
> >
> >
> > Falko
> > --
> > ______________________________________________________________________
> > Falko Braeutigam mailto:falko@smb-tec.com
> > SMB GmbH http://www.smb-tec.com
> >
> >
--
______________________________________________________________________
Falko Braeutigam mailto:falko@smb-tec.com
SMB GmbH http://www.smb-tec.com