You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Nadir Amra <am...@us.ibm.com> on 2010/06/05 02:13:41 UTC
AXIS2C transport sender/receiver in one library?
I was just wondering, does transport sender and receiver have to be in
different libraries? Can they be built in one library and the Axis2.xml
point to the same library for sender and receiver?
And if so, would it be better to just one library for the transport
sender/receiver?
Nadir Amra
Integrated Web Services for IBM i Operating System
Internet: amra@us.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org
Re: AXIS2C transport sender/receiver in one library?
Posted by Nandika Jayawardana <ja...@gmail.com>.
In axis2.xml transport sender and transport receiver are configured
differently. Hence it is necessary to have different configurations for the
sender and receiver.
Regards
Nandika
On Mon, Jun 7, 2010 at 9:28 AM, Damitha Kumarage <da...@wso2.com> wrote:
> Nadir Amra wrote:
>
>> I was just wondering, does transport sender and receiver have to be in
>> different libraries? Can they be built in one library and the Axis2.xml
>> point to the same library for sender and receiver?
>>
>> And if so, would it be better to just one library for the transport
>> sender/receiver?
>>
>>
> I think it is OK to have same library for sender and receiver. But I
> think we should have the flexibility of specifying them differently on
> configuration file.
> In that case we can give the same library for sender and receiver.
>
> Thanks,
> Damitha
>
> Nadir Amra
>> Integrated Web Services for IBM i Operating System
>> Internet: amra@us.ibm.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: c-dev-help@axis.apache.org
>>
>>
>>
>>
>
>
> --
> __________________________________________________________________
>
> Damitha Kumarage
> http://people.apache.org/
> __________________________________________________________________
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: c-dev-help@axis.apache.org
>
>
--
http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com
Re: AXIS2C transport sender/receiver in one library?
Posted by Nandika Jayawardana <ja...@gmail.com>.
In axis2.xml transport sender and transport receiver are configured
differently. Hence it is necessary to have different configurations for the
sender and receiver.
Regards
Nandika
On Mon, Jun 7, 2010 at 9:28 AM, Damitha Kumarage <da...@wso2.com> wrote:
> Nadir Amra wrote:
>
>> I was just wondering, does transport sender and receiver have to be in
>> different libraries? Can they be built in one library and the Axis2.xml
>> point to the same library for sender and receiver?
>>
>> And if so, would it be better to just one library for the transport
>> sender/receiver?
>>
>>
> I think it is OK to have same library for sender and receiver. But I
> think we should have the flexibility of specifying them differently on
> configuration file.
> In that case we can give the same library for sender and receiver.
>
> Thanks,
> Damitha
>
> Nadir Amra
>> Integrated Web Services for IBM i Operating System
>> Internet: amra@us.ibm.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: c-dev-help@axis.apache.org
>>
>>
>>
>>
>
>
> --
> __________________________________________________________________
>
> Damitha Kumarage
> http://people.apache.org/
> __________________________________________________________________
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: c-dev-help@axis.apache.org
>
>
--
http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com
Re: AXIS2C transport sender/receiver in one library?
Posted by Damitha Kumarage <da...@wso2.com>.
Nadir Amra wrote:
> I was just wondering, does transport sender and receiver have to be in
> different libraries? Can they be built in one library and the Axis2.xml
> point to the same library for sender and receiver?
>
> And if so, would it be better to just one library for the transport
> sender/receiver?
>
I think it is OK to have same library for sender and receiver. But I
think we should have the flexibility of specifying them differently on
configuration file.
In that case we can give the same library for sender and receiver.
Thanks,
Damitha
> Nadir Amra
> Integrated Web Services for IBM i Operating System
> Internet: amra@us.ibm.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: c-dev-help@axis.apache.org
>
>
>
--
__________________________________________________________________
Damitha Kumarage
http://people.apache.org/
__________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org
Re: AXIS2C why axutil_error_default.h and axutil_error.h
Posted by Damitha Kumarage <da...@wso2.com>.
Hi Nadir,
Nadir Amra wrote:
> I am trying to understand the need for axutil_error_default.h. My
> thinking is the single thing in this file:
>
> AXIS2_EXTERN axutil_error_t *AXIS2_CALL
> axutil_error_create(
> axutil_allocator_t * allocator);
>
> Should be in axutil_error.h and axutil_error_default.h eliminated.
>
> I plan on doing this unless there is something that I am missing?
>
This is because we need to be able to pass environment a custom
implementation of error.
When creating environment one can use a constructor like
axutil_env_create, which just take
allocator as argument. In that case it create the default error by using
axutil_error_create().
However one can use a function like axutil_env_create_with_error_log in
which case she can pass
her own error implementation. In that case she will implement her own
error implementation by including
error.h, not error_default.h. She will have her own error constructor in
different name.
Thanks,
Damitha
> Nadir Amra
> Integrated Web Services for IBM i Operating System
> Internet: amra@us.ibm.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: c-dev-help@axis.apache.org
>
>
>
--
__________________________________________________________________
Damitha Kumarage
Technical Lead; WSO2 Inc.
"Oxygenating the Web Service Platform; " http://www.wso2.com/
blog: " http://damithakumarage.wordpress.com/
__________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org
Re: AXIS2C why axutil_error_default.h and axutil_error.h
Posted by Damitha Kumarage <da...@wso2.com>.
Hi Nadir,
Nadir Amra wrote:
> I am trying to understand the need for axutil_error_default.h. My
> thinking is the single thing in this file:
>
> AXIS2_EXTERN axutil_error_t *AXIS2_CALL
> axutil_error_create(
> axutil_allocator_t * allocator);
>
> Should be in axutil_error.h and axutil_error_default.h eliminated.
>
> I plan on doing this unless there is something that I am missing?
>
This is because we need to be able to pass environment a custom
implementation of error.
When creating environment one can use a constructor like
axutil_env_create, which just take
allocator as argument. In that case it create the default error by using
axutil_error_create().
However one can use a function like axutil_env_create_with_error_log in
which case she can pass
her own error implementation. In that case she will implement her own
error implementation by including
error.h, not error_default.h. She will have her own error constructor in
different name.
Thanks,
Damitha
> Nadir Amra
> Integrated Web Services for IBM i Operating System
> Internet: amra@us.ibm.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: c-dev-help@axis.apache.org
>
>
>
--
__________________________________________________________________
Damitha Kumarage
Technical Lead; WSO2 Inc.
"Oxygenating the Web Service Platform; " http://www.wso2.com/
blog: " http://damithakumarage.wordpress.com/
__________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org
AXIS2C why axutil_error_default.h and axutil_error.h
Posted by Nadir Amra <am...@us.ibm.com>.
I am trying to understand the need for axutil_error_default.h. My
thinking is the single thing in this file:
AXIS2_EXTERN axutil_error_t *AXIS2_CALL
axutil_error_create(
axutil_allocator_t * allocator);
Should be in axutil_error.h and axutil_error_default.h eliminated.
I plan on doing this unless there is something that I am missing?
Nadir Amra
Integrated Web Services for IBM i Operating System
Internet: amra@us.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org
AXIS2C why axutil_error_default.h and axutil_error.h
Posted by Nadir Amra <am...@us.ibm.com>.
I am trying to understand the need for axutil_error_default.h. My
thinking is the single thing in this file:
AXIS2_EXTERN axutil_error_t *AXIS2_CALL
axutil_error_create(
axutil_allocator_t * allocator);
Should be in axutil_error.h and axutil_error_default.h eliminated.
I plan on doing this unless there is something that I am missing?
Nadir Amra
Integrated Web Services for IBM i Operating System
Internet: amra@us.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org
Re: AXIS2C transport sender/receiver in one library?
Posted by Damitha Kumarage <da...@wso2.com>.
Nadir Amra wrote:
> I was just wondering, does transport sender and receiver have to be in
> different libraries? Can they be built in one library and the Axis2.xml
> point to the same library for sender and receiver?
>
> And if so, would it be better to just one library for the transport
> sender/receiver?
>
I think it is OK to have same library for sender and receiver. But I
think we should have the flexibility of specifying them differently on
configuration file.
In that case we can give the same library for sender and receiver.
Thanks,
Damitha
> Nadir Amra
> Integrated Web Services for IBM i Operating System
> Internet: amra@us.ibm.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: c-dev-help@axis.apache.org
>
>
>
--
__________________________________________________________________
Damitha Kumarage
http://people.apache.org/
__________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org