June 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-1246) service beans code completion is broken

by Max Andersen (JIRA)

service beans code completion is broken --------------------------------------- Key: JBIDE-1246 URL: http://jira.jboss.com/jira/browse/JBIDE-1246 Project: JBoss Tools Issue Type: Bug Components: JBossAS Reporter: Max Andersen Assigned To: Rob Stryker Fix For: 2.1 While fixing the identification of service xml I found that the code completion is broken in service.xml It looks like the code is searching for code completions manually and assumes way too much about what the searchengine can/should find. e.g. PackageTypeSearcher.getPackage() assumes only one packagefragment per name will be found, but that is not the case if you have multiple projects with the same jar or simply uses the same package name in diffeerent projects. One way to solve it is to use the built in codecompetlion in JDT - an example of that is to be found in CompletionHelper.java in the hibernate plugins. -- 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, 5 months

4
3
0 / 0

[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, 5 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, 5 months

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

6
12
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, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1273) When hot code replace fails, offer "restart deployment "as an alternative

by Gavin King (JIRA)

When hot code replace fails, offer "restart deployment "as an alternative ------------------------------------------------------------------------- Key: JBIDE-1273 URL: http://jira.jboss.com/jira/browse/JBIDE-1273 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King The dialog box t hat eclipse pops up when hot code replace fails is very irritating, but it would be less irritating if it offered "restart deployment" as an alternative. Actually it should be smart enough to NOT pop this dialog at all for classes in src/action. So I think the Seam tools need to hijack this whole feature of eclipse. -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-3113) Consolidation/clean up of preference pages

by John Graham (JIRA)

Consolidation/clean up of preference pages ------------------------------------------ Key: JBIDE-3113 URL: https://jira.jboss.org/jira/browse/JBIDE-3113 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, drools, jbpm Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk Reporter: John Graham Priority: Minor JBT currently has three preference page categories: 1. Drools 2. JBoss jBPM 3. JBoss Tools The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss: - JBoss -- Drools -- jBPM Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) ) -- 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, 5 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5099) OpenOn for custom Jsf 2.0 components

by Maxim Areshkau (JIRA)

OpenOn for custom Jsf 2.0 components ------------------------------------ Key: JBIDE-5099 URL: https://jira.jboss.org/jira/browse/JBIDE-5099 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing, Visual Page Editor core Affects Versions: 3.1.0.M4 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.1.0.CR1 OpenOn for custom Jsf 2.0 components from source part. -- 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
17
0 / 0

[JBoss JIRA] Created: (JBIDE-1104) .sar file cannot be included in .ear file

by Juergen Zimmermann (JIRA)

.sar file cannot be included in .ear file ----------------------------------------- Key: JBIDE-1104 URL: http://jira.jboss.com/jira/browse/JBIDE-1104 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.Beta4 Environment: JBoss Tools nightly build 20071017 Reporter: Juergen Zimmermann I need a .ear file which contains a .sar file (service archive for JBoss). Such a .sar file is declared in META-INF/jboss-app.xml of the EAR project "hska" as follows: <jboss-app> <security-domain>java:/jaas/hska</security-domain> <module> <service>hska.sar</service> </module> </jboss-app> I have a "General Project" named hskaSAR which has a META-INF subdirectory for the xml files of the .sar file. Creating hskaSAR/hska.sar via the "Project Archives" view of JBoss Tools works fine. However, there is no possibility to include the .sar file within the (exploded) .ear. I tried to edit and extend the file .settings/org.eclipse.wst.common.component within the EAR project as follows: <dependent-module deploy-path="/" handle="module:/classpath/lib/hskaSAR/hska.sar"> <dependency-type>uses</dependency-type> </dependent-module> However, this workaround doesn't work. -- 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

6
23
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 June 2010