[jira] Commented: (TUSCANY-2542) core-databinding module has required dependency on interface-java-jaxws

["Simon Laws (JIRA)" <de...@tuscany.apache.org>]

    [ https://issues.apache.org/jira/browse/TUSCANY-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621753#action_12621753 ] 

Simon Laws commented on TUSCANY-2542:
-------------------------------------

The DataBindingModuleActivator  also fires up a  JAXWSJavaInterfaceProcessor.  So you would need extension points for both fault exception mappers and interface processors. I'm not sure if you are suggesting an automated way of detecting if the jars are available before using JAXWS function or simply that the user would include interface-java-jaxws and its dependencies if they knew jaxws processing was required. Sounds like this could be a bit of a stretch for 1.3.1? 

> core-databinding module has required dependency on interface-java-jaxws
> -----------------------------------------------------------------------
>
>                 Key: TUSCANY-2542
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2542
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-1.3
>            Reporter: ant elder
>             Fix For: Java-SCA-1.3.1
>
>
> The core-databinding module DataBindingModuleActivator code  news up a JAXWSFaultExceptionMapper which is from the interface-java-jaxws module, and this drags in the jaxws-api and jsr181-api jars as required dependencys for core-databinding. The jaxws-api and jsr181-api dependencys should be optional and not required in environments where the annotations are not being used.
> I guess we need something like a DefaultFaultExceptionMapper and a plug point so interface-java-jaxws can override the default if the api jars are available.
> See also TUSCANY-2514

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.