I pretend to replace Metro with CXF in the future. Will current clients of there web services break, requiring the WSDL to be reimported?
2015-10-27 9:12 GMT-02:00 Romain Manni-Bucau <[email protected]>: > Hi > > for you pretty much nothing but using CXF you can get a performance boost > if you are on the oracle JVM. > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> > > 2015-10-27 12:10 GMT+01:00 Felipe Jaekel <[email protected]>: > > > Hi, > > > > I have a Metro based web service app that I'd like to run on TomEE. > > > > Currently it runs on Tomcat with Metro libs on the server. > > > > Adding Metro libs to WEB-INF I was able to run it on TomEE. Didn't found > > any issues so far. > > > > I noticed the following section on system.properties: > > > > > > # These properties are only for cxf service (SOAP webservices) and TomEE+ > > # If you don't use special tricks and sun default implementation, > > uncommenting these 4 lines forces TomEE to use it without overhead at > all = > > # javax.xml.soap.MessageFactory = > > com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl > > # javax.xml.soap.SOAPFactory = > > com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl > > # javax.xml.soap.SOAPConnectionFactory = > > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory > > # javax.xml.soap.MetaFactory = > > com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl > > > > > > What would be the advantage of uncommenting these lines? > > > > Thanks > > >
