tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Varga (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TOMEE-2439) Wrong default SAAJMetaFactory
Date Wed, 02 Jan 2019 19:58:00 GMT

    [ https://issues.apache.org/jira/browse/TOMEE-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732379#comment-16732379
] 

Peter Varga commented on TOMEE-2439:
------------------------------------

It's not clear to me whether TomEE is compiling javaee-api itself from a copy of the javaee-api
source code. If not, then this can just be closed since there it's not actually TomEE's source
code. The workaround is easy enough - to specify the factories within the app.

> Wrong default SAAJMetaFactory
> -----------------------------
>
>                 Key: TOMEE-2439
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2439
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 8.0.0-M1
>            Reporter: Peter Varga
>            Priority: Minor
>
> In javaee-api 8.0, the class javax.xml.soap.SAAJMetaFactory has a hardcoded default factory
of "org.apache.axis2.saaj.SAAJMetaFactoryImpl". This class from javaee-api is getting invoked
since JDK11 no longer includes javax.xml.soap.*. 
> Ultimately, this causes problems for applications that use a native JAX-WS stack and
don't include axis2 since TomEE itself does not either. 
> This code should work more like the implementation in org.apache.openejb.server.webservices.saaj.SaajFactoryFinder,
which figures out which factory to use based on what's available.
> Same issue with javax.xml.soap.SOAPConnectionFactory



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message