You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Sam Carleton <sc...@miltonstreet.com> on 2009/04/05 23:23:08 UTC
Application scope parameters
In my web service, there are a few setup tasks that only need to
happen at initialization. The results need to be saved for the life
of the service. To accomplish the setup tasks, the service needs to
get a parameter from the configuration:
Question:
>From within the services init function, is there any way to get a
parameter element from axis2.xml or services.xml?
Question:
After much digging around, is looks like the correct place to persist
the results of the setup tasks is in the
axis2_svc_skeleton.func_array, is this correct?
Sam
Re: Application scope parameters
Posted by Supun Kamburugamuva <su...@gmail.com>.
Yes, as I have mentioned in a previous mail you can put the info into
conf_ctx and retrieve it from the service.
Supun
On Mon, Apr 6, 2009 at 8:37 AM, Sam Carleton <sc...@gmail.com> wrote:
> On Sun, Apr 5, 2009 at 11:15 PM, Supun Kamburugamuva <su...@gmail.com>
> wrote:
>
> > On Mon, Apr 6, 2009 at 2:23 AM, Sam Carleton <scarleton@miltonstreet.com
> >
> > wrote:
> >
> >> Question:
> >>
> >> From within the services init function, is there any way to get a
> >> parameter element from axis2.xml or services.xml?
> >
> > It is not possible to access these parameters from init function. You can
> > access the parameters when the first request comes to the service using
> the
> > msg_ctx.
>
> So the init function call is really only designed to allocate and
> setup the svc_skeleton, nothing else, correct?
>
> For me to use Axis2/C, I really MUST get this setup done during the
> initialization. My server is Apache and I have already added the
> mod_axis2 code to another custom Apache module. The setup that needs
> to be done is already happening in the Apache module.
>
> Question:
>
> Is there any way to pass the vital information from the Apache module
> (axis2_module_init or axis2_handler) into the service?
>
> Sam
>
--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com
Re: Application scope parameters
Posted by Sam Carleton <sc...@gmail.com>.
On Sun, Apr 5, 2009 at 11:15 PM, Supun Kamburugamuva <su...@gmail.com> wrote:
> On Mon, Apr 6, 2009 at 2:23 AM, Sam Carleton <sc...@miltonstreet.com>
> wrote:
>
>> Question:
>>
>> From within the services init function, is there any way to get a
>> parameter element from axis2.xml or services.xml?
>
> It is not possible to access these parameters from init function. You can
> access the parameters when the first request comes to the service using the
> msg_ctx.
So the init function call is really only designed to allocate and
setup the svc_skeleton, nothing else, correct?
For me to use Axis2/C, I really MUST get this setup done during the
initialization. My server is Apache and I have already added the
mod_axis2 code to another custom Apache module. The setup that needs
to be done is already happening in the Apache module.
Question:
Is there any way to pass the vital information from the Apache module
(axis2_module_init or axis2_handler) into the service?
Sam
Re: WS-Policy support
Posted by Vivian Wang <vi...@yahoo.com>.
Hi Manjula,
Thanks for your reply. But I am working on the web service client side, so it's still not clear to me that how I should handle ws-policies either defined in WSDL or in some other seperate files. Can you elaborate the following:
(1) Is it possible to attach the ws-policy settings on the client side like in the ws client policy file?
(2) Also, when I parse a WSDL, how do I know if a ws-policy is a WS security policy or other CUSTOM policy? Do I need to differentiate the different kinds of policies?
(3) Is there a general way to handle ws-policies defined in a WSDL (like the one in the WSDL is pasted here at the end of my message)? As you can see, ws-policies are defined and then referenced in portType, operation and binding definitions in the WSDL. How do I apply these at run time when I send out the web service call?
I mean, what I am trying to build is a generic web service client that can handle different kinds of WSDLs (web servers), so I DO NOT use a particular WSDL to generate the client stub code. I need a more generic way to handle WS-policy definitions and references in any kind of WSDLs.
Thanks!
Vivian
----- Original Message ----
From: Manjula Peiris <ma...@wso2.com>
To: Apache AXIS C User List <ax...@ws.apache.org>
Cc: axis-c-dev@ws.apache.org
Sent: Tuesday, April 7, 2009 1:05:20 AM
Subject: Re: WS-Policy support
Axis2/C Neethi framework handles WS-policy. If you want implement custom
policies you can do that in [1]. For more details see how secpolicy and
rmpolicy is implemented. You can attach polices in services.xml for
service, operation and message.
[1]
https://svn.apache.org/repos/asf/webservices/axis2/trunk/c/neethi/src
On Mon, 2009-04-06 at 16:40 -0700, Vivian Wang wrote:
> Hi All,
>
> I am working on using axis2/c to built a web service client. I have a
> few questions regarding WS-policy support in axis2/c. From the manual
> in axis2/c web site, it seems that the WS-policy support is built in
> to the axis2/c. I would like to know the following:
>
> (1) Are there any documents regarding how to use WS-policy in
> axis2/c?
>
> (2) Are there any examples regarding how to use WS-policy in axis2/c?
>
> (3) I have a customer presenting me with a WSDL that contains some
> policy definitions and then referenced in operation/binding
> definitions, suppose I can parse the WSDL and extract all the policy
> information, at runtime, how do I use axis2/c to set the related
> policy in a operation/binding when I create a web service client
> (using axis2/c)? Any APIs?
>
> The afore mentioned WSDL (shortened to contain only related info)
> is pasted at the end of the message :
>
> Thanks much in advance!
> Vivian
> ===========================================
> <wsdl:definitions ....>
> <wsp:UsingPolicy wsdl:required="true" />
> <wsp:Policy wsu:Id="BN_BN_BatchByIDQueryResponse_Binding">
> <wsp:ExactlyOne ...>
> </wsp:ExactlyOne>
> </wsp:Policy>
> <wsp:Policy wsu:Id="IF_IF_BatchByIDQueryResponse_In">
> <xyzAdmin:CentralAdministration
> xmlns:xyzAdmin="http://www.xyz.com/webas/1000/soap/features101/"
> wsp:Optional="true" />
> </wsp:Policy>
> - <wsp:Policy wsu:Id="OP_IF_OP_BatchByIDQueryResponse_In">
> <xyzcomhnd:enableCommit
> xmlns:xyzcomhnd="http://www.xyz.com/NW05/soap/features/commit/">false</xyzcomhnd:enableCommit>
> <xyzblock:enableBlocking
> xmlns:xyzblock="http://www.xyz.com/NW05/soap/features/blocking/">true</xyzblock:enableBlocking>
> </wsp:Policy>
> <wsdl:types>
> .....
> </wsdl:types>
> ...
> <wsdl:portType name="BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#IF_IF_BatchByIDQueryResponse_In" />
> </wsp:Policy>
> <wsdl:operation name="BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#OP_IF_OP_BatchByIDQueryResponse_In" />
> </wsp:Policy>
> <wsdl:input message="tns:BatchByIDQuery_sync" />
> <wsdl:output message="tns:BatchByIDResponse_sync" />
> <wsdl:fault name="StandardMessageFault"
> message="tns:StandardMessageFault" />
> </wsdl:operation>
> </wsdl:portType>
> <wsdl:binding name="BatchByIDQueryResponse_Binding"
> type="tns:BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#BN_BN_BatchByIDQueryResponse_Binding" />
> </wsp:Policy>
> <soap:binding
> transport="http://schemas.xmlsoap.org/soap/http" style="document" />
> <wsdl:operation name="BatchByIDQueryResponse_In">
> <soap:operation soapAction="" style="document" />
> <wsdl:input>
> <soap:body use="literal" />
> </wsdl:input>
> <wsdl:output>
> <soap:body use="literal" />
> </wsdl:output>
> <wsdl:fault name="StandardMessageFault">
> <soap:fault name="StandardMessageFault"
> use="literal" />
> </wsdl:fault>
> </wsdl:operation>
> </wsdl:binding>
> ......
> </wsdl:definitions>
>
>
Re: WS-Policy support
Posted by Manjula Peiris <ma...@wso2.com>.
Axis2/C Neethi framework handles WS-policy. If you want implement custom
policies you can do that in [1]. For more details see how secpolicy and
rmpolicy is implemented. You can attach polices in services.xml for
service, operation and message.
[1]
https://svn.apache.org/repos/asf/webservices/axis2/trunk/c/neethi/src
On Mon, 2009-04-06 at 16:40 -0700, Vivian Wang wrote:
> Hi All,
>
> I am working on using axis2/c to built a web service client. I have a
> few questions regarding WS-policy support in axis2/c. From the manual
> in axis2/c web site, it seems that the WS-policy support is built in
> to the axis2/c. I would like to know the following:
>
> (1) Are there any documents regarding how to use WS-policy in
> axis2/c?
>
> (2) Are there any examples regarding how to use WS-policy in axis2/c?
>
> (3) I have a customer presenting me with a WSDL that contains some
> policy definitions and then referenced in operation/binding
> definitions, suppose I can parse the WSDL and extract all the policy
> information, at runtime, how do I use axis2/c to set the related
> policy in a operation/binding when I create a web service client
> (using axis2/c)? Any APIs?
>
> The afore mentioned WSDL (shortened to contain only related info)
> is pasted at the end of the message :
>
> Thanks much in advance!
> Vivian
> ===========================================
> <wsdl:definitions ....>
> <wsp:UsingPolicy wsdl:required="true" />
> <wsp:Policy wsu:Id="BN_BN_BatchByIDQueryResponse_Binding">
> <wsp:ExactlyOne ...>
> </wsp:ExactlyOne>
> </wsp:Policy>
> <wsp:Policy wsu:Id="IF_IF_BatchByIDQueryResponse_In">
> <xyzAdmin:CentralAdministration
> xmlns:xyzAdmin="http://www.xyz.com/webas/1000/soap/features101/"
> wsp:Optional="true" />
> </wsp:Policy>
> - <wsp:Policy wsu:Id="OP_IF_OP_BatchByIDQueryResponse_In">
> <xyzcomhnd:enableCommit
> xmlns:xyzcomhnd="http://www.xyz.com/NW05/soap/features/commit/">false</xyzcomhnd:enableCommit>
> <xyzblock:enableBlocking
> xmlns:xyzblock="http://www.xyz.com/NW05/soap/features/blocking/">true</xyzblock:enableBlocking>
> </wsp:Policy>
> <wsdl:types>
> .....
> </wsdl:types>
> ...
> <wsdl:portType name="BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#IF_IF_BatchByIDQueryResponse_In" />
> </wsp:Policy>
> <wsdl:operation name="BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#OP_IF_OP_BatchByIDQueryResponse_In" />
> </wsp:Policy>
> <wsdl:input message="tns:BatchByIDQuery_sync" />
> <wsdl:output message="tns:BatchByIDResponse_sync" />
> <wsdl:fault name="StandardMessageFault"
> message="tns:StandardMessageFault" />
> </wsdl:operation>
> </wsdl:portType>
> <wsdl:binding name="BatchByIDQueryResponse_Binding"
> type="tns:BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#BN_BN_BatchByIDQueryResponse_Binding" />
> </wsp:Policy>
> <soap:binding
> transport="http://schemas.xmlsoap.org/soap/http" style="document" />
> <wsdl:operation name="BatchByIDQueryResponse_In">
> <soap:operation soapAction="" style="document" />
> <wsdl:input>
> <soap:body use="literal" />
> </wsdl:input>
> <wsdl:output>
> <soap:body use="literal" />
> </wsdl:output>
> <wsdl:fault name="StandardMessageFault">
> <soap:fault name="StandardMessageFault"
> use="literal" />
> </wsdl:fault>
> </wsdl:operation>
> </wsdl:binding>
> ......
> </wsdl:definitions>
>
>
Re: WS-Policy support
Posted by Manjula Peiris <ma...@wso2.com>.
Axis2/C Neethi framework handles WS-policy. If you want implement custom
policies you can do that in [1]. For more details see how secpolicy and
rmpolicy is implemented. You can attach polices in services.xml for
service, operation and message.
[1]
https://svn.apache.org/repos/asf/webservices/axis2/trunk/c/neethi/src
On Mon, 2009-04-06 at 16:40 -0700, Vivian Wang wrote:
> Hi All,
>
> I am working on using axis2/c to built a web service client. I have a
> few questions regarding WS-policy support in axis2/c. From the manual
> in axis2/c web site, it seems that the WS-policy support is built in
> to the axis2/c. I would like to know the following:
>
> (1) Are there any documents regarding how to use WS-policy in
> axis2/c?
>
> (2) Are there any examples regarding how to use WS-policy in axis2/c?
>
> (3) I have a customer presenting me with a WSDL that contains some
> policy definitions and then referenced in operation/binding
> definitions, suppose I can parse the WSDL and extract all the policy
> information, at runtime, how do I use axis2/c to set the related
> policy in a operation/binding when I create a web service client
> (using axis2/c)? Any APIs?
>
> The afore mentioned WSDL (shortened to contain only related info)
> is pasted at the end of the message :
>
> Thanks much in advance!
> Vivian
> ===========================================
> <wsdl:definitions ....>
> <wsp:UsingPolicy wsdl:required="true" />
> <wsp:Policy wsu:Id="BN_BN_BatchByIDQueryResponse_Binding">
> <wsp:ExactlyOne ...>
> </wsp:ExactlyOne>
> </wsp:Policy>
> <wsp:Policy wsu:Id="IF_IF_BatchByIDQueryResponse_In">
> <xyzAdmin:CentralAdministration
> xmlns:xyzAdmin="http://www.xyz.com/webas/1000/soap/features101/"
> wsp:Optional="true" />
> </wsp:Policy>
> - <wsp:Policy wsu:Id="OP_IF_OP_BatchByIDQueryResponse_In">
> <xyzcomhnd:enableCommit
> xmlns:xyzcomhnd="http://www.xyz.com/NW05/soap/features/commit/">false</xyzcomhnd:enableCommit>
> <xyzblock:enableBlocking
> xmlns:xyzblock="http://www.xyz.com/NW05/soap/features/blocking/">true</xyzblock:enableBlocking>
> </wsp:Policy>
> <wsdl:types>
> .....
> </wsdl:types>
> ...
> <wsdl:portType name="BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#IF_IF_BatchByIDQueryResponse_In" />
> </wsp:Policy>
> <wsdl:operation name="BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#OP_IF_OP_BatchByIDQueryResponse_In" />
> </wsp:Policy>
> <wsdl:input message="tns:BatchByIDQuery_sync" />
> <wsdl:output message="tns:BatchByIDResponse_sync" />
> <wsdl:fault name="StandardMessageFault"
> message="tns:StandardMessageFault" />
> </wsdl:operation>
> </wsdl:portType>
> <wsdl:binding name="BatchByIDQueryResponse_Binding"
> type="tns:BatchByIDQueryResponse_In">
> <wsp:Policy>
> <wsp:PolicyReference
> URI="#BN_BN_BatchByIDQueryResponse_Binding" />
> </wsp:Policy>
> <soap:binding
> transport="http://schemas.xmlsoap.org/soap/http" style="document" />
> <wsdl:operation name="BatchByIDQueryResponse_In">
> <soap:operation soapAction="" style="document" />
> <wsdl:input>
> <soap:body use="literal" />
> </wsdl:input>
> <wsdl:output>
> <soap:body use="literal" />
> </wsdl:output>
> <wsdl:fault name="StandardMessageFault">
> <soap:fault name="StandardMessageFault"
> use="literal" />
> </wsdl:fault>
> </wsdl:operation>
> </wsdl:binding>
> ......
> </wsdl:definitions>
>
>
WS-Policy support
Posted by Vivian Wang <vi...@yahoo.com>.
Hi All,
I am working on using axis2/c to built a web service client. I have a few questions regarding WS-policy support in axis2/c. From the manual in axis2/c web site, it seems that the WS-policy support is built in to the axis2/c. I would like to know the following:
(1) Are there any documents regarding how to use WS-policy in axis2/c?
(2) Are there any examples regarding how to use WS-policy in axis2/c?
(3) I have a customer presenting me with a WSDL that contains some policy definitions and then referenced in operation/binding definitions, suppose I can parse the WSDL and extract all the policy information, at runtime, how do I use axis2/c to set the related policy in a operation/binding when I create a web service client (using axis2/c)? Any APIs?
The afore mentioned WSDL (shortened to contain only related info) is pasted at the end of the message :
Thanks much in advance!
Vivian
===========================================
<wsdl:definitions ....>
<wsp:UsingPolicy wsdl:required="true"/>
<wsp:Policywsu:Id="BN_BN_BatchByIDQueryResponse_Binding">
<wsp:ExactlyOne...>
</wsp:ExactlyOne>
</wsp:Policy>
<wsp:Policywsu:Id="IF_IF_BatchByIDQueryResponse_In">
</wsdl:definitions>
<xyzAdmin:CentralAdministration xmlns:xyzAdmin="http://www.xyz.com/webas/1000/soap/features101/"wsp:Optional="true"/>
</wsp:Policy>
- <wsp:Policywsu:Id="OP_IF_OP_BatchByIDQueryResponse_In">
<xyzcomhnd:enableCommitxmlns:xyzcomhnd="http://www.xyz.com/NW05/soap/features/commit/">false</xyzcomhnd:enableCommit>
<xyzblock:enableBlockingxmlns:xyzblock="http://www.xyz.com/NW05/soap/features/blocking/">true</xyzblock:enableBlocking>
</wsp:Policy>
<wsdl:types>
.....
</wsdl:types>
...
<wsdl:portTypename="BatchByIDQueryResponse_In">
<wsp:Policy>
<wsp:PolicyReference URI="#IF_IF_BatchByIDQueryResponse_In"/>
</wsp:Policy>
<wsdl:operationname="BatchByIDQueryResponse_In">
<wsp:Policy>
<wsp:PolicyReference URI="#OP_IF_OP_BatchByIDQueryResponse_In"/>
</wsp:Policy>
<wsdl:input message="tns:BatchByIDQuery_sync"/>
<wsdl:output message="tns:BatchByIDResponse_sync"/>
<wsdl:fault name="StandardMessageFault"message="tns:StandardMessageFault"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:bindingname="BatchByIDQueryResponse_Binding"type="tns:BatchByIDQueryResponse_In">
<wsp:Policy>
<wsp:PolicyReference URI="#BN_BN_BatchByIDQueryResponse_Binding"/>
</wsp:Policy>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"style="document"/>
<wsdl:operationname="BatchByIDQueryResponse_In">
<soap:operation soapAction=""style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:faultname="StandardMessageFault">
<soap:fault name="StandardMessageFault"use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
......
WS-Policy support
Posted by Vivian Wang <vi...@yahoo.com>.
Hi All,
I am working on using axis2/c to built a web service client. I have a few questions regarding WS-policy support in axis2/c. From the manual in axis2/c web site, it seems that the WS-policy support is built in to the axis2/c. I would like to know the following:
(1) Are there any documents regarding how to use WS-policy in axis2/c?
(2) Are there any examples regarding how to use WS-policy in axis2/c?
(3) I have a customer presenting me with a WSDL that contains some policy definitions and then referenced in operation/binding definitions, suppose I can parse the WSDL and extract all the policy information, at runtime, how do I use axis2/c to set the related policy in a operation/binding when I create a web service client (using axis2/c)? Any APIs?
The afore mentioned WSDL (shortened to contain only related info) is pasted at the end of the message :
Thanks much in advance!
Vivian
===========================================
<wsdl:definitions ....>
<wsp:UsingPolicy wsdl:required="true"/>
<wsp:Policywsu:Id="BN_BN_BatchByIDQueryResponse_Binding">
<wsp:ExactlyOne...>
</wsp:ExactlyOne>
</wsp:Policy>
<wsp:Policywsu:Id="IF_IF_BatchByIDQueryResponse_In">
</wsdl:definitions>
<xyzAdmin:CentralAdministration xmlns:xyzAdmin="http://www.xyz.com/webas/1000/soap/features101/"wsp:Optional="true"/>
</wsp:Policy>
- <wsp:Policywsu:Id="OP_IF_OP_BatchByIDQueryResponse_In">
<xyzcomhnd:enableCommitxmlns:xyzcomhnd="http://www.xyz.com/NW05/soap/features/commit/">false</xyzcomhnd:enableCommit>
<xyzblock:enableBlockingxmlns:xyzblock="http://www.xyz.com/NW05/soap/features/blocking/">true</xyzblock:enableBlocking>
</wsp:Policy>
<wsdl:types>
.....
</wsdl:types>
...
<wsdl:portTypename="BatchByIDQueryResponse_In">
<wsp:Policy>
<wsp:PolicyReference URI="#IF_IF_BatchByIDQueryResponse_In"/>
</wsp:Policy>
<wsdl:operationname="BatchByIDQueryResponse_In">
<wsp:Policy>
<wsp:PolicyReference URI="#OP_IF_OP_BatchByIDQueryResponse_In"/>
</wsp:Policy>
<wsdl:input message="tns:BatchByIDQuery_sync"/>
<wsdl:output message="tns:BatchByIDResponse_sync"/>
<wsdl:fault name="StandardMessageFault"message="tns:StandardMessageFault"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:bindingname="BatchByIDQueryResponse_Binding"type="tns:BatchByIDQueryResponse_In">
<wsp:Policy>
<wsp:PolicyReference URI="#BN_BN_BatchByIDQueryResponse_Binding"/>
</wsp:Policy>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"style="document"/>
<wsdl:operationname="BatchByIDQueryResponse_In">
<soap:operation soapAction=""style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:faultname="StandardMessageFault">
<soap:fault name="StandardMessageFault"use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
......
Re: Application scope parameters
Posted by Supun Kamburugamuva <su...@gmail.com>.
See my comments inline.
On Mon, Apr 6, 2009 at 2:23 AM, Sam Carleton <sc...@miltonstreet.com>wrote:
> In my web service, there are a few setup tasks that only need to
> happen at initialization. The results need to be saved for the life
> of the service. To accomplish the setup tasks, the service needs to
> get a parameter from the configuration:
>
> Question:
>
> From within the services init function, is there any way to get a
> parameter element from axis2.xml or services.xml?
>
It is not possible to access these parameters from init function. You can
access the parameters when the first request comes to the service using the
msg_ctx.
>
> Question:
>
> After much digging around, is looks like the correct place to persist
> the results of the setup tasks is in the
> axis2_svc_skeleton.func_array, is this correct?
Correct place to put service specific persistant data is axis2_svc_ctx_t.
You can put them in axis2_conf_ctx_t as well.
You can find some useful info here
http://wsaxc.blogspot.com/2008/11/axis2c-handler-parameters.html
http://wsaxc.blogspot.com/2008/11/axis2c-modules-and-persistent.html
Supun.
>
>
> Sam
>
--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com