February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5235) Error during struts kick start project execution on bundled EAP 5.0

by Jiri Peterka (JIRA)

Error during struts kick start project execution on bundled EAP 5.0 ------------------------------------------------------------------- Key: JBIDE-5235 URL: https://jira.jboss.org/jira/browse/JBIDE-5235 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS, struts/shale Affects Versions: 3.1.0.CR1 Environment: jbdevstudio-eap-linux-gtk-x86_64-3.0.0.v200911180352M-H96-M4 sun jdk-6u17-linux-x64 Reporter: Jiri Peterka Steps to reproduce: 1. Use bundled EAP 5.0 as runtime 2. Create Struts kick start project 3. Run it on the server 4. Open page in eclipse web browser Error message: TTP 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: An exception occurred processing JSP page /pages/inputname.jsp at line 8 5: <title>KickStart: Input name</title> 6: </head> 7: <body> 8: <html:form action="/greeting.do"> 9: <table border="0" cellspacing="0" cellpadding="0"> 10: <tr> 11: <td><b>Input name:</b></td> 0:05:19,647 ERROR [RequestUtils] Error creating form bean of class demo.GetNameForm java.lang.ClassNotFoundException: demo.GetNameForm at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:303) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at org.apache.struts.util.RequestUtils.applicationClass(RequestUtils.java:207) at org.apache.struts.util.RequestUtils.applicationInstance(RequestUtils.java:231) at org.apache.struts.util.RequestUtils.createActionForm(RequestUtils.java:837) at org.apache.struts.taglib.html.FormTag.initFormBean(FormTag.java:552) at org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:520) at org.apache.jsp.pages.inputname_jsp._jspx_meth_html_005fform_005f0(inputname_jsp.java:133) at org.apache.jsp.pages.inputname_jsp._jspx_meth_html_005fhtml_005f0(inputname_jsp.java:106) at org.apache.jsp.pages.inputname_jsp._jspService(inputname_jsp.java:73) 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) Workaround: After server restart it works. Note: Unable to simulate this without JBDS/JBT so it seems like JBDS/JBT issue -- 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

14 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1253) Editor for JBoss -ds.xml files

by Gavin King (JIRA)

Editor for JBoss -ds.xml files ------------------------------ Key: JBIDE-1253 URL: http://jira.jboss.com/jira/browse/JBIDE-1253 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King Configuring datasources is hard for many users. Let's help them out with a nice editor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

7
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7822) Deployment from workspace metadata does not work when workspace path contains space character

by Dominik Pospisil (JIRA)

Deployment from workspace metadata does not work when workspace path contains space character --------------------------------------------------------------------------------------------- Key: JBIDE-7822 URL: https://jira.jboss.org/browse/JBIDE-7822 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Beta2 Environment: WinXP, Linux x86 Reporter: Dominik Pospisil Assignee: Rob Stryker Priority: Critical Deployment from workspace metadata does not work when workspace path contains space character. Steps to reproduce: 1) create empty workspace on a path containing space character 2) create web project 3) try to deploy on a server with workspace metadata deployment No error logged, but nothing happens. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

8
25
0 / 0

[JBoss JIRA] Created: (JBIDE-6063) Add JBoss Enterprise Platforms to Server Adapters.

by Joao Paulo Viragine (JIRA)

Add JBoss Enterprise Platforms to Server Adapters. -------------------------------------------------- Key: JBIDE-6063 URL: https://jira.jboss.org/jira/browse/JBIDE-6063 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.0.GA Reporter: Joao Paulo Viragine Attachments: New Server _001.png Add JBoss Enterprise Platforms to Server Adapters (JBoss Enterprise Middleware) E.g.: JBoss Enterprise Portal Platform JBoss Enterprise SOA Platform JBoss Enterpise BRMS Platform -- 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

14 years, 4 months

7
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6065) Default Invm Scope to GLOBAL - Usability

by Burr Sutter (JIRA)

Default Invm Scope to GLOBAL - Usability ---------------------------------------- Key: JBIDE-6065 URL: https://jira.jboss.org/jira/browse/JBIDE-6065 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.0.0.GA Reporter: Burr Sutter Attachments: INVM_Scope.png I have found that I normally forget to set the INVM Scope to GLOBAL when creating a new service. Forgetting to set this attribute results in a runtime error message upon deployment. It is very common to forget the attribute because of is placement - at the service level instead of the listener level. User will tend to follow these steps: - Add a Service - Add a HTTP Listener with a urlpattern - Add a SOAPProxy Action and forget to go back to the Service screen and flip INVM scope to Global see screen shot -- 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

14 years, 4 months

6
12
0 / 0

