You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Thomas Gentsch (JIRA)" <de...@tuscany.apache.org> on 2010/06/18 15:25:25 UTC
[jira] Created: (TUSCANY-3598) AxiomHelper should re-use Axis2c ENV
rather than creating own
AxiomHelper should re-use Axis2c ENV rather than creating own
-------------------------------------------------------------
Key: TUSCANY-3598
URL: https://issues.apache.org/jira/browse/TUSCANY-3598
Project: Tuscany
Issue Type: Improvement
Components: C++ SDO
Affects Versions: Cpp-M3
Reporter: Thomas Gentsch
Priority: Minor
The AxiomHelper always creates its own axis2c ENV object. In many cases this is sufficient, however I want the AxiomHelper to use the same logger as defined for the Axis2c main prog.
This is only possible if there is a way to make the AxiomHelper using an "imported" env object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-3598) AxiomHelper should re-use Axis2c ENV
rather than creating own
Posted by "Thomas Gentsch (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Gentsch updated TUSCANY-3598:
------------------------------------
Attachment: sdo_axiom.cpp-PATCH
sdo_axiom.h-PATCH
NOTE: The patch is slightly outdated and is based on the current SVN trunk of SDO C++.
With Axis2c 1.6 the type axis2_env_t has been renamedn to axutil_env_t. This is not consiedered in this patch.
See subsequent patch files.
> AxiomHelper should re-use Axis2c ENV rather than creating own
> -------------------------------------------------------------
>
> Key: TUSCANY-3598
> URL: https://issues.apache.org/jira/browse/TUSCANY-3598
> Project: Tuscany
> Issue Type: Improvement
> Components: C++ SDO
> Affects Versions: Cpp-M3
> Reporter: Thomas Gentsch
> Priority: Minor
> Attachments: sdo_axiom.cpp-PATCH, sdo_axiom.h-PATCH
>
>
> The AxiomHelper always creates its own axis2c ENV object. In many cases this is sufficient, however I want the AxiomHelper to use the same logger as defined for the Axis2c main prog.
> This is only possible if there is a way to make the AxiomHelper using an "imported" env object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-3598) AxiomHelper should re-use Axis2c ENV
rather than creating own
Posted by "Thomas Gentsch (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Gentsch updated TUSCANY-3598:
------------------------------------
Attachment: sdo_axiom.cpp-PATCH-withAxis2c-1.6
sdo_axiom.h-PATCH-withAxis2c-1.6
Now with Axis2c 1.6
> AxiomHelper should re-use Axis2c ENV rather than creating own
> -------------------------------------------------------------
>
> Key: TUSCANY-3598
> URL: https://issues.apache.org/jira/browse/TUSCANY-3598
> Project: Tuscany
> Issue Type: Improvement
> Components: C++ SDO
> Affects Versions: Cpp-M3
> Reporter: Thomas Gentsch
> Priority: Minor
> Attachments: sdo_axiom.cpp-PATCH, sdo_axiom.cpp-PATCH-withAxis2c-1.6, sdo_axiom.h-PATCH, sdo_axiom.h-PATCH-withAxis2c-1.6
>
>
> The AxiomHelper always creates its own axis2c ENV object. In many cases this is sufficient, however I want the AxiomHelper to use the same logger as defined for the Axis2c main prog.
> This is only possible if there is a way to make the AxiomHelper using an "imported" env object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.