On Tuesday, November 08, 2011 6:48:45 PM Evangelina wrote: > Well yes, the thing is that I'm still using the client instance when the > ClientProxy is gc, which destroys the state of client.
That Client object is definitely tied to the lifecycle of the proxy. That is per design. If you are only interested in the Client object, you should likely use the JaxWsClientFactoryBean (or ClientFactoryBean) and not the factories that create the proxy. Dan > > > On Tue, Nov 8, 2011 at 11:30 PM, Jeff Wang-2 [via CXF] < > > ml-node+s547215n497647...@n5.nabble.com> wrote: > > This should be expected, right? The client represents an active > > connection (the conduit.) Shouldn't you be calling > > ClientProxy.getClient(...) again when you need a new client? > > > > Jeff > > > > On Tue, Nov 8, 2011 at 11:28 AM, Evangelina <[hidden > > email]<http://user/SendEmail.jtp?type=node&node=4976473&i=0>>> > > wrote: > > > Hi, > > > > > > I'm having a few issues trying to migrate CXF from 2.3.1 version to > > > > 2.5.0. > > > > > The main issue is with the Client that I'm creating using the > > > ClientProxyFactoryBean. > > > > > > I'm creating my client like this: > > > > > > ClientProxy.getClient(cpf.create()) > > > > > > where cpf is the instance of ClientProxyFactoryBean, and then in my > > > application I use the client that I get from that invocation. > > > > > > After migrating to 2.5.0 I'm running into NullPointerException > > > because > > > > the > > > > > client is being destroyed when the method finalize is called on the > > > ClientProxy instance. I haven't had this issue before, because in > > > 2.3.1 > > > > the > > > > > method finalize is not implemented in the ClientProxy class. > > > > > > Is this a bug or working as expected? And if so, is there any way > > > the > > > > client > > > > > can outlive the clientProxy? since that instance is created inside > > > the > > > getClient static method, I cannot get hold of it. > > > > > > Thanks in advance for the help, > > > Eva > > > > > > -- > > > > > View this message in context: > > http://cxf.547215.n5.nabble.com/Problem-migrating-from-2-3-1-to-2-5-0-tp > > 4975395p4975395.html> > > > Sent from the cxf-user mailing list archive at Nabble.com. > > > > ------------------------------ > > > > If you reply to this email, your message will be added to the > > discussion > > > > below: > > > > http://cxf.547215.n5.nabble.com/Problem-migrating-from-2-3-1-to-2-5-0-tp > > 4975395p4976473.html> > > To unsubscribe from Problem migrating from 2.3.1 to 2.5.0, click > > here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=u > > nsubscribe_by_code&node=4975395&code=ZXZhbmdlbGluYW1ybUBnbWFpbC5jb218N > > Dk3NTM5NXwzMDY0Njk3NDM=>> > > . > > See how NAML generates this > > email<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=ma > > cro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namesp > > aces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view > > .web.template.InstantMailNamespace&breadcrumbs=instant+emails%21nabble%3 > > Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21na > > bble%3Aemail.naml> > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Problem-migrating-from-2-3-1-to-2-5-0-tp497 > 5395p4976515.html Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com
