On 05/19/2011 04:50 PM, Thiago H. de Paula Figueiredo wrote: > What are you trying to do with these generated types and what exactly > is failing? Tapestry's classloader just changes classes that are in > controlled pages (pages, components, mixins, base). Anything else is > not touched (changed) by Tapestry. And anything that isn't a page > shouldn't be in a pages controller, sames for components and mixins. >
Hi Thiago, One of the big benefits of tapestry in how I use it is to be able to dynamically generate bean forms from dynamically generated types. Due to the fact that tapestry uses its own classloader hierarchy (esp. limited at javassist) it can't use types generated by other classloaders that were generated on the fly. To work around this, I had to literally use ClassFactory/ClassFab and implement the methods as required to support my bean generation, because I could not use CGLIB's BeanGenerator no matter how many tries I made at making it go with different classloaders, etc. Dan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
