I've heard about "metro", but I don't understand what it means. However JAXWSProperties is in the JDK 1.7_25 libraries so I thought that was very portable. Still it's com.sun.internal so not a good idea I know, but I've looked at a lot of solutions online and no one has a good simple solution.
I work in a big company and my library needs to be easy for other groups in the company to use. If I use CXF then some people who have JBOSS might have trouble. Also some people have older Servicemixes, so I would have to build "two" libraries, one with an old CXF and one with a new CXF. Some groups don't use Servicemix and need normal java libraries. If I include CXF then they need to add all the CXF libraries and make sure there are no class package conflicts. Less code and less java libraries is always better code, don't you agree? I was hoping to avoid a lot of problems by only using libraries from Java, but I can't figure out how. I also don't have much time left. My company wants my library to be done in 2 days : ( Right now the only solution I have is to have two java libraries. Library A - Uses only Java libraries Library B - Uses library A but I create a Factory to give me back CXF WSDL service instance. Outside of Servicemix I use only A. Inside of Servicemix I use A and B. Not the best solution but it is all I can think of. Freeman, since you are a CXF expert can you think of a better solution that only uses the Java Libraries? CXF was built on top of JAX-WS so I would think there is a solution of some kind that would work for both. -- View this message in context: http://servicemix.396122.n5.nabble.com/JAXWSProperties-in-Servicemix-tp5717833p5717844.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
