Re: [VOTE] Apache Johnzon 2.0.1

+1 txs and LieGrue, strub > Am 23.03.2024 um 20:58 schrieb Markus Jung : > > Hi all, > > I'm excited to start a vote for Apache Johnzon 2.0.1. > Please note that I am NOT a PMC member. I have done the manual work of > creating this release candidate, but the final steps will be carried out

Re: [VOTE] Apache Johnzon 2.0.0

+1 LieGrue, strub > Am 24.10.2023 um 15:16 schrieb Jean-Louis Monteiro : > > Hi all, > > I'm very excited to start a vote for Apache Johnzon 2.0.0 which is the > first Jakarta compatible version in sources. > > It fully passes Jakarta EE 10 TCK for both JSON-B 3.0.0 and JSON-P 2.1.1. > >

Re: a few EE-4.0 TCK questions

the history on that feature, we didnt take the spec >> path at all pre-spec time. >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <https://rmannibucau.metawerx.net/> | Old Blog >> <http://rmannibucau.wordpress.com

Re: a few EE-4.0 TCK questions

ok > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le mar. 19 sept. 2023 à 16:21, Mark Struberg a > écrit : > >> I've now created a github issue. >> https://github.com/jakartaee/jsonb-api/issues/344 >> >

Re: a few EE-4.0 TCK questions

I've now created a github issue. https://github.com/jakartaee/jsonb-api/issues/344 Jean-Louis, you are more experienced in this area: is this the correct way to file a TCK challenge for JSON-B? txs and LieGrue, strub > Am 19.09.2023 um 13:56 schrieb Mark Struberg : > > This gets ev

Re: a few EE-4.0 TCK questions

assumes different behaviour than the TCK test for deserialisers which use CDI? Should not be imo! LieGrue, strub > Am 19.09.2023 um 13:42 schrieb Mark Struberg : > > hi! > > Trying to work on the few TCK tests which still fail in Johnzon. > > Does anyone underst

a few EE-4.0 TCK questions

hi! Trying to work on the few TCK tests which still fail in Johnzon. Does anyone understand why the following deserializer is expecting to see a START_OBJECT of the actual items instead of the actual current JsonValue event which is a START_ARRAY?

[jira] [Commented] (JOHNZON-399) JsonbLocalDateConverter should also read javascript date format

[ https://issues.apache.org/jira/browse/JOHNZON-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751389#comment-17751389 ] Mark Struberg commented on JOHNZON-399: --- Well, it's actually a bit more complicated I fear

[jira] [Created] (JOHNZON-399) JsonbLocalDateConverter should also read javascript date format

Mark Struberg created JOHNZON-399: - Summary: JsonbLocalDateConverter should also read javascript date format Key: JOHNZON-399 URL: https://issues.apache.org/jira/browse/JOHNZON-399 Project: Johnzon

Re: [VOTE] Apache Johnzon 1.2.21

+1 txs and LieGrue, strub > Am 26.06.2023 um 15:52 schrieb Jean-Louis MONTEIRO : > > Up... > Missing a binding vote, please > > Le jeu. 22 juin 2023 à 21:10, David Blevins a > écrit : > >> Nevermind back to +1. >> >> Thought I saw jakarta namespace changes in the tag, but after double, >>

Re: [VOTE] Release Apache Johnzon-1.2.20

+1 LieGrue, strub > Am 13.03.2023 um 19:53 schrieb Jean-Louis Monteiro : > > Hi all, > > Here is the vote to release Apache Johnzon 1.2.20. > Highlights are: > > There is only one issue fixed but this version is pretty stable and users > were actively waiting on it. > > Changelog: >

Re: [VOTE] Release Apache Johnzon-1.2.19 (stage 2)

+1 LieGrue, strub > Am 17.08.2022 um 10:46 schrieb Romain Manni-Bucau : > > Hi all, > > Here is the vote to release Apache Johnzon 1.2.19. > Highlights are: > > * Better exception messages in our mapper (thanks David) > * Simple PojoGenerator from JSON-Schema > * Jakarta support for

Re: [VOTE][RESULT] Release Apache Johnzon-1.2.18

Good morning! Time to tally the VOTE. The vote has succeeded with the following: +1: Romain, David, Jean-Louis, Ray, JBO, Reini, Mark No -1 nor 0 has been casted. Will continue with the release. txs 2 all who voted! LieGrue, strub > Am 30.04.2022 um 13:58 schrieb Mark Struberg : >

Re: [VOTE] Release Apache Johnzon-1.2.18

t; >> +1 >> >> lG >> reini >> >>> Am 02.05.2022 um 10:49 schrieb Jean-Baptiste Onofré : >>> >>> +1 (non binding) >>> >>> Regards >>> JB >>> >>> On Sat, Apr 30, 2022 at 1:58 PM Mark Struberg

Re: [VOTE] Release Apache Johnzon-1.2.18

t; fails - Snippet impl). > > Le sam. 30 avr. 2022 à 13:59, Mark Struberg a > écrit : > >> Good afternoon! >> >> I'd like to call a VOTE on releasing Apache Johnzon 1.2.18 >> >> Since 1.2.17 we mainly fixed the following tickets >> >> Bu

