Hi there, Recently I've been working on supporting runtime generated types with tapestry and have been successful after many attempts. However, the method by which I am able to support these runtime types is prohibitive of working with Drools a business rule system.
Particularly, the classloader hierarchy inside tapestry is very prohibitive of supporting new runtime types. In fact, I was generating classes at first with BeanGenerator from CGLIB and tried just about everything with regards to changing the classloader and the construction of the objects but it was to no avail. The solution that did work was using ClassFactory injected into one of my pages and then implementing all the respective methods on top of that to generate the types, and then those types would be part of classloader used by tapestry. While I am able to set the classloader for drools which itself can generate its own types in its rule system, those types are not exportable to tapestry. Additionally, they do not contain any annotations which makes their value even less to tapestry. I'm looking for a solution that would allow me to add annotations to dynamically generated types, as well as being exportable to drools in a way that allows the user of the rules system to be able to interact with those generated types. Additionally, if there was a way I could simply add more classloaders to tapestry other than just classpaths based on the underlying implementation, this may be greatly simplified. Any thoughts or suggestions are welcome. Thanks, Dan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
