Thanks for suggestion Will! In this moment we're studying a solution; I post update here at the end of work.
Regards, Mauro > > We've done this a few times. What we've done: > > - Subclassed the ImportHandler and ImportTarget of the data module to allow > a JDBC DB as the source for the import > - Then wrote a custom import handler class (extending our database import > handler above) which creates the Magnolia user accounts > - Of course the user accounts are created in some sort of hierarchical > structure because you don't want thousands of records as subnodes of one > single node > > Just have a look at the ImportHandler and ImportTarget class and you will > see that this is not rocket science. > > -will > > > On 27.10.2010, at 13:38, Mauro Esposito wrote: > > > > > Hallo All, > > > > we have an oracle database with information of 1500 users that we need to > import in magnolia as admin or public users. > > > > Anyone has ever had this problem? > > > > Any help or tips will be apreciated. > > > > Thanks, > > Mauro > > > > > > > > ---------------------------------------------------------------- > > For list details see > > http://www.magnolia-cms.com/home/community/mailing-lists.html > > To unsubscribe, E-mail to: <[email protected]> > > ---------------------------------------------------------------- > > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
