Re: [XMLSchema] Adding an extension registry and custom serializers/deserializers

[Ajith Ranabahu <aj...@gmail.com>]

Hi Jeremy,
Sorry for the delay, Well really the reason behind putting up this
proposal is to ultimately use it in woden (and ofcourse I got the
inspiration from WSDL4J and Woden extension registries) :) So if we
can factor something out it would be great. However I believe that
Woden have the flexibility to have different XML schema models (say
may be a plain DOM model). To keep it that way may be we should allow
each model have its own way of handling extensions ?

Ajith

On 2/26/07, Jeremy Hughes <hu...@apache.org> wrote:
> Ajith, This does look useful. It would be good to use a similar
> (identical) extension registry mechanism across Woden and XMLSchema.
> Have you taken a look at that? Perhaps there is something worth
> factoring out.
>
> Cheers,
> Jeremy
>
> On 24/02/07, Davanum Srinivas <da...@gmail.com> wrote:
> > +1 Ajith.
> >
> > -- dims
> >
> > On 2/23/07, Ajith Ranabahu <aj...@gmail.com> wrote:
> > > 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: commons-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: commons-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: commons-dev-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>


-- 
Ajith Ranabahu

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [XMLSchema] Adding an extension registry and custom serializers/deserializers

[Jeremy Hughes <hu...@apache.org>]

On 02/03/07, Ajith Ranabahu <aj...@gmail.com> wrote:
> Hi Jeremy,
> Sorry for the delay, Well really the reason behind putting up this
> proposal is to ultimately use it in woden (and ofcourse I got the

great!

> inspiration from WSDL4J and Woden extension registries) :) So if we

Take a look at the Woden extension registration. It's moved on a bit
since WSDL4J. e.g. XMLElement is used to abstract away from DOMElement
and OMElement

> can factor something out it would be great. However I believe that
> Woden have the flexibility to have different XML schema models (say
> may be a plain DOM model). To keep it that way may be we should allow
> each model have its own way of handling extensions ?

I think we can develop a common extension mechanism which is
generalised across DOM and OM.

Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org