[VOTE] Release Apache Johnzon-1.2.18

Good afternoon! I'd like to call a VOTE on releasing Apache Johnzon 1.2.18 Since 1.2.17 we mainly fixed the following tickets Bug [JOHNZON-368 ] - [mapper][jsonb] JsonGeneratorFactory does not respect encoding Improvement [JOHNZON-369

Re: Showing a chunk of json in exceptions

Means we are good to go and ship another release? Would love to do that and then update TomEE and Meecrowave with it (tests do look good in both). Wdyt? Would start the release train in 2h, love getting it out before the weekend. LieGrue, strub > Am 28.04.2022 um 08:27 schrieb David Blevins :

Re: [VOTE] [RESULT] Release Apache Johnzon 1.2.17

hi folks! The VOTE did pass with the following: +1: Ray, JBO, Romain, Jean-Louis, Mark no -1 nor 0 txs 2 all who reviewed! LieGrue, strub > Am 13.04.2022 um 21:36 schrieb Mark Struberg : > > Hi! > > I'd like to call a VOTE on releasing Apache Johnzon-1.2.17. > > The

Re: [VOTE] Release Apache Johnzon 1.2.17

And my own +1 Will tally the vote soon. LieGrue, strub > Am 13.04.2022 um 21:36 schrieb Mark Struberg : > > Hi! > > I'd like to call a VOTE on releasing Apache Johnzon-1.2.17. > > The following tickets got resolved: > > Bug > > [JOHNZON-359 <https://i

[VOTE] Release Apache Johnzon 1.2.17

Hi! I'd like to call a VOTE on releasing Apache Johnzon-1.2.17. The following tickets got resolved: Bug [JOHNZON-359 ] - Fix lost OSGi metadata [JOHNZON-361 ] - Johnzon maven plugin

Re: OK to release Johnzon 1.2.17?

Will start a release soonish. LieGrue, strub > Am 12.04.2022 um 10:07 schrieb Mark Struberg : > > took your PR and enhanced on top of it. > > Plz review! > > txs and LieGrue, > strub > >> Am 10.04.2022 um 20:08 schrieb Romain Manni-Bucau : >> >&

Re: OK to release Johnzon 1.2.17?

re back yep >> >> >>> LieGrue, >>> strub >>> >>> >>>> Am 10.04.2022 um 17:24 schrieb Romain Manni-Bucau < >>> rmannibu...@gmail.com>: >>>> >>>> Le dim. 10 avr. 2022 à 17:16, Mark Struberg >>

Re: OK to release Johnzon 1.2.17?

Oki will re-introduce that ct. Should then be backward compat, isn't? LieGrue, strub > Am 10.04.2022 um 17:24 schrieb Romain Manni-Bucau : > > Le dim. 10 avr. 2022 à 17:16, Mark Struberg a > écrit : > >> Actually there is not much diff. There is one c

Re: OK to release Johnzon 1.2.17?

