You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Thamizh <tc...@yahoo.co.in> on 2008/04/29 15:16:25 UTC
Reg passing values dynamically to web service
Hi,
I have deployed the web service using .jws method. Now I wanted to change those into .wsdd method.
Can I pass dynamic values to web service using web service deployment descriptor. If so can you please tell me How?
E.g String licenseServer="mgr@chn.com" . This mgr@chn.com needs to be passed dynamically using wsdd.
Regards,
Thamizhannal P
---------------------------------
Best Jokes, Best Friends, Best Food. Get all this and more on Best of Yahoo! Groups.
RE: Axis2 1.3 - new attribute TYPE in SOAP Response
Posted by "Nath, Niraj" <Ni...@cns-inc.com>.
Thanks Nadir for the info.
Regards
-----Original Message-----
From: Nadir Amra [mailto:amra@us.ibm.com]
Sent: Tuesday, April 29, 2008 10:26 AM
To: axis-user@ws.apache.org
Cc: axis-user@ws.apache.org
Subject: Re: Axis2 1.3 - new attribute TYPE in SOAP Response
Niraj,
I assume you are using POJOs to expose as Web service? If so, there is
a
JIRA that I hope to complete by end of week that should resolve this
problem:
http://issues.apache.org/jira/browse/AXIS2-3651
Unfortunately, it will not make the 1.4 release.....
Nadir Amra
"Nath, Niraj" <Ni...@cns-inc.com> wrote on 04/29/2008 09:10:08 AM:
> Hi All,
> I?m trying to move from Axis2 1.0 to Axis2 1.3 version. I?m
> using the war distribution.
> Now I see a new attribute for the complex data types (as highlighted
> below ) in the response below. Can someone please explain why it
> comes & how to suppress that (if possible) ?
>
>
>
>
> <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Body>
> <ns:getRAByDateMRResponse
xmlns:ns="http://claims.webservices.ecams.com
> ">
> <ns:return type="com.ecams.webservices.claims.RAInfoReturn"
> xmlns:ax294="http://claims.webservices.ecams.com/xsd" xmlns:ax295="
> http://iterfaces.webservices.ecams.com/xsd">
> <ax294:wsStatus
type="com.ecams.webservices.iterfaces.WsStatus">
> <ax295:statusCode>2</ax295:statusCode>
> <ax295:statusDescription>No Records are present for
> your criteria.</ax295:statusDescription>
> <ax295:statusType>BUSINESSMESSAGE</ax295:statusType>
> </ax294:wsStatus>
> </ns:return>
> </ns:getRAByDateMRResponse>
> </soapenv:Body>
> </soapenv:Envelope>
>
> Regards
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
This electronic message contains information from CNSI, which may be company sensitive, proprietary, privileged or otherwise protected from disclosure. The information is intended to be used solely by the intended recipient(s). If you are not an intended recipient any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 1.3 - new attribute TYPE in SOAP Response
Posted by Nadir Amra <am...@us.ibm.com>.
Niraj,
I assume you are using POJOs to expose as Web service? If so, there is a
JIRA that I hope to complete by end of week that should resolve this
problem:
http://issues.apache.org/jira/browse/AXIS2-3651
Unfortunately, it will not make the 1.4 release.....
Nadir Amra
"Nath, Niraj" <Ni...@cns-inc.com> wrote on 04/29/2008 09:10:08 AM:
> Hi All,
> I?m trying to move from Axis2 1.0 to Axis2 1.3 version. I?m
> using the war distribution.
> Now I see a new attribute for the complex data types (as highlighted
> below ) in the response below. Can someone please explain why it
> comes & how to suppress that (if possible) ?
>
>
>
>
> <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Body>
> <ns:getRAByDateMRResponse
xmlns:ns="http://claims.webservices.ecams.com
> ">
> <ns:return type="com.ecams.webservices.claims.RAInfoReturn"
> xmlns:ax294="http://claims.webservices.ecams.com/xsd" xmlns:ax295="
> http://iterfaces.webservices.ecams.com/xsd">
> <ax294:wsStatus
type="com.ecams.webservices.iterfaces.WsStatus">
> <ax295:statusCode>2</ax295:statusCode>
> <ax295:statusDescription>No Records are present for
> your criteria.</ax295:statusDescription>
> <ax295:statusType>BUSINESSMESSAGE</ax295:statusType>
> </ax294:wsStatus>
> </ns:return>
> </ns:getRAByDateMRResponse>
> </soapenv:Body>
> </soapenv:Envelope>
>
> Regards
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Axis2 1.3 - new attribute TYPE in SOAP Response
Posted by "Nath, Niraj" <Ni...@cns-inc.com>.
Hi All,
I'm trying to move from Axis2 1.0 to Axis2 1.3 version. I'm using
the war distribution.
Now I see a new attribute for the complex data types (as highlighted
below ) in the response below. Can someone please explain why it comes &
how to suppress that (if possible) ?
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns:getRAByDateMRResponse
xmlns:ns="http://claims.webservices.ecams.com">
<ns:return type="com.ecams.webservices.claims.RAInfoReturn"
xmlns:ax294="http://claims.webservices.ecams.com/xsd"
xmlns:ax295="http://iterfaces.webservices.ecams.com/xsd">
<ax294:wsStatus
type="com.ecams.webservices.iterfaces.WsStatus">
<ax295:statusCode>2</ax295:statusCode>
<ax295:statusDescription>No Records are present for your
criteria.</ax295:statusDescription>
<ax295:statusType>BUSINESSMESSAGE</ax295:statusType>
</ax294:wsStatus>
</ns:return>
</ns:getRAByDateMRResponse>
</soapenv:Body>
</soapenv:Envelope>
Regards
This electronic message contains information from CNSI, which may be company sensitive, proprietary, privileged or otherwise protected from disclosure. The information is intended to be used solely by the intended recipient(s). If you are not an intended recipient any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify the sender immediately and delete all copies of this message.