No sorry... no OJB there :o).

It would be nice to produce an OJB version, but my main focus was always
keeping everything to a single WAR and making that WAR as small as
possible... so it's hand -coded SQL in one class. The class creates the
database tables as necessary on startup.

> -----Original Message-----
> From: Thomas Mahler [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 17 October 2002 8:39 a.m.
> To: OJB Users List
> Subject: Re: [General] OJB in use page
> 
> 
> Hi Gareth,
> 
> Gareth Cronin wrote:
> > Wiki sounds all good to me... I just happen to 
> write/maintain an open source
> > JSP/Servlet one :-):
> > http://veryquickwiki.croninsolutions.com
> 
> Cool ! I'm looking for a *simple* tomcat based wiki for a 
> long time now! 
>   I will check out your stuff!
> I see that you also support MySql for persistence. Are you also using 
> OJB in this setup?
> This would be a nice show-case for OJB!
> 
> IMO a wiki is the best solution for a user group site, as there is no 
> centralized management necessary. Everybody can post his/her 
> experience 
> questions without filtering through "OJB headquarters".
> 
> We only have to find a place to host this wiki !
> 
> cheers,
> Thomas
> 
> > 
> > G
> > 
> > 
> >>-----Original Message-----
> >>From: Mahler Thomas [mailto:[EMAIL PROTECTED]]
> >>Sent: Thursday, 17 October 2002 2:53 a.m.
> >>To: 'OJB Users List'
> >>Subject: AW: [General] OJB in use page
> >>
> >>
> >>Hi Gareth,
> >>
> >>
> >>>Just a suggestion... I notice that there are a large number 
> >>
> >>of regular
> >>
> >>>contributors /users on this list who like me are working with 
> >>>real solutions
> >>>using OJB. Some questions I have from time to time are so 
> >>>specific that it
> >>>would nice if I could direct them at someone or a group of 
> >>>people who I know
> >>>have had similar experiences. 
> >>>
> >>>It would be great if there was some facility on the OJB 
> >>>website where users
> >>>of OJB could register what they're doing with it, specific 
> >>
> >>challenges
> >>
> >>>they've faced and solved etc, and some optional contact 
> >>>details where other
> >>>users could email and ask them specific questions on one of 
> >>>these specific
> >>>areas: a knowledge base if you like. 
> >>
> >>Maybe it could be organized as a WIKI, this would reduce management
> >>overhead, as users could edit pages themselves.
> >> 
> >>
> >>>I know for one that I'd be happy to receive specific 
> >>>questions about some of
> >>>the things I've dealt with like deeply nested relationships, 
> >>>generation of
> >>>mapping descriptors, SQL and code from Rose models, and 
> >>>developing visual
> >>>tools to help with repetitive OJB-oriented tasks etc.
> >>>
> >>>This would also of course provide a place to point people to 
> >>>who like to ask
> >>>the old "is OJB OK for real projects" question... it would in 
> >>>effect be a
> >>>list of projects using OJB and could include details like the 
> >>>size of the
> >>>project, number of deployments, estimated time savings thanks 
> >>>to the tool
> >>>etc.
> >>
> >>I like your idea! 
> >>We have a page links.html (it is not yet on the website, but 
> >>you can find it
> >>in the doc folder of the distribution) that contains a lot of 
> >>useful links.
> >>
> >>We could extend this page to collect informations as you are 
> >>suggeting. 
> >>Disadvantage: Such a page can only be edited by commiters. 
> >>Thus it maybe a
> >>bit too static...
> >>
> >>IMO the best thing would be to have a wiki (like
> >>http://www.c2.com/cgi/wiki?ObjectRelationalBridge).
> >>Maybe we can start to build up this kind of knowledgebase there?!
> >>
> >>cheers,
> >>Thomas
> >>
> >>
> >>
> >>>Cheers,
> >>>
> >>>G.
> >>>
> >>>---------------------------------------------
> >>>Gareth Cronin
> >>>Analyst/Programmer
> >>>Kiwiplan NZ Ltd: http://www.kiwiplan.com
> >>>Ph (64 9) 2727622 x854
> >>>
> >>>--
> >>>To unsubscribe, e-mail:   
> >>><mailto:[EMAIL PROTECTED]>
> >>>For additional commands, e-mail: 
> >>><mailto:[EMAIL PROTECTED]>
> >>>
> >>>
> >>--
> >>To unsubscribe, e-mail:   
> >><mailto:[EMAIL PROTECTED]>
> >>For additional commands, e-mail: 
> >><mailto:[EMAIL PROTECTED]>
> >>
> > 
> > --
> > To unsubscribe, e-mail:   
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 
> 
> 



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

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

Reply via email to