You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "CHEN,SHIH-CHANG (HP-NewJersey,ex2)" <sh...@hp.com> on 2002/02/07 00:03:41 UTC
WSDD problem (3rd attempt)
I found a problem about the WSDD that the parameters of transport pivot are
not
populated to the java instnace. However, in the schema of wsdd, it looks
like
parameters are allowed for transport ... I wonder this is by design or a
bug.
Following is an example of client-config.wsdd:
<?xml version="1.0" encoding="UTF-8"?>
<deployment name="defaultClientConfig"
xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
<transport name="smtp"
pivot="java:org.apache.axis.transport.smtp.SMTPSender">
<parameter name="from-address"
value="shih-chang_chen@hp.com"/>
<responseFlow>
<handler name="receiver"
type="java:org.apache.axis.transport.smtp.Pop3Fetcher">
<parameter name="parm1"
value="shih-chang_chen@hp.com"/>
</handler>
</responseFlow>
</transport>
<transport name="http"
pivot="java:org.apache.axis.transport.http.HTTPSender"/>
</deployment>
For this case, if i invoked this.getOption( "from-address" )inside
SMTPSender.invoke(), I got a null. However, I can get the correct value when
I invokethis.getOption( "parm1" ) in Pop3Fetcher.invoke().
In the code of org.apache.axis.deployment.wsdd.WSDDDeployableItem, the
parameters are populated to new instance in
WSDDDeployableItem.makeNewInstance
method by invoking h.setOptions(getParametersTable()).
But this mehtod is overriden by
org.apache.axis.deployment.wsdd.WSDDTargetedChain
withod invoking pivot.setOptions(getParametersTable()).
Am i correct ?
Thanks,
ShihChang Chen