Hi Hans,
No Mandragora doesn't need to know the ojb_blank structure.
I think you have to add this to your web.xml
<servlet>
<servlet-name>QuartzInitializer</servlet-name>
<display-name>Quartz Initializer Servlet</display-name>
<servlet-class>org.quartz.ee.servlet.QuartzInitializerServlet
</servlet-class>
<load-on-startup>1</load-on-startup>
<init-param>
<param-name>shutdown-on-unload</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>start-scheduler-on-load</param-name>
<param-value>true</param-value>
</init-param>
</servlet>
That's why the ServiceLocator instance always the Quartz Scheduler Service.
I will modify it to not instance it if not explicitly invoked
On 9/12/07, Hans Novak <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> i have try your project. I have merged it with the ojb_blank project.
> (the jar file into the lib dir, the properties file in project root.
>
>
> when i do a
>
> BD bd =
> ServiceLocator.getInstance
> ().getManagerBD("BDFactoryDefaultClass","StandardBDDefaultClass");
>
> i get this error:
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/quartz/SchedulerException
> at de.repcom.osfaktura.aStartups.Test.machWas(Test.java:22)
> at de.repcom.osfaktura.aStartups.Test.<init>(Test.java:15)
> at de.repcom.osfaktura.aStartups.Test.main(Test.java:12)
>
> Maybe mandragora need some more infos about the ojb_blank structure
> (like the paths where the reposities are and so on)
>
> Hans
>
>
> Alessandro Colantoni schrieb:
> > Hi!
> > Mandragora is not part of the ojb project, but up now it is based on it
> and
> > use Ojb Persistence broker as persistence engine.
> > It is just a small project to provide you lots of the must common
> business
> > and Dao methods.
> > Just have a look. I hope improve documentation soon. Anyway it provides
> you
> > a very easy mechanism based on Factory pattern to write and use your
> > methods.
> > If you download it you have these methods available, and can add yours
> to
> > have a library very easy to reuse, and if you want, to share
> > The future? I'm the only one in the team up now, and I will give you all
> > support i can.
> > Anyway don't look at it as a big and complicate project that if a day
> close
> > you get in trouble.
> > Mandragora want just to be a set of reusable business and Dao methods
> (based
> > on ojb).
> > For example I had the same problem of you with trees, or collection. You
> > solved it writing your own method to delete object in the database not
> > present in your reference collection. I solved it with a generic method,
> so
> > I will use it again and again.
> > You can write other methods and sharing
> >
> >
> > On 9/12/07, Hans Novak <[EMAIL PROTECTED]> wrote:
> >
> >> aha .....!?
> >> Hmmmm... is the "mandragora" Project a part of the ojb project ?
> >> How looks ist for the future with it ?
> >> I ask this, because, i dontwant to use it and sometime it will be
> >> cancel'ed.
> >>
> >>
> >> Hans
> >>
> >>
> >>
> >> Alessandro Colantoni schrieb:
> >>
> >>> Hi
> >>> Yes it is normal.
> >>> When you have a main object that has a collection attribute, Ojb works
> >>>
> >> just
> >>
> >>> on value objects that are in the collection.
> >>>
> >>> I developed a framework based on Ojb called mandragora (
> >>> http://mandragora.sourceforge.net) that provides lots of method that
> can
> >>> help.
> >>>
> >>> The methods updateCollectionReference, updateCollectionReferences and
> >>> updateCreateTrees do just what you need
> >>>
> >>> http://mandragora.sourceforge.net/referenceguide/bd-api-guide.html
> >>>
> >>> Have a look. Documentation is very poor but in the following days I
> will
> >>> upload something more
> >>>
> >>> I hope this can help
> >>>
> >>> Best Regards
> >>> Alessandro
> >>>
> >>>
> >>>
> >>> On 9/12/07, Alessandro Colantoni <[EMAIL PROTECTED]>
> wrote:
> >>>
> >>>
> >>>> On 9/12/07, Hans Novak <[EMAIL PROTECTED]> wrote:
> >>>>
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> i am not shure, but is ist correct when i have an object, witch is a
> >>>>> tree of some other objects (colletions) and i delete a part of the
> >>>>>
> >> tree
> >>
> >>>>> and then store the hole object (tree) - in the database the deleted
> >>>>> object will also be deleted ?
> >>>>>
> >>>>> Everything works fine, when i store or update the object, but not
> when
> >>>>>
> >> i
> >>
> >>>>> delete.
> >>>>> The deleted part of the object will not be deleted in the database.
> I
> >>>>> can remove it by hand, when i run a remove.object (the part of the
> >>>>> tree) and then store the (changed) tree.
> >>>>>
> >>>>> Is this normal ?
> >>>>>
> >>>>>
> >>>>> Hans
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >> --
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------
> >>
> >>
> >> Repcom Datentechnik GmbH <http://www.repcom.de/>
> >> Hauptstr. 103 - 63110 Rodgau
> >> Tel. 06106-638081
> >> Fax 06106-638083
> >> Steuernummer 03524225030
> >> Ust-IdNr.: DE151061445 Bankverbindung:
> >> Deutsche Bank Dietzenbach,
> >> Kto. 1516400 BLZ 50570024 , Inhaber Repcom Datentechnik
> >>
> >> Internationale Zahlungen
> >> Kto. 1510304 BLZ 50570024, Inhaber J. Novak
> >> de54505700240151030400 BIC deutdedb538
> >> Öffnungszeiten:
> >> Mo.-Fr. 14.00-18.30 Uhr
> >> Tel. Hotline Mo.-Fr. 10.00-18.30 Uhr
> >> Sie finden uns hier: Anfahrtsbeschreibung
> >> <http://www.repcom.de/images/repcom/anfahrt.jpg>
> >> Messenger
> >> Yahoo
> >> ICQ
> >> : bforpc
> >> : 174290900
> >> MSN
> >> Skype
> >> : [EMAIL PROTECTED]
> >> : bforpc
> >>
> >> Unsere primären Web Adressen www.repcom.de <http://www.repcom.de/>
> >> und www.dataportal.de <http://www.dataportal.de/>
> >>
> >> Unsere AGB's finden Sie hier
> >> <http://www.repcom.de/index.php?main_page=conditions>.
> >>
> >> Vertraulichkeitshinweis
> >> Der Inhalt dieser E-Mail, einschliesslich etwaiger Anhäge, ist
> >> vertraulich und nur für den oben bezeichneten Adressaten bestimmt. Wenn
> >> Sie nicht dieser Adressat oder dessen Empfangsvertreter sein sollten,
> so
> >> beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung,
> >> Vervielfältigung, Weitergabe oder eines anderen Gebrauchs des Inhalts
> >> nicht gestattet ist und gesetzeswidrig sein kann. Bitte informieren Sie
> >> in diesem Fall unverzglich den Absender und vernichten Sie dieses
> E-Mail
> >> nebst Anhängen und aller Kopien.
> >>
> >>
> >>
> ------------------------------------------------------------------------
> >>
> >>
> >>
> >>
> >
> >
>
> --
>
>
>
> ------------------------------------------------------------------------
>
>
> Repcom Datentechnik GmbH <http://www.repcom.de/>
> Hauptstr. 103 - 63110 Rodgau
> Tel. 06106-638081
> Fax 06106-638083
> Steuernummer 03524225030
> Ust-IdNr.: DE151061445 Bankverbindung:
> Deutsche Bank Dietzenbach,
> Kto. 1516400 BLZ 50570024 , Inhaber Repcom Datentechnik
>
> Internationale Zahlungen
> Kto. 1510304 BLZ 50570024, Inhaber J. Novak
> de54505700240151030400 BIC deutdedb538
> Öffnungszeiten:
> Mo.-Fr. 14.00-18.30 Uhr
> Tel. Hotline Mo.-Fr. 10.00-18.30 Uhr
> Sie finden uns hier: Anfahrtsbeschreibung
> <http://www.repcom.de/images/repcom/anfahrt.jpg>
> Messenger
> Yahoo
> ICQ
> : bforpc
> : 174290900
> MSN
> Skype
> : [EMAIL PROTECTED]
> : bforpc
>
> Unsere primären Web Adressen www.repcom.de <http://www.repcom.de/>
> und www.dataportal.de <http://www.dataportal.de/>
>
> Unsere AGB's finden Sie hier
> <http://www.repcom.de/index.php?main_page=conditions>.
>
> Vertraulichkeitshinweis
> Der Inhalt dieser E-Mail, einschliesslich etwaiger Anhäge, ist
> vertraulich und nur für den oben bezeichneten Adressaten bestimmt. Wenn
> Sie nicht dieser Adressat oder dessen Empfangsvertreter sein sollten, so
> beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung,
> Vervielfältigung, Weitergabe oder eines anderen Gebrauchs des Inhalts
> nicht gestattet ist und gesetzeswidrig sein kann. Bitte informieren Sie
> in diesem Fall unverzglich den Absender und vernichten Sie dieses E-Mail
> nebst Anhängen und aller Kopien.
>
>
> ------------------------------------------------------------------------
>
>
>