No, because it was not spec compliant. It clearly didn't respect JsonbVisibility rules. LieGrue, strub > Am 10.04.2022 um 17:23 schrieb Romain Manni-Bucau : > > Le dim. 10 avr. 2022 à 17:19, Mark Struberg a > écrit : > >> PS: Ad JsonbAccessMode design: the problem is th

Re: OK to release Johnzon 1.2.17?

would likely break backward compat. We could do that in the next release. LieGrue, strub > Am 10.04.2022 um 17:15 schrieb Mark Struberg : > > Actually there is not much diff. There is one ct which was only used in > JsonbAccessMode as true. Everywhere else it was feed as false. &g

Re: OK to release Johnzon 1.2.17?

nibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le sam. 9 avr. 2022 à 23:49, Mark Struberg a > écrit : >

Re: OK to release Johnzon 1.2.17?

here we go. plz take a look! https://github.com/struberg/johnzon/tree/JOHNZON-364 <https://github.com/struberg/johnzon/tree/JOHNZON-364> txs and LieGrue, strub > Am 09.04.2022 um 23:14 schrieb Mark Struberg : > > Looked at your proposed solution, but it might be tricky to

Re: OK to release Johnzon 1.2.17?

as parameter over there. still not really perfect imo. Will try to ship a patch proposal tomorrow. LieGrue, strub > Am 28.03.2022 um 10:22 schrieb Romain Manni-Bucau : > > Le lun. 28 mars 2022 à 10:05, Mark Struberg <mailto:strub...@yahoo.de.invalid>> a > écrit : >

Re: OK to release Johnzon 1.2.17?

gt; > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> |

[jira] [Updated] (JOHNZON-364) JsonbVisibility must always win over default rules

