That is an Apache Xalan error message. Try putting the xalan.jar, xercesImpl.jar xml-apis.jar, xsltc.jar and serializer.jar from http://xml.apache.org/xalan-j/downloads.html into the WEB-INF/lib directory. That should fix your problem.
I have also created a Google Code project to contain the project that was built during the process of documenting the configuration of JSF2 on GAE: http://code.google.com/p/jsf2gae/ Derek On Oct 19, 2009, at 2:49 PM, Vik wrote: > Hie Derek > > So here another error i m facing after modifying web.xml. any > suggestions? > > > Failed startup of context > com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext > @1e779a7{/,/base/data/home/apps/sakshumwebjsf/1.337116897991188426} > com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! > Translet class loaded, but unable to create translet instance. > at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java: > 354) > at com.sun.faces.config.ConfigureListener.contextInitialized > (ConfigureListener.java:219) > at org.mortbay.jetty.handler.ContextHandler.startContext > (ContextHandler.java:530) > at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) > at org.mortbay.jetty.webapp.WebAppContext.startContext > (WebAppContext.java:1218) > at org.mortbay.jetty.handler.ContextHandler.doStart > (ContextHandler.java:500) > at org.mortbay.jetty.webapp.WebAppContext.doStart > (WebAppContext.java:448) > at org.mortbay.component.AbstractLifeCycle.start > (AbstractLifeCycle.java:40) > at > com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler > (AppVersionHandlerMap.java:191) > at > com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler > (AppVersionHandlerMap.java:168) > at > com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest > (JettyServletEngineAdapter.java:127) > at com.google.apphosting.runtime.JavaRuntime.handleRequest > (JavaRuntime.java:239) > at com.google.apphosting.base.RuntimePb$EvaluationRuntime > $6.handleBlockingRequest(RuntimePb.java:5135) > at com.google.apphosting.base.RuntimePb$EvaluationRuntime > $6.handleBlockingRequest(RuntimePb.java:5133) > at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest > (BlockingApplicationHandler.java:24) > at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java: > 363) > at com.google.net.rpc.impl.Server$2.run(Server.java:814) > at com.google.tracing.LocalTraceSpanRunnable.run > (LocalTraceSpanRunnable.java:56) > at com.google.tracing.LocalTraceSpanBuilder.internalContinueSpan > (LocalTraceSpanBuilder.java:516) > at com.google.net.rpc.impl.Server.startRpc(Server.java:769) > at com.google.net.rpc.impl.Server.processRequest(Server.java:351) > at com.google.net.rpc.impl.ServerConnection.messageReceived > (ServerConnection.java:437) > at com.google.net.rpc.impl.RpcConnection.parseMessages > (RpcConnection.java:319) > at com.google.net.rpc.impl.RpcConnection.dataReceived > (RpcConnection.java:290) > at com.google.net.async.Connection.handleReadEvent(Connection.java: > 436) > at com.google.net.async.EventDispatcher.processNetworkEvents > (EventDispatcher.java:762) > at com.google.net.async.EventDispatcher.internalLoop > (EventDispatcher.java:207) > at com.google.net.async.EventDispatcher.loop(EventDispatcher.java: > 101) > at com.google.net.rpc.RpcService.runUntilServerShutdown > (RpcService.java:251) > at com.google.apphosting.runtime.JavaRuntime$RpcRunnable.run > (JavaRuntime.java:396) > at java.lang.Thread.run(Unknown Source) > Caused by: javax.xml.transform.TransformerConfigurationException: > Translet class loaded, but unable to create translet instance. > at > com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses > > (Unknown Source) > at > com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance > > (Unknown Source) > at > com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer > (Unknown Source) > at > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer > > (Unknown Source) > at com.sun.faces.config.ConfigManager$ParseTask.getTransformer > (ConfigManager.java:965) > at com.sun.faces.config.ConfigManager$ParseTask.getDocument > (ConfigManager.java:905) > at com.sun.faces.config.ConfigManager$ParseTask.call > (ConfigManager.java:831) > at com.sun.faces.config.ConfigManager$ParseTask.call > (ConfigManager.java:787) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at com.sun.faces.config.ConfigManager.getConfigDocuments > (ConfigManager.java:656) > at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java: > 337) > ... 30 more > C10-18 02:43AM 44.862 > > Uncaught exception from servlet > javax.servlet.UnavailableException: Initialization failed. > at > com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler > (AppVersionHandlerMap.java:200) > at > com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler > (AppVersionHandlerMap.java:168) > at > com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest > (JettyServletEngineAdapter.java:127) > at com.google.apphosting.runtime.JavaRuntime.handleRequest > (JavaRuntime.java:239) > at com.google.apphosting.base.RuntimePb$EvaluationRuntime > $6.handleBlockingRequest(RuntimePb.java:5135) > at com.google.apphosting.base.RuntimePb$EvaluationRuntime > $6.handleBlockingRequest(RuntimePb.java:5133) > at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest > (BlockingApplicationHandler.java:24) > at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java: > 363) > at com.google.net.rpc.impl.Server$2.run(Server.java:814) > at com.google.tracing.LocalTraceSpanRunnable.run > (LocalTraceSpanRunnable.java:56) > at com.google.tracing.LocalTraceSpanBuilder.internalContinueSpan > (LocalTraceSpanBuilder.java:516) > at com.google.net.rpc.impl.Server.startRpc(Server.java:769) > at com.google.net.rpc.impl.Server.processRequest(Server.java:351) > at com.google.net.rpc.impl.ServerConnection.messageReceived > (ServerConnection.java:437) > at com.google.net.rpc.impl.RpcConnection.parseMessages > (RpcConnection.java:319) > at com.google.net.rpc.impl.RpcConnection.dataReceived > (RpcConnection.java:290) > at com.google.net.async.Connection.handleReadEvent(Connection.java: > 436) > at com.google.net.async.EventDispatcher.processNetworkEvents > (EventDispatcher.java:762) > at com.google.net.async.EventDispatcher.internalLoop > (EventDispatcher.java:207) > at com.google.net.async.EventDispatcher.loop(EventDispatcher.java: > 101) > at com.google.net.rpc.RpcService.runUntilServerShutdown > (RpcService.java:251) > at com.google.apphosting.runtime.JavaRuntime$RpcRunnable.run > (JavaRuntime.java:396) > at java.lang.Thread.run(Unknown Source) > Thankx and Regards > > Vik > Founder > www.sakshum.com > www.sakshum.blogspot.com > > > On Sun, Oct 18, 2009 at 3:11 PM, Vik <[email protected]> wrote: > okies > > Great.. please update on the group for others benefit as well. I > find it pretty time consuming to build JSF apps w/o IDE support in > case of GAE apps. > > Thankx and Regards > > Vik > Founder > www.sakshum.com > www.sakshum.blogspot.com > > > On Sun, Oct 18, 2009 at 7:52 AM, Derek Berube > <[email protected]> wrote: > IMHO, the most important things that the Google AppEngine Plug-In > for Eclipse does is: > Provide the ability to "create" a new AppEngine project. > Launch the AppEngine runtime environment so you can test/debug your > code. > Package and upload your AppEngine application to Google's cloud > infrastructure. > > Most of the other things that Eclipse does (code completion/tips) > work just fine with the 2.0 API. About the only thing I find myself > struggling with is remembering all the options for the markup for > the various tags you use (whether it's the default JSF HTML > components, ADF Faces, ICEFaces, RichFaces, etc.). Of course, help > is never more than a browser window away. > > I know that the 1.81 release of the ICEFaces runtime environment is > supposed to work on GAE. I think RichFaces has problems because it > uses some of the AWT classes internally and those classes are not > available in the GAE runtime environment. > > As a general rule, when I'm learning a new API or technology, I tend > to prefer to do things the "hard way". For me, it is a better way > to get to know how things work because you're forced to. Once one > understands how and why things work the way they do and after they > have endured the "hard way", then they can appreciate what it is > that the tools do for you. Believe me, I appreciate Netbeans, > IntelliJ, and Eclipse for all the amazing things they do for me - > largely because I know how hard it is to do things without them. > > You have, however, inspired me to take a look at the ICEFaces plug- > in for Eclipse. Perhaps I'll install that and see what it does for > me with respect to JSF on GAE/J development! > > Derek > > On Oct 16, 2009, at 2:43 PM, Vik wrote: > >> hie >> >> I am from ADF world and used awesome JDeveloper to build ADF apps. >> It is great to use the ide stuff to do all the page design of ADF >> pages. >> >> So,kinda hard for me to imagine how to write a JSF page in eclipse >> without all that support for a GAE app. >> >> Please enlighten how you do that >> >> Thankx and Regards >> >> Vik >> Founder >> www.sakshum.com >> www.sakshum.blogspot.com >> >> >> On Fri, Oct 16, 2009 at 7:03 PM, Derek Berube >> <[email protected]> wrote: >> I have been using Eclipse 3.5 with Google's AppEngine Eclipse >> Plugin and have found it to be quite useful. I am more interested >> in the JSF2 framework, so I have spent the bulk of my time using >> that with AppEngine. >> >> While the JSF2 specification is in final draft status and there is >> a second release candidate for Sun's reference implementation, >> tooling support specifically targeted at supporting JSF2 in only >> now starting to emerge. The milestone 2 release of Netbeans 6.8 is >> now out and it includes JSf2 support. I know the next major >> releases of ICEFaces and RichFaces will be formally supporting >> JSF2, so it will be interesting to see how those frameworks play in >> AppEngine as well. >> >> I just updated the step-by-step guide for JSF2 and Google AppEngine >> configuration guide. I plan on doing some more generic JSF1.2/JSF2 >> Facelets templating stuff as well as writing up some stuff on the >> new JSF2 resource management framework (awesome)!. >> >> Derek >> >> >> On Oct 13, 2009, at 2:58 PM, Vik wrote: >> >>> Well i believe ide features provide much more than just visual >>> design.. like looking at property inspector, binding to action >>> listeners and managed beans etc.. >>> >>> So, it means there is no easy way to build JSF apps targeted for >>> GAE? >>> >>> Thankx and Regards >>> >>> Vik >>> Founder >>> www.sakshum.com >>> www.sakshum.blogspot.com >>> >>> >>> On Wed, Oct 14, 2009 at 12:22 AM, Derek Berube <[email protected] >>> > wrote: >>> I don't really rely much on the visual design tools for building >>> out the GUI. I tend to prefer to work with the raw XHTML and >>> stylesheets while frequently previewing the work in my browser. >>> >>> Derek >>> >>> >>> >>> On Oct 13, 2009, at 9:08 AM, Vik wrote: >>> >>>> Derek >>>> >>>> Do you get to see page designer and component pellete etc when u >>>> just add libraries in your project related to JSF? >>>> >>>> >>>> Thankx and Regards >>>> >>>> Vik >>>> Founder >>>> www.sakshum.com >>>> www.sakshum.blogspot.com >>>> >>>> >>>> On Mon, Oct 12, 2009 at 8:41 AM, Derek Berube <[email protected] >>>> > wrote: >>>> Vik, >>>> >>>> When doing JSF development with the Google AppEngine and the >>>> Eclipse plug-in, go ahead and select the Google Web Application >>>> project. >>>> >>>> You'll have to manually copy the JSF libraries into the WEB-INF/ >>>> lib directory of your web application. The WEB-INF/lib directory >>>> for my JSF2 projects looks like this: >>>> >>>> WEB-INF >>>> |-- lib >>>> |-- appengine-api-1.0-sdk-1.2.5.jar >>>> |-- appengine-api-labs-1.2.5.jar >>>> |-- datanucleus-appengine-1.0.3.jar >>>> |-- datanucleus-core-1.1.5.jar >>>> |-- datanucleus-jpa-1.1.5.jar >>>> |-- el-api-1.1.jar >>>> |-- el-impl-1.1.jar >>>> |-- geronimo-jpa_3.0_spec-1.1.1.jar >>>> |-- geronimo-jta_1.1_spec-1.1.1.jar >>>> |-- jdo2-api-2.3-eb.jar >>>> |-- jsf-api.jar >>>> |-- jsf-impl.jar >>>> |-- serializer.jar >>>> |-- xalan.jar >>>> >>>> I've been meaning to re-write that page on getting JSF 2.0 to >>>> work with the GAE using a step-by-step tutorial process that I >>>> did for the 1.2 framework. I'll see if I can get around to >>>> writing that up and posted over the next couple of days. >>>> >>>> For the most part, the latest release of the JSF2 framework has >>>> been working great for me! The only caveat is that I'm using the >>>> client-side state management because it seems that reconstituting >>>> state on the server side causes timeouts at the persistence layer. >>>> >>>> Derek >>>> >>>> >>>> >>>> On Oct 6, 2009, at 11:29 PM, Vik wrote: >>>> >>>>> hie >>>>> >>>>> i m interested to use jsf 2.0 but when i chose project with icon >>>>> g+ and try to use jsf eclipse reports that i should use a >>>>> dynamic web project. >>>>> Any suggestions? >>>>> >>>>> Thankx and Regards >>>>> >>>>> Vik >>>>> Founder >>>>> www.sakshum.com >>>>> www.sakshum.blogspot.com >>>>> >>>>> >>>>> On Tue, Oct 6, 2009 at 11:40 PM, Jason (Google) <[email protected] >>>>> > wrote: >>>>> See "Will it play in App Engine" to see the compatible (and >>>>> incompatible) frameworks and libraries and how to configure them >>>>> for App Engine: >>>>> >>>>> http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine >>>>> >>>>> You may also want to look into Spring MVC and Guice, which are >>>>> established Java frameworks, but ultimately, you should use >>>>> whichever pattern or framework works best for you and your >>>>> project. >>>>> >>>>> - Jason >>>>> >>>>> >>>>> On Mon, Oct 5, 2009 at 5:27 AM, Vik <[email protected]> wrote: >>>>> Hie >>>>> >>>>> Any idea what are those limitations? >>>>> >>>>> Thankx and Regards >>>>> >>>>> Vik >>>>> Founder >>>>> www.sakshum.com >>>>> www.sakshum.blogspot.com >>>>> >>>>> >>>>> On Mon, Oct 5, 2009 at 5:36 PM, Jaziel Leandro <[email protected] >>>>> > wrote: >>>>> Hi vik, >>>>> >>>>> If i can recommend a framework to you, look to JSF(1.2 and 2) >>>>> and Google Web Toolkit(GWT). The JSF framework have some >>>>> limitations to work on GAE and need some configurations, but i >>>>> prefer this. >>>>> >>>>> 2009/10/5 Vik <[email protected]> >>>>> >>>>> Hie Guys >>>>> >>>>> I have an app which is build using pretty old technology stack >>>>> i.e using MVC1 design pattern and conventional Jsps with >>>>> scriplets to use as views and >>>>> for the controller logic and beans for model layer. >>>>> >>>>> So, if some has to redo it today what is the recommended >>>>> framework to be used which is supported by GAE. >>>>> >>>>> >>>>> Thankx and Regards >>>>> >>>>> Vik >>>>> Founder >>>>> www.sakshum.com >>>>> www.sakshum.blogspot.com >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
