I haven't used the 1.3.2 release, as switching between the point releases always requires a bit of this unpleasant hacking / setup and the possibility of new issues. Here are the issues that I remember having to deal with (historically, not all of them might be an issue right now):
* Replace the security manager - this is only needed to run in the dev server. There are no issues w/ the app in production. I'm not sure if this is still needed. * Replacing the default agent * An issue w/ javassist - had to switch back to an older version ( 3.9, was it ? ). Most of the tips I picked up from Dmitry's blog. I can check later on and send out my changes that do work w/ 1.3.0 . Although it does give a warning when I build the app w/ 1.3.0 (because there's a newer version), the app runs fine when I deploy to GAE ( http://www.zadachite.com) Regards, Alex K On Fri, Apr 16, 2010 at 3:00 PM, Christian Edward Gruber < [email protected]> wrote: > Actually, we're going to use 5.2 (I'm working with Mike Taylor on this) > > We'll check the list archives, but a lot of what we're seeing seems related > on first blush, but isn't related, because we can't get to the problem > solved in those e-mails (we're not getting the main page component looked-up > properly, let alone sub-components). > > Specifically, findResources() in appengine's dev kit returns an empty > enumeration for resources in the page path, but returns a non-empty enum > when executed in a standard jdk. > > cheers, > Christian. > > > On Apr 16, 2010, at 2:45 PM, Alex Kotchnev wrote: > > Mike, >> what version of GAE are you using ? >> >> T 5.1.0.5 still has an issue that prevents it from running out of the >> box. Search for GAE on this list to find it. The issue is fixed in 5.2 and >> works like magic ( I'm using the 5.2 snapshot build w/ GAE 1.3.0) >> >> There are a number of T5 apps running in GAE, search this list for more >> details. There are a couple of things you need to do to make the dev >> server >> run OK (e.g. there's some monkeying around w/ the agent that ships w/ the >> dev server), search for Dmitry Gusev's posts on this list (and on his >> blog) >> for details. >> >> >> Regards, >> >> Alex K >> >> >> >> >> On Fri, Apr 16, 2010 at 1:55 PM, Michael Taylor <[email protected] >> >wrote: >> >> Hello Tapestry Users, >>> >>> I’ve been playing around with getting Tapestry 5.1.0.5 working on Google >>> App Engine and I’m having a issue with running it on the DevApp server. >>> >>> Essentially the DevApp server uses a custom class loader to simulate the >>> class loading restrictions imposed by GAE. >>> >>> It looks as though for some reason this custom class loader is preventing >>> tapestry from being able to locate page classes. Specifically >>> >>> >>> >>> org.apache.tapestry5.ioc.internal.services.ClassNameLocatorImpl::findClassesWithinPath(String >>> packagePath) >>> >>> does the following lookup >>> >>> Enumeration<URL> urls = contextClassLoader.getResources(packagePath); >>> >>> which when I run it in the GAE DevApp always seems to come back empty. >>> >>> I did some searching around on line and found this issue >>> >>> http://code.google.com/p/googleappengine/issues/detail?id=1480 >>> >>> which seems suspiciously similar but isn’t quite the behavior I’m seeing. >>> In that case Tapestry was unable to load a component (Loop) that was >>> found >>> in a page. I don’t even seem to get that far. The filter never finds >>> any >>> of my page objects and thus never gets as far as looking for the >>> components >>> that they might use. >>> >>> Has anyone else run into this problem? Any pointers would be much >>> appreciated. >>> >>> Regards, >>> >>> Mike Taylor >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
