Hi all, As part of building an object model for SAWSDL we've realized that an extension architecture for XMLSchema is convenient and appropriate. I have included the usecase relevant to me (further down) but I'm sure there will be many other use cases that are similar.
I have introduced a few classes/interfaces and minor changes to the builder to achieve that. While there is a bit of details left to cover (such as the serialization) I have created a Jira [1] and attached my work in progress. Even though I have commit rights I want to discuss the change openly in the list before committing to the trunk. A simple explanation of the changes are as follows. Note that this feature addition does NOT break any existing applications. 1. Two interfaces extensionSerializer and extensionDeserializer 2. An extension registry that keeps track of the instances of serializers and deserializers. Users can register custom deserializers/serializers with the registry and at the time of building schema models (or serializing them) , the registry will be queried to find the relevant serializer/deserializer. A deserializer can custom deserialize a given element and attach the relevant object to the Schema object meta map and the serializer can do the opposite. As for the usecase while processing a SAWSDL file (basically an annotated WSDL file) it would be convenient to attach relevant custom objects (which we call 'model references' in SAWSDL) directly attached to the schema object tree rather than having them as just attributes. comments are welcome. -- Ajith Ranabahu [1] https://issues.apache.org/jira/browse/WSCOMMONS-171 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
