1. For bytecode generation: I can afford to use compile time weaver of byte
code enhancer.
2. For classloader: Can we load resin's classloader at startup via servlet
filter or listener and then use it for all class loading?
-Wesley
----- Original Message -----
From: Scott Ferguson
To: General Discussion for the Resin application server
Sent: Thursday, April 16, 2009 2:47 AM
Subject: Re: [Resin-interest] Any chance to support an out of box
JSR299implementation for GAE?
On Apr 15, 2009, at 10:20 AM, wesley wrote:
Hi there,
I wonder if Resin could distribute a library to support an out of box
JSR299 implementation for Google App Engine.
We know Resin can't run on GAE now, but I think Resin's implementation
of CanDI may be run on GAE.
Is there any plan for this?
Hmm. That's an interesting thought. Resin's CanDI is in resin-kernel.jar
and doesn't depend on Resin itself, with the important exception of the
Request and Session scopes.
Some of the Interception features wouldn't be available because of the
current Google limitations on file writing (and probably missing javac),
because Resin generates Java code instead of writing bytecode directly.
There would be a few changes needed because Resin CanDI does expect Resin
classloaders, but I think that would be straightforward to change.
-- Scott
regards
-Wesley
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
