I've tracked the error down to:
public PersistenceConfiguration(ComponentContainer container,
PersistenceConfigurationDescriptor pcd)
{
this.pcd = pcd;
this.ojb = (OJB) container.getInstance(OJB.class);
subContainer = container.createChildContainer();
subContainer.setSingletonInstance(this);
subContainer.setSingletonInstance(pcd.getJdbcConnectionDescriptor());
the call to pcd.getJdbcConnectionDescriptor() is returning null...I must
be configuring things wrong...any suggestions? If this is a bug, let me
know hov you want it fixed and I'll submit a patch.
On Sat, 2005-07-02 at 15:54 +0200, Thomas Dudziak wrote:
> On 7/2/05, Adam Jenkins <[EMAIL PROTECTED]> wrote:
> > Sorry, meant to reply to list for posterity...hit wrong button...repost
> > below:
> >
> > Thanks. So how do we swap JdbcConnectionDescriptors now? I'm used to
> > dealing with metadata manager (I have a completely new descriptor
> > pointing to a new database that I want to configure at runtime)
>
> In 1.1, we introduced with the PersistenceConfiguration a new
> indirection level that allows to configure JCDs and models more easily
> (though that part is not finished yet). In your case, you should
> create a new PersistenceConfigurationDescriptor and add it to the
> metadata manager via the addPersistenceConfiguration method. Then you
> can access it via the PBKey as before.
>
> Tom
>
> ---------------------------------------------------------------------
> 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]
