[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-c-dev
Subject:    [jira] Commented: (AXIS2C-1211) Improving the
From:       "Damitha Kumarage (JIRA)" <jira () apache ! org>
Date:       2008-06-30 15:33:45
Message-ID: 317028655.1214840025029.JavaMail.jira () brutus
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AXIS2C-1211?page=com.atlassian.jira.plugin \
.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609260#action_12609260 ] 

Damitha Kumarage commented on AXIS2C-1211:
------------------------------------------

Diluka,

Can you show me a specific situation where conf_ctx needed in service initialization. \
In Savan/C I can see that in publishing client sample and subscription manager \
service  a conf_ctx is created out of conf passed to init function. But even there it \
is not neccessary to create such a cont_ctx because it is not used for any useful \
things. It is created just because publishing cliet needs it. But when you look at \
publising client code it does not use it either. It jusr retrieve conf from it. It is \
the only use publishing client has from conf_ctx. So my suggestion is to pass just \
the conf to the service init as it is now. But in Savan/C we need to change \
publishing client code not to accept a conf_ctx but a conf.

> Improving the AXIS2_SVC_SKELETON_INIT_WITH_CONF
> -----------------------------------------------
> 
> Key: AXIS2C-1211
> URL: https://issues.apache.org/jira/browse/AXIS2C-1211
> Project: Axis2-C
> Issue Type: Bug
> Environment: Ubuntu 7.04
> Reporter: Diluka Moratuwage
> 
> I have some problem with AXIS2_SVC_SKELETON_INIT_WITH_CONF macro. Apparently it \
> allows the service to use the configuration, within the service, when it's starting \
> up. But, by the time this function is called (when loading services), we have \
> already created the conf_ctx. And as I have seen the very usage of this comes when \
> a service have to be started up. But in order to use it, we have to create conf_ctx \
> within the service most probably. So I think it will be appropriate to send the \
> conf_ctx instead of conf into a service. So if the service has any need of the \
> conf, still it can get the conf from the conf_ctx.

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]