It's borderline. I'd say, yes, Oracle might say no. We could certainly try it.
Though, I think I distracted us for the more important consideration. Let's assume TomEE+ was also certified, would we want to move JAX-WS from TomEE+ to plain TomEE? -David On May 4, 2012, at 3:02 PM, Mark Struberg wrote: > Disabling the JAX-WS functionality by just removing the > ServletListener/Filter for it would be ok? > Or still not? > > > LieGrue, > strub > > > > ----- Original Message ----- >> From: David Blevins <[email protected]> >> To: [email protected]; Mark Struberg <[email protected]> >> Cc: >> Sent: Friday, May 4, 2012 11:27 PM >> Subject: Re: JAX-RS in Web Profile >> >> I've spoken directly with Oracle's Java EE licensing rep on this topic. >> >> The reason we made TomEE+ was so we could take the uncertified parts out in >> order for Oracle to give us our certification. They explicitly said they >> would >> not otherwise. >> >> They also checked our website and require that we add the exact phase "NOT >> Java EE6 Certified" next to TomEE+. JBoss had the same text on their >> downloads page for their contains-non-passing-code distro. >> >> >> -David >> >> On May 4, 2012, at 1:12 PM, Mark Struberg wrote: >> >>> I don't think this is correct! >>> >>> JBossAS7.0 also had some non web-profile features which were _known_ to be >> incomplete/not spec compliant/buggy. >>> But that was not a problem, because those things are _not_ in the >> web-profile! >>> As long as you don't claim JAX-WS or full-profile compatibility it is >> imo not a problem. >>> >>> It would just be an 'additional' feature which is not officially >> supported by the release. >>> We can of course add in the Readme that >>> >>> 'despite being packaged, JAX-WS is not officially part of this TomEE >> release and did not pass any EE TCK.' >>> >>> >>> LieGrue >>> strub >>> >>> >>> >>> ----- Original Message ----- >>>> From: David Blevins <[email protected]> >>>> To: [email protected] >>>> Cc: >>>> Sent: Friday, May 4, 2012 10:07 PM >>>> Subject: Re: JAX-RS in Web Profile >>>> >>>> >>>> On May 4, 2012, at 12:54 PM, Romain Manni-Bucau wrote: >>>> >>>>> +1 to add it >>>>> -1 to split, it will make our build more complicated (again) and >> our >>>>> dependency management a mess >>>> >>>> Can you clarify on the "split". You understand that we >> can't add >>>> JAX-WS to the Web Profile unless it is certified, so if we don't >> split them >>>> it essentially means we cannot add JAX-RS. >>>> >>>> We'd have to get JAX-WS passing the TCK in TomEE+ before we could >> add it to >>>> TomEE. >>>> >>>> >>>> -David >>>> >>>>> Le 4 mai 2012 21:37, "David Blevins" >>>> <[email protected]> a écrit : >>>>> >>>>>> JAX-RS is being added to the Java EE 7 Web Profile. Given that >> and the >>>>>> fact that many of the recent user questions are about JAX-RS, >> perhaps >>>> we >>>>>> should consider adding it to our Web Profile distro now rather >> than >>>> later. >>>>>> >>>>>> The big question in my mind is, how small can we get it? Can >> we do it >>>>>> with CXF in a way that doesn't bring in JAX-WS? >>>>>> >>>>>> If we pull in JAX-WS too, then we have to certify it and that >> is a >>>> major >>>>>> effort. >>>>>> >>>>>> >>>>>> -David >>>>>> >>>>>> >>>> >>
