As far as I know, the parameters to "create()" just have to be serializable, and do not have to directly correspond to the fields of the bean. I see nothing wrong with sending a Collection or a bean of some sort (like a DTO). However, I'm not sure I see much point to this. You either have lots of parameters, or you have a single object with a constructor with lots of parameters. It's good to use DTOs or Collections to eliminate multiple round trips for setters/getters, but I don't where there'd be any performance difference with this approach.
> -----Original Message----- > From: Mike Landy [mailto:[EMAIL PROTECTED]] > > Hello, > > Are there any restrictions to put e.g. ArrayList or a own > class which contains member variables as parameters to > create/ejbCreate()-method? > > I'm using CMP bean having lot's of parameters. I would like "wrap" > them to under a wrapper class. > > Environment is EJB 1.1 and IBM WSAD 4.x. ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
