John, This is correct behavior. The entry id is an array and in a join there is no entry id because nothing is actually created. It is the responsibilty of the workflow (filters) to create the underlying records making up the join.
I have noticed this in the c api. Cheers Ben >----- ------- Original Message ------- ----- >From: John Baker ><[EMAIL PROTECTED]> >To: [email protected] >Sent: Wed, 25 Oct 2006 14:34:09 > >Hello, > >Consider the following: > > EntryFactory entryMan = >EntryFactory.getFactory(); > Entry entry = (Entry)entryMan.newInstance(); > entry.setContext(serverUser); > entry.setEntryItems(items); > entry.setSchemaID(new NameID(schema)); > entry.create(); > >System.out.println(entry.getEntryID().toString()); > >Should create a new Entry and output the EntryID. >This works fine, unless the >entry was created in a Join Form, in which case an >empty string (not null) is >output. > >I've tested with the v7.0 API (patch 1 & 2). > >Has anyone else seen this behaviour? Is it really a >bug or just incorrect use >of the API? > > >John > >Java System Solutions : >http://www.javasystemsolutions.com > >___________________________________________________ >____________________________ >UNSUBSCRIBE or access ARSlist Archives at >http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
