Hi Timothy
FYI, the jpa example (using openjpa3 feature) is executed/tests in the
itest. So, it works at least for the example.
Regards
JB
On 21/11/2019 04:22, tvogel wrote:
> JB,
> The feature installed fine using openjpa3. I'm in the process of testing
> my application to ensure it still fu
JB,
The feature installed fine using openjpa3. I'm in the process of testing
my application to ensure it still functions.
Thanks for the assistance!
Timothy
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
FWIW,
Another approach is to use OSGi Remote Services [1]...specifically ECF's
JaxRS distribution provider impls [2]. Remote Services Admin creates a
proxy for the remote service and this proxy is/may be treated as a local
service by SCR.
The ECF impl allows pluggable distribution providers,
OK, fragment is fine as well (the most important is to be in the
pax-jetty classloader).
And yes, Pax Web creates handler.
Maybe (for test), you can add a new jetty connector where you hack to
see if it works there.
Regards
JB
On 20/11/2019 18:17, Giamma wrote:
> Hi,
>
> my authenticator is in
Hi,
my authenticator is in a fragment that attaches to Fragment-Host:
org.ops4j.pax.web.pax-web-jetty, in fact my authenticator is correctly
instantiated.
(I verified this in debug, when the server starts and loads jetty.xml my
authenticator is created and registered into my custom instance of
Se
Hi
did you check if you have dynamic import on Jetty bundle (as I guess
your authenticator is in your own bundle) ?
Regards
JB
On 20/11/2019 17:41, Giamma wrote:
>
> Hello,
>
> please ignore the previous message, the jetty.xml snippet was removed by
> Nabble, this time I am using email.
>
> I
Hello,
please ignore the previous message, the jetty.xml snippet was removed by
Nabble, this time I am using email.
I am trying to implement a custom authenticator for Jetty. The idea is to
decode a custom HTTP header
and extract from there some credentials that I will validate in a custom
JAAS L
I understand where you’re coming from.
So Christian is basically right, the Jax-RS Whiteboard, like the whole DS
approach, feels somewhat like the future - a clean, elegant form of building
dynamic modular, standards-based services with Java. For me, the Wow! happened.
But it’s only almost, n
Hello,
I am trying to implement a custom authenticator for Jetty. The idea is to
decode a custom HTTP header
and extract from there some credentials that I will validate in a custom
JAAS LoginModule
I did the following:
1 - I created a Web application bundle with a web.xml in which the
auth-meth
Christian,
That's probably not going to happen as we migrate over with all the plugins,
providers and interceptors setup in the current environment to a better more
decoupled design but still using CXF. I'm not even 100% positive I'm free of
SOAP endpoints yet.
We a number of endpoints with diffe
That's another approach depending of the "control" you want.
The examples also show jaxrs whiteboard approach.
Regards
JB
On 20/11/2019 15:35, Christian Schneider wrote:
> The elegant way is to use the Aries JAXRS Whiteboard.
>
> Christian
>
> Am Mi., 20. Nov. 2019 um 00:54 Uhr schrieb Ranx0r0
The elegant way is to use the Aries JAXRS Whiteboard.
Christian
Am Mi., 20. Nov. 2019 um 00:54 Uhr schrieb Ranx0r0x <
regis...@bradleejohnson.com>:
> I noticed that when I stopped/uninstalled the bundle the CXF endpoint was
> still up and the bundle couldn't be reinstalled. By saving the Server
12 matches
Mail list logo
