Omar,
Implementing security in the plugin is on our todo-list.
For serialization to we use the jabsorb library.
Can you give an example of the javascript code that creates a return object and the resulting json and xml?
Rob
First of all, I want to apologize for my previous post. Frustration is not a good reason for such a rant, especially when there’s so much people willing to help. I mean it.
I didn’t file anything in the CRM yet because most of the thing I brought here for your interest aren’t really bugs, they’re more weaknesses (weaknesses that make very hard for us to leave our current low-level implementation in favor of the plugin at the moment).
Except for number 2, which is really weird and could depend on our configuration.
Anyway we found the issue with a fresh solution with just the ws_stuff and nothing else, we’ll see whether it’s our fault or not and then we’ll file it in the CRM.
To answer your points:
- working out of the main solution is not comfortable, anyway paul’s suggestion seems the right thing to do.
Authentication is very important, a basic Servoy Authentication it’s what I expected. You don’t see many unauthenticated ws around. If we deploy an unauthenticated read/write service the IT dept will shoot us (not to wound). - The serializer has issues. It will serialize this: [1,2,3] in something like java.lang.object… and then the values, the for Date objects. It hardly deserialize object it serialized sometimes (I’ll file this as soon as I can). We heavily rely on JSON even outside the ws world, and we developed a servoy-aware version of the JS JSON implementation, for this reason.
5.I understand the “be-fast-be-smart” Servoy tenets, but it’s unarguable that web services is “geek ground”, so a way to implement whatever authentication (even if it means dealing with request,response object) is really really important, we thought about modifying the plugin, but we just found faster options.
number 4 doesn’t really exists, It seems that in my anger i killed it.
the problems you see with the json serializer is because of how it is build.
It is a plugin which is a java plugin.
So if you give it a Array to serialize then the call to java will first unwrap that array to a java array and then it will do the serializing
Please make a case for this to see if we can enhance this somehow better, give some examples which do fail now for you.
rgansevles:
Implementing security in the plugin is on our todo-list.
I would REALLY love to know what is on the todo lists for a number of the high profile Servoy 5 features. Finding out the various and sometimes significant limitations on our own has resulted in quite a bit of frustration.
Without knowing what is on your roadmap our expectations were set based on marketing and what we heard at the Servoy world tour.
I realize the need for marketing to have their bullet points in a simple fashion. As a developer, I could use more solid information to base my expectations on.
David,
Please keep threads on topic.
Paul
pbakker:
David,Please keep threads on topic.
Paul