Browse Prior Art Database

Pluggable Java Bean from XML Schema Generation Framework

IP.com Disclosure Number: IPCOM000033401D
Original Publication Date: 2004-Dec-09
Included in the Prior Art Database: 2004-Dec-09
Document File: 6 page(s) / 135K

Publishing Venue

IBM

Abstract

Method for dynamically adding new Java Bean generators for XML Schema files into a user interface. The Framework allows dynamic registration and invocation of the Java Bean generators.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 27% of the total text.

Page 1 of 6

Pluggable Java Bean from XML Schema Generation Framework

Disclosed is a software framework that allows dynamic contribution of new Java Bean generators for XML Schema files without requiring modifications to the user interface (UI) code.

     A Java Bean generator allows users to create from an XML schema, java classes that represent the attributes and structure of an XML file. This allows easy creation and saving of these XML files in a Java oriented programming fashion. They typically require the configuration of additional classpath libraries that the generated classes rely on. This means that the user has to figure out how to invoke the generator and then also modify their classpath for their java project to allow successful compilation. For example, in Eclipse, each java project needs to modify their class path variable.

     From an IDE, you can write code to programmatically add the correct classpath variables to the java project's classpath when the user generates code using a certain generator. The problem arises when another Java generator is introduced later. Any UI that is relevant to allowing the user to invoke a Java Bean generator would now have to be changed and new code written to accomodate the new Java generator.

     With the framework in this invention, only an additional extension point needs to be defined in an XML file to add a new Java Bean generator. The extension point encapsulates the basic information that each Java Bean Generator needs in order to run. This includes how to invoke the generator as well as how parameters are passed to the generator. The XML file also contains information about additional classpath entries that need to be added to the build/run path (as is necessary from all Java Bean Generators since they all have basic runtime classes needed to support the generated Java Beans). All relevant defined extension points for each generator is dynamically read when the program is first initialized. This is stored in the framework, and is available for presentation in the UI so the user can choose the generation style they would like from their XML Schema file.

     The advantages of this method are pretty clear. It allows generators to be plugged in dynamically, yet still present a single common flow to the end user. The product does not need to have the code updated to allow the new generator to be plugged in. The class path modification is handled by the framework based on information that is read from the extension points. No custom hard coded values exist in the core framework code for this. Customers that urgently require a new generator to be used in their production environment that is not yet supported, or not planned to be supported by the product can easily plug in a new generator themselves, and still get a smooth seamless experience in their development environment.

Java Generation Framework Data

     When invoking a Java generator, there are static and dynamic information that need to be passed to the g...