Hi again,

> Hi Thomas,
> 
> For your answer to question 1: I was afraid of that. And 
> about question 2:
> the file 'tutorial4.jdo' has several tags <extension 
> vendor-name="obj" ...
> />. Thus I was under the impression that several 
> vendor-extensions were
> already supported by OJB.

That's a bit misleading. At some point in time we already had experimental
support for JDO file with OJB specific vendor extensions, but we dropped it
for the time being. 

> 
> I guess I better focus on switching to the OBJ / ODMG API 
> proper for the
> moment!

Yes, that's what I'm still recommending in the FAQ for production level
applications.

cheers,
thomas

> Thanks,
> 
> --Tim van der Leeuw 
> 
> -----Original Message-----
> From: Mahler Thomas [mailto:[EMAIL PROTECTED]
> Sent: dinsdag 10 juni 2003 13:27
> To: 'OJB Users List'
> Subject: RE: 2 Questions about JDO in OJB
> 
> 
> Hi Tim,
> 
> 
> > I have 2 questions about OJB's JDO:
> > - It's dependant on the SUN JDO-RI. To what extent does this 
> > impose a legal
> > problem for a commercial deployment of an application?
> 
> I'm not a lawyer. But if I understand the SUN JDO-RI licence 
> file correctly,
> you are not allowed to use it for a commercial deployment of 
> an application.
>  
> > - What vendor-extensions does it know in the metadata.jdo?
> 
> Currently none. the jdo file is needed for the enhancer only.
> All mapping information is still taken from OJB's repository.xml
> 
> > 
> > Regards,
> > 
> > --Tim van der Leeuw
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to