Re: Aegis binding and property/fiels removal

[tog <gu...@gmail.com>]

Hi Dan,

Sorry not to follow up quickly. Actually, the DefaultTypaMappingRegistry is
final and cannot be extended as you suggest.

Some more insights on what I want to achieve. Today, in GroovyWS, the users
have to write a .aegis.xml file for each bean they will  write  in Groovy.
This file is  always the same  containing the line:

<property name="metaClass" ignore="true"/>

I would like to modify the behavior of the BeanType inside the Aegis Binding
so that if such a field is present it can be ignored.

Is there some documentation on how to modify the DefaultTypeMappingRegisty ?

Cheers
Guillaume


>
> Step 4: Write your own type registry to return your own TypeCreator
>
> public class MyTypeMappingRegistry extends DefaultTypeMappingRegistry {
>
>     protected AbstractTypeCreator createDefaultTypeCreator() {
>         AbstractTypeCreator creator = new MyTypeCreator();
>         creator.setConfiguration(getConfiguration());
>         return creator;
>     }
> }
>
> Step 5: use it:
>
> ServerFactoryBean sfb = new ServerFactoryBean();
>
> AegisDatabinding db = new AegisDataBinding();
> db.setTypeMappingRegistry(new MyTypeMappingRegistry());
> sfb.setDatabinding(db);
> ...
>
> Hope that works for you!
>
> - Dan
>
> On 8/27/07, tog <gu...@gmail.com> wrote:
> >
> > Hiya
> >
> > I have some automatically generated classes that I use to generate a
> > server
> > using Aegis. This is done programmaticaly. I am using an
> > AegisServiceConfiguration class to avoid publishing methods that I want
> to
> > remove. I would like similarly to remove some fields/properties from the
> > serialization process.
> > How is that possible (programmaticaly) ?
> >
> > Thanks for your help.
> >
> > Guillaume
> >
>



-- 

Best Regards
Guillaume
http://cheztog.blogspot.com