I believe the easiest solution is to import the core classes into your project and customize them there.
http://appfuse.org/display/APF/AppFuse+Core+Classes If that doesn't work for you, full-source your project and customize to your heart's content. Matt On Sun, Jun 1, 2008 at 3:45 PM, mschipperheyn <[EMAIL PROTECTED]> wrote: > > Hi, > > I have an implementation with an independent user object. I basically don't > use the Appfuse User and Role model. In the process of migration I ran into > a problem with my custom UserDetails service. Using the default > implementation I get a "More than one UserDetailsService registered. Please > use a specific Id in your configuration". I'm sure I can work around this at > the sacrifice of the short xml configuration. > > I would like to suggest to move the User and Role classes and associated > generated code to the implementation directories of the generated > application as opposed to storing them in the appfuse jars. This gives more > flexibility for users who don't want to do a full source but just don't want > the out of the box pojo's and the limitations that come with them: > * not being able to use bean ids like user, userManager for your own user > beans > * loadUserDetails conflicts. > > It also feels like a more natural separation of concerns. > > Kind regards, > > Marc > -- > View this message in context: > http://www.nabble.com/UserDao-in-the-way-on-spring-security-tp17590739s2369p17590739.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
