April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6488) dashboard for jboss.org projects

by Dan Allen (JIRA)

dashboard for jboss.org projects -------------------------------- Key: JBIDE-6488 URL: https://jira.jboss.org/browse/JBIDE-6488 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.1 Reporter: Dan Allen Create a dashboard view for JBoss.org projects. This feature request is inspired by the Kenai.com dashboard view in NetBeans (screenshot attached). The general idea is to provide a view within the IDE of the JBoss.org projects (perhaps even other conforming projects). The view provides information about the project such as: = title = description = project members = source control = recent issues = blog feed (titles w/ summary and link) = ... You would then be able to interact with the form to pull the source into your IDE workspace and build it. That way, we can get new developers started as simple as possible and consistently across all projects. The key is that it's simple to get started, and we start the developer in JBoss Tools, then get them into the code. Most of the info could be extracted from the poms in the Nexus repo, and know URL patterns on jboss.org. http://netbeans.org/kb/docs/ide/kenai-create-project.html What would be stunning is if we could also tie this into collaborative editing in the IDE. -- 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, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8517) OOTB SOA-P 5 server config displays error "One or more ports have an invalid value"

by Len DiMaggio (JIRA)

OOTB SOA-P 5 server config displays error "One or more ports have an invalid value" ------------------------------------------------------------------------------------ Key: JBIDE-8517 URL: https://issues.jboss.org/browse/JBIDE-8517 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel, JBossAS Affects Versions: 3.2.0.CR1 Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930 SOA-P 5.1 GA JBoss Tools http://download.jboss.org/jbosstools/updates/nightly/trunk/ (BPEL editor) 1.0.0.v20110217-0324-H60-Alpha1 Reporter: Len DiMaggio Priority: Minor See the attached screenshot - setting this as minor priority as there does not seem to be any functional impact -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
13
0 / 0

[JBoss JIRA] Created: (JBDS-1449) Merge runtime related features from JBDS installer to runtime plug-in and reuse runtime plug-in binaries in installer

by Denis Golovin (JIRA)

Merge runtime related features from JBDS installer to runtime plug-in and reuse runtime plug-in binaries in installer --------------------------------------------------------------------------------------------------------------------- Key: JBDS-1449 URL: https://jira.jboss.org/browse/JBDS-1449 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer, runtime Affects Versions: 4.0.0.Beta2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.0.0.CR1 Now server search and validation for "server configuration dialog" in installer are duplicated in runtime plugin. That makes difficult to keep them in sync and that's why sometimes installer complains that version of selected server is not supported, but runtime plugin is actually can handle this version in a right way see JBDS-1380 as example. The idea is merge all what installer has in runtime and/or jbossas adapter plugin and use these plugins in installer to keep all code in one place. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
10
0 / 0

[JBoss JIRA] Created: (JBDS-1266) Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process

by Len DiMaggio (JIRA)

Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1266 URL: https://jira.jboss.org/browse/JBDS-1266 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: runtime, SOA Platform Affects Versions: 3.0.0.GA Environment: Version: 3.0.0.GA Build id: v201003100055R Build date: 201003100222 Reporter: Len DiMaggio Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png The sequence of events is: 1) Create a jBPM project 2) Successfully test the connection to a SOA-P server 3) Select credentials checkbox - enter invalid credentials 4) Deploy the jBPM project process - the deployment will use the credentials previously used during the test -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4093) Project archive isn't published to the deploy folder after changing temporary deploy directory.

by Anton Klimkovich (JIRA)

Project archive isn't published to the deploy folder after changing temporary deploy directory. ----------------------------------------------------------------------------------------------- Key: JBIDE-4093 URL: https://jira.jboss.org/jira/browse/JBIDE-4093 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create seam web project EXECUTE: Open Server Overview EXECUTE: Set checkbox to Use workspace metadata EXECUTE: Add project to the server ASSERT: Project is deployed to \ws3\.metadata\.plugins\org.jboss.ide.eclipse.as.core\jboss-soa-p.4.3.0\deploy\ EXECUTE: Open Server Overview EXECUTE: Set checkbox to Use a custom deploy folder or Use the JBoss deploy folder. Save changes. EXECUTE: Press Publish to the server button FAILURE: Only seam-ds.xml is published. Seam.war isn't published to the deploy folder. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3663) Show a warning when the user tries to open the launch configuration but the server editor is dirty

by Adrian Mitev (JIRA)

Show a warning when the user tries to open the launch configuration but the server editor is dirty -------------------------------------------------------------------------------------------------- Key: JBIDE-3663 URL: https://jira.jboss.org/jira/browse/JBIDE-3663 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.0.0.CR2 Environment: JBT N200901190612, java 1.5, windows XP Reporter: Adrian Mitev Something like "Server is not saved yet - the console configuration might be out of date. Do you want to save the serrver before opening the launch configuration ?" when users click the "open launch config". -- 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

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4185) Simpler load time weaving configuration

by Galder Zamarreño (JIRA)

Simpler load time weaving configuration --------------------------------------- Key: JBIDE-4185 URL: https://jira.jboss.org/jira/browse/JBIDE-4185 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Galder Zamarreño Assignee: Rob Stryker Right now, if you wanna use load time weaving, you need to modify jboss.aop:service=AspectManager MBean to have EnableLoadtimeWeaving to true and you need to pass the pluggable instrumentor in the VM parameters, i.e. -javaagent:/home/galder/access/eap-rel/4.3.0.ga.cp04/server/279798/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar >From JBDS, you need to put the full path to this, whereas if running standalone, you can just do: JAVA_OPTS="$JAVA_OPTS -javaagent:server/279798/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar" Now, it'd be really helpful if the JBoss AS/EAP server had an option that added did this (at least the javaagent part) if load time weaving was enabled (a new option server configuration window (i.e. double click server name)) -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2240) Speed up creation of runtime/servers, specially when creating clusters

by Galder Zamarreno (JIRA)

Speed up creation of runtime/servers, specially when creating clusters ---------------------------------------------------------------------- Key: JBIDE-2240 URL: http://jira.jboss.com/jira/browse/JBIDE-2240 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Galder Zamarreno We need to look at a way to streamline the creation of runtime/servers as I'm finding it really tedious, specially when it comes to clusters. First, I think It'd be nice to create a runtime and a server in a single step. This would fit very well my model where I take an EAP version, create a server configuration (could Tools do this for me as well? instead of me having to "cp -r server/default server/12345"), create a runtime for it and a server and the server's name to be exactly the same as the one from the runtime (no need to add the " Server" name clutter). Secondly, once I've created a server configuration + runtime + server, an ability to copy paste that one, having only to change the server configuration name (server/12345_1, server/12345_2....configurations) , runtime/server name and bind address (for those that don't do multiple IP addresses, enable binding manager and allow selecting the port collection, ports-01...etc). All this needs further baking and you have to take into account my specific use where I'm creating server configurations on a daily basis. -- 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

5
4
0 / 0

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

4
4
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 April 2011