RE: Setup Question.
I discovered that by experience. I gave up as I ran into a bug with the implementation. I then found an article which used the PersistenceBroker (instead of the PersistenceManager) and it worked fine. Since I am not very familiar with this framework, what is the difference between these classes? Cheers, Philip. -Original Message- From: Martin Kalén [mailto:[EMAIL PROTECTED] Sent: March 31, 2005 10:53 PM To: OJB Users List Subject: Re: Setup Question. Philip Denno wrote: Actually, I found the jar file, but now I get NullPointerExceptions. Did you check the JDO tutorial? http://db.apache.org/ojb/docu/tutorials/jdo-tutorial.html Regards, Martin P.S. JDO support in OJB is not yet production-ready, or as stated on the homepage: A full JDO implementation is scheduled for OJB 2.0 - 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]
Re: RE: Setup Question.
Ich bin bis 01.05.2005 nicht zu erreichen. In dringenden Fällen kontaktieren Sie bitte: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: RE: Setup Question.
Ich bin bis 01.05.2005 nicht zu erreichen. In dringenden Fällen kontaktieren Sie bitte: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: RE: Setup Question.
Ich bin bis 01.05.2005 nicht zu erreichen. In dringenden Fällen kontaktieren Sie bitte: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: RE: Setup Question.
Ich bin bis 01.05.2005 nicht zu erreichen. In dringenden Fällen kontaktieren Sie bitte: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: Re: RE: Setup Question.
Ich bin bis 01.05.2005 nicht zu erreichen. In dringenden Fällen kontaktieren Sie bitte: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: Re: Re: RE: Setup Question.
Ich bin bis 01.05.2005 nicht zu erreichen. In dringenden Fällen kontaktieren Sie bitte: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: Re: Re: Re: RE: Setup Question.
Ich bin bis 01.05.2005 nicht zu erreichen. In dringenden Fällen kontaktieren Sie bitte: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Re: Re: Re: Re: Re: RE: Setup Question.
Dear Mr/Ms List Admin - could you please remove this address from the mailing list. It's beginning to get on my nerves - I don't think I could put up with it until the beginning of may ! (Especially since I don't get a holiday until Christmas...) Cheers, Charles. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 01 April 2005 17:15 To: ojb-user@db.apache.org Subject: Re: Re: Re: Re: Re: Re: RE: Setup Question. Ich bin bis 01.05.2005 nicht zu erreichen. In dringenden Fällen kontaktieren Sie bitte: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ HPD Software Ltd. - Helping Business Finance Business Email terms and conditions: www.hpdsoftware.com/disclaimer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Problems with PersistenceBrokerSyncImpl
Hi Armin Should it not be hidden from the user of ojb. With this solution A user of ojb has to implement two different db layers: one for managed Environment and one for not managed environment. What happens if I inherit from your PersistenceBrokerFactorySyncImpl class And overwrite the begin, abort and commit Transaction function and implement This functions as empty function? Regards Matthias -Ursprüngliche Nachricht- Von: Armin Waibel [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. März 2005 20:42 An: OJB Users List Betreff: Re: Problems with PersistenceBrokerSyncImpl Hi Matthias, [EMAIL PROTECTED] wrote: Hello We use OJB in a websphere z/OS environment. If I set the PersistenceBrokerFactoryClass to PersistenceBrokerSyncImpl as it is recommended in the documentation I get following error if I try to insert, update or delete some thing: Exception data: java.lang.UnsupportedOperationException: In managed environments only JTA transaction demarcation allowed at org.apache.ojb.broker.core.PersistenceBrokerFactorySyncImpl$Persistenc eBroke rSyncImpl.beginTransaction() In managed environments the tx handling/demarcation is done by JTA, so it's no longer allowed to use the PB-tx demarcation. If I use the PersistenceBrokerFactoryDefaultImpl every thing works 'fine' (only the broker get out of synch with the container one time per day). If you use websphere as simple servlet engine without distributed tx, there is no need to use the JTA integration supported by PBFSyncImpl. If you use JTA it's mandatory to use PBFSyncImpl and JTA-tx demarcation. regards, Armin Can some one Help? Matthias Roth Bundesamt für Informatik und Telekommunikation BIT Office fédéral de l'informatique et de la télécommunication OFIT Ufficio federale dell'informatica e della telecomunicazione UFIT Monbijoustrasse 74, CH-3003 Bern Tel.++41 (0)31 325 84 68 Mobile++41 (0)79 307 45 29 Fax++41 (0)31 325 97 54 [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.bit.admin.ch/ - 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]
Re: AW: Problems with PersistenceBrokerSyncImpl
Matthias Roth wrote: Hi Armin Should it not be hidden from the user of ojb. With this solution A user of ojb has to implement two different db layers: one for managed Environment and one for not managed environment. What happens if I inherit from your PersistenceBrokerFactorySyncImpl class And overwrite the begin, abort and commit Transaction function and implement This functions as empty function? This could solve your problem, but this class is really complex. You have to extend inner class PBSyncHandle an override the methods. I will have a look at it, maybe I can integrate such a solution in the upcoming bug-fix release. regards, Armin Regards Matthias -Ursprüngliche Nachricht- Von: Armin Waibel [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. März 2005 20:42 An: OJB Users List Betreff: Re: Problems with PersistenceBrokerSyncImpl Hi Matthias, [EMAIL PROTECTED] wrote: Hello We use OJB in a websphere z/OS environment. If I set the PersistenceBrokerFactoryClass to PersistenceBrokerSyncImpl as it is recommended in the documentation I get following error if I try to insert, update or delete some thing: Exception data: java.lang.UnsupportedOperationException: In managed environments only JTA transaction demarcation allowed at org.apache.ojb.broker.core.PersistenceBrokerFactorySyncImpl$Persistenc eBroke rSyncImpl.beginTransaction() In managed environments the tx handling/demarcation is done by JTA, so it's no longer allowed to use the PB-tx demarcation. If I use the PersistenceBrokerFactoryDefaultImpl every thing works 'fine' (only the broker get out of synch with the container one time per day). If you use websphere as simple servlet engine without distributed tx, there is no need to use the JTA integration supported by PBFSyncImpl. If you use JTA it's mandatory to use PBFSyncImpl and JTA-tx demarcation. regards, Armin Can some one Help? Matthias Roth Bundesamt für Informatik und Telekommunikation BIT Office fédéral de l'informatique et de la télécommunication OFIT Ufficio federale dell'informatica e della telecomunicazione UFIT Monbijoustrasse 74, CH-3003 Bern Tel.++41 (0)31 325 84 68 Mobile++41 (0)79 307 45 29 Fax++41 (0)31 325 97 54 [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.bit.admin.ch/ - 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]
Re: AW: Problems with PersistenceBrokerSyncImpl
Armin Waibel wrote: Matthias Roth wrote: Hi Armin Should it not be hidden from the user of ojb. With this solution A user of ojb has to implement two different db layers: one for managed Environment and one for not managed environment. What happens if I inherit from your PersistenceBrokerFactorySyncImpl class And overwrite the begin, abort and commit Transaction function and implement This functions as empty function? This could solve your problem, but this class is really complex. You have to extend inner class PBSyncHandle an override the methods. sorry, forget to note: and override methods which instantiate PBSyncHandle Armin I will have a look at it, maybe I can integrate such a solution in the upcoming bug-fix release. regards, Armin Regards Matthias -Ursprüngliche Nachricht- Von: Armin Waibel [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. März 2005 20:42 An: OJB Users List Betreff: Re: Problems with PersistenceBrokerSyncImpl Hi Matthias, [EMAIL PROTECTED] wrote: Hello We use OJB in a websphere z/OS environment. If I set the PersistenceBrokerFactoryClass to PersistenceBrokerSyncImpl as it is recommended in the documentation I get following error if I try to insert, update or delete some thing: Exception data: java.lang.UnsupportedOperationException: In managed environments only JTA transaction demarcation allowed at org.apache.ojb.broker.core.PersistenceBrokerFactorySyncImpl$Persistenc eBroke rSyncImpl.beginTransaction() In managed environments the tx handling/demarcation is done by JTA, so it's no longer allowed to use the PB-tx demarcation. If I use the PersistenceBrokerFactoryDefaultImpl every thing works 'fine' (only the broker get out of synch with the container one time per day). If you use websphere as simple servlet engine without distributed tx, there is no need to use the JTA integration supported by PBFSyncImpl. If you use JTA it's mandatory to use PBFSyncImpl and JTA-tx demarcation. regards, Armin Can some one Help? Matthias Roth Bundesamt für Informatik und Telekommunikation BIT Office fédéral de l'informatique et de la télécommunication OFIT Ufficio federale dell'informatica e della telecomunicazione UFIT Monbijoustrasse 74, CH-3003 Bern Tel.++41 (0)31 325 84 68 Mobile++41 (0)79 307 45 29 Fax++41 (0)31 325 97 54 [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.bit.admin.ch/ - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Problems with PersistenceBrokerSyncImpl
more elegant is to: - extend PersistenceBrokerFactorySyncImpl - extend inner class PersistenceBrokerSyncImpl and override beginTx, ... methods to noop - override PersistenceBrokerFactorySyncImpl.wrapBrokerWithPoolingHandle and return the extended PersistenceBrokerSyncImpl class regards, Armin Armin Waibel wrote: Armin Waibel wrote: Matthias Roth wrote: Hi Armin Should it not be hidden from the user of ojb. With this solution A user of ojb has to implement two different db layers: one for managed Environment and one for not managed environment. What happens if I inherit from your PersistenceBrokerFactorySyncImpl class And overwrite the begin, abort and commit Transaction function and implement This functions as empty function? This could solve your problem, but this class is really complex. You have to extend inner class PBSyncHandle an override the methods. sorry, forget to note: and override methods which instantiate PBSyncHandle Armin I will have a look at it, maybe I can integrate such a solution in the upcoming bug-fix release. regards, Armin Regards Matthias -Ursprüngliche Nachricht- Von: Armin Waibel [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. März 2005 20:42 An: OJB Users List Betreff: Re: Problems with PersistenceBrokerSyncImpl Hi Matthias, [EMAIL PROTECTED] wrote: Hello We use OJB in a websphere z/OS environment. If I set the PersistenceBrokerFactoryClass to PersistenceBrokerSyncImpl as it is recommended in the documentation I get following error if I try to insert, update or delete some thing: Exception data: java.lang.UnsupportedOperationException: In managed environments only JTA transaction demarcation allowed at org.apache.ojb.broker.core.PersistenceBrokerFactorySyncImpl$Persistenc eBroke rSyncImpl.beginTransaction() In managed environments the tx handling/demarcation is done by JTA, so it's no longer allowed to use the PB-tx demarcation. If I use the PersistenceBrokerFactoryDefaultImpl every thing works 'fine' (only the broker get out of synch with the container one time per day). If you use websphere as simple servlet engine without distributed tx, there is no need to use the JTA integration supported by PBFSyncImpl. If you use JTA it's mandatory to use PBFSyncImpl and JTA-tx demarcation. regards, Armin Can some one Help? Matthias Roth Bundesamt für Informatik und Telekommunikation BIT Office fédéral de l'informatique et de la télécommunication OFIT Ufficio federale dell'informatica e della telecomunicazione UFIT Monbijoustrasse 74, CH-3003 Bern Tel.++41 (0)31 325 84 68 Mobile++41 (0)79 307 45 29 Fax++41 (0)31 325 97 54 [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.bit.admin.ch/ - 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] - 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]
