Chen, I'm glad we've got you going :).
Transport does have the parameters you have specified. The pivot didn't get them because pivot is another handler entity. In other words if you've done config.getTransport(Qname(null,"smtp")).getOption(...) you'll see the parameters as in your original deployment example. To make sure pivot got them you had to explicitly define it as a handler with parameters associated with THAT handler. WSDD schema is saying exactly this. -- Igor Sedukhin .. ([EMAIL PROTECTED]) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 -----Original Message----- From: CHEN,SHIH-CHANG (HP-NewJersey,ex2) [mailto:[EMAIL PROTECTED]] Sent: Friday, February 15, 2002 10:50 AM To: Sedukhin, Igor; [EMAIL PROTECTED] Cc: CHEN,SHIH-CHANG (HP-NewJersey,ex2) Subject: RE: Modified WSDDTargetedChain.java Igor, Glyn, Thanks, it does work for me. Attachment is the schema of wsdd i found. It may be old. But looks like transport is allowed to have parameters because transport extends DeployableItem. I think the wsdd shcema may need to be changed in next release. -chen > -----Original Message----- > From: Sedukhin, Igor [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 15, 2002 8:00 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: RE: Modified WSDDTargetedChain.java > > > Glyn, Chen, > > I think it's all good and we don't have to apply the change. > Here is why and how to take care of the original problem correctly. > > You're deploying a transport like > <transport name="smtp" > pivot="java:org.apache.axis.transport.smtp.SMTPSender"> > Well, you are actually getting a transport with parameters, > just that the pivot is not getting them, because it is a > shortened reference instead of a proper handler reference. > > Here is how you can solve this > <handler name="mySMTP_Channel" > type="java:org.apache.axis.transport.smtp.SMTPSender"> > <parameter name="from-address" value="[EMAIL PROTECTED]"/> > </handler> > <transport name="smtp" pivot="mySMTP_Channel"> > That'll get you objects with proper parameters. > > I also thought it was a bug until I hit this situation > myself, but in a little different manner, so please let me > know if this works for you :)... > > -- Igor Sedukhin .. ([EMAIL PROTECTED]) > -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 > > > > -----Original Message----- > From: Glyn Normington [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 15, 2002 5:02 AM > To: [EMAIL PROTECTED] > Subject: Re: Modified WSDDTargetedChain.java > > > > I don't know this area of Axis well enough to be sure, but > your fix looks plausible. However, comparing the code in > WSDDDeployableItem.makeNewInstance, I wonder if the following > line needs adding just before the new call to setOptions: > > pivot.setName(pivotQName.getLocalPart()); > > On the other hand, a more robust fix would avoid duplicating > this code sequence in WSDDDeployableItem and > WSDDTargetedChain, but it's not yet clear to me how to > achieve this. Maybe someone else would care to comment? > > Glyn >
