So yeah XML is still not solved in year 2018. Or so did I realize the last days.
I use jackson to serialize generic data to JSON.

Now I also want to provide serialization to XML. Easy right? Jackson also provides XML serialization facitlity similar to JAXB.

Works out of the box (more or less). Wait what? *rubbing eyes*

<User>
<pk>234235</pk>
<groups typeCode="usergroup">
<pk>6356679041773291286</pk>
</groups>
<groups typeCode="usergroup">
<pk>1095682275514732543</pk>
</groups>
</User>

Why is my groups property (java.util.Set) rendered as two separate elements? Who the fuck every though this is the way to go?

So OK *reading the docs* there is a way to create a collection wrapper. That must be it, I thought ...

<User typeCode="user">
<pk>2540591810712846915</pk>
<groups>
<groups typeCode="usergroup">
<pk>6356679041773291286</pk>
</groups>
<groups typeCode="usergroup">
<pk>1095682275514732543</pk>
</groups>
</groups>
</User>

What the fuck is this now? This is still not right!!!

I know XML offers a lot of flexibility on how to represent your data. But this is just wrong ...

The only logical way to display that data is:
<User typeCode="user">
<pk>2540591810712846915</pk>
<groups>
<groupsEntry typeCode="usergroup">
<pk>6356679041773291286</pk>
</groupsEntry>
<groupsEntry typeCode="usergroup">
<pk>1095682275514732543</pk>
</groupsEntry>
</groups>
</User>

It would be better if the individual entries would be just called "group" but I guess implementing such a logic would be pretty hard (finding a singular of an arbitrary word?).

So yeah theres a way for that * implementing a custom collection serializer* ... wait is that really the way to go? I mean common, am I the only one who just whants this fucking shit just work as expected, with the least amount of suprise?
Why do I have to customize that ...

So ok it renders fine now ... *writes test for it+
FUCK FUCK FUCK. why can't jackson not deserialize it properly anymore? The two groups are just not being picked up anymore ...

SO WHY, WHY WHY are you guys over at jackson, JAXB and the like not able to implement that in the right manner. AND NOT THERE IS ONLY ONE RIGHT WAY TO DO IT!

*looks at an apple PLIST file* *scratches head* OK, gues I'll stick to the jackson defaults, at least it's not as broken as the fucking apple XML:

<plist version="1.0">
<dict>
<key>PayloadOrganization</key>
<string>Example Inc.</string>
<key>PayloadDisplayName</key>
<string>Profile Service</string>
<key>PayloadVersion</key>
<integer>1</integer>
</dict>
</plist

I really wonder who at apple has this briliant idea ...

JSON de/serializer for C++, recommendations?

I used boost serialization until now, and it's fine.
But I will need to send some stuff over REST protocol to my future-web-GUI.
I would like something that is easy to build, not bloated, and could handle class serialization.
Shoot!

Converting javascript/ typescript Map to json
or python date to json

or anything complicated to json is mostly ending with implementing serialization patterns

With date it’s so annoying cause we have iso standards that every language implemented or have libraries

so typescript doesn’t recognize Map<string, string> so you have to convert it to array and then to object

with python you need to make your own serializer / deserializer

So much waste of power usage that if only Greta know it she would say ‘how dare you!’
It can stop global warming.

!rant

So, I've been working on a new project, it's basically a java library/package/jar with a lotta nice gadgets and stuff in.

The current functionality is limited, but will expand more as time goes on.

Right now it's able to:
apply ARGB filters to images (changing ARGB values), save objects in files on disk(Serializer/Deserializer), send emails with working create/load/unload configuration-system which saves a user-config to a file, loads and works with it, but the most coolest thing...

random char generation MY GOOOODDD

yea just wanted to post this cuz im rly proud

The documentation of scala akka http may be just gibberish as far as I am concerned. You would think that hooking into the marshalling process (aka de/serialization) would be straight forward, I've dealt with similar problems before and solved it.

I have an object, it should be transformed into a Json and vice versa. Should be easy as pie.

