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 "Iyengar, Kumar" <ku...@bmc.com> on 2007/11/16 02:45:32 UTC
axis 1.4 and Basic Profile
Hi all,
Does anyone know if Axis1.4 is Basic Profile 1.1 compliant?
Thanks,
--kumar
Re: axis 1.4 and Basic Profile
Posted by Anne Thomas Manes <at...@gmail.com>.
Kumar,
You can implement WS-I BP 1.1 compliant service endpoints using Axis
1.4. Axis 1.4 processes SOAP messages in accordance with the profile.
Anne
On Nov 16, 2007 2:27 AM, Iyengar, Kumar <ku...@bmc.com> wrote:
> Hi Lawrence,
>
> I do mean WS-I Basic Profile. If I understand correctly Basic Profile
> 1.1 has WSDL and SOAP compliance. I understand and agree with you on the
> WSDL compliance part. However, for SOAP we entirely depend on Axis and
> so the compliance for SOAP part of Basic Profile 1.1 has to come from
> Axis 1.x. I wanted to find out if Axis 1.4 is WS-I Basic Profile 1.1
> compliant.
>
> We are currently using Axis 1.2 and that is not BP 1.1 compliant (but it
> is BP 1.0 compliant).
>
> Axis2 is considered BP 1.1 compliant but I am having problems
> integrating with that.
>
> Thanks,
>
> --kumar
>
> -----Original Message-----
> From: Lawrence Mandel [mailto:lmandel@ca.ibm.com]
> Sent: Thursday, November 15, 2007 7:53 PM
> To: axis-dev@ws.apache.org
>
> Subject: Re: axis 1.4 and Basic Profile
>
> Hi Kumar,
>
> By basic profile I'm assuming you mean the WS-I basic profile. I don't
> think you can label a runtime as WS-I compliant as there are many things
>
> that you can do with Web services that are not recommended by the WS-I -
>
> that's why there is a WS-I - such as rpc encoded services and importing
> schemas in a WSDL document with the wsdl:import element. The real
> question
> when it comes to WS-I compliance is "is service X WS-I compliant"? If
> the
> service description and implementation follows the WS-I recommendations
> than it is compliant. Note that even if service X is compliant, service
> Y,
> which is deployed to the same runtime (Axis or otherwise), can be
> non-compliant.
>
> Lawrence
>
>
>
>
> "Iyengar, Kumar" <ku...@bmc.com>
> 11/15/2007 08:45 PM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> <ax...@ws.apache.org>
> cc
>
> Subject
> axis 1.4 and Basic Profile
>
>
>
>
>
>
> Hi all,
>
> Does anyone know if Axis1.4 is Basic Profile 1.1 compliant?
>
> Thanks,
>
> --kumar
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
RE: axis 1.4 and Basic Profile
Posted by "Iyengar, Kumar" <ku...@bmc.com>.
Hi Lawrence,
I do mean WS-I Basic Profile. If I understand correctly Basic Profile
1.1 has WSDL and SOAP compliance. I understand and agree with you on the
WSDL compliance part. However, for SOAP we entirely depend on Axis and
so the compliance for SOAP part of Basic Profile 1.1 has to come from
Axis 1.x. I wanted to find out if Axis 1.4 is WS-I Basic Profile 1.1
compliant.
We are currently using Axis 1.2 and that is not BP 1.1 compliant (but it
is BP 1.0 compliant).
Axis2 is considered BP 1.1 compliant but I am having problems
integrating with that.
Thanks,
--kumar
-----Original Message-----
From: Lawrence Mandel [mailto:lmandel@ca.ibm.com]
Sent: Thursday, November 15, 2007 7:53 PM
To: axis-dev@ws.apache.org
Subject: Re: axis 1.4 and Basic Profile
Hi Kumar,
By basic profile I'm assuming you mean the WS-I basic profile. I don't
think you can label a runtime as WS-I compliant as there are many things
that you can do with Web services that are not recommended by the WS-I -
that's why there is a WS-I - such as rpc encoded services and importing
schemas in a WSDL document with the wsdl:import element. The real
question
when it comes to WS-I compliance is "is service X WS-I compliant"? If
the
service description and implementation follows the WS-I recommendations
than it is compliant. Note that even if service X is compliant, service
Y,
which is deployed to the same runtime (Axis or otherwise), can be
non-compliant.
Lawrence
"Iyengar, Kumar" <ku...@bmc.com>
11/15/2007 08:45 PM
Please respond to
axis-dev@ws.apache.org
To
<ax...@ws.apache.org>
cc
Subject
axis 1.4 and Basic Profile
Hi all,
Does anyone know if Axis1.4 is Basic Profile 1.1 compliant?
Thanks,
--kumar
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: axis 1.4 and Basic Profile
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
Hi Kumar,
By basic profile I'm assuming you mean the WS-I basic profile. I don't
think you can label a runtime as WS-I compliant as there are many things
that you can do with Web services that are not recommended by the WS-I -
that's why there is a WS-I - such as rpc encoded services and importing
schemas in a WSDL document with the wsdl:import element. The real question
when it comes to WS-I compliance is "is service X WS-I compliant"? If the
service description and implementation follows the WS-I recommendations
than it is compliant. Note that even if service X is compliant, service Y,
which is deployed to the same runtime (Axis or otherwise), can be
non-compliant.
Lawrence
"Iyengar, Kumar" <ku...@bmc.com>
11/15/2007 08:45 PM
Please respond to
axis-dev@ws.apache.org
To
<ax...@ws.apache.org>
cc
Subject
axis 1.4 and Basic Profile
Hi all,
Does anyone know if Axis1.4 is Basic Profile 1.1 compliant?
Thanks,
--kumar
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org