> On Dec 11, 2019, at 2:53 PM, David Blevins wrote:
>
>> On Dec 9, 2019, at 4:56 AM, Daniel Kulp wrote:
>>
>>> On Dec 8, 2019, at 9:17 PM, Jim Ma wrote:
>>> If both JAXB and JAX-WS changes, should cxf community join the effort to
>>> contribute and drive the jax-ws spec thing ?
>>
>> Well, th
> On Dec 9, 2019, at 4:56 AM, Daniel Kulp wrote:
>
>> On Dec 8, 2019, at 9:17 PM, Jim Ma wrote:
>> If both JAXB and JAX-WS changes, should cxf community join the effort to
>> contribute and drive the jax-ws spec thing ?
>
> Well, the issue is whom in the community CAN contribute and drive it.
If anyone wants to follow the conversation, the mailing is public and the
archives are here: https://www.eclipse.org/lists/jakartaee-platform-dev/.
There was some discussion about JAXB and JAXWS not being included in
Jakarta EE 9, which was a concern for me as I see these as widely used and
I feel
> On Dec 8, 2019, at 9:17 PM, Jim Ma wrote:
> If both JAXB and JAX-WS changes, should cxf community join the effort to
> contribute and drive the jax-ws spec thing ?
Well, the issue is whom in the community CAN contribute and drive it. With
Jakarta moving to Eclipse, it has also become “pay
If both JAXB and JAX-WS changes, should cxf community join the effort to
contribute and drive the jax-ws spec thing ?
Cheers,
Jim
On Fri, Dec 6, 2019 at 11:49 PM Daniel Kulp wrote:
>
> Interesting discussion… I'm honestly not sure how I feel about it.
>
> On one hand, it would be nice to be abl
A new major version where just the package names changes?
There are no good solutions to this. Oracle screwed this one majorly up.
fre. 6. des. 2019, 16:49 skrev Daniel Kulp :
>
> Interesting discussion… I'm honestly not sure how I feel about it.
>
> On one hand, it would be nice to be able to e
Interesting discussion… I'm honestly not sure how I feel about it.
On one hand, it would be nice to be able to enhance the specs in the future.
On the other hand, there hasn’t been an enhancement or any plans for an
enhancement for several years. Thus, it could end up being a lot of work
If we have to rename package for JAX-RS, JSONB , JSONP in CXF , then why
not for JAX-WS in a major version ?
If we leave it behind, we'll lose chance to evolve JAX-WS api in the
future.
On Wed, Nov 27, 2019 at 2:35 PM David Blevins
wrote:
> Thanks for the feedback, Romain.
>
> So everyone has c
Thanks for the feedback, Romain.
So everyone has context JAX-RS, JSONB, JSONP all will be renamed and therefore
CXF will not be able to escape the impact. Everything Romain mentions will
happen regardless.
The question really is, when this change happens for JAX-RS, JSONB, JSONP and
we unavoi
Hi David,
Guess enhnacements will go in jaxrs (better router etc)
On packages, no change is the only viable option for end users (javaagent,
maven plugins, sed, etc dont work in enough envs, break the portability ee
had been after for years and requires actual work and validation - qa time)
so gue
There is a discussion and vote going on the Jakarta EE side of the fence as to
if the following APIs should be moved from javax into jakarta namespaces.
- JAXB (javax.xml.bind -> jakarta.xml.bind)
- JAX-WS (javax.xml.ws -> jakarta.xml.ws)
What "move" means is these APIs would be able to contin
11 matches
Mail list logo
