November 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, 6 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, 6 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, 6 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, 6 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, 6 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, 6 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-9913) NPE on start and publish of servers

by Max Rydahl Andersen (Created) (JIRA)

NPE on start and publish of servers ----------------------------------- Key: JBIDE-9913 URL: https://issues.jboss.org/browse/JBIDE-9913 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.M4 Currently breaking the builds and any usage of any server: !ENTRY org.eclipse.core.jobs 4 2 2011-10-13 23:25:40.580 !MESSAGE An internal error occurred during: "Starting org.jboss.ide.eclipse.as.42". !STACK 0 java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.server.internal.BehaviourModel.getLaunchDelegate(BehaviourModel.java:61) at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.getDelegate(DelegatingStartLaunchConfiguration.java:47) at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:61) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3402) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3340) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

9
10
0 / 0

[JBoss JIRA] (JBIDE-10045) Incremental Publish forcing a push request for openshift when it should not.

by Rob Stryker (Created) (JIRA)

Incremental Publish forcing a push request for openshift when it should not. ----------------------------------------------------------------------------- Key: JBIDE-10045 URL: https://issues.jboss.org/browse/JBIDE-10045 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M4 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.M4, 3.3.0.Beta1 Every attempt to run as -> run on server creates a publish request, though if no changes have been made it's an incremental request. In the case where there are no changes in the workspace, the request to push is still being initiated even for these incremental publishes. Bad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
7
0 / 0

[JBoss JIRA] (JBIDE-10109) can't compile openshift in trunk

by Nick Boldt (Created) (JIRA)

can't compile openshift in trunk -------------------------------- Key: JBIDE-10109 URL: https://issues.jboss.org/browse/JBIDE-10109 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS/Servers, openshift Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Rob Stryker This failure has been happening for the last few builds: https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/30... [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.openshift.express.ui 2.3.0.qualifier [ERROR] Missing requirement: org.jboss.tools.openshift.express.ui 2.3.0.qualifier requires 'bundle org.jboss.ide.eclipse.as.egit.core 2.3.0' but it could not be found [ERROR] [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.jdt.core 3.7.0.v_OTDT_r200_201105240906 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.jboss.tools.openshift.express.ui 2.3.0.qualifier to bundle org.jboss.ide.eclipse.as.egit.core 2.3.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] Perhaps your feature/plugin don't properly declare this dependency? Or the org.jboss.ide.eclipse.as.egit.core bundle's not on the composite site? Or it's not being built via as/plugins/pom.xml ? Please attempt to build your stuff locally using this pom as input: {code}cd ~/trunk/build; mvn clean install -f pom-core.xml{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-9797) Errors occurred during the build

by Ron Ratovsky (JIRA)

Errors occurred during the build -------------------------------- Key: JBIDE-9797 URL: https://issues.jboss.org/browse/JBIDE-9797 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core, Webservices Affects Versions: 3.3.0.M3 Environment: Windows 7 64 bit Eclipse Indigo 3.7 SR1 64 bit Java 1.6.0_26 64 bit Reporter: Ron Ratovsky Assignee: Alexey Kazakov When restarting eclipse, it rebuilds the whole workspace and I encounter the following error: Errors occurred during the build. Errors running builder 'JAX-RS Builder' on project 'some-project-name'. org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType Looking at the logs, I found the following: !ENTRY org.eclipse.core.resources 4 75 2011-09-29 18:28:26.111 !MESSAGE Errors occurred during the build. !SUBENTRY 1 org.jboss.tools.ws.jaxrs.core 4 75 2011-09-29 18:28:26.111 !MESSAGE Errors running builder 'JAX-RS Builder' on project 'some-project-name'. !STACK 0 java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType at org.jboss.tools.ws.jaxrs.core.metamodel.ResourceMethod.merge(ResourceMethod.java:103) at org.jboss.tools.ws.jaxrs.core.metamodel.ResourceMethod.<init>(ResourceMethod.java:58) at org.jboss.tools.ws.jaxrs.core.metamodel.Resource.mergeMethods(Resource.java:210) at org.jboss.tools.ws.jaxrs.core.metamodel.Resource.merge(Resource.java:160) at org.jboss.tools.ws.jaxrs.core.metamodel.Resource$ResourceBuilder.build(Resource.java:101) at org.jboss.tools.ws.jaxrs.core.metamodel.Resources.addFrom(Resources.java:53) at org.jboss.tools.ws.jaxrs.core.metamodel.Metamodel.addElements(Metamodel.java:221) at org.jboss.tools.ws.jaxrs.core.internal.builder.JaxrsMetamodelBuilder.fullBuild(JaxrsMetamodelBuilder.java:184) at org.jboss.tools.ws.jaxrs.core.internal.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:92) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Not sure what other information may be important here, so please let me know. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

9
14
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 November 2011