Hello,
> 1. Do you parse a schema definition every time it is needed by the > listeners? Or do the listeners store the received information somewhere? In my project, the XML schema definition is only parsed once and each listener/plugin stores the files it generates (jsp, java and XSL-FO files). This is mainly because we have post-generation operations (for instance, generation of SQL statements to create DB tables) so it was not possible to have a dynamic generation ... > 2. What exactly are the listeners? Template motors for html generation? We have different kind of listeners : one is dedicated to generation of Java business objects (POJOs decorated with XDoclet tags), one is dedicated to HTML/jsp forms and Struts actions generation (via Velocity templates), another one is dedicated to XSL-FO files generation (also via Velocity templates), ... > 3. Is it possible for you to sketch an overall design/scenario? Actually, there are two different "stages" : * The generation of application files which is done only once. The generated files are then integrated into the rest of the application. * The application is then deployed and generated files (along with XML Beans generated objects) are used to display HTML forms to users, display HTML or PDF representation of data entered by users, ... > Where does your example code fit? Hope these questions are not too stupid. The example code is the central function of the XML schema files parser. I put it to show the methods used from the XML Beans API to access XML schema information (the whole application will be released under the GPL in June or July but 'till then I can only show code snippets :-( ...). I hope it's clearer for you now ... (a "big picture" is really missing ...) Regards, Benoit. -- Benoit Orihuela - [EMAIL PROTECTED] - GPG-PGP : C94615BE Architecte logiciel, Zenexity - http://www.zenexity.fr Mobile : +33 (0)6 87 42 71 07 - Tél : +33 (0)1 44 89 47 67 Zenexity, 101-103 boulevard Mac Donald 75019 Paris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
