Hmm. I don't suppose you would be willing to contribute a cut-down version of your problem. I'd wrestle with it until it worked and then check it in as a sample.
On Fri, Mar 6, 2009 at 1:19 PM, relphie <[email protected]> wrote: > > > I don't think that is true. With scope = prototype, none of my custom type > mappings are saved. Perhaps it is because I am registering them wrong. If > you have an example, I would greatly appreciate it. Whenever I attempt to > register a custom type mapping on the server side, I end up getting the same > types of exception as when I was re-using the databinding. I somehow think > the similarity may be from the databinding getting initialized wrong / again > when registering (just like when the same databinding was being initialized > for one service and used for another). > > Again, I would love an example to look at. > > > bimargulies wrote: >> >> It should work just the same. It will just make more copies of everything. >> >> On Fri, Mar 6, 2009 at 11:37 AM, relphie <[email protected]> wrote: >>> >>> >>> So, using scope=prototype on the databinding, how would you then be able >>> to >>> register a new type mapping using spring config? >>> >>> >>> dkulp wrote: >>>> >>>> On Thu March 5 2009 3:06:02 pm Benson Margulies wrote: >>>>> What I've been telling people to do is to use scope='prototype' on >>>>> service factories and data bindings. Example-wise, I bet we're short. >>>>> Glenn or Dan? >>>> >>>> Yea, scope=prototype is the way to go. >>>> >>>> Dan >>>> >>>> >>>>> On Thu, Mar 5, 2009 at 3:00 PM, relphie <[email protected]> wrote: >>>>> > I agree that sharing the databindings could cause a conflict and thus >>>>> > should probably not be allowed. I am also confused, because I think >>>>> you >>>>> > are saying that a large part of my configuration is bad (i.e. reusing >>>>> the >>>>> > service-factory). Is that the case, and can you show me or point me >>>>> to >>>>> > an example of a configuration that generates 2 services? >>>>> > >>>>> > bimargulies wrote: >>>>> >> If it worked for you in 2.0, it worked purely by accident, I think. >>>>> >> However, I am a bit confused as follows. Reusing the entire service >>>>> >> factory for multiple endpoints had never worked, period. That >>>>> doesn't >>>>> >> necessarily imply that a databinding couldn't be used in multiple >>>>> >> service factories. However, the data binding does look at the >>>>> service >>>>> >> to find the root elements. They could conflict, so it doesn't make >>>>> >> sense to me to share them. Anyone else (Dan?) care to express an >>>>> >> opinion? >>>>> >> >>>>> >> On Thu, Mar 5, 2009 at 2:51 PM, relphie <[email protected]> wrote: >>>>> >>> Hello, >>>>> >>> >>>>> >>> There appears to be an inconsistency in the ability to reuse an >>>>> Aegis >>>>> >>> Databinding across multiple services. In cxf 2.0, it was possible, >>>>> but >>>>> >>> in >>>>> >>> the latest 2.2-SNAPSHOT it is not. Can anyone explain this, and >>>>> >>> whether it >>>>> >>> is intended? >>>>> >>> >>>>> >>> Here is a sample the configuration that works in 2.0 but not in >>>>> >>> 2.2-SNAPSHOT: >>>>> >>> >>>>> >>> <bean id="aegisBean" >>>>> >>> class="org.apache.cxf.aegis.databinding.AegisDatabinding" /> >>>>> >>> >>>>> >>> <jaxws:endpoint id="RelationshipService" >>>>> implementor="#ReltnService" >>>>> >>> implementorClass="relationship.service.RelationshipService" >>>>> >>> address="/RelationshipService"> >>>>> >>> <jaxws:serviceFactory> >>>>> >>> <bean >>>>> >>> class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> >>>>> >>> <property name="dataBinding" >>>>> >>> ref="aegisBean" /> >>>>> >>> </bean> >>>>> >>> </jaxws:serviceFactory> >>>>> >>> </jaxws:endpoint> >>>>> >>> >>>>> >>> <alias name="relationship.service.RelationshipService" >>>>> >>> alias="ReltnService" /> >>>>> >>> >>>>> >>> <jaxws:endpoint id="OrganizationService" >>>>> implementor="#OrgService" >>>>> >>> implementorClass="organization.service.OrganizationService" >>>>> >>> address="/OrganizationService"> >>>>> >>> <jaxws:serviceFactory> >>>>> >>> <bean >>>>> >>> class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> >>>>> >>> <property name="dataBinding" >>>>> >>> ref="aegisBean" /> >>>>> >>> </bean> >>>>> >>> </jaxws:serviceFactory> >>>>> >>> </jaxws:endpoint> >>>>> >>> >>>>> >>> <alias name="organization.service.OrganizationService" >>>>> >>> alias="OrgService" >>>>> >>> /> >>>>> >>> >>>>> >>> >>>>> >>> Thanks, >>>>> >>> >>>>> >>> Brian >>>>> >>> -- >>>>> >>> View this message in context: >>>>> >>> >>>>> http://www.nabble.com/Aegis-Databinding-Re-use-tp22359219p22359219.html >>>>> >>> Sent from the cxf-user mailing list archive at Nabble.com. >>>>> > >>>>> > -- >>>>> > View this message in context: >>>>> > >>>>> http://www.nabble.com/Aegis-Databinding-Re-use-tp22359219p22359397.html >>>>> > Sent from the cxf-user mailing list archive at Nabble.com. >>>> >>>> -- >>>> Daniel Kulp >>>> [email protected] >>>> http://www.dankulp.com/blog >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Aegis-Databinding-Re-use-tp22359219p22375998.html >>> Sent from the cxf-user mailing list archive at Nabble.com. >>> >>> >> >> > > -- > View this message in context: > http://www.nabble.com/Aegis-Databinding-Re-use-tp22359219p22377822.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
