using a different entity (created a new entity which is replica of employee and named manager) solves the issue. looks like LCDS follows a simple strategy: one entity for each assembler, no reuse.
-Rajeev On Thu, May 7, 2009 at 12:36 PM, Rajeev Goel <[email protected]> wrote: > hi All, > > I am using LCDS 2.6 with Flex SDK 3.2. > > One of my existing assemblers (say EmployeeAssembler) is using entity > object called Employee. > Is it possible to have another assembler (say ManagerAssembler) which also > uses Employee object ? > > data-management-config.xml: > > <destination id="*employeeAssembler*"> > <adapter ref="java-dao" /> > <properties> > <source>employeeAssemblerBean</source> > <factory>spring</factory> > <metadata> > <identity property="*uniqueId*" /> > <one-to-many property="childList" destination="employeeAssembler" > read-only="true"/> > </metadata> > </properties> > </destination> > <destination id="*managerAssembler*"> > <adapter ref="java-dao" /> > <properties> > <source>managerAssemblerBean</source> > <factory>spring</factory> > <metadata> > <identity property="*uniqueId*" /> > <one-to-many property="childList" destination="*managerAssembler*" > read-only="true"/> > </metadata> > </properties> > </destination> > > The primary key attribute is "uniqueId" and of type string. > To prevent manager assembler from getting confused, code adds a prefix to > the unique id for differentiation. this way uniqueId should never clash. > > Issue is that server pushes on ManagerAssembler are not showing up on > client. Also its uid is mangled (sample value: > 09C348F9-3DEB-45F0-33F4-19D033896417). > Usually uid contans assembler's name. > > Could someone point me to right direction ? > > thanks, > Rajeev > >