Not with scala and akka-http. The docs tell you how to achieve something in dozen different ways yet lack a complete example. My first custom marshaller I created in a "marshall" package in my! namespace, but it was breaking scala compilation due to some black magic.

It's not clear how when and why marshallers are added, they just somehow are. Why do I have to deal with entity marshallers vs response marshallers. I just want each instance of a certain type to be transformed into a specific Json presentation.

Asking on stackoverflow also only yields in incomplete hints of "just do boargh" presupposing certain knowledge while sounding borderline condescending.

Currently, I just want to burn the project and rebuild it with fucking PHP. Flame all you want, at least I would get things done and the JMS serializer library has decent documentation and it works in an expected way.

Akka-http, combined with Scala, looks from my current rage-driven perspective like a solution worse than the problem.

Manual serializer. I've found some of this in our code and wonder who could be that insane.

Duuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuck off you bloody infamous basterds flattening their fat asses at Microsoft.

I wasted half of my dev day to configure my wcf rest-api to return an enumeration property as string instead of enum index as integer.

There is actually no out-of-the-box attribute option to trigger the unholy built-in json serializer to shit out the currently set enum value as a pile of characters clenched together into a string.

I could vomit of pure happiness.

And yes.
I know about that StringEnumConverter that can be used in the JsonConvert Attribute.

Problem is, that this shit isn't triggered, no matter what I do, since the package from Newtonsoft isn't used by my wcf service as a standard serializer.

And there is no simple and stable way to replace the standard json serializer.

Christ, almighty!

:/

If I kept track of all the hours wasted on issues due to overloads of functions called ToList() it would probably make up a sizable portion of the project budgets.

If I call ToList on a query object, it looks like I'm trying to serialize the query definition into some kind of array. That's what it *should* do with that name. Bonus if the object implements some generic enumerable interface, ToList makes it call your database, you can just toss the query into some json serializer that blocks while calling ToList for you, and people end up doing exactly this because the code turned out so much neater.

Because that's the thing. It's like people implement it because it's "neat" and the user shouldn't care about its internals. How many tears would be shed by just calling it ExecuteAsync?

Been stuck a week with JSON serializer struggles on the backend I'm working on... First of all, this project has source code dating back to 2013, and the dudes back then decided to use three versions of json. So you have your usual application/json and then two custom ones.

Not happy with that, they decide on using two serializers, XStream and Jackson. One custom and application/json run through XStream, and the other more legacy custom JSON runs through Jackson. So this is a bloody mess.

But now they want application/json running through Jackson, and this is breaking all the regression tests. Have to reimplement all the type, field, alias and other kinds of mappings they made for XStream, and sort out all the regressions this causes.

And the dude who designed all of this is revered in the company, although he left a while back. Not sure if I'm too much of an idiot to understand the utter brilliance of the approach, or its just poorly designed... Fuck my life, those due dates just keep creeping closer and closer and this kinda crap just keeps coming :S

Which way you prefer to write code?

1.
server.addHandler(...)
server.addSerializer(...)
server.addCompressor(...)
...

2.
server.add("handler",...)
server.add("serializer",...)
server.add("compressor",...)
...

3. Both. (as per mood) :p

If I ever work with people who use Python professionally I will go postal in under a day they are some of the most unprofessional snarky little fucking bastards on the internet !

Apparently a question with a million hits who's cure all answer DOESN'T WORK, is me being stupid.

So question, how many of you when looking at a third party client that doesn't have great documentation, export class data into a file to look it over at your leisure by using a serializer that just dumps the shit into said file so you can look at it ?

I mean fire and forget. Just works. Just descends into the data structure and starts dumping field values. Done. One line of code.
Json.PUTMYSHITINASTRING(FUCKINGCLASS) ???????

DON'T SAY MY METHOD OF WORKING IS BAD ! ESPECIALLY WHEN THERE FUCKING EXPORT CODE AS A CHECK_CIRCULAR BOOLEAN PARAMETER INDICATING IT SHOULD WORK BETTER THAN IT FUCKING DOES AND THE FUCKING DEBUGGER CAN REFLECT THE OBJECT !!!!