[JBoss JIRA] Created: (JBIDE-4734) Layout for VPE tool bar formatting is broken under Linux.
by Yura Zhishko (JIRA)
Layout for VPE tool bar formatting is broken under Linux.
---------------------------------------------------------
Key: JBIDE-4734
URL: https://jira.jboss.org/jira/browse/JBIDE-4734
Project: JBoss Tools
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.M3
Environment: Linux 2.6.27.21-0.1-default x86_64
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
Attachments: screenshot-1.jpg
No VPE tool bar formatting is Expanded (see related issue). But there are some problems with buttons' and comboBoxes' layout.
1) Begin to decrease Visual Pane Size from right side until tool bar button I (Italic) doesn't become invisible. And Chevron button (>>) appears.
2) Press Chevron button (>>)
ASSERT: I (Italic), B (Bold) and two buttons with color formatting appeared.
ASSERT FAILED: I (Italic) button is invisible (see screenshot-1)
3) Continue to decrease Visual Pane Size and stop when achieve Text Font comboBox. Press Chevron.
ASSERT: Text Font comboBox should disappear from main tool bar and should be available from expanded menu
ASSERT FAILED: ComboBox doesn't disappear from main tool bar (screenshot-2).
4) Restore default Visual Pane Position (No Chevron buttons. All buttons and comboBoxes are visible on the tool bar formatting panel).
5) Press Text Font comboBox
RESULT: Layout is broken (screenshot-3)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-4544) Getting to theJBoss Project Examples in Eclipse isn't obvious
by James Livingston (JIRA)
Getting to theJBoss Project Examples in Eclipse isn't obvious
-------------------------------------------------------------
Key: JBIDE-4544
URL: https://jira.jboss.org/jira/browse/JBIDE-4544
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 3.0.1.GA
Environment: JBoss Developer Studio 2.0, and Eclipse with JBoss Tools 3.1.0M1
Reporter: James Livingston
When in the Seam perspective, the menu item File->New->Example... opens the standard Eclipse example wizard which does not contains any of the JBoss examples. To get to the JBoss ones, you need to go to File->New->Example... then JBoss Tools->Project Examples.
This isn't very obvious, and makes it difficult to find the JBoss examples if you don't know where they are. It would be good if there was a "JBoss Examples" item in File->New, as well as or replacing the Eclipse one, or having them both in the same wizard.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-4627) JSF 1.2 with Facelets kickstart project failed to start with JBoss AS 5.1GA
by Anton Klimkovich (JIRA)
JSF 1.2 with Facelets kickstart project failed to start with JBoss AS 5.1GA
---------------------------------------------------------------------------
Key: JBIDE-4627
URL: https://jira.jboss.org/jira/browse/JBIDE-4627
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.2.GA
Environment: Jdk 1.6.0
JBossTools-ALL-win32-3.0.2.GA-N200907151103-H77.zip
JBoss AS 5.1GA
Reporter: Anton Klimkovich
Assignee: Rob Stryker
EXECUTE: Create JSF 1.2 with Facelets project KickStart w/o libs with JBoss 5.1 runtime
EXECUTE: Run project on the server JBoss 5.1GA
FAILURE: java.lang.NullPointerException
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:510)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:553)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:444)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310)
at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:696)
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:667)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:59)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months