[JBoss JIRA] Created: (JBDS-1574) What's up with the "ISO downloads" of JBDS PE 2.x and 3.x?

by Nick Boldt (JIRA)

What's up with the "ISO downloads" of JBDS PE 2.x and 3.x? ---------------------------------------------------------- Key: JBDS-1574 URL: https://issues.jboss.org/browse/JBDS-1574 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build, servers Reporter: Nick Boldt Assignee: mark yarborough Found some interestingly described JBDS 3.0 and earlier downloads in the CSP. Steps to repro: 1. Log in here: https://www.redhat.com/wapps/sso/login.html 2. Click "Red Hat Network Preferences" -> https://rhn.redhat.com/network/my_account/my_prefs.pxt 3. Click the "Download software" icon/button on the left-hand side of the site: !software_downloads_rhn.png! 4. Observe list of downloads - CTRL-F to search for Developer Studio https://rhn.redhat.com/rhn/software/downloads/SupportedISOs.do !Screenshot-1.png! 5. Click on one of the entries, such as "JBoss Developer Studio - Portfolio Edition for Linux ", and get here: https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=9103 "ISO Image Downloads NOTE: By downloading this software, you agree to the terms and conditions of the applicable License Agreement (available at http://www.redhat.com/licenses/) Not sure how to download and use these images? Check out our ISO Download Help. Latest Release Below please find the complete set of ISO images for the latest release of JBoss Developer Studio - Portfolio Edition for Linux. Depending on the variant of JBoss Developer Studio - Portfolio Edition for Linux you'd like to install, you may only need a subset of these discs. (more information) " !Screenshot-2.png! 6. Have a WTF moment as you consider how a jarred installer can be classified as an ISO image. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8002) (incorrect) faces-config validation error upon project clean

by erik van altena (JIRA)

(incorrect) faces-config validation error upon project clean ------------------------------------------------------------ Key: JBIDE-8002 URL: https://issues.jboss.org/browse/JBIDE-8002 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.Beta2 Environment: Eclipse Helios Reporter: erik van altena Assignee: Alexey Kazakov Priority: Minor In my project (jsf 1.2 capabilities) I have multiple faces-config files, configured as follows in the web.xml file: <context-param> <param-name>javax.faces.CONFIG_FILES</param-name> <param-value>/WEB-INF/faces-config.xml,/WEB-INF/navigation.xml,/WEB-INF/form-config.xml,/WEB-INF/storage-config.xml,/WEB-INF/search-config.xml</param-value> </context-param> So far so good. However, each time I now clean the project, I get a validation error in the problems list (and the project is marked as having an error) on the fact that one of these files does not exist - it seems random which one it complains about but the error does happen consistently. This validation error is not shown in the web.xml file itself when I open it, and when I alter and save the web.xml file, the error disappears from the problems list and the project no longer has errors. I did not ever see this otherwise minor issue in beta 1. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6546) Can not enter multibyte character in JSF HTML Palette attribute dialog value field

by Hitoshi Ozawa (JIRA)

Can not enter multibyte character in JSF HTML Palette attribute dialog value field ---------------------------------------------------------------------------------- Key: JBIDE-6546 URL: https://jira.jboss.org/browse/JBIDE-6546 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.1 Environment: Windows Reporter: Hitoshi Ozawa Assignee: Alexey Kazakov When I drag a JSF HTML Palette, an Attribute dialog opens. In this dialog, I'm not able to enter multibyte characters (i.e. Japanese) value field. The current workaround is to leave it blank and create an HTML tag, and enter a Japanese text in the HTML tag but having a attribute dialog box open each time which I'm not able to use is really bothersome. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7455) New JSF Project wizard creates web.xml 3.0 with incorrect namespaces.

by Alexey Kazakov (JIRA)

New JSF Project wizard creates web.xml 3.0 with incorrect namespaces. --------------------------------------------------------------------- Key: JBIDE-7455 URL: https://jira.jboss.org/browse/JBIDE-7455 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.Beta2 1. Open New JSF Project wizard. 2. Select JSF 2 & Servlet Version 3.0. Press Finish. 3. Open the created web.xml. It has <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" ...> But it should have <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"...> shouldn't it? And btw, could we use Servetl 3.0 as default value for JSF 2.0 projects in our wizard? Not it's 2.5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8225) Richfaces component installed on Eclipse SDK is not fully functional

by Denis Golovin (JIRA)

Richfaces component installed on Eclipse SDK is not fully functional -------------------------------------------------------------------- Key: JBIDE-8225 URL: https://issues.jboss.org/browse/JBIDE-8225 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Priority: Critical -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2011