Re: Setting HTTP headers
Thanks Dinesh. I will try ur suggestion and let you know the result.
On Fri, Jan 9, 2009 at 1:32 PM, Dinesh Premalal wrote:
> Hi, Subra,
>
> "Subra Aswathanarayanan" writes:
>
> > I just wanted to clarify my question. In a axis2c webservice, when
> responding
> > to the client with a soap response, is there a way one can set a standard
> http
> > header too?
>
> AFAIK, there is no decent method for doing this. I think, in SOAP engine
> point
> of view this is something out of its scope. It would rather a job of
> transport. However you could figure out a way for setting http
> headers. Here is something I did while ago for client side [1]. Hope It
> would work for server side too. I never try it on the server side though.
>
>
> axis2_http_header_t *axis2_header;
> axutil_property_t *header_property;
> const char *header = (char *) wsclient_options->value;
>
> axis2_header = axis2_http_header_create_by_str (env, header);
> axutil_array_list_add (header_list, env, (void *)axis2_header);
> header_property = axutil_property_create(env);
> if (header_property && header_list)
> {
>axutil_property_set_value(header_property, env,
> header_list);
>axutil_property_set_free_func (header_property, env,
> axutil_array_list_free_void_arg);
>axis2_options_set_property(options, env,
> AXIS2_TRANSPORT_HEADER_PROPERTY,
> header_property);
> }
>
>
>
> 1.
> https://wso2.org/svn/browse/wso2/trunk/wsf/c/wsclient/src/stub.c?view=markup
>
Re: Setting HTTP headers
Hi, Subra,
"Subra Aswathanarayanan" writes:
> I just wanted to clarify my question. In a axis2c webservice, when responding
> to the client with a soap response, is there a way one can set a standard http
> header too?
AFAIK, there is no decent method for doing this. I think, in SOAP engine point
of view this is something out of its scope. It would rather a job of
transport. However you could figure out a way for setting http
headers. Here is something I did while ago for client side [1]. Hope It
would work for server side too. I never try it on the server side though.
axis2_http_header_t *axis2_header;
axutil_property_t *header_property;
const char *header = (char *) wsclient_options->value;
axis2_header = axis2_http_header_create_by_str (env, header);
axutil_array_list_add (header_list, env, (void *)axis2_header);
header_property = axutil_property_create(env);
if (header_property && header_list)
{
axutil_property_set_value(header_property, env,
header_list);
axutil_property_set_free_func (header_property, env,
axutil_array_list_free_void_arg);
axis2_options_set_property(options, env, AXIS2_TRANSPORT_HEADER_PROPERTY,
header_property);
}
1.https://wso2.org/svn/browse/wso2/trunk/wsf/c/wsclient/src/stub.c?view=markup
Re: Setting HTTP headers
I just wanted to clarify my question. In a axis2c webservice, when
responding to the client with a soap response, is there a way one can set a
standard http header too?
I searched in the archive but wasn't able to find any definitive answer.
On Thu, Jan 8, 2009 at 5:16 PM, Subra Aswathanarayanan
wrote:
> Hello,
> Is there a way to set standard http header ('Server' for e.g.) in the
> response.
>
> Subra
>
Re: link axis2c libraries as static libraries
I do not think you would be able to statically link and get Axis2/C to work, because it assumes dynamic loading for some of the behavior in the engine. Someone worked on static linking sometime back, but it was not completed. Samisa... Fan, Jan-fon wrote: Hi, I am trying to link the static libraries:AXIS2C_HOME/lib/*.a with my application. But when I build my application I got lots of “undefined reference to xxx_function” such as: /nfs/scec/disks/imo181/mtse/MaskTools/axis2c-src-1.3.0/lib/libaxis2_engine.a(svc_client.o)(.text+0x1274): In function `axis2_svc_client_send_receive_with_op_qname': /nfs/scec/disks/imo181/mtse/MaskTools/axis2c-src-1.3.0/src/core/clientapi/svc_client.c:777: undefined reference to `axiom_soap_envelope_get_body' I am using the following include directories in my make file: $(AXIS2C_HOME)/include $(AXIS2C_HOME)/include/axis2-1.3.0 $(AXIS2C_HOME)/samples/user_guide/clients What might be wrong? Thanks, Jan No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.5/1881 - Release Date: 1/7/2009 5:59 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company"
Re: Rampart Axis2C segfaults at rampart_context_free operation
Raju, Ideally with TransportBinding Rampart should send the message in a secure transport. This is a bug I guess. Please put a JIRA. BTW, If you want to send UserNameToken in a non secure transport like http then you can use AsymmetricBinding. Please see scenario2 in Rampart/C samples. -Manjula. On Thu, 2009-01-08 at 15:30 +0530, Srinivasa Raju, Somashekar (IE10) wrote: > Axis2C Team, > > > > AXIS2C - 1.4.0 Rampart - 1.2 > > > > I have configured an Axis2C webservice with WS-Security > TransportBinding policy and Rampart Authn Provider Module for > UserNameToken processing. Authn Module performs the UserNameToken > validation correctly but Axis2_http_server/Apache HTTPD segfaults in > rampart_context_free function at rampart_context.c:255. Rampart Authn > module code is same as the one provided in the Rampart samples. > > > > Please provide some pointers to investigate this issue. > > > > Thanks & Regards, > > Somashekar Raju > > Honeywell > > P We have a responsibility to the environment > Before printing this e-mail or any other document, let's ask ourselves > whether we need a hard copy. > > > > "This email and any attachments thereto, are intended only for use by > the addressee(s) named herein and contain Honeywell confidential > information. If you are not the intended recipient of this email, you > are hereby notified that any dissemination, distribution or copying > which amounts to misappropriation of this email and any attachments > thereto, is strictly prohibited. If you have received this email in > error, please immediately notify me and permanently delete the > original and any copy of any email and any printout thereof." > > > > > >
