Congrats to the hero.
+1
Having duplicated annotations/types using multiple modules is always painful. A unique
type helps users a lot to pick the right class.
Can we actually submit a PR somewhere to get our changes into JSR250 or will be this done
by someone else?
Am 28.04.2016 um 10:46 schrieb Romain Manni-Bucau
<rmannibucau(a)gmail.com>:
Hi guys (and the hero ;))
Do you think there is a hope we can move (copy for compatibility) TypeLiteral to JSR
250?
Here is the rational behind it:
- CDI and JAXRS have more or less the same class
- JSONB needs it as well
Each spec can duplicate it but it makes the overall EE API inconsistent and the learning
curve harder.
Since generics are really important in nowaday coding and the class itself if not that
big I think JSR 250 can be a good place to put it.
Let me know if there is no hope at all and i'll give this feedback to JSONB, if there
is a hope please give me some pointers to move forward.
My overall vision is to make TypeLiteral and GenericType (JAXRS) deprecated and support
both current and JSR 250 new API to slowly support a single type in the whole stack.
wdyt?
Romain Manni-Bucau
@rmannibucau <
https://twitter.com/rmannibucau> | Blog
<
http://rmannibucau.wordpress.com/> | Github <
https://github.com/rmannibucau>
| LinkedIn <
https://www.linkedin.com/in/rmannibucau> | Tomitriber
<
http://www.tomitribe.com/> | JavaEE Factory
<
https://javaeefactory-rmannibucau.rhcloud.com/>
2016-04-26 13:55 GMT+02:00 Mark Struberg <struberg(a)yahoo.de
<mailto:struberg@yahoo.de>>:
You are a hero!
txs,
strub
> Am 23.04.2016 um 11:36 schrieb Antoine Sabot-Durand <antoine(a)sabot-durand.net
<mailto:antoine@sabot-durand.net>>:
>
> Hi all,
>
> I have some news from Linda about JSR 250 MR. It should be launched in the coming
weeks. I don't have confirmation of the estimated release date yet, but it should be
ok for our own release date.
>
> Antoine
> _______________________________________________
> cdi-dev mailing list
> cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/cdi-dev
<
https://lists.jboss.org/mailman/listinfo/cdi-dev>
>
> Note that for all code provided on this list, the provider licenses the code under
the Apache License, Version 2 (
http://www.apache.org/licenses/LICENSE-2.0.html
<
http://www.apache.org/licenses/LICENSE-2.0.html>). For all other ideas provided on
this list, the provider waives all patent and other intellectual property rights inherent
in such information.
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/cdi-dev
<
https://lists.jboss.org/mailman/listinfo/cdi-dev>
Note that for all code provided on this list, the provider licenses the code under the
Apache License, Version 2 (
http://www.apache.org/licenses/LICENSE-2.0.html
<
http://www.apache.org/licenses/LICENSE-2.0.html>). For all other ideas provided on
this list, the provider waives all patent and other intellectual property rights inherent
in such information.
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
Note that for all code provided on this list, the provider licenses the code under the
Apache License, Version 2 (
http://www.apache.org/licenses/LICENSE-2.0.html). For all other
ideas provided on this list, the provider waives all patent and other intellectual
property rights inherent in such information.