10776Re: [soapbuilders] [ANN]JAX-WS 2.1 FCS released
- Feb 9, 2007Thanks Steve,
I will bring this up internally and get back to you next week.
Steve Loughran wrote:
> On 2/9/07, Davanum Srinivas <davanum@...
> <mailto:davanum%40gmail.com>> wrote:
> > Doug,
> > Just to be on the record..."Use endorsed mechanism" works for RI
> > because of this:
> > It's a bit unfair to other jaxws implementors to have to implement
> > hacks like this to get our stuff working under JDK6. I brought his up
> > before:
> > http://blogs.cocoondev.org/dims/archives/004717.html
> oh, that is devious. We could probably put a block on that in ant if
> it was felt to endanger the stability of hosting IDEs. We'll have to
> see what the eclipse perf team say about it, they being the best team
> at tracking down memory leaks -and classloaders do leak if you dont
> clean up very carefully. AntClassLoader extends BuildListener purely
> to clean itself up at the end of an IDE-hosted build (
> More subtly, AntClassLoader already blocks all classes from the parent
> except for those that come with the JRE; look at buildJrePackages()
> Doug. please communicate to your team that Ant too welcomes
> constructive code contributions, and one Sun employee does in fact
> have commit rights.
> If having JAX-WS 2.0 on the classpath of Java6 is felt to be a
> problem, we could just block it out entirely; it would cease to exist
> for tasks and java code in the same VM, but return for forked apps.
> Its kind of a brutal solution, but it may suit Dims, who no doubt has
> to field support requests of the kind "Axis 2 stops working on Java
> Dims, what do you think? de-endorse JAX-WS 2.0 in Ant1.7.1?
- << Previous post in topic Next post in topic >>