14 Replies Latest reply on Jul 26, 2007 9:16 AM by maxandersen

    3 problems running Exadel Studio Pro JSF app in Tomcat !

    mild7_adsl

      Dear exadel Support Staff: I've just started to get familiar with Exadel for
      developing JSF application. I got some problems as below with detail:Thanks a
      My environment settings are: Eclipse version:Version: 3.2.2
      Exadel Studio version :Pro 4.0.4Tomcat 5.5
      > ===========================
      Problems are:
      1. I tried to input Chinese characters driectly in the Visual Page Editor
      mode, but it simply does not work, no typing to show at all. Is any way to sovle this problem??

      >
      2. In visual page editor mode, does Exadel Stuido Pro support "component absolute postion layout" like "grid" in Sun Studio Creator?? If not, will this feature be available in future open source "JBoss Studio"??

      3 In Window->Preferences->Exadel->Library Sets, I have added"Myfaces 1.1.3" and aslo added its related 3 (.jar files), and then I tried to drag and drop a component called "navigationMenuItem" into the jsp page in the visual page editor mode, but when I tried to run the page I got the following error message: HTTP Status 500 - type Exception report
      message description The server encountered an internal error () that prevented it from fulfilling this request.


      exception
      > org.apache.jasper.JasperException: The absolute uri:
      > http://myfaces.apache.org/tomahawk cannot be resolved in either web.xml or the
      > jar files deployed with this
      > applicationorg.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
      >
      > root cause
      >
      > org.apache.jasper.JasperException: The absolute uri:
      > http://myfaces.apache.org/tomahawk cannot be resolved in either web.xml or the
      > jar files deployed with this
      > applicationorg.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)javax.servlet.http.HttpServlet.service(HttpServlet.java:802)com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:703)org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:670)org.apache.jsp.index_jsp._jspService(index_jsp.java:50)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)javax.servlet.http.HttpServlet.service(HttpServlet.java:802)org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
      >
      > root cause
      >
      > org.apache.jasper.JasperException: The absolute uri:
      > http://myfaces.apache.org/tomahawk cannot be resolved in either web.xml or the
      > jar files deployed with this
      > applicationorg.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:114)org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:316)org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:147)org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:423)org.apache.jasper.compiler.Parser.parseDirective(Parser.java:492)org.apache.jasper.compiler.Parser.parseElements(Parser.java:1552)org.apache.jasper.compiler.Parser.parse(Parser.java:126)org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:155)org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303)org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)javax.servlet.http.HttpServlet.service(HttpServlet.java:802)com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:703)org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:670)org.apache.jsp.index_jsp._jspService(index_jsp.java:50)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)javax.servlet.http.HttpServlet.service(HttpServlet.java:802)org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
      >

        • 1. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
          maxandersen

          with respect to #1 I couldn't find any chinese keyboard layout options so I tried to enable Japanese on my keyboard and by holding shift down I could see japanese signs in the visual editor.

          Is chinese and japanese method of entering chars completely different ?

          If not, could you elaborate on what issue you have ?

          • 2. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
            mild7_adsl

            Thanks for your reply on #1,

            To be more specific, for chinese input under Windows XP, normally we have to do "Ctrl+Space Bar" and then so Chinese input method show up(I believe Japanese should be the same way) in the screen. However, when I started to make the chinese ccharacters and press "enter", there's simply no corresponding chinese characters showed in the Visual Page Editor. So so that I truned out to type chinese characters in "Sources" mode directly for example within "<h2> and /h2>".

            Do I miss any step or is there any setting to be set in the Exadel Pro Studio??
            Thanks !

            • 3. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
              loge

              As for question 1. I'm using Exadel Studio Pro 4.0.4a with Eclipse 3.2.2 and the OS is Windows XP Pro Traditional Chinese version. I can easily type any Traditional Chinese characters and they will show up in VPE, but you have to set the file encoding to either Big5 or UTF-8 by adding

              <%@ page contentType="text/html; charset=Big5"%>

              or
              <%@ page contentType="text/html; charset=UTF-8"%>


              Because the default file encoding is determined from content and it's ISO-8859-1. You will see the error message telling you "Some characters cannot be mapped using ISO-8859-1 character encoding. Either change the encoding or remove the characters which are not supported by the ISO-8859-1 character encoding." while you save JSP files.

              • 4. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                mild7_adsl

                I did, I have this

                <%@ page language="java" contentType="text/html; charset=utf-8" pageEncoding="utf-8"%>


                But I want to type in Chinese characters directly in the "Visual Page Editor" mode, but the charactrers simlpy not showing up, no effect at all"

                what you described is the situation of when typing chinese charactrers in "source" mode. When you type Chinese characters in VPE, can you make it??
                thanks!

                • 5. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                  loge

                  Indeed the Chinese characters will not show up in the Visual pane while you type them in it. You have to type them in the Source pane. Why not using the message bundles instead of typing them directly in JSP pages?

                  • 6. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                    mild7_adsl

                    using the message bundles might be a solution but it's not a good idea for web pages consist of lots of Chinese contents, it's troublesome, isn't it??

                    It's werid that a Visual Page Editor can not accept multilanguage characters editing...

                    thanks anyway...

                    • 7. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                      maxandersen

                      I have talked with our russian team and they have no problems entering their characters and they also tried enabling simple chinese and it worked - also in the VPE...

                      • 8. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !

                        #1
                        I test Chinese Simplified input in VPE. All work fine.

                        For WinXP:
                        Plz, check ur regional and language settings. Exactly - check option "Enable support for Eastern Asian Languages", and check chinese simplified, and other chinese codepages.

                        Windows Vista work with asian languages by default.

                        U can find more info about regional settings at microsoft site.

                        • 9. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                          loge

                          dear max,
                          I've tried 3 commonly used built-in input method in Windows XP Pro Traditional Chinese edition. None of them made the Chinese characters show up in VPE(just Visual pane, Source pane is fine). The most commonly used input method is called phonetic input method. Users have to make some key conbinations in sequence(pronounce the character) and there will be a list of characters with the same pronunciation shows up for users to choose the right one. But the list never shows up in VPE.

                          • 10. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                            maxandersen

                            Ok - then I suggest that you open an issue in jira with a screenshot of the chinse input method working inside eclipse (not the VPE) and optimally with steps on how a non-chinese like I could reproduce this ;) Thanks.

                            • 11. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                              mild7_adsl

                              Dear max and Anis:

                              The regional and language setting in my windows XP shouldn't b a problem since my chinese typing in any other editors works perfectly.
                              To describe the problem more specifically as below:

                              Normally when multilanguage(other than English) input is needed in Windows, we have to press "Ctrl+Space bar" concurrently to bring up a little icon showed up in the lowe left corner of the screen. For Traditional Chinese, we call it "Phoetic Input Method", so when the little icon shows we started to make traditional chinese character one after one y using the phonetic method, when the intended character showed, your press "Enter" that intended character should be able to be typed IN(and showed) the editor. But for Exadel Studio Pro's visual Page Editor, it simply fails at this step. Failure here mean, you can not SEE that Character show in the VPE.

                              It's really weird....

                              • 12. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                                maxandersen

                                next step: report in jira with screenshots and how I can setup my windows box to reproduce this...

                                • 13. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                                  mild7_adsl

                                  OK, I have got in the JIRA issue creation page, but there seems no way to post .jpg files for showing screenshots..please tell me how.thanks!!

                                  • 14. Re: 3 problems running Exadel Studio Pro JSF app in Tomcat !
                                    maxandersen

                                    on the left side there should be an "Attach file" ...visible after you have created the issue