[ https://issues.apache.org/jira/browse/JOHNZON-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated JOHNZON-364: -- Description: It seems we trashed {{@JsonbVisibility}} for fields when we implemented JOHNZON

Re: OK to release Johnzon 1.2.17?

To sum this up: The problem lies partly in the JSON-B spec. It doesn't define what happens if there are class hierarchies like class A extends B. In 3.7.1 it states that For a serialization operation, if a matching public getter method exists, the method is called to obtain the value of the

[jira] [Resolved] (JOHNZON-364) JsonbVisibility must always win over default rules

[ https://issues.apache.org/jira/browse/JOHNZON-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-364. --- Resolution: Fixed > JsonbVisibility must always win over default ru

[jira] [Created] (JOHNZON-364) JsonbVisibility must always win over default rules

Mark Struberg created JOHNZON-364: - Summary: JsonbVisibility must always win over default rules Key: JOHNZON-364 URL: https://issues.apache.org/jira/browse/JOHNZON-364 Project: Johnzon Issue

potentially trashed FieldVisibilityStrategy with JOHNZON-250?

Hi! 3.7.1 of the JSON-B spec defines the following visibility rules for fields * if public setter/getter exists -> take that * if non public setter/getter exists -> ignore * OTHERWISE (no setter/getter at all) -> use fields But all that must not get evaluted if an explicit VisibilityStrategy

Re: Implement JSON-B 3 API?

Seems like a good idea! LieGrue, strub > Am 23.02.2022 um 13:44 schrieb Romain Manni-Bucau : > > Hi all, > > There is mainly a new API in JSON-B for polymorphism: > https://github.com/eclipse-ee4j/jsonb-api/blob/master/api/src/main/java/jakarta/json/bind/annotation/JsonbTypeInfo.java > (and

Re: [VOTE] Release Apache Johnzon 1.2.16

+1 LieGrue, strub > Am 03.02.2022 um 10:30 schrieb Romain Manni-Bucau : > > Hi all, > > Here is the vote for Apache Johnzon 1.2.16. > > Here is the changelog: > > [image: Major][image: Task]JOHNZON-354 > Next spec version will > enable

Re: [VOTE] Apache Johnzon 1.2.15

+1 LieGrue, strub > Am 12.10.2021 um 23:12 schrieb Jean-Louis MONTEIRO : > > Hi! > > I’d like to call a VOTE on Apache Johnzon 1.2.15 > > Here is the staging repo > https://repository.apache.org/content/repositories/orgapachejohnzon-1051 >

Re: [VOTE] Release Apache Johnzon 1.2.14

+1 LieGrue, strub > Am 04.07.2021 um 16:27 schrieb Romain Manni-Bucau : > > +1 > > Romain Manni-Bucau > @rmannibucau | Blog > | Old Blog > | Github | >

Re: [VOTE] Release Apache Johnzon 1.2.13

+1 LieGrue,strub On Wednesday, 2 June 2021, 17:52:02 CEST, Jean-Baptiste Onofre wrote: +1 (non binding) Regards JB > Le 2 juin 2021 à 17:50, Romain Manni-Bucau a écrit : > > Hi all, > > I'd like to release Apache Johnzon 1.2.13. > Here is the changelog: > >

Re: [VOTE] Release Apache Johnzon 1.2.12

+1 LieGrue, strub > Am 17.05.2021 um 14:04 schrieb Romain Manni-Bucau : > > Hi all, > > Due to some fixes and requests i'd like to release Apache Johnzon 1.2.12. > Here is the changelog: > > PTKeySummaryAssigneeStatus > [image: Blocker] [image: Bug] JOHNZON-345 >

[jira] [Commented] (JOHNZON-345) StackOverflow when serializing Collection

[ https://issues.apache.org/jira/browse/JOHNZON-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346096#comment-17346096 ] Mark Struberg commented on JOHNZON-345: --- +1 we need to support URL and URI according to 3.4.2

[jira] [Resolved] (JOHNZON-333) Invalid String serialization from JsonB string objects

[ https://issues.apache.org/jira/browse/JOHNZON-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-333. --- Resolution: Fixed > Invalid String serialization from JsonB string obje

[jira] [Commented] (JOHNZON-333) Invalid String serialization from JsonB string objects

[ https://issues.apache.org/jira/browse/JOHNZON-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17271637#comment-17271637 ] Mark Struberg commented on JOHNZON-333: --- but we return test as java String so {{"

Re: [VOTE] Apache Johnzon 1.2.9

+1 txs and LieGrue, strub > Am 15.12.2020 um 15:52 schrieb Jean-Louis Monteiro : > > Hi everyone, > > Here is the vote for Apache Johnzon 1.2.9 with few fixes > > Here is the changelog: > Bug > > - [JOHNZON-141 ] - > support object

Re: [DISCUSS] default adapters rework?

+1, should also make things faster a bit. LieGrue, strub > Am 10.07.2020 um 09:42 schrieb Romain Manni-Bucau : > > Hi everyone, > > Wonder if we should change a bit our converter (in our mapper)/adapter > (jsonb) handling. > > Currently we have a static map of converters and in jsonb layer

Re: [VOTE] Release Apache Johnzon 1.2.7 take 2

+1 LieGrue, strub > Am 01.06.2020 um 13:22 schrieb Romain Manni-Bucau : > > Hi everyone, > > As mentionned on the list, here is the vote for Apache Johnzon 1.2.7. > This second take fixes @JohnzonAny forwarding of properties when used on a > field (take one was not ignoring explicit

Re: [VOTE] Release Apache Johnzon 1.2.6

+1 LieGrue, strub > Am 11.05.2020 um 09:19 schrieb Reinhard Sandtner > : > > +1 > > lg > reini > >> Am 11.05.2020 um 06:32 schrieb Jean-Baptiste Onofre : >> >> +1 (non binding) >> >> Regards >> JB >> >>> Le 10 mai 2020 à 16:19, Romain Manni-Bucau a écrit : >>> >>> Hi everyone, >>> >>>

Re: [VORE] Release Apache Johnzon 1.2.3

+1 LieGrue, strub > Am 24.01.2020 um 13:52 schrieb Romain Manni-Bucau : > > Hi all, > > Here is the vote for Apache Johnzon 1.2.3, it fixes OSGi metadata for jsonb > module and enables to use record types as JSON mappers: > > [image: Major] [image: New Feature] JOHNZON-300 >

Re: Request for release

I could roll the release if necessary. Every ticket resolved you want to have in? Or is there something we still need to address? LieGrue, strub > Am 10.12.2019 um 23:04 schrieb Raymond Auge : > > Hello all, > > I'd like to request a release if that would be possible sometime in the > near

[jira] [Commented] (JOHNZON-293) Potential Memleak in DateConverter

[ https://issues.apache.org/jira/browse/JOHNZON-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987557#comment-16987557 ] Mark Struberg commented on JOHNZON-293: --- hmm don't think so. We could make a test for it, but I

[jira] [Commented] (JOHNZON-293) Potential Memleak in DateConverter

[ https://issues.apache.org/jira/browse/JOHNZON-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987001#comment-16987001 ] Mark Struberg commented on JOHNZON-293: --- Cool, that sounds like using the immutable Java8 time

Re: passing the json-p tck

e api maybe to ensure we are covered. > > Le mar. 20 août 2019 à 23:29, Mark Struberg a > > écrit : > > > Here are the tests which fail: > > > > > > > > > > > > FAILEDcom/sun/ts/tests/jsonb/api/config/JsonbConfigTest.java#testW

Re: passing the json-p tck

snapshot, it is more reliable in > current state than "tomee setup" for these 2 specs and only takes like 3mn > to run. Will enable to be sure quickly. > > Le mar. 20 août 2019 à 23:14, Mark Struberg a > écrit : > > > hmmm might be because the javaee-api did not get upd

Re: passing the json-p tck

hmmm might be because the javaee-api did not get updated to the new geronimo- jsonb-api? LieGrue, strub Am Dienstag, den 20.08.2019, 23:10 +0200 schrieb Mark Struberg: > wel, bad news: 27 errors in JSON-B now ;) > > Did let it run as part of TomEE. > > LieGrue, > strub &

Re: passing the json-p tck

/www.tomitribe.com > > > On Tue, Aug 20, 2019 at 9:02 PM Romain Manni-Bucau > wrote: > > > If jsonp part didnt change anything - which shouldnt since we dont use > > stream api - we are good. > > > > Just need a G jsonb api release. Can run it tmr if it he

passing the json-p tck

tomee-tck]$ ./runtests --web tomee-plus com.sun.ts.tests.jsonp === Completed running 744 tests (0:20:59.095): Passed: 744 Failed: 0 Errors: 0

[jira] [Created] (JOHNZON-271) fix non spec-conform behaviour of JsonParser Stream API

Mark Struberg created JOHNZON-271: - Summary: fix non spec-conform behaviour of JsonParser Stream API Key: JOHNZON-271 URL: https://issues.apache.org/jira/browse/JOHNZON-271 Project: Johnzon

Re: JsonGenerator#writeXxxx and null values

And another question: JsonNumber#isIntegral for lng values - too long for long ;) How to determine whether it fits into a long? Should isIntegral() still return true if the numbers of digits are too long for long? LieGrue, strub Am Montag, den 19.08.2019, 08:08 +0200 schrieb Mark

JsonGenerator#writeXxxx and null values

hi folks! What happens if you pass a null to the various JsonGenerator#write methods, e.g https://docs.oracle.com/javaee/7/api/javax/json/stream/JsonGenerator.html#write-java.math.BigInteger- ? Should they blow up with a NullPointerException? Or should they write a Json.NULL value? I didn't

Re: JSON-B TCK

right now also running the tcks on my box. But you have been faster as usual - congrats :) +1 for doing a release. Will do some perf regression tests before that and then I could pull the trigger this weekend. LieGrue, strub Am Samstag, den 17.08.2019, 18:40 +0200 schrieb Jean-Louis Monteiro:

Re: [VOTE] [RESULT] Release Apache Johnzon-1.1.13

Good morning! And with my own +1 I'd like to tally the vote The VOTE did succeed with the following: +1: Hendrik, Romain, Jean-Louis, Mark I'll continue with the release process. txs and LieGrue, strub > Am 01.08.2019 um 19:40 schrieb Mark Struberg : > > Good afternoon! >

[VOTE] Release Apache Johnzon-1.1.13

Good afternoon! I'd like to call a VOTE on releasing Apache Johnzon-1.1.13. The following tickets got resolved: Bug • [JOHNZON-178] - Mapper#writeArray(new short[] {1,2}) blows up with a ClassCastException • [JOHNZON-204] - update to geronimo-json_1.1_spec api.jar to prevent

[jira] [Commented] (JOHNZON-177) Deserialization of numbers can produce overflows and underflows

[ https://issues.apache.org/jira/browse/JOHNZON-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898081#comment-16898081 ] Mark Struberg commented on JOHNZON-177: --- Removing fix version as this requires a spec change

[jira] [Updated] (JOHNZON-177) Deserialization of numbers can produce overflows and underflows

[ https://issues.apache.org/jira/browse/JOHNZON-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated JOHNZON-177: -- Fix Version/s: (was: 1.1.13) > Deserialization of numbers can produce overfl

[jira] [Resolved] (JOHNZON-226) Various Performance improvements

[ https://issues.apache.org/jira/browse/JOHNZON-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-226. --- Resolution: Fixed * various performance enhancements for array operations * improve caching

releasing johnzon-1.1.13?

hi folks! wdyt about releasing johnzon-1.1.13? LieGrue, strub

Re: JsonValue.NULL equals

tly portable again. LieGrue, strub > Am 31.07.2019 um 18:56 schrieb Mark Struberg : > > hi folks! > > We have quite some JsonValue.NULL.equals(...) in our code. > Seems this part is slow according to YourKit. > > Wouldn't it be perfectly enough to use JsonValue.NULL == ? > > LieGrue, > strub >

JsonValue.NULL equals

hi folks! We have quite some JsonValue.NULL.equals(...) in our code. Seems this part is slow according to YourKit. Wouldn't it be perfectly enough to use JsonValue.NULL == ? LieGrue, strub

Re: [johnzon] branch master updated: JOHNZON-226 use own Array.length

> Am 30.07.2019 um 14:19 schrieb Mark Struberg : > > > Will do. > LieGrue, > strub > > >> Am 29.07.2019 um 23:12 schrieb Romain Manni-Bucau : >> >> Hmm, this breaks the isolation between our modules - jsonp impl must stay >> switchable

Re: [johnzon] branch master updated: JOHNZON-226 use own Array.length

johnzon.git > > > The following commit(s) were added to refs/heads/master by this push: > new 41e0fdc JOHNZON-226 use own Array.length > 41e0fdc is described below > > commit 41e0fdc50c59153a03e49e85afac534949ece4e6 > Author: Mark Struberg > AuthorDate: M

[jira] [Created] (JOHNZON-226) Various Performance improvements

Mark Struberg created JOHNZON-226: - Summary: Various Performance improvements Key: JOHNZON-226 URL: https://issues.apache.org/jira/browse/JOHNZON-226 Project: Johnzon Issue Type: Improvement

[jira] [Resolved] (JOHNZON-202) org.apache.johnzon.mapper.Adapter JavaDoc wrong and IllegalArgumentException-message from org.apache.johnzon.mapper.Mappings misleading

[ https://issues.apache.org/jira/browse/JOHNZON-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-202. --- Resolution: Fixed Fix Version/s: 1.1.13 Thanks for the report. Docs fixed. Please

[jira] [Assigned] (JOHNZON-166) Jsonb Adapters not applied on Map keys

[ https://issues.apache.org/jira/browse/JOHNZON-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned JOHNZON-166: - Assignee: Mark Struberg > Jsonb Adapters not applied on Map k

[jira] [Updated] (JOHNZON-146) Mapper json processing should use the order in the Json, not setters

[ https://issues.apache.org/jira/browse/JOHNZON-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated JOHNZON-146: -- Fix Version/s: (was: 1.1.13) 1.1.14 > Mapper json processing sho

[jira] [Updated] (JOHNZON-192) Switch johnzon-maven-plugin class generation from manual source writer to a more robust solution

[ https://issues.apache.org/jira/browse/JOHNZON-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated JOHNZON-192: -- Fix Version/s: (was: 1.1.13) > Switch johnzon-maven-plugin class generation from man

[jira] [Assigned] (JOHNZON-206) toStructure of arrray of JsonObjects serializes JsonObjectImpl like an arbitrary Object

[ https://issues.apache.org/jira/browse/JOHNZON-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned JOHNZON-206: - Assignee: Mark Struberg > toStructure of arrray of JsonObjects seriali

[jira] [Resolved] (JOHNZON-213) Make @JsonbTypeAdapter works with accessors

[ https://issues.apache.org/jira/browse/JOHNZON-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-213. --- Resolution: Not A Problem Assignee: Mark Struberg I think this can be resolved, right

[jira] [Resolved] (JOHNZON-218) JsonProviderDelegate is now useless and can be dropped

[ https://issues.apache.org/jira/browse/JOHNZON-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-218. --- Resolution: Fixed Fix Version/s: 1.1.13 > JsonProviderDelegate is now usel

[jira] [Assigned] (JOHNZON-218) JsonProviderDelegate is now useless and can be dropped

[ https://issues.apache.org/jira/browse/JOHNZON-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned JOHNZON-218: - Assignee: Mark Struberg > JsonProviderDelegate is now useless and can be drop

[jira] [Commented] (JOHNZON-218) JsonProviderDelegate is now useless and can be dropped

[ https://issues.apache.org/jira/browse/JOHNZON-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892713#comment-16892713 ] Mark Struberg commented on JOHNZON-218: --- Indeed, it was only useful when we did not expose

[jira] [Resolved] (JOHNZON-221) use the config from the underlying JSON-P for JSON-B operations

[ https://issues.apache.org/jira/browse/JOHNZON-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-221. --- Resolution: Fixed Romain already committed passing on the buffer strategy etc from jsonp

[jira] [Commented] (JOHNZON-221) use the config from the underlying JSON-P for JSON-B operations

[ https://issues.apache.org/jira/browse/JOHNZON-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880994#comment-16880994 ] Mark Struberg commented on JOHNZON-221: --- Also unify the system property which is used to configure

[jira] [Created] (JOHNZON-221) use the config from the underlying JSON-P for JSON-B operations

Mark Struberg created JOHNZON-221: - Summary: use the config from the underlying JSON-P for JSON-B operations Key: JOHNZON-221 URL: https://issues.apache.org/jira/browse/JOHNZON-221 Project: Johnzon

[jira] [Resolved] (JOHNZON-178) Mapper#writeArray(new short[] {1,2}) blows up with a ClassCastException

[ https://issues.apache.org/jira/browse/JOHNZON-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-178. --- Resolution: Fixed now all primitive arrays are also supported > Mapper#writeArray(

[jira] [Resolved] (JOHNZON-204) update to geronimo-json_1.1_spec api.jar to prevent classloader locking

[ https://issues.apache.org/jira/browse/JOHNZON-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-204. --- Resolution: Fixed update to geronimo-jsonp-1.2 done > update to geronimo-json_1.1_s

optimisations with buffer initialisation

hi folks! we have some potential enhancements in our init routines which could lead to slightly less resource consumption. static class JsonProviderDelegate extends JsonProvider { private final BufferStrategy.BufferProvider bufferProvider =

[jira] [Resolved] (JOHNZON-217) Allow to plugin a custom BufferStrategy

[ https://issues.apache.org/jira/browse/JOHNZON-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved JOHNZON-217. --- Resolution: Fixed It's now possible to have a custom implementation of {{BufferStrategy

[jira] [Updated] (JOHNZON-217) Allow to plugin a custom BufferStrategies

[ https://issues.apache.org/jira/browse/JOHNZON-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated JOHNZON-217: -- Summary: Allow to plugin a custom BufferStrategies (was: Allow to plugin in custom

[jira] [Updated] (JOHNZON-217) Allow to plugin a custom BufferStrategy

[ https://issues.apache.org/jira/browse/JOHNZON-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated JOHNZON-217: -- Summary: Allow to plugin a custom BufferStrategy (was: Allow to plugin a custom

[jira] [Created] (JOHNZON-217) Allow to plugin in custom BufferStrategies

Mark Struberg created JOHNZON-217: - Summary: Allow to plugin in custom BufferStrategies Key: JOHNZON-217 URL: https://issues.apache.org/jira/browse/JOHNZON-217 Project: Johnzon Issue Type

[jira] [Assigned] (JOHNZON-216) JsonStreamParserImpl.readString throws ArrayIndexOutOfBoundsException when dealing with string that contains escape characters

[ https://issues.apache.org/jira/browse/JOHNZON-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned JOHNZON-216: - Assignee: Mark Struberg > JsonStreamParserImpl.readString thr

Re: [VOTE] Release Apache Johnzon 1.1.12

+1 txs and LieGrue, strub > Am 26.05.2019 um 10:24 schrieb Romain Manni-Bucau : > > Hi everyone, > > Here is the vote for Apache Johnzon 1.1.12, > > Here is our changelog: > > > PTKeySummaryAssigneeStatusDevelopment > [image: Major] [image: Bug] JOHNZON-199 >

[jira] [Created] (JOHNZON-204) update to geronimo-json_1.1_spec api.jar to prevent classloader locking

Mark Struberg created JOHNZON-204: - Summary: update to geronimo-json_1.1_spec api.jar to prevent classloader locking Key: JOHNZON-204 URL: https://issues.apache.org/jira/browse/JOHNZON-204 Project

Re: Potential deadlock while classloading in JsonValue

opment/java-ee-8-high-performance> Le mar. 26 févr. 2019 à 09:25, Mark Struberg a écrit : >  The point is that does NOT show up in the stack trace. So it must > be cinit. > Also a pointer is that the thread is in state RUNNABLE but blocked by > Object.wait().Which is often a c

Re: Potential deadlock while classloading in JsonValue

:13:57 CET, Romain Manni-Bucau wrote: Hi Mark If you can reproduce it a lazy init in the g spec would be eady to test That said if it is in init it is after cinit so in the constructor. Can it be the buffer strategy config you run with? Romain Le mar. 26 févr. 2019 à 07:57, Mark Struberg

Potential deadlock while classloading in JsonValue

Hi folks! We've seen a mysterious deadlock in Johnzon on startup under heavy load.    java.lang.Thread.State: RUNNABLE     at org.apache.johnzon.core.JsonArrayBuilderImpl.build(JsonArrayBuilderImpl.java:319) --    java.lang.Thread.State: RUNNABLE     at

[jira] [Commented] (JOHNZON-203) How do I map a Java Bean to javax.json.JsonValue?

[ https://issues.apache.org/jira/browse/JOHNZON-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772844#comment-16772844 ] Mark Struberg commented on JOHNZON-203: --- I suggest we still solve this at least in our Mapper

Re: [VOTE] [RESULT] move our Johnzon GIT repo to gitbox.apache.org

Hi folks! VOTE passed with +1: Mark, Jean-Louis, Romain, Olivier, Reinhard, James, Raymond, Hendrik, Matthew, Jon, Daniel. No -1 nor 0 LieGrue, strub > Am 08.01.2019 um 09:18 schrieb Mark Struberg : > > Hi folks! > > We've made good experience with gitbox in other ASF proj

[jira] [Commented] (JOHNZON-177) Deserialization of numbers can produce overflows and underflows

[ https://issues.apache.org/jira/browse/JOHNZON-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736357#comment-16736357 ] Mark Struberg commented on JOHNZON-177: --- Hi [~jwcarman]! It was clarified with the EG

Re: [VOTE] Apache Johnzon 1.1.11

+1 LieGrue,strub On Tuesday, 18 December 2018, 10:48:19 CET, Romain Manni-Bucau wrote: Hi guys, As mentionned here is the vote for Johnzon 1.1.11 The staging repo is: https://repository.apache.org/content/repositories/orgapachejohnzon-1032 Tag is on the main source repo and sources

  1   2   3   >