tainer |
**
> -Original Message-
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 04, 2004 10:55 AM
> To: 'OJB Users List'
> Subject: RE: [OTM] bi-directional 1:n not working (still not working)
>
> Rest of the test stuf
anks,
>
> Rob :)
>
> > -Original Message-
> > From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, 4 March 2004 11:48 a.m.
> > To: 'OJB Users List'
> > Subject: RE: [OTM] bi-directional 1:n not working
> >
> > Hi Oleg,
58 PM
> To: OJB Users List
> Subject: Re: [OTM] bi-directional 1:n not working
>
> On Wednesday 03 March 2004 16:50, Weaver, Scott wrote:
> > Removing these appears to have fixed this:
> >
> > auto-delete="true"
> > auto-update="true"
> > a
ROTECTED]>|
| Apache Jetspeed Portal Project |
| Apache Pluto Portlet Container |
**
> -----Original Message-
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 01, 2004 5:29 PM
> To: 'OJB Users List'
> Subj
I went a head segmented out my test cases to see if I could get some better
insight into what might be causing this. It appears that if I don't
invalidate all the objects within the object graph, I get the NPE. However,
if I make sure I have invalidated each of the objects in the graph,
everythin
tainer |
**
> -Original Message-
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 02, 2004 10:01 AM
> To: 'OJB Users List'
> Subject: RE: [OTM] invalidating cache causes NPE on next collection query
>
> I p
ortlet Container |
**
> -Original Message-
> From: Martin Kalén [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 02, 2004 9:13 AM
> To: OJB Users List
> Subject: Re: [OTM] invalidating cache causes NPE on next collection query
>
> Weaver, Scott wro
RE: [OTM] bi-directional 1:n not working
>
> I'm having a great day, so ignore the previous post. :P
>
> Is appId field in the PortletDefinitionImpl populated when you retrieve
> it (as opposed to the app reference)?
>
> Rob :)
>
>
>
> > -Or
I have a PortletApplicationDefinitionImpl contains n PortletDefinitionImpl
s. Each portlet definition has a reference back to its parent
PortletApplicationDefinition. PortletApplicationDefinitionImpl works
correctly and its collection of PortletDefinitionImpls is populated.
However, anytime I re
tainer |
**
> -Original Message-
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 01, 2004 2:16 PM
> To: 'OJB Users List'
> Subject: [OTM] invalidating cache causes NPE on next collection query
>
> After invalidating an object then trying to retriev
After invalidating an object then trying to retrieve the object via a query,
I get a NullPointerException. As a soon as remove the invalidation, the
test runs without exception. Any ideas?
org.apache.ojb.broker.PersistenceBrokerException:
java.lang.NullPointerException
at
org.apache.ojb.
Hi All,
Having some issues with the object caching in OJB.
Use case:
I need to make sure all objects come from the DB with in every test case
within my test suite.
A(1)-->(n)B
Using PB auto-update, auto-retrieve and auto-delete == true:
Start Tx.
Create A.
Create B.
Add B to A.
Commit tx.
; Sent: Wednesday, January 21, 2004 9:37 AM
> To: OJB Users List
> Subject: Re: SQL exceptions when using DList
>
> Hi Scott,
>
> Weaver, Scott wrote:
> > Hi All,
> >
> > I have never used the ODMG specific collection classes before. That
> being
> >
Hi All,
I have never used the ODMG specific collection classes before. That being
said, I just started using DList in some of my mappings.
Example:
However, when I do specify the DListImpl, I get this error when updating to
the DB:
Could not obtain next object: Can't build new s
ageableArrayList" as part
> of your
>
> That will solve your problem..
>
> Axel
> [EMAIL PROTECTED]
>
> -Original Message-
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 19, 2003 1:41 PM
> To: 'OJB Users List'
> Su
I have a non-decomposed relationship between object A and B. Using ODMG, if I remove
a B from the collection of B's in A and commit, not only is the relationship entry in
the indirection table deleted but so is B's record. Is there anyway to turn this off
as auto-delete="false" has no effect.
1. Should collections for 1:n relationships be updated automatically?
Example: I have a class "foo" which has a collection of "bars". The bar class has a
corresponding reference to its parent "foo." If I create a new bar, do a
bar.setFoo(fooInstance) and save that bar, should I expect fooIn
Is the OTM, layer stable enough to use in production, or should I just stick with ODMG
for now?
If yes, were is the most stable source: HEAD or rc4 from the apache download site?
Thanks,
||
| Scott T Weaver |
| <[E
>
> This did the trick. Thank you! Now I just have to
> understand WHY it did the trick :-)
>
> Bonnie MacKellar
> software engineer
> Mobius Management Systems, Inc.
> [EMAIL PROTECTED]
>
>
> > -Original Message-
> > From: Weaver, Scot
*
* Jakarta Jetspeed Portal Project *
* [EMAIL PROTECTED] *
*===*
> -Original Message-
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 07, 2003 5:21 PM
> To: 'OJB Users List'
> Subject: RE: Weblogic, threads, and
Some simple questions:
1. Where do you have the OJB resources (OJB.properties, repository.xml, etc.)? To
make things easy, they should be in the default package of your webapp's
WEB-INF/classes directory.
2. Where is your OJB jar? For the most predictable results, it should be in your
weba
> Sent: Thursday, July 03, 2003 1:04 PM
> To: OJB Users List
> Subject: Re: basic question: update with odmg api
>
> Hi again Scott,
>
> It only works for a single instance. So the traversal of the object
> graph must be done by the user :-(
>
> cheers,
> Thom
Have you looked at ODMG yet? I think the ODMG collection implementations provide this
type of functionality.
*===*
* Scott T Weaver *
* Jakarta Jetspeed Portal Project *
* [EMAIL PROTECTED] *
*===*
> -O
Thomas,
Does this trick work for the entire object graph or just the top level object?
Thanks,
*===*
* Scott T Weaver *
* Jakarta Jetspeed Portal Project *
* [EMAIL PROTECTED] *
*===*
> -Original Message
Try using this cache instead of the default one:
org.apache.ojb.broker.cache.MetaObjectCachePerClassImpl
It allows you to set a class's cache to "null" effectively preventing instance caching
of that specific type.
hth,
*===*
* Scott T Weaver
This works for me:
// 1. Start the transaction
TransactionImpl tx = (TransactionImpl) odmg.newTransaction();
// 2. remove object from the OJB cache
PersistenceBroker pb = tx.getBroker();
pb.removeFromCache(object);
tx.begin();
// 3. retreive a "stale" version of this obje
cases for FieldConversions on PrimaryKey fields, but I think
> no
> tests for 1:n plus backreference + FieldConversion on foreignkey.
>
> Can you modify your setup to test without fieldconversion?
>
> cheers,
> thomas
>
>
> > -Original Message-
> > Fro
or 1:n plus backreference + FieldConversion on foreignkey.
>
> Can you modify your setup to test without fieldconversion?
>
> cheers,
> thomas
>
>
> > -Original Message-
> > From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> > Sent: Monday, June 30, 200
rt3a.getArticleName());
> }
> catch (Throwable t)
> {
> System.out.println(t.getMessage());
> t.printStackTrace();
> fail(t.getMessage());
> }
> }
>
> Ar
I have been having the same issue with 1:n mappings were n's FK is not getting updated
if "n" has a reference-descriptor back to "1".
*===*
* Scott T Weaver *
* Jakarta Jetspeed Portal Project *
* [EMAIL PROTECTED] *
*==
I asked this about a week ago and received no response so I will try again as seems to
be a simple question.
I have a 1:n mapping like this. BasePortletApplicationDefinition has a number of
portlets assoc. with and each portlet has a reference back to its parent application.
The problem I am e
In ODMG, I have a 1:1 relationship between object A and object B. I retrieve object A
using PB. I proceed to make a change to object B that was materialized along with
object A. I then pass object A to a method that contains the code below, update(A).
In rc3 object B's changes were made pers
)
>
> > -Original Message-
> > From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, June 24, 2003 5:24 PM
> > To: 'OJB Users List'
> > Subject: RE: extents and mapping inheritence
> >
>
ors avaible
> to extents.
>
>
> On Tue, 2003-06-24 at 10:17, Weaver, Scott wrote:
> > I was looking at the DescriptorRepository class and I feel I could
> easily patch it to walk the inheritance tree for "invisible" mappings via
> i
of field- and relationship-descriptors.
> > but there are some discussions going on regarding this feature.
> >
> > hth
> > jakob
> >
> > Weaver, Scott wrote:
> >
> > >Is there anyway to have a class-descriptor inherit the mappings of a
> pre
2003 1:47 AM
> To: OJB Users List
> Subject: Re: extents and mapping inheritence
>
> Hi Scott,
>
> Weaver, Scott wrote:
> > Is there anyway I can remove the mapping for B entirely. It
> > implements the interface AB and extends A. That should be good
> > eno
nal Message-
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 3:21 PM
> To: 'OJB Users List'
> Subject: RE: extents and mapping inheritence
>
> Thanks Jakob.
>
> I Guess I'll have to use ENTITY references instead. Do you
relationship-descriptors.
> but there are some discussions going on regarding this feature.
>
> hth
> jakob
>
> Weaver, Scott wrote:
>
> >Is there anyway to have a class-descriptor inherit the mappings of a
> previously defined class-descriptor?
> >
>
Is there anyway to have a class-descriptor inherit the mappings of a previously
defined class-descriptor?
Example:
AB is an interface. A implements AB and B extends A.
The question: How can define the class-descriptor for B without having to copy the
identical mappi
naling took my interest. So how do you manage to use OJB
> without having to use transactions? Do you use the ODMG API?
>
> Thanks,
> Mete
>
> -- Original Message --
> From: "Weaver, Scott" <[EMAIL PROTECTED]>
> Reply-
BC transactions.
> Thus there is a switch in OJB.properties to ignore AutoCommitExceptions
> related to this problem.
> Maybe this could work for DB2/400 too?
>
> cheers,
> Thomas
>
> Weaver, Scott wrote:
> > For commitment control, I am almost positive journaling is required
This is a strange one, or maybe I'm just being ignorant.
STEP 1: I define a collection descriptor within PortletApplactionDefinition to the
PortletDefinition. Everything runs as expected with the mapping below. Adding
PortletDefinitions to the "portlets" collection in PortletApplication corr
For commitment control, I am almost positive journaling is required. I highly suggest
you take Jack's suggestion use Collections as opposed to standard AS/400 libraries. I
know that's a crappy, since most of us using OJB to connect to the AS400 are doing so
to hook into legacy databases that w
I use a "tinyint" in MySQL but you could use any INTEGER definition in your DDL
depending on your RDBMS.
0=false
1=true
This is what my mapping looks like:
Scott
> -Original Message-
> From: Brian McCallister [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 10:34 AM
> T
44 matches
Mail list logo
