I see both jackson and johnzon are now part of TomEE 8 M2:
jackson-annotations-2.9.0.jar
jackson-core-2.9.4.jar
jackson-databind-2.9.4.jar
jackson-dataformat-yaml-2.9.4.jar
johnzon-core-1.1.11.jar
johnzon-jaxrs-1.1.11.jar
johnzon-jsonb-1.1.11.jar
johnzon-mapper-1.1.11.jar
Should not only johnzon b
I think ActiveMQ pulls jackson in, as it uses Jackson internally. I don't
know that we could avoid that without forking and making some (potentially
big) changes.
Jon
On Wed, Jun 19, 2019 at 9:36 AM dkwakkel wrote:
> I see both jackson and johnzon are now part of TomEE 8 M2:
> jackson-annotatio
Hello,
I agree with dkwakkel, Apache Johnzon should be enought for all TomEE
runtime requirements.Mixing two different JSON processors in same
classpath can lead to a dependency mess.
After all, ActiveMQ is an Apache project, and even if when it was
developed Apache Johnzon wasn't available, it w
It can certainly be requested. It would be up to the ActiveMQ project to
decide if they wanted to make that change. I'd certainly be happy to see
what's involved and have a go and send a PR, but if it involves significant
effort, I personally would prefer to work on EE8 as a higher priority.
Ultim
Unless it can be demonstrated that it actually causes an issue we should
leave it as is and focus on other priorities. Pinging ActiveMQ about it
would not hurt but I suspect its not a priority for them either.
On Wed, Jun 19, 2019 at 5:45 AM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote
Hi,
I'm working in a REST service that throws WebApplicationExcepion with
custom messages. I need pass the custom exception message to the client,
but it is ignored. After some search, I found that
the WebApplicationExceptionMapper was the responsible for ignoring the
exception message, but it has
Hi,
We've updated to 8.0.0-M3 and our builds are failing;
Failed to execute goal
org.apache.tomee.maven:tomee-maven-plugin:8.0.0-M3:run (startTomee) on
project XXX: Execution startTomee of goal
org.apache.tomee.maven:tomee-maven-plugin:8.0.0-M3:run failed: Plugin
org.apache.tomee.maven:tomee-mave
Can you try adding this staging repository to your ~/.m2/settings.xml:
https://repository.apache.org/content/repositories/orgapachetomee-1134
Something like this should do the trick:
staging-1134
staging-1134
