Understand. However, the fact that currently I am not being able to play with the Call object is my major issue. I ultimately need the ability to play with it outside the Stub. I agree that the header stuff probably belong more to the service than the call though.
I guess I am simply looking for an alternative until we have a real support for header. This being said +1 for a public setOption() that allows to setup the Call from outside of the Stub. Sylvain. -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 3:11 PM To: [EMAIL PROTECTED] Subject: RE: [server-config.wsdd] <parameter name="sendMultiRefs" value="f alse "/> Making the getCall method public doesn't do any good. Well, it might do SOME good. getCall gives you a Call object, but that Call object would never be used in a stub invocation. The only good it does is if you call methods (like setOption!) that affect low-level objects that hang around longer than the Call object. The proper thing MIGHT be to have some of these methods on the service rather than the stub, but we'll have to think about it a bit. Russell Butek [EMAIL PROTECTED] "St-Germain, Sylvain" <[EMAIL PROTECTED]> on 03/14/2002 01:33:23 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: RE: [server-config.wsdd] <parameter name="sendMultiRefs" value ="f alse "/> I tend to agree with you but in the mean time it is impossible for someone to set the options without hacking it in the Stub class. I have the same problem with seting the Call's soap header. I've allways avoided to ask the following question, but here it is: Could we make the getCall() method public? so we can overcome the current Axis limitations regarding header stuff and properties/options (among other thing) (ouch) Sylvain. -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 2:11 PM To: [EMAIL PROTECTED] Subject: RE: [server-config.wsdd] <parameter name="sendMultiRefs" value="f alse "/> You don't. A new Call object is instantiated for every invocation, so there is no Call object per Stub. I'm considering putting a _setOption method on the Stub that forwards the setOption to the Call once it's instantiated, but I haven't decided whether that's the right thing to do. It's an easy addition, so it's probably the wrong thing to do (aren't they all?). Russell Butek [EMAIL PROTECTED] "St-Germain, Sylvain" <[EMAIL PROTECTED]> on 03/14/2002 12:49:56 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: RE: [server-config.wsdd] <parameter name="sendMultiRefs" value ="f alse "/> How do you get to the Call object from the Stub? Sylvain. -----Original Message----- From: Simon McClenahan [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 10:34 AM To: [EMAIL PROTECTED] Subject: RE: [server-config.wsdd] <parameter name="sendMultiRefs" value="false "/> On the client you set an option on the Call. >From http://marc.theaimsgroup.com/?l=axis-user&m=101534226125705&w=2 call.setOption(AxisEngine.PROP_DOMULTIREFS, new Boolean(false)); I have posted requesting the ability to set Call options such as this with WSDL2Java, but no response yet. http://marc.theaimsgroup.com/?l=axis-user&m=101544868326157&w=2 cheers, Simon -----Original Message----- From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 9:19 AM To: [EMAIL PROTECTED] Subject: RE: [server-config.wsdd] <parameter name="sendMultiRefs" value="false "/> server-config.wsdd sounds obvious it has only to do with the server side (!), it's my mistake... My question should have been: Does this hability exists on the client side as well? Sylvain. -----Original Message----- From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 10:48 AM To: Axis-User (E-mail) Subject: [server-config.wsdd] <parameter name="sendMultiRefs" value="false "/> May this option have been broken recently? I do not see any differences on the request between setting it to true and false... It allways sends the refs encoding. -- Sylvain This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.
