Ok, I raised a PR to add parent scanning. I'm not sure if it makes sense
to do it a bit more cautiously, but to me it makes sense that app path is
inherited (and hence raised a ticket on JAX-RS spec).
John
On Sun, Aug 7, 2016 at 4:26 PM John D. Ament wrote:
> Hi Andriy,
>
> That explains quit
Hi Andriy,
That explains quite a few things then. I basically rewrote the test from
scratch, got rid of the original errors, but now just get 404's.
I may actually have a fix for you. I'll let you know this evening.
John
On Sun, Aug 7, 2016 at 4:15 PM Andriy Redko wrote:
> Hi John,
>
> That
Hi John,
That's pretty interesting, the issue caused by the fact that in your test
the Application class instances are Weld proxies, while in orginal test case
they aren't. As such, the @ApplicationPath annotations happen to be lost for
Weld
proxies, which causes address conflicts for JAXRSServ
Hi Andriy,
Actually I had come to that conclusion a couple of days ago. So I have to
wonder, was the test ever valid? I know that JAX-RS 2 specified that it was
OK to have multiple application impls per deployment, so I figure that
should work.
And if this is the issue, how come it was fine with
Hey John,
The exception in question comes from the fact that your deployment descriptor
contains 2 applications, BookStoreApplication and BookStoreCustomApplication:
return ShrinkWrap.create(WebArchive.class)
.addClasses(BookStoreApplication.class,
BookStoreCustomApplica
Hey John,
Sorry for delayed response. I haven't seen this kind of exception, I will
try to take a look and help you out.
Thanks.
Best Regards,
Andriy Redko
JDA> So I'm running into an interesting issue. I'm not sure if I found a bug,
JDA> or if I've gone way far into the deep end here.
JD
So I'm running into an interesting issue. I'm not sure if I found a bug,
or if I've gone way far into the deep end here.
I'm getting this exception: https://paste.apache.org/8WEp
You can see my changes here:
https://github.com/johnament/cxf/tree/arquillian
I suspect what's happening is that CXF
Hi Andriy,
Thanks for the prompt reply.
On Tue, Aug 2, 2016 at 9:28 PM Andriy Redko wrote:
> Hi John,
>
> Thanks a lot for your fixes, much appreciated and of great value for CDI
> users. To answer a couple of your questions / concerns.
>
>
>
> *JDA> First, its assuming that Weld is the only te
Hi John,
Thanks a lot for your fixes, much appreciated and of great value for CDI
users. To answer a couple of your questions / concerns.
JDA> First, its assuming that Weld is the only testable container.
This is very true. The reason for that is Weld was the only one implementing
CDI 1.2 at the
Hi,
Long time user, first time contributor to CXF. Though I'm no stranger to
the ASF by any long shot.
I was looking at putting in some fixes for issues I reported. First one
was a non-problem. However, when trying to figure out how to add tests to
ensure that empty application class applicati
10 matches
Mail list logo
