ConstructorAccess with an expensive parent classloader

[seth/nqzero]

i'm porting a kryo v1 application to the current kryo/reflectasm. it uses a network classloader which is expensive

ContructorAccess attempts to load an accessor class (eg, Dummy --> DummyConstructorAccess) which triggers a network roundtrip (and if Dummy has been used on the other side of the network with kryo, the accessor might exist and be sent over the wire, which is probably not what we want). the other access classes look similar

what's the best way to avoid this ?

the best that i've come up with so far is to match against ".*{Field,Method,Contructor,PublicConstructor}Access" and just skip them in my classloader. but some user could write code using those fairly common words and things would mysteriously fail

is there a better way ?

[seth/nqzero]

here's a pull request that addresses the problem at the root

https://github.com/EsotericSoftware/reflectasm/pull/51

--
You received this message because you are subscribed to the "reflectasm-users" group.
http://groups.google.com/group/reflectasm-users
---
You received this message because you are subscribed to the Google Groups "reflectasm-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reflectasm-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.