Re: support.JaxWsServiceFactoryBean as factory for multiple endpoints
On Thursday 24 January 2008, Benson Margulies wrote: > On Thu, 2008-01-24 at 13:54 -0500, Daniel Kulp wrote: > > Yea, that definitely won't work. The service factories record way > > to much state specific to that endpoint. > > > > That said, you MAY be able to get it to work by doing: > > > > > id='jaxws-and-aegis-service-factory' > > class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> > > > > That is, scope='prototype'. This works in a live app of mine. Listen to him, not me. I have no clue what I'm talking about... :-) -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: support.JaxWsServiceFactoryBean as factory for multiple endpoints
On Thu, 2008-01-24 at 13:54 -0500, Daniel Kulp wrote: > Yea, that definitely won't work. The service factories record way to > much state specific to that endpoint. > > That said, you MAY be able to get it to work by doing: > > id='jaxws-and-aegis-service-factory' > class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> > That is, scope='prototype'. This works in a live app of mine.
Re: support.JaxWsServiceFactoryBean as factory for multiple endpoints
Yea, that definitely won't work. The service factories record way to much state specific to that endpoint. That said, you MAY be able to get it to work by doing: That should cause Spring to create a new instance for each ref. (I think. I'm not exactly a spring expert) Dan On Thursday 24 January 2008, Ron Piterman wrote: > hi, > in http://cwiki.apache.org/CXF20DOC/aegis-databinding.html it is > suggested to use > org.apache.cxf.aegis.databinding.AegisDatabinding as factory bean for > endpoints. > > The described syntax implies the use of a single factory bean for > multiple endpoints, whereas this does not work. > > Is this a known issue ? > > When using the same factory for more than one endpoint: > > address="/MyIndex"> > > > > > cfx delegates methods of one endpoint to another, trying to invoke a > Method on an target bean which doesn't own it. > > the workaround is : > > address="/MyIndex"> > class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> > > > > class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/> class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration"/> > class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/> > > > > > > > > Chears, > > Ron -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: support.JaxWsServiceFactoryBean as factory for multiple endpoints
sorry, the factory class is ofcause not org.apache.cxf.aegis.databinding.AegisDatabinding but org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean Cheers, Ron Ron Piterman wrote: > hi, > in http://cwiki.apache.org/CXF20DOC/aegis-databinding.html it is > suggested to use > org.apache.cxf.aegis.databinding.AegisDatabinding as factory bean for > endpoints. > > The described syntax implies the use of a single factory bean for > multiple endpoints, whereas this does not work. > > Is this a known issue ? > > When using the same factory for more than one endpoint: > > address="/MyIndex"> > > > > > > cfx delegates methods of one endpoint to another, trying to invoke a Method > on an target bean which doesn't own it. > > the workaround is : > > address="/MyIndex"> > > > > > > class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/> > class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration"/> > class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/> > > > > > > > > Chears, > > Ron > > >
support.JaxWsServiceFactoryBean as factory for multiple endpoints
hi, in http://cwiki.apache.org/CXF20DOC/aegis-databinding.html it is suggested to use org.apache.cxf.aegis.databinding.AegisDatabinding as factory bean for endpoints. The described syntax implies the use of a single factory bean for multiple endpoints, whereas this does not work. Is this a known issue ? When using the same factory for more than one endpoint: cfx delegates methods of one endpoint to another, trying to invoke a Method on an target bean which doesn't own it. the workaround is : Chears, Ron