You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2010/03/11 16:01:30 UTC
[jira] Created: (TUSCANY-3492) Investigate the use of JAX-WS plug
points in Axis to implement our ws binding
Investigate the use of JAX-WS plug points in Axis to implement our ws binding
-----------------------------------------------------------------------------
Key: TUSCANY-3492
URL: https://issues.apache.org/jira/browse/TUSCANY-3492
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Axis Binding Extension
Affects Versions: Java-SCA-2.0-M4
Environment: All
Reporter: Simon Laws
At the moment we have an amount of detailed integration code that provides our integration with the Axis engine. There are a number of downsides to this.
- it's complicated
- it doesn't allow us to plug other providers in easily
- it breaks easily when we upgrade to a new Axis version
We could look at the JAX-WS SPI in Java and plug into that instead.
May be issues with how we control Axis and apply policy but seems to be worth investigating.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-3492) Investigate the use of JAX-WS plug
points in Axis to implement our ws binding
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws reassigned TUSCANY-3492:
-----------------------------------
Assignee: Simon Laws
> Investigate the use of JAX-WS plug points in Axis to implement our ws binding
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-3492
> URL: https://issues.apache.org/jira/browse/TUSCANY-3492
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-2.0-M4
> Environment: All
> Reporter: Simon Laws
> Assignee: Simon Laws
>
> At the moment we have an amount of detailed integration code that provides our integration with the Axis engine. There are a number of downsides to this.
> - it's complicated
> - it doesn't allow us to plug other providers in easily
> - it breaks easily when we upgrade to a new Axis version
> We could look at the JAX-WS SPI in Java and plug into that instead.
> May be issues with how we control Axis and apply policy but seems to be worth investigating.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.