Jacob, I'm definitely the new guy on the volunteer block on Aegis. When Dan isn't off at a conference, he generally jumps on Aegis issues quickly. I'm pitching in as well, but I'm still not entirely confident about some architectural issues. I'm sure we'll get to this stuff.
We just added a JIRA category for Aegis, please make sure that your issues have it selected. --benson > -----Original Message----- > From: Jacob Marcus [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 12, 2007 7:45 AM > To: [email protected] > Subject: Re: DefaultTypaMappingRegistry issue [was: Aegis binding and > property/fiels removal] > > Benson, > > I have seen a couple of issues related to Aegis binding. > > 1) If the simple front end POJO has java.lang.Object in it's signature, > binding fails if you send subclasses of Object in the soap message. This > is > fairly easy to reproduce and seems to be related the name space handling > in > the ObjectType class. I have solved it temporarily by extending the > ObjectType. > > 2) I have logged a Jira issue. (My first issue, so please forgive me if > have > not filled all the fields correctly). > http://issues.apache.org/jira/browse/CXF-992 > > I hope these are on some one's radar. > > Thanks, > Jacob > > > On 9/12/07, Benson Margulies <[EMAIL PROTECTED]> wrote: > > > > I have some ideas in this area, but we need to finish some of what's > > currently outstanding. We could enhance the options class. > > > > > -----Original Message----- > > > From: tog [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, September 11, 2007 10:21 AM > > > To: [email protected] > > > Subject: DefaultTypaMappingRegistry issue [was: Aegis binding and > > > property/fiels removal] > > > > > > 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 < [EMAIL PROTECTED]> 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 > > > > > > -- > > > > > > Best Regards > > > Guillaume > > > http://cheztog.blogspot.com > >
