I agree and would recommend Apache Digester, it would be perfect for this job, it transforms XML into Java objects (it's a useful SAX implematation).
Wouter Heijke Finalist IT Group -----Oorspronkelijk bericht----- Van: Edwin van der Elst [mailto:[EMAIL PROTECTED] Verzonden: Friday, June 11, 2004 12:07 PM Aan: '[EMAIL PROTECTED]' Onderwerp: RE: What are we going to do with the MMBase edit wizards ? I used a profiler on the editwizards about a year ago to find out if it could be made faster. For displaying 1 editwizard, there are hundreds of XPath queries and XSL transformations performed. This can probably be made faster if the builders and editwizard definitions are stored internally as java objects and not queried using XML techniques, but (for example) using Hashmaps. Edwin van der Elst Finalist IT Group -----Oorspronkelijk bericht----- Van: Pierre van Rooden [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 11 juni 2004 12:50 Aan: [EMAIL PROTECTED] Onderwerp: Re: What are we going to do with the MMBase edit wizards ? Peter Reitsma wrote: > But what do you mean by abandoning the XML-part ? That's what makes it > so powerful imho. It has been voiced that that is what slows down the wizards (using Dove instead of bridge directly, etc). However, if you want to fully avoid this, you have to totally abandon xml, else you will simply be building Dove again, this time in the wizards itself. Note that all the creation and loading tasks are passed almost directly to Dove, so they hardly make a difference in speed if you implement it outside the Dove. Re-inventing the wheel, so to speak. I would like to know if people actually have a concrete idea on how you would define a 'new' wizard? If in xml, what would it look like (and why would it be easier than the old format)? -- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
