We definitely don't use it in TomEE. As noted already there are definitely no
plans in Jakarta to adopt OSGi -- even support for modules isn't required or in
any current plans.
-David
> On Oct 19, 2022, at 5:49 AM, Alessio Soldano wrote:
>
> I agree, especially considering the Jakarta aspec
Hey Andriy,
Sounds like a workable plan. If 4.0.0 is still ongoing once TomEE 9 is
released, I'd help there before moving onto any potential 4.1 work. I'd expect
TomEE 10 work to go far into next year, so there's no immediate time pressure
-- just trying to get a feel for how it might all com
> On Oct 8, 2022, at 8:21 PM, Andriy Redko wrote:
>
> I was thinking about that as well, since Jakarta EE 10 is already out [1]. If
> I am not mistaken,
> we haven't discussed the future Jakarta plans yet, trying to address major
> 4.0.0 migration issues.
> Personally I was thinking that havin
Jumping into a random spot in this thread.
My understanding of the current state of 4.0.0 is:
- Targets Java 17 due to Spring deps
- Targets Jakarta EE 9 / Jakarta Rest 3.0
The trick for us on the TomEE side is that Jakarta EE 9.1 requires support for
Java 11. We're still using 3.5.x with by
> On Apr 30, 2021, at 11:09 AM, David Blevins wrote:
>
> There's a bunch of tests that got fixed because we weren't properly getting
> the classes a MessageBodyReader or Writer supports via it's generic
> declaration. So there's a handful of tests that are
the next 48 hours for us to make the EE 9.1 release.
> Meanwhile, wanted to give everyone a heads up so there isn't just one big
> surprising PR. I mean, it'll still be big, but at least not surprising :)
>
> DB> Thanks again to Andriy and Andy for all the support! I&#x
have gotten
this far without either of you.
-David
> On Apr 16, 2021, at 2:29 AM, David Blevins wrote:
>
> Hi All,
>
> Spinning a new thread as to not overload the original "@Encoded TCK issue"
> too much.
>
> Thanks, Andriy, for the Jenkins information and
n you used. That might
make for a good way to get through these really quickly (or at least quicker).
Thank you so much for all the help, Andriy!
-David
> On Apr 22, 2021, at 7:44 PM, David Blevins wrote:
>
>> On Apr 22, 2021, at 6:38 PM, Andriy Redko wrote:
>>
>>
> On Apr 22, 2021, at 6:38 PM, Andriy Redko wrote:
>
> You are very fast :-D I found the problem but I don't know yet what is
> happening in details. The test
> fails not because of ContextResolver but the presence of TckJaxbProvider. So
> what is happening, on the reading
> side, the CXF's JA
Thanks for that test case, Andriy! Pulling it down to debug through it to
learn how all this is put together.
Likely there's something unrelated then tripping this up.
-David
> On Apr 21, 2021, at 8:53 PM, David Blevins wrote:
>
> I'm investigating CXF-8516 (jaxrs.spec.p
I'm investigating CXF-8516 (jaxrs.spec.provider.jaxbcontext
readWriteProviderTest) and have some questions on ContextResolvers in general.
The TL;DR of readWriteProviderTest:
- There is an application supplied javax.ws.rs.ext.ContextResolver for
JAXBContext
- The resolver returns a custom JAX
> On Apr 16, 2021, at 4:46 AM, Andriy Redko wrote:
>
> Good idea to create a subtask for each failure, personally haven't found time
> to do that, my bad,
> thank you.
Happy to help!
> I will go over them and point to the relevant pull requests, some of these
> issues
> have been worked on al
Hi All,
Spinning a new thread as to not overload the original "@Encoded TCK issue" too
much.
Thanks, Andriy, for the Jenkins information and TCK setup scripts. Thanks
also, Andy, for the link to the proper JIRA issue.
Here's what I've done. I converted the Jenkinsfile into a script and hamme
> On Apr 14, 2021, at 1:13 PM, David Blevins wrote:
>
> Is there any information on how to setup the TCK to run against plain CXF?
> If so I can maybe create an https://tck.work/cxf/ project and for a non-TomEE
> view and get some pure-CXF-only results.
Think I found it.
che.org/jira/browse/CXF-7996 - in the most recent
> report,
> AM> there were ~80 failures, but it's possible that some of them have already
> AM> been fixed since then. It might help if you post your failures in that
> AM> issue to keep better track of them.
>
> On Apr 13, 2021, at 9:10 AM, Andy McCright
> wrote:
>
> Hi David,
>
> I had to do some digging - but yes, we addressed that issue in our Open
> Liberty fork of CXF and I must not have contributed that fix back to the main
> CXF fork (apologies for that).
>
> Here are the changes I made in
Hi All,
I'm investigating a Jakarta EE TCK failure:
-
com/sun/ts/tests/jaxrs/ee/rs/beanparam/form/plain/JAXRSClient#formFieldParamEntityWithEncodedTest_from_standalone
This test posts a form and is checking to ensure the @Encoded annotation is
being respected. The code to respect that annota
> 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
> 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.
unavoidably take a hit, do we want to also take JAX-WS and JAXB with us or
do we leave it behind?
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Nov 26, 2019, at 1:28 PM, Romain Manni-Bucau wrote:
>
> Hi David,
>
> Guess enhnacements will go in jaxrs
e?
- Are there people willing to help or do the work?
Do people have any thoughts, questions or preferences?
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
lcome!
- https://github.com/apache/cxf/pull/556
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
/docs/jax-rs.html
>
> The intro gives some points
> Le 22 sept. 2013 01:29, "David Blevins" a écrit :
>
>> Putting together some information on Apache and Java EE 7 for JavaOne next
>> week.
>>
>> There any information on JAX-RS 2.0 status?
>>
>>
>> -David
>>
>>
Putting together some information on Apache and Java EE 7 for JavaOne next week.
There any information on JAX-RS 2.0 status?
-David
On Jun 18, 2011, at 9:16 PM, Ryan Zoerner wrote:
> It has been a while since I have written to the dev list, but I am working
> on putting an JAXRSEJBInvoker together. The naive implementation (in this
> case, that means rough draft), consists of taking JAXRSInvoker, replacing
> all instances of
25 matches
Mail list logo
