On Oct 17, 2012, at 9:00 AM, efe4dsip <[email protected]> wrote:
> Hi > > I am currently trying to get a webapp deployed, that expose some webservices > build on CXF stack. > > The application developpers have delivered during last iteration a > webservice that must be called the > "Dynamic Invocation Interface" way. That means the stubs will be generated > on the fly, and then must be compiled. > > In addition, my platform provider says we will not be allowed to use a JDK > on target platform. > > As tomcat distribution includes from 5.5 onwards the eclipse JDT compiler, > used by JASPER using > the "Compiler API" (see org.apache.jasper.JspCompilationContext), JDT could > maybe be setup as alternative compiler. > > Is there a way to tell CXF which compiler to use? Not that I'm aware of, no. WIth that old of a version of CXF, it likely just calls out to javac on the command line. Thus, you may be able to jury rig something by having a javac shell script in the path or something. With more recent versions of CXF, we use the javax.tools.JavaCompiler API's available on Java6. In that case, you would need to wire a tool into the standard ServiceLoader.load(..) things to load the appropriate JavaCompiler class. Dan > > My target platform is > Oracle-JDK-1.6 > tomcat-5.5 (7.0.x soon) > cxf-2.3.0 > > Regards > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Possible-to-select-Compiler-used-by-CXF-tp5716831.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
