Artem Gr Kozarezov

Show:

What's happening?

  • Followup: RE: flexjson 1.8, value type lost in a Map

    > The rule of thumb of using Map > whenever nothing is specified for a > path is a good one, but you'd still > need to specify Foo either in a use() > or ClassLocators. That's right. And also using the "class" field emitted by the Serializer.

    2009-11-04 16:12:41 UTC in Flexjson

  • Followup: RE: flexjson 1.8, value type lost in a Map

    Charlie, have you missed the two problems I mention? 1) There is {\"class\":\"Foo\"} in the JSON string, however, I see no way to deserialize it into Foo using default Deserializer. 2) ClassLocator have no way to differentiate maps from arrays. > So the idiomatic solution you proposed > doesn't tell the deserializer what > classes it's binding into. Wrong...

    2009-11-04 16:01:56 UTC in Flexjson

  • Followup: RE: flexjson 1.8, value type lost in a Map

    I solved it for now by using a ClassLocator, see http://www.gulic.org/pastebin/77 - however it only works with maps and breaks with arrays.

    2009-11-01 02:29:04 UTC in Flexjson

  • flexjson 1.8, value type lost in a Map

    I'm trying to deserialize a Map<String, Foo>. With new JSONDeserializer() .use (null, HashMap.class) .deserialize ("{\"1\": {\"class\":\"Foo\"}}") I expect to get {1=Foo@} but I get {1={class=Foo}} Any suggestions? (Most idiomatic for me would've been to simply use `new JSONDeserializer() .deserialize...

    2009-11-01 02:02:35 UTC in Flexjson

  • Followup: RE: Performance

    > Ultimately, it comes down to String.charAt() performance. You could try copying the String into char[] array with String.toCharArray.

    2009-11-01 00:20:26 UTC in Flexjson

  • Followup: RE: Index not used in ValuesCriteriaQuery?

    > I have tested some value queries with index and they do use the index. Well, maybe I'm doing something wrong? Here is how I use CriteriaQuery: odb.getObjects[Test] (new CriteriaQuery (classOf[Test], Where.equal ("key", random.nextLong))) and here is how I use ValuesCriteriaQuery: odb.getValues (new ValuesCriteriaQuery (classOf[Test], Where.equal ("key"...

    2009-04-17 17:10:14 UTC in NeoDatis ODB

  • Followup: RE: Change of classloaders.

    > try calling this after changing the class loader: > > OdbConfiguration.getCoreProvider().getClassIntrospector().reset(); > OdbConfiguration.getCoreProvider().getClassPool().reset(); > > This will reset class cache and class fields cache. Yes, it works now. Thanks!

    2009-04-17 17:06:20 UTC in NeoDatis ODB

  • Followup: RE: Change of classloaders.

    > I am sorry, I don't know any thing about Scala > so I may ask some stupid questions.... This isn't about Scala per se, but about dynamic deployment of it inside an URLClassLoader. > When you say recompilation, do you mean recompilation during the runtime? > So that the current executing runtime automatically changes its classloader? Yes, we compile a fresh version of...

    2009-04-17 16:34:32 UTC in NeoDatis ODB

  • Followup: RE: Change of classloaders.

    > Did you need any specific 'workaround or trick' > to have NeoDatis working with Scala? I have trouble working with NeoDatis from under different classloaders. The first run is okay, but after any recompilation of the code (which goes into a different classloader) I get: http://gist.github.com/97026.

    2009-04-17 13:56:42 UTC in NeoDatis ODB

  • Followup: RE: Index not used in ValuesCriteriaQuery?

    > Did you need any specific 'workaround or trick' > to have NeoDatis working with Scala? Nope, works out of the box! : )

    2009-04-17 12:31:44 UTC in NeoDatis ODB

About Me

  • 2001-08-05 (8 years ago)
  • 289741
  • artemgr (My Site)
  • Artem Gr Kozarezov

Send me a message