No, you always can override it as showed in this thread, test it if you
doubt.
Le dim. 23 sept. 2018 23:24, exabrial12 a écrit :
> So we're in agreement? Whether it's a specification note or not, the user
> cannot replace Johnzon because it is annotated */* and necessitates an
> option to overri
Hi Jonathan,
What is important is to use LocalMBeanServer to allow to disable that. Then
using a dynamicmbean - through our wrapper if you prefer the api - is nice
because you can put description easily versus a standard mbean where it is
less natural. For the name building, using the objectnamebu
TomEE Devs: I want to work on a patch that can monitor the thread pool sizes
ManagedExecutorService and ManagedScheduledExecutorService that a user might
create in their tomee.xml. There's a couple of different methods in the
code, I was curious if someone could point me to the "best" or "current"
So we're in agreement? Whether it's a specification note or not, the user
cannot replace Johnzon because it is annotated */* and necessitates an
option to override the default behavior so the developer can select the
proper choice for their application?
--
Sent from: http://tomee-openejb.979440.
Le dim. 23 sept. 2018 21:25, exabrial12 a écrit :
> Sorry, posting from my phone, it's not annontated *exclusively* */*, but
> that's my point.
Yes, but both must be used to sort providers properly and it is spec
behavior.
If I never want Johnzon to handle anything, you simply
> can't change
Sorry, posting from my phone, it's not annontated *exclusively* */*, but
that's my point. If I never want Johnzon to handle anything, you simply
can't change the behavior without this patch.
Keep in mind, this doesn't modify the default behavior of Tomee and provides
an extension point.
--
Sen
https://github.com/eclipse/eclipselink.runtime/blob/master/moxy/org.eclipse.persistence.moxy/src/org/eclipse/persistence/jaxb/rs/MOXyJsonProvider.java
Its not annontated */*
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Ok so to clarify:
1. no "bug" in the stack for your case except that you app uses jaxb to
model json objects which is not clearly specified as required (think you
created a jira on that already)
2. you can use moxy if you follow the rules i mentionned - maybe the not
obvious part is cxf compares *
