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 "Damitha Kumarage (JIRA)" <ji...@apache.org> on 2010/06/02 05:17:38 UTC
[jira] Commented: (AXIS2C-723) Should dynamically resolve to
transport
[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874395#action_12874395 ]
Damitha Kumarage commented on AXIS2C-723:
-----------------------------------------
Nadir,
You can dynamically add a new transport implementation for a existing transport dynamically by giving the transport library name in axis2.xml. For example you can implement a new http transport sender/receiver library and give it's library name as the class attribute of the transport sender/receiver.
However you cannot add a completely new transport dynamically, for example JMS without some code changes to Axis2/C.
> Should dynamically resolve to transport
> ---------------------------------------
>
> Key: AXIS2C-723
> URL: https://issues.apache.org/jira/browse/AXIS2C-723
> Project: Axis2-C
> Issue Type: Improvement
> Components: core/transport
> Affects Versions: 1.1.0
> Environment: OS:WindowsXP
> Reporter: Atsushi Monna
> Assignee: Damitha Kumarage
>
> I have a desire for new trasnport in Axis2/C.
> I found a hard cording the transports in axis2_const.h like this.
> #define AXIS2_TRANSPORT_HTTP "http"
> #define AXIS2_TRANSPORT_SMTP "smtp"
> #define AXIS2_TRANSPORT_TCP "tcp"
> #define AXIS2_TRANSPORT_XMPP "xmpp"
> #define AXIS2_TRANSPORT_HTTPS "https"
> typedef enum
> {
> AXIS2_TRANSPORT_ENUM_HTTP = 0,
> AXIS2_TRANSPORT_ENUM_SMTP,
> AXIS2_TRANSPORT_ENUM_TCP,
> AXIS2_TRANSPORT_ENUM_XMPP,
> AXIS2_TRANSPORT_ENUM_HTTPS,
> AXIS2_TRANSPORT_ENUM_MAX
> } AXIS2_TRANSPORT_ENUMS;
> And using like this.
> /**
> * Adds a transport in description.
> * @param conf pointer to conf struct
> * @param env pointer to environment struct
> * @param transport pointer to transport in description. conf assumes
> * ownership of the struct
> * @return AXIS2_SUCCESS on success, else AXIS2_FAILURE
> */
> AXIS2_EXTERN axis2_status_t AXIS2_CALL
> axis2_conf_add_transport_in(axis2_conf_t *conf,
> const axutil_env_t *env,
> axis2_transport_in_desc_t *transport,
> const AXIS2_TRANSPORT_ENUMS trans_enum);
> If we want to add a new transport, we must defin a transport in axis2_const.h and re-build Axis2/C modules.
> In Axis2 (Java), we don't need to re-build Axis2 modules, if we think so.
> We can only provid a class implemented TransportProvider I/F and add a entry at axis2.xml file.
> Axis2 said in key features, engine is completely transport-independent at "Transport Fremework".
> I think the realization like Axis2 is advisable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
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
AXIS2C transport sender/receiver in one library?
Posted by Nadir Amra <am...@us.ibm.com>.
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
AXIS2C transport sender/receiver in one library?
Posted by Nadir Amra <am...@us.ibm.com>.
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